Vixen 3.0 New E1.31 Output Module

[boarder3]

I got it to work i need to ignore that 451 and start vixen on 300 worked like a charm thanks.

[j1sys]

it may be 'working' but i think you have overlapped universes. 300 pixels will be 900 slots. so 1-450 is universe 1, 451-900 is universe 2. that is start=1, slots=450 and start=451, slots=450.

[lortiz]

Hi Ed,

Thanks for this output module.

I'd like to suggest that you keep the most recent version of the module in the very first post.

Keep up the good and much appreciated work.

Leo

[budude]

+1 on updating first post.

I gave this a try tonight with a fairly small setup - RPM Bridge (DMX) to a Ren64 using the channel LEDs as indicators. Very smooth transitions - looks just great - looking forward to using Vixen 3 more and more!

[aussiephil]

Well I finally got some hardware setup to do some actual testing.

Many Thanks to Ed (j1sys) for this plugin

Setup
Vixen 3 with J1SYS E131 Plugin
160 RGB Channels define
Plugin defined with 480 output slots
One 160 pixel 2801 Flexible strip
1:29 Sequence with audio

Here's the video to prove it all works.....

http://vimeo.com/36180172

Now to do the behind the scenes How-to on the actual setup and sequence

Cheers
Phil

[Shockwave]

It is working on my Vixen 3 beta and I am able to see the traffic on the dev unit.

I'm also noticing that when you press Stop, the music and graphics halt, but the data coming out the ethernet continues on until the end of the data in the sequence. I'm not sure if that's the DLL or Vixen 3 error.

I also wonder where to report bugs to the community. I'm eager to help get this working right since the power it'll give us is phenomenal. Do we have a bug reporting section of the forum for this latest version of Vixen and all associated plugins?

[j1sys]

The plugin is getting data pushed to it. it is called every 'x' milliseconds by the sequencer. we don't create any data, just transmit it.

Currently, it appears, that the sequencer calls the output all the time, even when we think of it as idle. I expect some of the issues you are seeing could be related to that. Are you saying the the sequenced data are continuing to appear? or just some empty transmissions.

This plugin was a first attempt to follow our understandings of the output 'rules' from Vixen 3.0 based on information disclosed so far. I expect some changes/fixes/updates to the rules in the next release. But have no inside information to base that on. I am on the outside gleaning information as well are the users.

-Ed

[Shockwave]

Yes, actual sequence data is being thrown to my MCUs. When the 22 seconds test chase finishes, the data stops arriving at the MCU. Your data matches mine -- Vixen3 continues to sequence even when you press stop. I suspect the same problem will exist for others with other output plugins in the future too.

BTW: Thank you for these sACN dlls. I'm having a blast with them and they allow me to integrate Vixen and music into my existing stand-alone homebrew system with ease. Thanks a lot.

[Materdaddy]

I also wonder where to report bugs to the community. I'm eager to help get this working right since the power it'll give us is phenomenal. Do we have a bug reporting section of the forum for this latest version of Vixen and all associated plugins?

Vixen bugs go to http://bugs.vixenlights.com/
I believe they do NOT want plugin bugs there, only bugs for Vixen 3.0 itself.

[Shockwave]

POST DELETED BY POSTER

reason: symptoms caused by test configuration