"PT unable to auto backup your session" Assertion in...

[gordon Russell]

I have a Powerbook G4, OSX.4, 1.67 GHz, 2 M Ram, PT 7.1, 002R, Octopre LE , OWC Mercury Elite PRo 360 GB firewire drive for session/data files. I have Garritan Personal Orchestra (RTAS). I produced a few tracks for a rock band, added some strings, etc. and started getting this error message: PT unable to backup your session: "Assertion in: CNeal0Block.cpp, line 792... The line numbers increase with manual saves and restarts.
I did the vast majority of fixes from the troubleshootin guide, incl. setup, energy saver, pace drivers, trashing prefs, databases and volumes, with restarts, and I dont have any virus protection. I'm a little nervous about re-installing PT cause I had the original version, plus a downloaded upgrade which I had to do twice and still have a couple of files with 6.9 interface hanging around.
In addition to this, I was trying to add a string with GPO on another session, and in record mode, PT would not stop with the space bar, or the mouse. I had to force quit the entire Powerbook.
Any suggestions?
javascript:void(0)
Thanks!

[Scott Church]

Hi Gordon,

Give this a shot. Create a new Pro Tools session (empty) and then choose File > Import Session data and just bring everything in new. Then try to save or do a Save Copy In if needed. It has helped me before with something very similar, so I thought I would suggest it.

Cheers,
Scott

[gordon Russell]

Thanks Scott, I tried a new session and it won't let me save it!. I get the message: "Assertion in CNeal0Block.cpp at line 1242."
Ouch.

gord

[gordon Russell]

I tried the new session again and it saved, even though I got the message. I then tried recording the midi. This time it would stop, but Igot the message: "could not perform requested operation because of assertion in CNealblock.cpp line 1242."
Also, it did not save what I recorded, the track was blank.
Any more sugg.?

thanks, I really appreciate anyone's help.

javascript:void(0)

[Faulty Records]

I know this is off topic but...

Hey Scott, are you the same Scott Church from Cherokee Recording Studios circa 1984-85?

Drop me a line.

David Eaton
[email protected]

[Rail Jon Rogut]

Generally a neoaccess error means your DigiBase folders are corrupted - delete the folders and files as directed in the sticky Troubleshooting thread. I have seen this also occur when running RTAS Instruments which use up large amounts of RAM... usually restarting Pro Tools helps.

Rail

[j-man]

I am currently recieving a similar NEO assertion Error, ending in CNEOBLOCK as well. I have RTAS plug ins running in the track. How should I configure my session, so i can use the RAM I need without messing up the track?

[Rail Jon Rogut]

Well, firstly have you deleted the DigiBase folders? Did that clear the error?

Rail

[j-man]

where is the thread w instructions on how to delete corupted digibase folders? If this is happening in more then one session would that mean that they are all corrupted, or are they having a problem navigating through external hardrives?

[j-man]

where is the thread w instructions on how to delete corupted digibase folders? If this is happening in more then one session would that mean that they are all corrupted, or are they having a problem navigating through external hardrives?