Sync pt001 6.1 to da38

[pete doherty]

Hi,
recently upgraded to 6.1 and the sync i used in 5.3 no longer works. i use a tascam mmc 38 interface unit to the midi in of 001.
i am recieving incoming time (it syncs up in the incoming time box) but doesn't play sound. in the edit window the play cursor jumps to the new position every few seconds. in the transport window the sync clock, play and stop icons flash.

when i alter the session setup time i get this message 'Unable to maintain original timecode locations with the entered start time because a region and/or and alternative playlist would exist outside the session boundaries. Click ok to maintain relative position.'

if i put the transport in record mode this message comes up when the sync point is reached..' missed the sync point, due to time spent allocating disc space. please use a larger pre roll or limit disc allocation for better performance.'
i've done all this but no luck.
any hints would be greatly appreciated.
pete

[Rail Jon Rogut]

Are you trying to do an analog or digital transfer?

In the Session Setup Window.. is the incoming LTC earlier than the session start time?

Rail

[pete doherty]

analogue transfer. when opened the session start box says 00:16:00:00. when i change it to match the da38 session start time a box says 'unable to maintain original time code...' the ltc( i assume this is the incoming time) matches the display on the da38.
pete

[Rail Jon Rogut]

Well, there's yur problem.. you need to trim the front of the session (also check for any automation, etc) so that you can set the session start time to the same value required for the transfer.

What's the Tascam time code value?

Rail

[pete doherty]

hi Rail,
thanks for taking the time. i opened a new session and no longer get the 'unable to maintain time code...' message but it still wont record. i still get 'missed the sync point...'
the sync,play and stop buttons still flash in the transport window and dont stop once the incoming time from the da38 reaches the set session start time.
To answer your question; the incoming time in my session setup window matches the display in da38 and stays in sync. i set the da38 to play 10 seconds before the session start time(to give pt time to sync up) In short, I'm doing everything i did with pt5.1 but it no longer works.
One thing is new.. In the session setup window every time i open a session, the session start time is set at 00:16:00:00.
pete

[Rail Jon Rogut]

What time does your DA38 start at? Create a new session in Pro Tools, open the Session Setup Window (Ctrl+2) and change the session start time to 00:00:00:00.. check your record in lock or at timeline preference... set it to record at lock.

Your session start time has to be earlier than the time you want to be in record.. and you should have at least 10 to 15 seconds of preroll before you can expect Pro Tools to lock.

Rail

[pete doherty]

checked all you said...still no joy.
pete

[Rail Jon Rogut]

Unarm any record armed tracks.. does Pro Tools chase? If you're online, your session start time is before the incoming LTC stream, and your preference is set to record at online lock.. then your system must chase incoming MTC if you see the numbers changing in the Session Setup Window. In the Transport Window, is transport = Pro Tools?

Rail

[pete doherty]

all tracks are record dis-armed. transport=pro tools.does pro tools chase? in the session setup window the incoming time matches the da 38 display and chases. preference set to record online at timecode lock. what do you mean by 'my session start time is before the incoming ltc stream?' i have set the session start time to match the time code on the da38 where i want pro tools to sync...in other words, i set the pro tools session start time at (for example) 00:10:00:00 and play the da38 from 00:09:45:00. The incoming time and the da 38 sync but pro tools will not perform either play or record functions. the sync,stop and play buttons in the transport window continue to flash when passing the session start time whereas they used to go solid when the sync functioned correctly.
pete

[Rail Jon Rogut]

No - set your session start time before (at least 10 to 15 seconds) where the SMPTE starts on the Tascam.

Rail