Neo Assertion Error

[Reckless Erik]

Can anyone tell me what this is and how to avoid in the future. Has caused lengthy delay to my work flow.

Neo Assertion in “Volumes/Development/vb_joplin/AlturaPorts/SDKs/Neo61/Libraries/Macintosh/Environments/Alone/../../../../Source/CneolOBlock.cpp”, line 164

Thanks, Nick

[Reckless Erik]

By the way, trashing DBs and prefs "fixed" this but it would be good to know what is causing this. Tnx

[tclash]

I have never figured out what causes this, but ever since I've made the habit of trashing the DB folders every day when I start the computer (the free utility is in my startup items) it hasn't happened once.

[Reckless Erik]

Thanks tclash. Redoing my prefs every day is not something I would relish though. Digi, this also gave me 2 kernel panics (the black curtain variety) in the space of 10 mins so I would appreciate some input from tech support.

[DigiTechSupt]

There are many possibly causes - some likely candidates are data corruption due to read/write errors, dynamic state decorelleation (meaning the state of what is being read or written does not agree with the actual state) and possible bugs that reveal themselves only in certain circumstances.

You could ask the same question about why any application or it's preferences could become corrupt. It happens and sometimes there's no clear-cut reason for it, or there are too many possible variables to account for what could contribute to the problem.

Certainly, if you have a specific set of steps the reproduce the problem, we want to know about it so that it can be looked into and fixed.

[Reckless Erik]

Thank you for your reply. I will keep you posted, especially if this is something that repeats itself on a regular basis.

[Asp]

Well, I don't understand why Digidesign can't answer for this one?

I've experienced this problem with my HD rig too many times recording 5.1 soundtracks via 192 I/O. I use a dedicated internal Seagate Baracuda on my G5 2.7 Ghz/2.5Gb RAM machine only for Pro Tools sessions. I've installed an independent firewire controller for external drives. I've trashed database and volume files and run disc repair again and again, and still the problem returns.

I use Logic and Digital Performer as well on the same machine and they never crash on this issue. My answer to the problem is that the Pro Tools data handling system is inferior and simply not good enough. Could it be because Digidesign fails to rely on OSX's data handling system? You don't see the other applications use their own database system.

[Alécio Costa]

Every 15 days I have to trash all that stuff, repair permissions and so.
The Utility helps a lot but it is prety boring having to deal this in some situations where time is a concern.

[thin ice]

I think there are too many possible causes to be an easy fix. In my case in got constantly worse and it was diagnosed as a hardware repair by Apple. No problems since the repair and now fine on an Intel Mac.

[MorganPost]

Can anyone tell me what this is and how to avoid in the future. Has caused lengthy delay to my work flow.

Neo Assertion in “Volumes/Development/vb_joplin/AlturaPorts/SDKs/Neo61/Libraries/Macintosh/Environments/Alone/../../../../Source/CneolOBlock.cpp”, line 164

Thanks, Nick

We've just started getting this EXACT error in one of our mix suites. PT 7.4cs2, G5 Dual Processor w/192, Mix 888/24 & Control 24.