Anyone else get Assertion Errors?

[beggehorn]

I've been recently plagued with "assertion errors" on certain sessions (three or four now) when I try to compact the audio files for those sessions. When they occur, the system freezes and I am forced to restart. I realize that this is usually caused by corrupt audio files. The only solution I've found is to create a new session, import each track from the bad session (one by one) and compact the audio until I find the track with the corruption. I then route and re-record the audio to a new track (duplicating, or consolidating does not work). The sessions this problem is occurring in are sessions I started in PT 5.x (don't know if thats a factor or not). I do know that this problem started after upgrading to PT 6.1 which I'm currently running on WinXP with an HD2 system.

[steve at Your Heaven]

John,

Has this been resolved yet? I'm considering the upgrade, but not if I will have to spend hours reconstructing every session I have.

[beggehorn]

Hi Steve,

I'm still unsure what's causing these errors. I called Digi last time it happened and they just told me it was caused by corrupt audio files and suggested a few ways to work around it. Fortunately all the tracks have always played back just fine. The error only occurs when trying to compact. I'm thinking it is the metadata of the older session's audio files, though it doesn't happen to all files. The last session it happened to had 4 or 5 bad tracks. I'm not sure if it was a single region on those tracks or maybe more. For each bad track, I just opened a new track and bounced it over as a new single file and it fixed the problem. A bit unnerving and time consuming to say the least.

Ben

[steve at Your Heaven]

Thanks - at least the workaround sounds simple, I think I can live with that (I'll mostly avoid compacting).

[beggehorn]

I just fixed the last session that had this problem. There were two tracks with corrupted files, and those tracks had just been recorded within the last two weeks or so. Hmmmm...I guess its not a PT5.X to PT6.X session conversion issue...