Annoying bug when reaching 12:30:00:00 in timecode

[dkroger]

Hi.

I'm syncing up to an incoming SMPTE code using the Sync i/o.

The problem is that when I reach around 12:30:00:00 Pro Tools denies to use the timecode. The sync window correctly displays the incoming timecode and the Sync i/o doesnt complain. The online button flashes but it doesn't react to the timecode.
The funny is that when after reaching this point Pro Tools denies to read ANY timecode until Pro Tools has been restarted.

To get around this problem I tried to let Pro Tools be the master and let the other machine sync op to Pro Tools instead. But when I try to start Pro Tools from the above mentioned timecode I get a "DAE Error 9060".

I have tried to setup up new sessions to see if it was some sort of corrupt session but with same result.

For now I have made a -10:00:00:00 offset to get around the problem but it's definetly not an optimal way of doing it.

Has anyone noticed this behavipur as well or have a work around for it?

[Frank Kruse]

It´s not a bug it´s a restriction of PT. It can only handle a session length below 11h40minutes at 48k.

you need to set your session start so that the total length doesn´t exceed 11:30 or somethinglike that.

frank.

[dkroger]

Thanks for your answer Frank

Couldn't find any information about this on the website or manual...
I'm running at 44.1/24 and found out that it can't go above 12.26.10.xx . Tried to spot a region above that point.

Is there an easy way to move the material I have now to the true timecode (+10 hours) with a correct timestamp and a session start that alows the material in that spot. I have nothing below 09:12:00:00 and nothing above 15:17:00:00