My Windows XP-SP3-based Media Composer v3.5.4 software (with
first-generation MOJO) has begun acting quite irritable. I'm getting
frequent & spontaneous "Exception: Unsupported Resolution" messages.
The error message will sometimes appear randomly when the play head is
parked and no action is being taken. The behavior is present regardless
of whether a sequence contains mixed (OMF/MXF) formats or only one.
I've observed this behavior in MXF & OMF based projects, specifically at
the following settings.
60i / 29.97 (OMF)
720p / 59.94 (MXF)
Here are the steps I've taken thus far to troubleshoot:
I researched the following article "Exception Unsupported
Resolution[262861]" at the Avid Knowledge Base using the following link:
http://avid.custkb.com/avid/app/selfservice/search.jsp?DocId=262861&Hili\
te=Exception%3A+Unsupported+Resolution
The article suggests deleting the databases at the following directory:
C:\Documents and Settings\All Users\Shared Documents\Avid
MediaComposer\Avid MediaFiles
That directory did not exist at that location. I went ahead and deleted
all other database files from their respective locations, then created
an empty " Avid MediaFiles" directory at:
C:\Documents and Settings\All Users\Shared Documents\Avid MediaComposer
I then shut the entire system down and power-cycled the MOJO's. I
rebooted & relaunched without MOJO attached to the firewire port, then
emptied the Recycle Bin and launched Media Composer.
According to the progress indicator, databases appeared to have been
rebuilt on the C:\ (Boot/OS/Application) , D:\ (Onboard SCSI RAID) and
H:\ (External USB 2.0) drives. Except for the test patterns in the
Supporting Files folder and the sample Avid project ("Avid Boston
Project DV25"), I have no other media on this drive. The Avid sample
project was automatically installed to the C:\ drive, and has not yet
been consolidated to another media drive.
Upon project/user selection & load, I'm greeted with the "Exception:
Unsupported Resolution" message. The current project is 720p/59.94, and
has a sequence with three video layers in it:
V1 = SMPTE BARS
V2 = Marquee Title (Black Rectangle)
V3 = Marquee Title (White Rectangle; smaller, placed over Black
Rectangle)
The SMPTE BARS are continuous, and the black & white rectangles are
staggered. I can click through the error message and render the
sequence. The message appears again after render, yet I can click
trough and play normally. I quit Media Composer, reattach MOJO to the
firewire port, relaunch Media Composer and observe the same behavior (no
external video, of course).
When I open the "Avid Boston Project DV25" project and load the "Boston
Sequence" from the "Boston Seq DV25" bin, I get the error message
regardless of playhead position.
Also of note, cycling through the Video Quality Setting at the bottom of
the timeline window brings up the message every time. No resolutions
have been disabled manually. Additionally, no databese files appear to
have been created at:
C:\Documents and Settings\All Users\Shared Documents\Avid
MediaComposer\Avid MediaFiles
Aside from the ability to see my titles in the source monitor, my major
annoyance is the continual "Exception: Unsupported Resolution" message.
Any ideas on what's going on here?
Thanks.
--Jesstator--
[Non-text portions of this message have been removed]
------------------------------------
Search the offical complete Avid-L archives at: http://archives.bengrosser.com/avid/
Everything you MUST know about Color Correction in one book: http://tinyurl.com/ColorCorectionforvideo Get your copy todayYahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/Avid-L2/
<*> Your email settings:
Individual Email | Traditional
<*> To change settings online go to:
http://groups.yahoo.com/group/Avid-L2/join
(Yahoo! ID required)
<*> To change settings via email:
Avid-L2-digest@yahoogroups.com
Avid-L2-fullfeatured@yahoogroups.com
<*> To unsubscribe from this group, send an email to:
Avid-L2-unsubscribe@yahoogroups.com
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
No comments:
Post a Comment