David Eaks
Forum Replies Created
-
It shows which clip is “active”, so when you go to make adjustments in the inspector you know which clip is going to be affected, without having to actually select the clip.
-
Thanks Craig,
I also had Matrox MXO2 utilities from before Mavericks and after the first crash, that was the first thing I did. Removing it stopped the crashing, leaving me at the blank Compressor without any UI.
I’ll trash those files.
Looking forward to info about the new hardware h.264 encoding and comparing it to Matrox MAX.
-
Having trouble here too. Same thing, either crash while opening or just the Compressor file bar with no window.
Logging in as a guest user gets around the problem.
Being the testing partition on my secondary system, I’m not all that surprised. Will do a clean OS install tonight and report back with results.
-
Nope, I’m hoping for a surprise Motion X release as well.
-
Just got a call, still on the phone. Tomorrow, confirmed Mac Pro release.
Edit:
In case you missed all the other posts. -
Or a drop shadow like in the Dramatic title in FCPX?
-
Or option 3, Apple allows Registered Developers to install pre-release Beta versions.
Then I can play with the buggy new version on a secondary system in advance as well as be prepared for the new features when it is released.
Except that after the first beta version, all future beta releases would become “normal” timing and we would once again be anxiously waiting, only now for the new beta version.
Other than that, I’d definitely prefer a timely release. Even if it is buggy, it won’t make it onto my main system until my workflow is tested. I’ve learned that lesson the hard way, when I got myself into an awful dual-boot split-workflow scenario, stuck waiting for driver updates.
-
And this- why-final-cut-pro-x-works-and-an-introduction-to-fcpworks-by-sam-mestman
With this quoted from the last paragraph- “Now, that’s a lot of talk. Talk is cheap, and as editors, we believe in showing rather than telling. So, if you want to see a new version of Final Cut Pro X in action running on a new Mac Pro playing back 6K RED Dragon footage on a 4K projector via AJA hardware; cutting an absurd number of streams of multicam 4K footage natively in realtime; moving in and out of DaVinci Resolve seamlessly in a high end Quantum SAN environment (as well as some other things we haven’t released yet)— you’ll want to come to the FCPWORKS launch event on Saturday, January 25th at Unici Casa in Los Angeles.”
Interesting
-
Something to read in the meantime- Should you buy the new Mac Pro or an iMac?
-
If I had purchased Digital Rebellions Pro Maintenance Tools, used Corrupt Clip Finder/Crash Analyzer/Media Salvage and had good results, I would recommend it. But I haven’t, so I can’t.
Bet it’s a good buy though.
Is there anything that might be suspect around the halfway point (or right at the end, I notice most of my exports actually finish at 50%). If so, turn off or disable that effect/clip/image and try to export again. If there isn’t any specific plugin or effect etc. you think could be a potential problem, Bill’s process of elimination is a good method. I’d probably start with a test export of about 1/3 of the timeline, centered on where you think the problem might be and repeat. Trading likelihood of correctly guessing the problem portion, for faster test exports and more accuracy when found.
You could also try logging in as a new user and try to export, or deleting all render files, trash prefs and repair permissions.
Don’t forget to report back here with the cause, once you find it.