--
Contact support anytime: sup...@figure53.com
Follow QLab on Twitter: https://twitter.com/QLabApp
User Group Code of Conduct: https://qlab.app/code-of-conduct/
---
You received this message because you are subscribed to the Google Groups "QLab" group.
To unsubscribe from this group and stop receiving emails from it, send an email to qlab+uns...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/qlab/137603eb-da58-4ed0-91ef-1b50616a72afn%40googlegroups.com.
Finally, if you do end up using timecode, I cannot recommend strongly enough that you use LTC and not MTC. If you’ve attended a class of mine, you’ll know that I think timecode is a dreadful protocol that should be banished from theaters everywhere, but out of the two, MTC is definitely the inferior version because it uses a quarter-frame format: you need four ticks of the clock to tell what frame you’re on, instead of LTC’s single tick. Plus, distributing LTC is easy because audio infrastructure is easy and cheap. Distributing MTC requires MIDI splitters and MIDI-to-XLR adapters… messy.
I’m still aghast at that opinion that timecode is a "dreadful protocol that should be banished” being as we use it daily in broadcast very successfully and robustly.
Your dislike of timecode (for whatever reason - that I’d like to understand more) perhaps hints at the reticence of QLab to embrace sync’ing to it - the capability of which would be a tremendous boon to my workflow.
I think you might want to do more dance shows if you think there's no room for timecode in live theatre? ;P
I'm not sure I completely agree with this interpretation – although I've avoided actually using MTC so may have missed something that comes up with experience?
The precise timecode address is sent over 8 "quarter-frame" messages, but these are sent at 4x frame rate – so your conductor marks quarter beats but only tells you where you are every other beat, Timing information is arguably four times better than LTC (?), but positional information is half as good. This is only relevant when changing position though, so it affects how long a slave takes to lock up. You should include pre-roll to allow for this regardless of timecode format.
I believe a device following MTC won't be off at all, and certainly not by 4 frames. It will take a minimum of 2 frames to catch up with a positional change.
Rich
On 3 Dec 2020, at 14:37, Sam Kusnetz <s...@figure53.com> wrote:
My dislike is not for timecode in and of itself. My dislike is for exactly three aspects of timecode:
First: MIDI timecode, because it must exist within the technical limitations MIDI which are objectively very restrictive by modern standards, uses a quarter-frame format. For those who don’t know, that means that four frames of MTC must be read before the receiving device knows exactly what frame we’re on. It’s like a conductor reading measure numbers: “ONE two three four, TWO two three four, THREE two three four…” it’s fine in principle, but in practice what it means is that at 24 frames per second, a device following MTC might be as much as 1/6 of a second off. When the purpose of timecode is perfect sync, 1/6 of a second feels like a gigantic margin of error. LTC does not have this problem at all.
--
Contact support anytime: sup...@figure53.com
Follow QLab on Twitter: https://twitter.com/QLabApp
User Group Code of Conduct: https://qlab.app/code-of-conduct/
---
You received this message because you are subscribed to the Google Groups "QLab" group.
To unsubscribe from this group and stop receiving emails from it, send an email to qlab+uns...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/qlab/720D9BE2-4F4E-43E2-B061-A462BA26B164%40mac.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/qlab/9b493ee4-537f-4327-a714-1640cc718df7%40Spark.
--
Contact support anytime: sup...@figure53.com
Follow QLab on Twitter: https://twitter.com/QLabApp
User Group Code of Conduct: https://qlab.app/code-of-conduct/
---
You received this message because you are subscribed to the Google Groups "QLab" group.
To unsubscribe from this group and stop receiving emails from it, send an email to qlab+uns...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/qlab/555A056E-DCA8-47CC-924A-149CA4A5AB29%40mac.com.
Timecode pre-rolling and full, proper timecode sync/lock/follow are on the slate for the future of QLab,
I’ll gently bend our company guidelines against sharing future roadmaps to say:
Indeed! I’d call the audio side of it “done”; still working on the video side. Expected in v5. (No ETA yet on v5 though.)
--
Contact support anytime: sup...@figure53.com
Follow QLab on Twitter: https://twitter.com/QLabApp
User Group Code of Conduct: https://qlab.app/code-of-conduct/
---
You received this message because you are subscribed to the Google Groups "QLab" group.
To unsubscribe from this group and stop receiving emails from it, send an email to qlab+uns...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/qlab/d6ce10c0-0a25-4c88-a38a-484fb72fefefn%40googlegroups.com.