"playback has reached the end of the session"...

[Arno Peeters]

huh?

Diskdrive enough (37 gb), default window-length to the max, open ended disc allocation... It just refuses to go on after 372 mins and some...

Anyone?
There's no mention in the answerbase or in the forums

[MikeAP]

I think that there were some issues with a ProTools session that had a session start time of 00:00:00:00 (in the session setup window) having trouble going past something like 13 hours. Would is be possible to set the session start time closer to the beginning of the audio?

The other thing that you may be running into is if you have one long file is that there is a 2GB file size limit... Not sure if it's still there in X, but a single file cannot be larger than 2GB in OS9...

[Arno Peeters]

Nope, since the recording alltogether is something like 6 hours. It just refuses to go past 370 mins or so.
Even stranger: if I move a region halfway past that point and move it back (object mode) it just cuts off everything that is beyond that point.... Weird!

Digi?

[DigiTechSupt]

Hi,

What is your session start time and what sample rate are you at? At 48k the max session length is about 12 hours, at 96K it is about 6 hours. If you continue to have problems you may want to try using import session data into a new session document, it is possible that you current session is corrupt.

Thanks,
Digidesign Tech Support

[tele_player]

another 'possible session corruption'?

Sure would be nice if Digidesign would include a tool for validating integrity of session files. If I were a developer at Digidesign, I'd be curious as to the nature of the corruption.

[SuperScott]

another 'possible session corruption'?

Sure would be nice if Digidesign would include a tool for validating integrity of session files. If I were a developer at Digidesign, I'd be curious as to the nature of the corruption.

yeah because that would be worth spending time on.

[Arno Peeters]

Indeed: it's 96/24bits, so 370 min is quite correct than. Still I find this limitation somewhat weird. Is it the waveform-data and session database that will be too heavy to hold after 6 hours?

[Rail Jon Rogut]

No it's the 32 bit variables which are imposed by the developer tools available and OS limitations. When OS 9 can be forgotten as a supported platform then limitations like this and 32 character file names can be dropped. Perhaps next time the session file format is changed. The other issue is file sizes - the WAV and AIFF file formats require data values for the file and data size to be DWORDs which can only hold a maximum value of 4,294,967,295 before it rolls over (add 1 to it and it starts at 0 again).

Rail

[Arno Peeters]

Rail, you're as informed as ever. Thanx!

[wav28]

I'm having this problem since day one.(2/24/12)..sometimes I get 2 hours or so use
( when it's working at all) and sometimes it's less than 10 minutes. What gives Avid guys?
Can you tell us in LAYMAN'S terms, instead of computer school verbage?