You are exactly right about the plug-in. At the time I was working on the hardware there were still very few people writing plug-ins and they were working hard on projects that had a lot more general interest.
This may be better suited for the ledtricks forum, but what strategy are you thinking of? I was leaning towards defining a font in firmware and sending text and scrolling direction and rate from Vixen. Add 60 custom frames for animation and you would have a lot of capability without much load on the CPU...
Pete
right now i was thinking KISS principle. Keep it simple stu..d.
simply have it recieve 16 x 48 bits of binary info for on off info.
maybe in a packet format like row#,colum Data... , Stop.
adding fonts and different features could be added later quite easily i think once the interface is stable . but i hadnt really thought to much about that.
peter
Simple is good. I don't have a lot of insight into where the performance load is with the current design, and I'm looking forward to knowing if it's in generating the frames or just clocking them out to the board...
Please let us know what you find out!
Pete
well i have it fired up on a bread board. doing a simple test seems to work ok.
ill give it a harder test once i have some more time.
one thing i found out that i didnt know is that vixen only sends packets when the lights update.
ie i have it set to a 25ms sequence but if i only change the lights every 500ms it only transmits every 500ms. not what i expected.
time to start playing.
Yeah I remember the discussions regarding the DMX packets and there was mention there that Vixen only sends out data when items change, unlike DMX which constantly repeats the data over and over. You can easily detect when a DMX fault occurs as there is suddenly no DMX data (and I believe that the DMX version of the Renard firmware then fades to 0 over time), but if Vixen fails you never know about it as the lights just freeze where they are.
