New Pro tools error im getting in 7.4

[Jake 2.0]

I attached a pic of the error message its not oe of the usual ones i've seen can anyone tell me what this is all about?

if you dont wanna download the pic the error says

"assertion in /"volumes/devolpment/vb_joplin/alturaports/newfilelibs/corefondation/macbuild/../../sys/macos/sys_fileutilsmacos.cpp", line 481 while deleting "palm GTR_02.wav"

the only thing i understand is it may have something to do with deleting regions but everything else is gibberish to me

Thanks guys!

[Tony Shepperd]

Have you upgraded to 7.4 cs1?

[Jake 2.0]

Nope i haven't i wasn't aware Digi came out with an update already for 7.4 i just got it a week or two ago. thanks i iwll try that and see if that heps

[elambo]

Restart the computer. I've seen those in the past and a restart fixed it.

[Jake 2.0]

I tried a bunch of things and that was one of them, im gonna install the update tonight and that will hopefully help! thanks

[elambo]

Let us know...

[Tony Shepperd]

Make sure to get rid of your old preferences.
I have been using this utility which is fantastic.

ProTools Prefs & Database Helper

[Jake 2.0]

Thanks tony i've been using the utility in th past and recently its fantastic! the fix for this was was just a lil bug in 7.4 the update cleared it up and all is well know. Thanks y'all

[galaga]

The cs1 update only addresses some control surface issues.

[Jake 2.0]

So i heard...but i stopped getting that popup so maybe that was a prefences trashing fix.

[Tony Shepperd]

Originally Posted by galaga

The cs1 update only addresses some control surface issues.

Who said those fixes are the ONLY fixes?
Don't kid yourself, those announcements are for the known bugs.
There are always little fixes that Digidesign does in the background and never announces.

[Jake 2.0]

Tony has a valid point. Im sure digi isnt proud of little bugs so better left unsaid sometimes

[IIIG]

Jake,

The assertion error may happen again in the future; it creeps up from time to time. If so, erase the 'Digidesign Database' folder on each of your connected drives. That has always worked for me and consider it the fix for that error.

D®...

[Jake 2.0]

I've done that a bunch of times but i guess its one of those things that keeps coming back thanks