Hey
This is my first message on this forum , nice to meet you all !
I play in a rock band , today we use an application to send MIDI controls to a stairville dmx foot controller , this solution works great but has limitations(channel count, scene count)
So i'm planning to test QLC+ and it seems to be a great solution , but i 'm questionning about the latency of midi & dmx orders as we have a lot of short flashing scenes synchronized with the snare drums
Do you guys have any experience with this kind of configuration with quick MIDI changes?
Thx
Button controlled by MIDI vs Latency ?
-
GGGss
- Posts: 3052
- Joined: Mon Sep 12, 2016 7:15 pm
- Location: Belgium
- Real Name: Fredje Gallon
Welcome to the forum,
QLC+ defaults to 50Hz internal clock and an input operation needs 2 ticks; so there would be a 2x20ms latency which still is double as fast than the human eye can distinguish.
QLC+ defaults to 50Hz internal clock and an input operation needs 2 ticks; so there would be a 2x20ms latency which still is double as fast than the human eye can distinguish.
All electric machines work on smoke... when the smoke escapes... they don't work anymore
-
Cyril
- Posts: 8
- Joined: Mon Jan 09, 2023 10:47 pm
- Real Name:
Hey
Thx for your feedback , Actually i did some tests with QLC , a virtual MIDI interface (loop MIDI) , and a midi sequence played on the same PC
When i push the button manually ( with keyboard shortcuts) the change is very fast
When i play the sequence , it seems the buttons are not triggered as fast as manually
But maybe the MIDI loopback is not a representative method to test this behaviour
Thx for your feedback , Actually i did some tests with QLC , a virtual MIDI interface (loop MIDI) , and a midi sequence played on the same PC
When i push the button manually ( with keyboard shortcuts) the change is very fast
When i play the sequence , it seems the buttons are not triggered as fast as manually
But maybe the MIDI loopback is not a representative method to test this behaviour