Can anyone shed any light on the following error message?[\Monk\main\common\PremiereShell\Src\PlayerFactory.cpp-379]I'm half way through a project; all was well when I shut down yesterday, but today the project won't open. The error message offers me a "continue" option, but doing so only opens a "working" dialogue which sits at 0% and does nothing. Audition is otherwise happy, all other projects opening fine, just not the one I need!

Thanks for responding Eric. Yeah, meanwhile I found another long thread from which I learn that it's in fact not an uncommon problem, but always a fatal one.The only work-around apperars to be saving double, even treble, versions of sessions under different names.

Would it be possible to e-mail one or both of the corrupt session files to audbugs@adobe.com so we can take a look at them? There were some cases in 3.0 where this might happen, but those issues were addressed in the 3.01 update. Did this occur on the same machine or were they both using different systems?

Hey Durin - Just to follow up, the 3.0.1 patch was indeed not installing via Group Policy, even though it showed up on Add/Remove programs, and got as far as updating the Audition splash screen. Go figure.

Anyway, we're reinstalling the patch the old-fashioned way. Sounds like maybe this will do it.

"so If I save a back up of my project under the same name...and then the original gets corrupted...then the backup will ALSO not work unless it's been labeled under a different name??"

Well if someone saves a backup under the same name in the same location then clearly it is actually overwritting the original and yes as they are now the same session then if one is corrupt the 'backup' is corrupt.

Clearly this isn't a backup.

But in your situation you are making a backup to a different drive/etc so if the original session file (.ses) gets corrupted no your backup will not be corrupted.

You can also use this utility http://www.mediasweeper.com.au/ to examine your session files and see the exact path of the files referenced within your session file.

But note that if you make a copy of your session & media (ie the whole folder - lets say on H: drive) and put it on another drive (say E:) if you open the session on the E: drive then (as MediaSweeper will show you) AA will open the session on E: and reference the files on the H: drive but if those files are no longer on the H: drive (ie the original location) then AA will look in the current folder that the session is in.

Its handy to know that otherwise you may think you are working on a backup but you are actually working on the original.

yea shure sounds great; but that could end up screwing you...if you were to have a corrupt session and save that across your couple backups then their all bad now, because you saved early and often...if you only saved "early" but not often then maybe you wouldn't end up saving the corrupt session but you might not have all the files from that session in your backup, but somethings better then nothing.

The session should tell you it's corrupted before you save it, people going around saving corrupted session unknowingly that's dangerous.

and what you described is downright ridiculous, if I open the session on drive E: I want it to reference and save files to that folder.

Are you sure this is true? What I do is make a folder for each project which contains both the session file and the wav files.

In this case when the session and sound files are contained in their own folder does it still reference the original?

What I change the name you know like if the original session was called "experimental" and I renamed the backup "experimental#2" would the back up still reference the original?