I use PT as my timecode master. It's generating code outta the SYNC to a distripalyzer and I have a V1 and PCM 800 chase. No, it doesn't happen 100% of the time. But today is a good example. I just finished a mix and printed stems for about 14 min. I stopped the record, saved and closed the session. I rebooted the Mac, re-opened and I got the error message. 14 minutes of a continuous record of 3 stereo tracks disappeared!
We have been having same problem. We print the mix back into protools. Everything is there until we close the session. Once session is closed and reopened, all the mixes we printed is gone from the session. Tracks are there, empty. They are even not in bin. (Funny, all the audio files are in proper audio file folder. ) We wanna know what's going on with the system!!! ProTools HD w/Sync I/O, Protools Version 6.4 with cs8, OS X.3.4, session is 44.1, 24bit, SD2s, all playing back and printed back to one firewire drive, maximum 40 tracks. Songs are only 3-4 minuites.
Hi I've started getting this regularly on my HD4 system. I haven't changed or added any software or plugs but it's becoming more and more regular ... usually nothing is audibly missing but yesterday the strings were no longer in the first chorus ... I bluffed through it so as not to alarm the client but I know they were there prior to opening the session and getting that message ... I wasn't locked to code of any sort .. just working internally ... This happens on my system and other (well maintained) systems that I use regularly. I have the correct versions of OS and everything ... Ren
Uh, closed the session last night, no problems, open today and i get "some regions...." -are you kidding me? what the @#$*! is this? Seems a bit incredulous that this problem exists at all, that is, PT has decided for ME that some regions are too small!? too small for what?! they're 10 seconds long! so i search the duc and find that this is not the demons of drugs past mocking me, but there is actually an unresolved post about it. has anyone uncovered a solution/cause/explanation to this?
I've just updated to 6.4cs9 and started (for the first time) to get the same message when opening a session that I had been happily working on yesterday b4 the cs9 update........ Can I really "safely ignore this message" as it says in the answerbase? I'm not locked to code. Clocking internally. BTW the setup is Mac OS 10.3.4, PT HD 1, PT 6.4 cs9, Mac DP1.25,1GB Ram. Ray