So you hove some sort of a mapping table between the two.
Have you included sACN yet?
timon wrote:So you hove some sort of a mapping table between the two.
Not sure what you mean by this? If you are asking, how do I convert the LOR unit id to a DMX channel, that is straight forward. The LMS file for a "channel" has a unit, circuit, and network. The formulas are:
DMX Channel = (((unit-1)*16)+ circuit) + network*512;
And if it is marked as a DMX universe in the LOR lms file the formula is:
DMX Channel = circuit + (network-1)*512;
If you mean the effects, there are only three: intensity, shimmer, twinkle
Each one can ramp up and down, and that ramping is just a calculated linear slope based on time delta and intensity delta.
As for shimmer, it is one cycle one, one cycle off.
For twinkle there is some randomness. It is one for a random number of cycles (between 3 and 8), and high between 5 and 12.
Everything is sampled at 25msec, for that is what I run at.
Ok, you use the basically the same mapping as the xLights default.
What about sACN, E1.31, support.
I really like being able to run the show at different speeds. The Mac API makes that easy compaired to other platforms. The hardest part I see using you program is writing the XML for the visualizer. Do you do it by hand or do you have something that creates each prop?
Totally agree the visualizer xml is tedious (not hard, just a lot of copy/paste and tweaking). The offset to that is it is pretty much a one shot thing, and then it is good. As I mentioned earlier, I have plans to do a graphical interface for creating it, but that is way down on my priority (recall, I also design/build hardware to control lights, so time is very limited). So no automated way, but it is a pretty easy format, that if you have similar things in your display, it is just copying and editing the channels (It has scale factors and origins so one can change the reference location that the other items delta off of and the scale).
As for E1.31, no I haven't incorperated that. Probably low on my priority, as for just not something high up on my list (I believe I can obtain reasonable channel counts less expensively, and have dmx extractors that one can use to siphon off the SSD stream if necessary). Doing ethernet is probably a higher priority (using a different protocol that doesn't require me to stitch small packets together which is another discussion) before I adopt E1.31. BUt I have it in consideration, again, just one of those time things.
