Did you ever get an answer for this? I am curious about the same thing...

If you are referring to MC 3.5 then yes that supports 10.5.6 otherwise any flavor of version 3 before 3.5 requires 10.5.5. Make sense? In short versions: 3.0.5-3.1.3 are only supported on OS 10.5.5 and below. HTH Gardiner

I know I just saw that. I am trying to avoid doing the 2 partition thing (2nd partition for FCP with an up to date OS). Things run fine for both right now so maybe I can hold off for awhile longer.

[quote user="Kevin Klimek"] Who is this upgrade for? This version is for customers already using Avid Media Composer v3.0.x, v3.1.x, Avid NewsCutter v7.0.x, v7.1.x and Avid Symphony v3.0.x and v3.1.x. A dongle update is NOT required. Customers who have upgraded to Avid Media Composer v3.5.x, Avid NewsCutter v7.5.x and Avid Symphony v3.5.x

Long shot, but is the older AVID DV411 QT component (codec) installed? In the past when using an AVID codec QT file on a computer that does not have that particular codec you would get white or black on playback. Not sure this is the case, but it did come to mind...

Great, I figured that was the case, but wanted to have my facts straight before pressing that dongle update button. Appreciate the quick response. Quick side note, is there upgrade pricing from Mojo and/or Adrenaline to the new Mojo DX box posted anywhere or should I just ask my reseller? I thought I read somewhere that it would be in the $7,500 range

I am curious as to whether I can still run MC 2.8 if I update my dongle for use with MC3. I currently have one machine that I want to keep running Tiger for a bit longer so I am concerned I will lose the ability to run Media Composer on that machine if the updated dongle doesn't allow for older versions of the software to run. From what I read I

For those of you still coming across this error, I found another method that solved my problem (I believe Todd mentioned this in the beginning of another thread). I somehow had 44.1 and 48 Khz clips in the same timeline which was causing the export to choke and fail. So before going through several partial exports to find the "bad" media, try this:

Well instead of circling around the same problems in 2.7.2 I decided to give 2.7.5 a shot. Loaded it and logged in using a test user account and everything worked so I imported my settings then logged back into my regular account and I seem to be back on my way. Confused as to what happened in the first place and a lot of head scratching has left a

BLKDOG, I apologize if I am confusing my threads, but I am responding to the thread that refers to getting the "Exception: Invalid argument, filename: ave" error am I not? Let me clarify that I received this only after I got the ???? in my settings then tried to replace them with my backup Avid user settings. So it did start out as a settings issue