• Date
    matzestrobel
  • Date
  • Replies 5 replies
  • Subscribers 186 subscribers
  • Views 3733 views
  • Users 0 members are here

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

  • 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.

  • Do you know what framerate the external timecode is in?  It could be running at 30fps or 24fps or 29.97.......options options... if the internal timecode is not at the correct rate then the timing will appear off more and more as you get further into the track.

     

  • in reply to Druuka

    Hi,

    i have set the internal framrate to 25 which is the same for the external trigger.

    @pwiegand: sadly, it's not "just" an offset by time x, it starts at the correct time but then the offset gets bigger and bigger. so it's more like the internal clock is running much faster.

     

    example: Cue 100 is recorded at 00:10:20:23, however the actual timecode point in the music track and with the external trigger is at 00:08:50:12 (values are random...just making an example ;). So the desk seems to go faster in time..we found a time machine !

     

    Anyway thanks for your input !

    Matze

  • in reply to matzestrobel

    It sounds like you ran the internal clock while playing the track to pre-program the times, and are now syncing to the timecode that's actually striped onto the track.

    Have you timed it with a stopwatch?

    It appears one of these is not running at real time, and given that you see the same thing on both the Ion and the Offline Mac, it's very likely that the external timecode is in fact running slower than "real time".

    - eg the tape has stretched or the timecode was not striped at real time rate originally.

    (Note that the 30 fps Non-Drop-Frame rate loses 3.59 seconds per hour by specification.)



    [edited by: Richard at 2:49 PM (GMT -6) on Thu, Apr 4 2013]
  • in reply to matzestrobel

    can you give a real example of when a cue fires and when it should fire? if it's off by 1/6 that would indicate that it's a 25 vs. 30 frames issue...

Related

www.etcconnect.com