Can't set milli second accuracy to .01

[joe]

Hiya

Trying to make a speed control w/ loodbacks etc, however I can't set the range of the speed dials minimum to 0.01. Can only get it to 0.10 which is nowhere near low enough.

[plugz]

It's a 10ms precision, so 0.01s.

This is the max precision of everything in QLC+.

[janosvitok]

Joe, what are you trying to achieve? Why do you need so low numbers?

1 DMX frame at 40 Hz is 25 ms. 1 beat at 200 BPM is 300 ms. In this context 10 ms seemed low enough.

[TEL0000]

Joe, what are you trying to achieve? Why do you need so low numbers?

1 DMX frame at 40 Hz is 25 ms. 1 beat at 200 BPM is 300 ms. In this context 10 ms seemed low enough.

Actually the difference between 200 BPM and 199 BPM is 1.5 ms per beat. So 10 ms is not low enough to make a chase go with the beat.

Edit: btw. the time on my post is wrong. It's 4:27 pm now, but my post got the same time as the post i've quoted.

[joe]

I find that RGB Matrix effects aren't at the right speed until you get them down to .01 MS.

[plugz]

A speed dial showing .01 ms means .01 seconds, so really it's 10ms.

[joe]

A speed dial showing .01 ms means .01 seconds, so really it's 10ms.

I need to get it down to *1 millisecond*. The pixel chase effect is still pretty slow at 10ms. Try it.

[fooschnickens]

This is precisely why I've requested having the option to switch between m/s/ms and BPM for speed dial settings in the VC. You can get it kinda close to the beat, but with many tempos, their corresponding value in ms is fractional (140 BPM = 428.6ms) and simply rounding up/down will get you several BPM off (420ms = ~143BPM, 430ms = 138.5BPM) which can lead to very obvious desyncing after a few beats..