Timecode woes

[Indrestudios]

So the other day, I'm on location with one of our ProTools HD flypack kits - chasing 29.97 drop code provided by the TV production folks and PT drops out of record when it hits 11:25:39;10. All I can say is "Thank god for the backup machine!"

The system was set to JAM sync, and I'm scratching my head to figure out why it stopped rolling.

I was able to duplicate the problem back at the shop, and indeed it will stop playing (or recording) whenever the incoming code hits exactly 11:25:39;10. It will not chase any code after that particular timestamp, the sync and play transport buttons just blink. I did confirm that the session frame rate matched the incoming rate.

There are no regions highlighted, or anything obvious in the session preferences. The session start is set at 11:00:00;00, and we were recording at 24bit/48k. I even tried creating a new session from scratch, same results - won't drop in after 11:25:39;10

Is this some magic code number that I don't know about? I've done about zillion other broadcasts where 11:25:39 probably came and went without incident.

I posted this as well on the Digi DUC forum, but I know there are many remotesters here who have to chase code on a daily basis.

ProTools HD III version 7.4
Sync i/o firmware 1.1.4

-MC

[AlphaMutt]

Check your allocated disk space for record in preferences. If that's set to a strange number once you hit that time it will drop out of record.

J.S.

[Indrestudios]

I always select "use all available space" when doing remotes. Double checked this setting.

[Remoteness]

Thanks Joel,

I was hoping you would chime in on this one.

Michael, did you get a chance to check your allocated disk space for record like Mr. Singer suggested?

[Indrestudios]

I actually borrowed a couple other TC generators yesterday (Deneke & Brainstorm) and I get the same behavior regardless of the device. Always stops at that same code #.

Remember, I'm set to JAM sync - I'm able to yank incoming code and PT keeps rolling, only stops exactly at 11:25:39 each time.

I tried the usual PT stuff - pitching prefs, etc. and even re-installing the Sync i/o firmware in case something got corrupted...same behavior.


very strange.

[AlphaMutt]

Tried this myself on several different systems and can't replicate. Do you have another Sync IO to try. I had one take a crap on our West Coast truck a couple of weeks ago. But that caused loop sync issues not TC issues. Maybe you could post the session file and a few of us could try it on our systems.

J.S.

[Indrestudios]

Thanks Joel. I'm sure you have much better things to do with your time than troubleshoot my PT rig.

I do have another Sync i/o I can try, good idea. If I have some time today I will post a link to download the session file if anyone else feels like giving it a try.

[Remoteness]

Brilliant!

[huub]

Do you always start from the same template? I once had a template that caused wrong timestamps after a software update, after building a new one all was fine..

[Indrestudios]

No, our projects vary so much that I don't have a standard "go to" template. Everything up until now has been built from the ground up for each session.

[AlphaMutt]

Not a problem. Was in the shop getting the truck out to Nashville and had some of the PT systems out and running. If you still want to post I'll still take a look at my system here at home.

After I thought about it I don't think the Sync IO will be the culprit. It would either be working on TC or not. But swapping it may show you something else. Check the peripherals page for the Sync IO and make sure nothing strange is checked in there either.

Keep in touch.

J.S.

[Indrestudios]

PROBLEM SOLVED! Thank God.

A Digi tech chimed in on the D.U.C. board and informed me that the issue was resolved in a CS software update back in 2007. Here's how it is listed in the Digi 7.4cs2 update page:

Fixed: Time Code Chasing Not Possible After Time Code Reaches ~ 11 hours, 25 minutes, regardless of session start time (Item #99605)
This would occur with a session start time anywhere between 01 to 11 hours

Installed the update and everything works like a charm now. Thanks to all who offered up suggestions.

I've been a very late adopter of software updates when our rig seemed to be rock solid. "If it ain't broke...". But here's a case of where I should have been paying more attention to their CS documentation.

-MC

[Remoteness]

I'm glad to hear everything is everything again!

[AlphaMutt]

Well there you go. I would say you should update to 7.4.2cs4. One of the more stable PT operating systems. It solved quite a few problems we had past 7.4.1. Mac OS 10.5.5 is also the ticket there. We seem to have found these two working in harmony make for a happy PT system.

J.S.

[Indrestudios]

I updated to the last CS version for 7.4 - 7.4cs10 and everything seems to be working well.

That particular system is built on an older PPC G5 running 10.4.9. I think you need 10.5 to jump up to PT 7.4.2. Too many numbers.