@mike_strong: GPU? Also, can you post a crash log? Step-by-step instructions here: http://community.avid.com/forums/p/138100/783793.aspx#783793 Don't need the whole thing. Just up to line 6 in the crashed thread portion.

@blueuw: ignore the App Nap stuff. Different person, different problem. Read my reply post above: http://community.avid.com/forums/p/138329/785233.aspx#785233 I think you found a memory leak. Post another crash log when it happens. Report the actions that led up to it.

Try this: http://community.avid.com/forums/t/135540.aspx MDV's what Media Tool should be. It'll show you what media's available for a project. Sift, copy, move, or delete whatever you want!

@Shannon Zawartka: first of all, congrats! Second: [quote user="Shannon Zawartka"]Isaquit0, I've heard others made mention of this before, and typically followed this practice, but I'm not sure why I'm doing it.[/quote] I've never had a successful H.264 export from MC. That was many moons ago. For all the reasons you mentioned

[quote user="JKL32"]I don't see "Prevent App Nap"... but as for as I can remember, I think I enabled that function systemwide a long time ago.... Maybe thats the reason why I am not seeing it?[/quote] (This is getting interesting.) According to this Apple Discussion thread, it was removed from Yosemite: https://discussions.apple

[quote user="JKL32"]Okey. Sorry. But under User Diagnostic Reports I don't see any Avid crash reports..[/quote] Ah! You have a different problem. Since it's a hang, try this: 1. Quit Media Composer. 2. In Finder, find the AvidMediaComposer app (/Macintosh HD/Applications/Avid Media Composer. 3. Click on it and do a Get Info ([Command

@JKL32: actually, this is from System Diagnostics Reports. Can you re-send one from User Diagnostic Reports ? Should end in ".crash".

Hey Everybody, A 2013 Mac Pro went bad on me last September. 3.5GHz processors with AMD D500 GPU's. I jumped through fiery hoops to get a repair. The repair became repairs (logic board, both GPU's, RAM, power supply). Six weeks later, I received a replacement. Apple recognizes it's a problem. If you have a Late 2013 Mac Pro, read this: http

In my case, it was clear something was wrong. Scrambled graphics rendering, displays cutting to black and back. After the repair, it's been solid! Mind you, this user's still on OS X 10.10.2 and MC 8.3.1.

@blueuw: OK, you have a couple interesting things going here. 1. The good news: this crash is exactly the same! Here are the interesting bits: [quote user="blueuw"] Crashed Thread: 0 Main Thread Dispatch queue: com.apple.main-thread Exception Type: EXC_BAD_ACCESS (SIGSEGV) Exception Codes: EXC_I386_GPFLT Thread 0 Crashed:: Main Thread Dispatch