I just upgraded to Media Composer 3.5.4 and am now experiencing a problem opening the startup project from the "Select Project" window. 

Upon launching Avid the "Select Project" window opens and shows Avid Boston Project DV25 in the Shared area.  After selecting it and clicking OK a window pops up reading, "This volume has not yet been mounted by the application. You can either mount all volumes or load another project."  I click on the button labeled "Mount All Volumes" and it returns me to the Select Project window, and subsequent attempts to load the project fail.  

If I open the Boston startup project from the Finder it opens without issue.  

I am able to create new projects and open them from the Select Project window.

This installation is for our school lab, and I'd really like the students to be able to open the startup project from the Select Project window.

Troubleshooting steps taken:

I have uninstalled and reinstalled Avid and deleted the Startup project and Mediafiles folder and reinstalled.

Thanks in advance for any suggestions or solutions you may be able to offer.

--

Dual 3GHz Mac Pro, 10.5.7, Quicktime 7.6

I also recently had this problem on MC 3.5.4 / OS 10.5.7 / QT 7.6, project and media on local storage on a system connected to a Unity.

In my case I had a drive containing corrupt media.  I shut down the project, took the drive offline and then was unable to open the project.  I could not then, on any system (even on an 3.1.2 in another edit suite) open the project....

My solution (I was on a deadline) was to open just the bin in a fresh project.  All the bins open without any problem.

My conclusion is that 3.5.4 corrupts the project in certain circumstances giving rise to this error (that I had never seen before, even when I had drive/media troubles).   If this is a bug then is it is a serious one.

AMA was turned on, I turned it off later (I think I just turned it off before the error but I'm not sure).

It is also odd that with AMA turned on you can no longer unmount fixed drives - a feature that was very useful when you purposefully wish to bring a drive offline (which contains low-res media for example) - no idea why this was disabled.

Janusz

Thanks for your reply.  I'm also on a deadline, and though I am able to open the bins in a new project, I'd rather have the startup project as it comes from Avid, so I'm going back to 3.5.1.  Fortunately I have an earlier version of this image (I'm preparing a disk image for distribution to all the computers in our lab) with 10.5.6, etc.  

In any case, if it's a bug it's perplexing, if it's specific to this installation it's equally perplexing to me but of less concern to anyone else reading this.  Is anyone with some spare time able to test opening the startup project via the Select Project window? The startup project installer is in the Media Composer section of the Avid download center.

Scondon - Were you successful in going back to 3.5.1?  If so, I will do the same.

Thanks,

marluc

My solution has been to downgrade to the previous 3.5.1 release, and now all is fine.  Clearly this is a bug that is unexplained, and we hope it is fixed by the next release!

marluc

Yes, downgrading to 3.5.1 worked for me.  The students won't be using the very latest version, but it's more important that they're able to use the startup project.

So is this an officially recognized bug? When will it be addressed? A have a few dozen systems to setup and need to know ASAP!

"Officially" recognized by me!  Ask Marianna.

marluc

We are experiencing the same problem with 3.5.4. It will randomly (as far as we can tell) a project file so that it can't be opened via the project selection window at startup. This has happened on three systems that were just upgraded, all with different projects going on. It does not matter if it is P2 media, tape-based, standard definition, or high definition... it still corrupts the project file.

Strangely, the PC version of Avid 3.5.4 that we have has not yet done this. Did Avid just smooth out the PC version and then recompile for Mac without really testing it thoroughly?

Avid... this is one that needs to be addressed soon!

I just wish that someone @ Avid would at least acknowledge the problem and give some sense of when it would be addresed. Dozens of systems to update; I need to inform people what version it will be within a couple of weeks.

I have escalated this issue. Stay tuned...

THE SOLUTION!!!! (Thanks to one of the London support guys!)

Delete the MC STATE file in the application folder of AVID Media Composer/Settings.

Then create a new user profile!

They told me, that some user-settings of previous versions are corrupt for 3.5.4

Everythings works perfect now, even the FullScreenPlayback-function!!!

Daniel Hantschel

CEO episode eleven productions GmbH

www.episode-eleven.com

Hi,

I just wanted to add that this solution didn't work for me. I don't think it's the user settings as other projects are fine; it's only when certain projects were imported and opened that I got the error.

I just created a new project in MC 3.5.4 (same settings as original) and copied all the old folders and bins into the new project. This worked for me and I didn't need to create a new user profile or jump back a software version.

Hope that helps.

Ditto,  didn't work for me either.  After having reinstalled the previous version, I decided to try oldskookjunkie's method, and this does work. I am now running MC 3.5.4 with my old problem project now loaded into a "new" project, and all seems to be fine.  Since it was only this one project that caused the error message, it was simple to fix this way.  Marluc