Compatibility FCPX on Mavericks & Other Apps

After popping onto the Blackmagic Forums today, I found out that Desktop Video 9.9.2 fixed audio/stability issues people like myself had been having with BM I/O hardware.

All seems to be hunky dory now.

dgwvideo wrote: one irritating bug is that if capturing SD video with erratic timecode, poor control track, etc., FCPX will abort capture,

All you need is an old time base corrector off of Ebay.

I am new here. I hope I have not made a mistake in putting download before the horse, but Maverick has make me go Hmmmmm. First there was an issue starting After Effects and Adobe had the patch. When exporting a Master, it defaults to an mp3 vs a mov. Not sure what gives, but if anyone has any thoughts, I would to hear what you have to say.

Good news. I've solved the issue with FCP 7 and Mavericks. I had some issues and and disk repair and trashed permissions (a few times) and voila. It all works now with Log and Transfer. So to answer a lot of questions on this forum, Mavericks and Final Cut Pro 7 play nice. Yes, I know it's an old version of FCP. But I have yet to update and I was in the middle of a project. I was having issues with L&T and it would crash after trying to open it.

All solved. And if you're wondering if you can upgrade to Mavericks and run FCP 7, you can. I'm doing it without any other issues.

Thanks for the feedback, everyone.

Smartsound does work with MAVERICK. You just need a free patch from Smartsound.

I've looked around the forum and through this thread, but I can't seem to find any discussion about multiple monitor "annoyances". I'm not sure it's really an issue, but I have two monitors and when I have it setup where each monitor has its own space, FCPX doesn't ever put my event window in the second display, it keeps it in the main display behind the main FCPX window. In order for me to get it to the second monitor I have to do a bunch of crazy maneuvering with the window, but I eventually get it into place. Does anyone else have this issue? This is definitely not my idea of "better support for multiple displays". Even the dock showing up on both displays is pretty weak.

Julian wrote: I've looked around the forum and through this thread, but I can't seem to find any discussion about multiple monitor "annoyances". I'm not sure it's really an issue, but I have two monitors and when I have it setup where each monitor has its own space, FCPX doesn't ever put my event window in the second display, it keeps it in the main display behind the main FCPX window. In order for me to get it to the second monitor I have to do a bunch of crazy maneuvering with the window, but I eventually get it into place. Does anyone else have this issue? This is definitely not my idea of "better support for multiple displays". Even the dock showing up on both displays is pretty weak.

You can change this behavior in Mission Control by disabling "Displays have separate Spaces" option.

Thankfully, mine works just fine. I'm assuming that the settings migrated over as they were from 10.8, since I didn't have to go in to the settings to change anything, as was suggested.

Although I was reluctant to switch, using the upgrade method (not a clean install), has served me absolutely no problems yet. I've been on Mavericks since day 2 of the release.

FCPX (10.0.9) & Mavericks (on a 2011 MacBook Pro, Intel HD 3000):

The Good:
Memory management is slightly better (I imagine the improvement is OS side): the inactive memory is freed more rapidly.
Even the purge command (via terminal or memory management apps) is lightning fast with respect to previous OSs.

The Bad:
Always about memory: it's not good enough yet, because several plugins suck memory at each tweak. Even the effects/titles previews (by scrubbing on the effect/title itself in the right pane) suck memory as I scrub. So, there's a long road to walk, yet, and I'm sticking at Snow Leopard to have reliability.
It's sad but it's true: I couldn't complete slightly complex projects in Lion or Mountain Lion, so I've downgraded to Snow Leopard just for the sake of FCPX, and never looked back so far.

The Ugly:



Complete freeze and need to shutdown abruptly. Enough said, I think: I simply can't use FCPX on Mavericks, for now.

Also after Mavericks update Aperture also is not working as it should, hangs and crashes. Yup even after the Aperture updates.

Subject drift... the only Aperture Issue I've had with Mavericks is using the new, unimproved Nik plug-ins from Google. I re-loaded the old version from a backup and Aperture has been mostly bug free. The minor exception is that using the white balance picker in temperature and tint mode sometimes gives me a green tint of -50 or so. Adjusting the tint slider resolves that issue.

I've had no issues with FCPX on a Core i7 iMac that is less than a year old with LOTS of memory.

Aperture crashes during launch for me. It worked in Mavericks up until a couple of days ago. And now, useless. Ugh...

Aperture, FCPX all working fine on my end in 10.9.

I have repaired permissions a few times. Perhaps that might do the trick.

I've done everything, repair, reinstall, delete prefs, nothing seems to get Aperture to successfully launch.

That is a drag Ben. What machine are you on?

Did you try to create another user account?

I haven't seen any issues with Aperture so far. Works absolutely fine.
(2010 i7 MBP, 2012 i7 iMac - both fully loaded)

The only issue I had was that Fip4Mac showed up as non-compatible. However, I haven't checked for updates for quite a while, and it's a non-issue for as I have conditioned my clients to NOT deliver me any .wmv or expect .wmv as a final product... :evil:

Does "everything" include launching with cmd-option pressed and selecting rebuild database?

Boot Safe mode, then Open Aperture, then quit.
Restart normal...

Or, this may be helpful. (Scroll to bottom of page)
discussions.apple.com/message/22956761#22956761

Yes, tried all of that, doesn't work. I did find this, and PluginManager.framework simply doesn't exist. No clue what it is supposed to be for.

Dyld Error Message:
Library not loaded: /Library/Frameworks/PluginManager.framework/Versions/B/PluginManager
Referenced from: /Applications/Aperture.app/Contents/MacOS/Aperture
Reason: image not found

Now, if someone wrote an Aperture equivalent of FCS Remover...

I found the PluginManager.framework package inside of the system drive root, Developer > Examples > FxPlug directory. Seems when I just installed the XCode update the other day, it did something screwy.

But I copied it into the location Aperture was looking for it, and it works now. Aperture just acts like it is brand new, that's all.

Whew, that was scary!