Event Period timing

[txag2008]

I have a question about selecting your 'Event Period' for a sequence. I realize what this is referring to and how it changes how long the time breakouts are for each channel. My question is about what timing most people use? I used 100ms last year, but I was just using a real simple controller with no dimming capabilities. Is it worth going to 50ms?

Why did you choose this 'event period' timing? Are there limitations of your setup that need to be considered when choosing this? (for the record, I'm using a combination of Ren and RenSS controllers.)

Thanks for the help ya'll.

[ctmal]

I have always used 50ms. As far as I've seen I believe this is what most people seem to use. With 50ms I've always found I can pretty much hit the beat of the song dead on.
I can't imaging going any lower would give much of a benefit(other than ensuring the rest of my hair would fall out).

[j1sys]

Being a newbie I can't talk from much experience.

I played with Vixen to lay down some beat tracks and found 100ms just a little to large for some fast trills in a piano solo (George Winston).

Then I switched to 50ms and found it better. Plus (if i did my math right), for 60hz power, 50ms would be 1/20 of a second or 3 cycles of 1/60th which I thought would be about as fast as you needed to get.

just my thoughts/observations.

-Ed

[christmas-light]

I am also only using 50ms, because then it is easiest to make a song, I think that it that worth :p

C - L

[aussiephil]

25mS all the time

Why: I use a lot of fades and LED's and this gives me the smoothest fades.

A half second fade at 50mS has only 10 steps where 25mS has 20 steps - this makes a significant visible difference.

When this was a simply On/Off hobby choicing the period based on timing requirements made sense. These days of fading event timing periods should be as short as possible and match the protocol update rate.

As i use DMX i would love to see Vixen support a 44Hz timing period so we have a direct one to one from timing period to protocol update period.

Cheers
Aussiephil

[BF210]

As i use DMX i would love to see Vixen support a 44Hz timing period so we have a direct one to one from timing period to protocol update period.

What happens when you try it with a 22 or 23 ms period? (The fractional 22.7 ms period that equates to 44 frames per second isn't supported -- periods must be integers.) I know Vixen's new sequence wizard complains, but how does the sequence actually perform?

Some folks here use the Tap Tempo (http://doityourselfchristmas.com/forums/showthread.php?t=8129) add-on to discover the exact tempo of a song and set the period to match.

You can change the event period from the menu under Sequence: Settings. When you do that Vixen tries to stretch or shrink any existing events in your sequence to match the new timing, but it doesn't recalculate ramp-on or -off spans to match the new endpoints. Thus setting the period before entering events is a good idea.

(yet another Don)