Since you indicate that you have already deleted and rebuilt the database files without results (very unsual in this case), that leads me to believe the sequence file itself is corrupted. Try creating a fresh, new sequence and then edit this sequence end to end into the new one. DO NOT just duplicate the sequence as that will only duplicate the problem.
Also, can you play the sequence at all? In other words, can you play it up to a certain point or region and then it freezes? If so, you have a corrupted clip somewhere in the timeline.
To answer your other question, there never seems to be any explainable reason as to why files become corrupted...at least none that I've ever heard.
Larry Rubin
Senior Editor
The Pentagon Channel
www.pentagonchannel.mil
In agreement, Unity. In Disagreement, Discussion. In all things, Charity.
Found a fix for this (for me anyway) on a Mac. I had the same problem "Exception: Unsupported Resolution". Tried all the things the forums suggested, including a complete re-install of the MC software... STILL had the problem. Eventually distilled it down to this: apparently the Avid did not think that's it "internally generated" media files were supported. By "interally generated" I mean, basically, Avid internal BLACK signal media, etc. Turns out the Avid software ships with an "Avid Media Files" folder in the Application folder than contains media and media databases. Trash those 2 databases (just like you would on any regular media directory) and, upon relaunch, Avid rebuilds them and... poof... no more "Exception: Unsupported Resolution". Here is the directory path to delete the database files:
/Applications/Avid Media Composer/SupportingFiles/Avid_MediaFiles/ ---> delete "msmMMOB.mdb" and "msmFMID.pmr"
Good luck and Godspeed.
This is probably late for the original author of this thread but here's what I did to fix this rather annoying error.
I crashed during an import so when I booted backup I got this error and we tried deleting the MSM files and restarting and all of that good stuff. None of it works. However I noticed as I went through my cuts, a very early cut was able to playback. So I went back to my corrupt cut and I did notice two things were offline (even though the whole cut doesn't play any video at all). So I noticed a title that I had collapsed into a scene had gone offline and when I removed the title (after getting two more "exception: unsupported resolution") everything came back online. Apparently one corrupt title can handicap an entire sequence.
Anyway, that's my two cents.
We experienced exactly the same problem on Windows XP + Avid Mediacomposer 3.5.The system would not load its own filler (!) into the player window - "exception: unsupported resolution"Deleting the "normal" media databases did not help.Your solution worked as a charm. Had to search for this "hidden" media directory with its supporting media files on the C:\ drive, but found it and deleted its media databases.
Result: everyhting works again!
Had the "Exception: Unsupported Resolution" error on a PC running MC 3.1.3. Clips played fine, but always had the error when trying to play a sequence unless it was a new sequence containing only 1 clip. Problem was the media database files on the C drive that index things like filler. To find the files I used the Windows Search going to "more advance functions" and turning on the checkbox for "search hidden files and folders" and searching for "msmMMOB". Once found, I deleted the msmMMOB file and the msmFMID files. Relaunched Media Composer, watched the databases scan and rebuild on the C drive and verything worked!
Mark:Avid STRONGLY RECOMMENDS that media files never be written to the system C: drive, but to another separate drive, either internal, external or a RAID array. The C: drive has enough work to do just running and managing a very complex and demanding application, let alone be additionally tasked with storing, retrieving, cueing and seamless playback in real time of media stream fragments. You will very quickly overtask your system drive.
Yes I know!!!
These are media files Avid puts there for stuff like filler. I'm actually using a Unity for media storage on our 3 systems. I never put media to my system drives!!! DUH!!
MarcRose: Had the "Exception: Unsupported Resolution" error on a PC running MC 3.1.3. Clips played fine, but always had the error when trying to play a sequence unless it was a new sequence containing only 1 clip. Problem was the media database files on the C drive that index things like filler. To find the files I used the Windows Search going to "more advance functions" and turning on the checkbox for "search hidden files and folders" and searching for "msmMMOB". Once found, I deleted the msmMMOB file and the msmFMID files. Relaunched Media Composer, watched the databases scan and rebuild on the C drive and verything worked!
I made the comment I did because NOWHERE in this post do you indicate that you are writing files to anything but your C: drive. No need to get rude.
Sorry Larry I had no intention to come off as rude. It did seem as though you thought (or jumped to the conclusion) I was ignorant enough to write my media to a system drive. If you had read my post more clearly..."Problem was the media database files on the C drive that index things like filler." perhaps you would not have felt it necessary to hit me over the head with the "Avid recommends...".
To be clear, the media and databases on the C drive are put there by Avid and contain various resolutions of Black (filler if you like) as well as other media for Offline and Format messages. on my system they're located at:
C:\Program Files\Avid\Avid Media Composer\Avid_MediaFiles
me too
=> It is not me who put these files on my system drive : it is avid during the installation of the Media Composer 5 suite !!
From now I get these errors
1. Segment too small, without any consolidate process done (I put In/Out to play in In/Out range and find the file and reedit it)2. MSN : no directory specified3. exeption : unsupported resolution
... does the v5.0 I bought could be a pre alpha version ?
Regards.
SteF
Thank you lymetyme, your solution worked for me on my PC!
Media Composer v4.0.5 again on a PC.
It took a lot of searching to find this solution.
-Lash
THANK YOU!
Started get the error this morning for no reason. Searched and evetually found this. Life-saver.
Avid should put this on the KB.
Ra-ey
Media Composer 6 Certified User
Media Composer 6 Certified Professional
ra-eysaleh.com
LinkedIn
Showreel
I also just had this problem, and by trashing the media databases in avid application folder, this worked for me.
cheers
Bruce
© Copyright 2011 Avid Technology, Inc. Terms of Use | Privacy Policy | Site Map | Find a Reseller