first of all, thank you a lot for adding this feature. This is awesome!
Looking forward for looping parts
I have tested the cycle function using MTC Follow and found the following issues:
Sometimes the destination (Cubase Pro 12 in my case) doesnât loop although the cycle started again, it runs further in Cubase
Sometimes the destination stops playing and starts again at the next cycle start
In the attached video I have cycled measure 3 and 4 in VST Live. Sometimes Cubase goes further than 4; sometimes it stops playing.
Video 1
1 MacBook Pro running VST Live (left) and 1 MacBook Pro running Cubase 12 (right)
connected directly via LAN cable using MIDI Network - VST Live on the left MacBook, Cubase on the right
Video 2
1 MacBook Pro - VST live and Cubase are connected via MTC with IAC driver - Cubase on top, VST Live below)
Any form of timecode is not supposed to jump in time. The MTC (MIDI Time Code) writer detects discontinuity in the project position when the cycle jumps backwards, and internally stops, relocates, and continues to send MTC from up the new position. It does not know what the receiver does with that.
Do you have any reference system that works as you expect it to? Which DAW puts out MTC in a way that allows Cubase to follow a loop (cycle) operation in sync?
Do you have any reference system that works as you expect it to? Which DAW puts out MTC in a way that allows Cubase to follow a loop (cycle) operation in sync?
I am using the Arranger Track in one Cubase project which has parts that are sometimes looped. Via MTC it triggers another Cubase on another PC.
Of course, it is not 100% accurate. Sometimes doesnât loop and loops the next time, but definitely not as often as when VST Live triggers the loop. So, mostly it works rather good with Cubase to Cubase.
See this screenshot with 3 looped arranger track parts:
That comes to no surprise. Timecode is generally not supposed to jump at all, so this is just pure luck.
Sorry, but we canât do more than send TC following the cursor. If jumps occur, that is propagated directly to the timecode and it is more or less random how the receiving system reacts to that.
Furthermore when I started using LTC a few yrs ago for my concerts, an expert teached me to leave at least of 12 frames let the systems read LTC position. And in my experience 12frame was really a bare/safe minimum. So my experience prooves @musicullum : TC can handle jumping but needs read/understand first.
Hi guys! Iâm sorry for what Iâm writing. First I have to let you know, last time I had to TC Cubase it was the time when we did it with Atari + Tape machine (lol, Iâm sorry about, but true)
Second, I canât exclude, itâs Cubases fault as it is working okay with Reaper, see:
But doesnât with Cubase 12 pro
But have to admit, Iâm just a current user of LTC for visual + lights but not for Cubase. @musicullum am I doing something wrong with Cubase?
Meanwhile @Matze_Keys : working or not or will or not. I would kindly suggest you to reduce your live system one DAW only (if it is possible) regardless of cycle is working via TC or not. (Also Cycle is not the root purpose of TC.)
Currently VST Live is still not usable for us as we are working on 2 computers and VST Live should sync Cubase Pro on the computer.
Maybe when it will be possible in future weâll both use VST Live and one will be triggered by the other.
What Iâm wondering is, why it is working when we are both using Cubase Pro. With the Arranger Track the parts are triggered and the cursor follows the loops/parts quite reliable with MTC.
With VST Live it is not so good with loops. Seems to me like the MTC is not sent sequently.
Sure! Absolutely not meant, Iâm composing with Cubase also, but whispering what if to ask also at the Cubase product thread?
While this is interesting, what meight cause the difference
Jumping in timecode is not supported. MTC/LTC is intented as a realtime and continuous, uninterrupted stream. Looping etc requires preloading of data (like reading audio from a disc), which is impossible if a jump occurs in realtime in the middle of a continuous stream of time (like life, so to speak).
Actually cycle mode is not needed, BUT once it is possible to loop a Part, will it work better with MTC?
That was the reason why I have already tested MTC with the cycle function because I think this is essentially the same as a Part Loop.
Essentially, the MTC writer checks for jumps, but waits until a threshold (2 quarterframes) is exceeded before it re-locates to compensate for timing errors. While this may cause hiccups on the receiver side, it should re-sync shortly after the jump. Not sure what you mean by âdoesnât workâ, as ever so often
With the next version, if preference âMTC follows Cursorâ is activated, it will locate immediately when a jump is detected. Pls check if that improves the situation then.
@musicullum I have made some tests and I figured out that using Frame Rate 25 works more accurate than 30. Strange, but using 25 frames I mostly donât get dropouts and the cycle loops rather fine. MTC drop outs on the destination DAW (Cubase) only after a while (after some continued loops).
Thatâs probably one of the 30 fps formats that arenât actually 30, but 29. something. You may try to set the other side to another 29 or 30 fps type if applicable, unless that breaks its internal sync.
