Internal Timecode offset issue

Hello,

 

I have pre-programmed a show on a Gio and recorded lots of Showcontrol events using the internal timecode trigger. 

 

After loading the show on an Ion I found out that the internal timecode has a rather big offset of over a minute after 10 minutes already (as compared to an external timecode trigger used for the show).

 

I was a bit irritated by that to say the least and loaded the show in the offliner on a Mac - same result.

 

Has anyone had this before ? Am I simply missing something ? I hope this is something that can get fixed since it makes using timecode during pre-programming almost useless. (Since I had to re-record all events again with an external trigger.) I am using 25 frames / minute timecode.

 

Software version 2.0.

 

Thanks for replies - Matze

Parents
  • Depending on how the external time code was burned onto a track, the actual start point may be different.  Not all hope is lost.  Here is how you can fix this. 

    Select all the events in the list (Event x thru y)

    press the time button (Time)

    enter in the offset (+2500)

    your command line will read

    Event x thru y Time: +00:00:25:00

    The result for this would adjust you time code for all events select 25 seconds ahead.  Likewise if I used - the time would be 25 seconds behind.

    Hope this helps.

Reply
  • Depending on how the external time code was burned onto a track, the actual start point may be different.  Not all hope is lost.  Here is how you can fix this. 

    Select all the events in the list (Event x thru y)

    press the time button (Time)

    enter in the offset (+2500)

    your command line will read

    Event x thru y Time: +00:00:25:00

    The result for this would adjust you time code for all events select 25 seconds ahead.  Likewise if I used - the time would be 25 seconds behind.

    Hope this helps.

Children
No Data
Related