I'm working on this new controller and my own sequence software (my own version of Vixen). I want to be launching it for this next Christmas season.
I had asked in a Vixen 3 thread if Vixen could pass hi-level commands because certain commands make sense to be performed in hardware - not necessarily in software. I was implementing a complex "effect group" into my sequencer and it occurred to me that the "Twinkle" function could be moved into the controller - making it easier to design complex sequences in software.
I have my own thoughts on Twinkle and Shimmer (I have read Vixen's and LOR's) - but I would like some feedback from end users.
To me --- a Twinkle is a three segment effect: An attack (ramp up) to an ON intensity level followed by a decay (ramp down). Variables are length of time associated with attack and decay, level of ON, and length of time for ON.
In actual practice - do you find one set of variables will fit 90% of the needs? I can see a Twinkle command having a specified intensity, specified duration and then select from a set of preset attack and delay profiles.
What length of attack and delay do you find most common in practice?
What ON duration is used most often? -- or Range of duration.
Vixen documentation states that Shimmer is like Twinkle but it is applied to multiple channels all having exactly the SAME profile.
Is my understanding correct?
Does Shimmer have different attack and delay times from Twinkle.
Are there any other types of effects that could be moved into the controller (LOR states their twinkle is in the controller - not the software).
Thanks in advance for your replies.
Joe
In LOR, I believe that both Twinkle and Shimmer are full on and full off.
I believe that Twinkle is a random 1-2 seconds of on time, for each channel for the length of time in the sequence.
Shimmer appears to be full on, every other cycle. It’s kind of like the old time movie flickering. This is synchronized to zero crossing.
ErnieHorning wrote:In LOR, I believe that both Twinkle and Shimmer are full on and full off.I believe that Twinkle is a random 1-2 seconds of on time, for each channel for the length of time in the sequence.
Shimmer appears to be full on, every other cycle. It’s kind of like the old time movie flickering. This is synchronized to zero crossing.
May I challenge you to make sure we have the same understanding.
The LOR software states that it will command non-LOR controllers hard on/off. Doesn't the LOR software command a LOR controller differently?
I was under the impression that LOR controllers actually did more than ON/OFF otherwise the protocol and use of the LOR software would not be different.
If shimmer is like a flickering movie - then the cycle rate should be less than 24 events per second (movies are 24 to 30 frames per second I think). Any faster rep-rate and our eyes just integrate the effect. I say that because you stated every other cycle - I take that as whole cycles - so a rep-rate of 30 per sec. I would think that we would not see a flicker but just a dimming effect of the lights because the rep-rate is above 24.
If that's the case than a rep-rate of 5 or 10 or 15 should be perceived as flicker.
Is that Shimmer?
Thanks
Joe
Hi Joe,
I don't think there's any need for a ramp on/off time.
My understanding is that 'shimmer' is a bunch of channels that 'twinkle' in sync (same changes at the same time) with each other.
Here's my C source for twinkle... this assumes the function is called every 50ms. If you want the rest of the program, I'm happy to share. It doesn't play Vixen files, just cycles various patterns on the lights. No music.
What language are you writing in? I have another sequencer written in Java called JLux which does play Vixen files. Collaborate?
Frank
void twinkle(int max_strands)
{
int strand;
for (strand = 0; strand map %u
", strand,strands[strand][0]);
if (rand() < RAND_MAX / 4) continue;
set_strand(strand, rand() * (100.0 / RAND_MAX));
}
}
Picture of my sequencer. C++. Working on adding grouped effects.
Shimmer - as defined in the Vixen documents I have read - states Shimmer is Twinkle across multiple channels - all in-sync with each other.
I'm weighing what I want to accomplish in PC software and what I want in controller software.
The basic building blocks are "Level" - intensity at a fixed level, ramp-up, ramp-down, and DMX specified value. From these blocks, more complex "Effects" can be defined by grouping them together and then using them as a group - not as individuals.
That's why I started weighing Twinkle - in PC software or controller. A simple twinkle is ON at some intensity for some duration and then off. Simple - yes. Appealing to the eye and capturing the effect of a twinkling star - maybe not. That is why I stated a Twinkle should be considered a group of 3 simple effects: ramp-up, level, ramp-down. By changing the associated variables related to each - a nice single event twinkle should be produced.
Then - when you create a sequence - a Twinkle sequence time block would have a random number of random twinkle events.
So far I've stayed in a single channel. When you take a single or series of channel effects and copy them into other channels AND apply what I call a "Shared" attribute - then all channels are actually being driven by ONE defined effect - so all channels respond exactly the same way - same time. Change one and they all change.
So --- if I can define a Shimmer for a single channel - which just might be a twinkle - I can "Share" that effect across multiple channels giving what is referred to as a Shimmer in the Vixen world.
That is why I am asking - is a single channel Shimmer event the same as a Twinkle - with exceptions - twinkles probable have shorter duration and are random - shimmer occurs at a rate which produces flicker ... but at a longer decay time?
I'm hoping to hear what looks good.
Thanks
Joe

