-
Avid MC3 crashes when setting custom export
Hello, everyone. I’m new to this website so forgive me if I forget to mention something relevant. I’m working on an HP nw9440 Notebook with nVidia Quadro 1500, and recently upgraded to MC 3.0 from Xpress Pro 5.7.
Today I attempted to do a custom QT export setting (from a job I initially edited on Xpress Pro) and Avid immediately seized up and crashed when I tried to adjust the video compression settings. I saw a post on a similar issue on this website but could not find any answers to it.
I thought it might be a version issue with Sorenson software, and tried updating my Sorenson Squeeze to 5.0, but that did not fix the problem. Could it be another dreaded Quicktime software conflict? I recently had to roll back my QT version (based on advice on this site!) to fix an audio import problem.
Does anyone know what might be causing Avid to crash upon trying to adjust export settings?
-
7 Replies
-
What version of Quicktime are you using? Also, did you create new user settings when you upgraded from Xpress Pro to Media Composer?
Michael
-
Thanks for the reply, Michael. Quicktime is 7.3.1. I had to roll back to this version because of an audio import bug where audio-only files would import in without sound.
I did create a new user. Should I perhaps create another one, as well as delete the old project settings in my current project (which dates back to Xpress Pro)?
Jim Spione
-
Hi, again. Just to follow up, I tried creating a new user and new project settings, to no avail. Any other ideas???
Jim Spione
-
MC 3.0 needs QT 7.4.5. Why did you roll back so far?
Jon
“Jamming our heads full of figures and angles
And telling us stuff that we already know”Willie The Wandering Gypsy & Me
Billy Joe Shaver -
I’m pretty sure the solution is this:
In your Quicktime player settings, make sure to uncheck DirectX and choose GDI-only. It’s a known issue that this setting can cause issues with QT exports on v3 and later. I had it myself, and this fixed it for me.As said, you probably rolled back too far on your QT version, though. Check the version matrix to make sure.
https://avidtechnology.custhelp.com/cgi-bin/avidtechnology.cfg/php/enduser/std_adp.php?p_faqid=75147&p_created=1202760115&p_sid=pqo_72sj&p_accessibility=0&p_redirect=&p_lva=&p_sp=cF9zcmNoPTEmcF9zb3J0X2J5PSZwX2dyaWRzb3J0PSZwX3Jvd19jbnQ9NTIsNTImcF9wcm9kcz0yNzYmcF9jYXRzPTAmcF9wdj0xLjI3NiZwX2N2PSZwX3BhZ2U9MSZwX3NlYXJjaF90ZXh0PW1hdHJpeA**&p_li=&p_topview=1 -
Tinyurl of the version matrix:
https://tinyurl.com/7hakjp -
Thank you! The Direct-X setting was the problem and that fixed it right away.
As far as the Quicktime version, I’ll double check, but I think I needed to roll back that far to allow audio importing.
One does wish Quicktime would stop messing with their codec!
Jim Spione
Reply to this Discussion! Login or Sign Up