"Some regions had invalid bounds and were adjusted or deleted"

[Fidelis]

Originally Posted by SessionKat

1. Simply opening a pre-existing session posts message YES
2. Editing moves made? YES/NO Fades created/adjusted? NO
3. RECORDING passes performed? YES

-tv

Just updated to 8.0.4 before reading this post. Just opened a session I did yesterday and got the message. Saved the text file an it was just the last undo recording i did. Didn't lose anything. But it's scaring me. Should we go back to 8.0.3? Digi, or Avid, or... whatever, I'm getting tired of all this PT8 problems. It's no fun anymore...

BTW, Mac Pro 8-core, OSX 10.5.8, PT HD3 Accel, 2 Euphonix McMix.

[SWSPHX]

And no answer from digi (avid) as the days go on....

[Dizzi45Z]

This is an annoying bug. I do have to wonder how stuff like this gets past beta testing. It pops up all the time at the beginning of almost any session that I have just done some recording in (started once I went to 8.0.4).

It sounds like Avid has figured out what causes this bug (posted earlier). Seems like nothing harmful, just annoying. We can all cross our fingers for a speedy update.

[SessionKat]

Originally Posted by SWSPHX

And no answer from digi (avid) as the days go on....

Read back through the posts from me and you'll see some responses from Digi/Avid (uh, me) which acknowledge and clarify this issue.

-tv

[innesireinar]

Hi SessionKat, is there a plan in Digi for decarbonizing PT?
I had lots of problems with the 8.0.3 under SL, many crashes, rainbow wheel every few minutes that forced me to restart the sys. I went back to 10.5.8 with the 8.0.1 that seems very stable. When the 8.0.4 came out I upgraded my OS to SL again and I was happy with the 8.0.4 for a while, then it started to behave like the 8.0.3. Now I definitively downgraded to the 8.0.1 on the 10.5.8. I don't know what is happening but I've never seen something instable like versions newer than 8.0.1 of PT8, at least in my system.

[David Pye]

I was also getting this message the other day on 8.0.4 on latest Snow Leopard.
Never had a file ACTUALLY missing from the session, but got this message every time I opened one of the PT sessions.
Disconcerting, and not great when you have a band stood behind you thinking they've lost stuff. Luckily not damaging though.

[Orange_METaL]

+1 for the all these issues and I've go another one to add


when I get the "Some regions had invalid bounds and were adjusted or deleted" dialog and I click on "No" to not save a report protools will crash on me
then I try and restart and get a total computer freeze - ???

Tried saving report - opened fine

Day 2 - tried saving report - crash and restart and then the computer freeze.

Seems now that its a bit of a round-robyn as to if I open the session or crash

[SessionKat]

Originally Posted by David Pye

....and not great when you have a band stood behind you thinking they've lost stuff. Luckily not damaging though.

I hear you loud and clear David.

[SessionKat]

Originally Posted by Orange_METaL

+1 for the all these issues and I've go another one to add

when I get the "Some regions had invalid bounds and were adjusted or deleted" dialog and I click on "No" to not save a report protools will crash on me
then I try and restart and get a total computer freeze - ???

Tried saving report - opened fine

Day 2 - tried saving report - crash and restart and then the computer freeze.

Seems now that its a bit of a round-robyn as to if I open the session or crash

I suggest the crashing is not related to the regions' save dialog yes or no. If you find a consistent session(s) or scenario which causes a crash submit/post it NEW to avoid it getting lost/confused with this issue.

Just an idea...

-tv

[WernerF]

Originally Posted by Orange_METaL

+1 for the all these issues and I've go another one to add


when I get the "Some regions had invalid bounds and were adjusted or deleted" dialog and I click on "No" to not save a report protools will crash on me
then I try and restart and get a total computer freeze - ???

Tried saving report - opened fine

Day 2 - tried saving report - crash and restart and then the computer freeze.

Seems now that its a bit of a round-robyn as to if I open the session or crash

Hey dude, It's Werner. How's it goin up in the great white north? .

Anyway, my 8.0.4 is working great here. Stable as a rock. No problems with the dialog crashing the system or the computer.