Hi, I would like to know why there are 2 seconds of difference between the CD built inside and the LTC or MIDI timecode? when I use the cd to trigger cues in my shows and after I transpose the same timing on a MIDI timecode or a LTC timecode or a Simulate timecode, I find a latency about two seconds. note that the audio files on the CD and MIDI timecode and LTC time code is the same!!!! I think it's 'cause the CD fisical time to initialize the disk and then to read from the first track. It's possible to reduce this latency, without use a pc to read a wave track and the internal simulate Timecode to syncronize with the pc? It's very heavy!!!!!!!
Since finding out that the timecode 'shift' functionality does actually exist, I have not thought to play with it.
The one problem with shifting on the Hog 2 is that timecode in the Duration column of a Link cue (i.e. exit TC for a loop) would not be shifted with all of the timecode in the Wait column.
Does the exit TC for a loop on the H3 have to be manually updated after a timecode shift, or does the console know to shift these exit points as well?
PG
PS - If the answer is no, any chance of getting a Feature Request for this?
Since finding out that the timecode 'shift' functionality does actually exist, I have not thought to play with it.
The one problem with shifting on the Hog 2 is that timecode in the Duration column of a Link cue (i.e. exit TC for a loop) would not be shifted with all of the timecode in the Wait column.
Does the exit TC for a loop on the H3 have to be manually updated after a timecode shift, or does the console know to shift these exit points as well?
PG
PS - If the answer is no, any chance of getting a Feature Request for this?
