[Doug Metz]

The Libraries that you’ve opened with the new version have been converted, so even if you had a copy of the old version in backup somewhere, I don’t think you’d be able to use them. Admittedly, I haven’t tried.

Maybe we can help resolve the other issues so you don’t have to revert…

I haven’t experienced the locking up issue, so I’ll come back to that. I’ve imported plenty of Animation codec stuff from AE – In my case, when alpha wasn’t recognized it was one of two things: artist didn’t specify Millions+ (accidentally a few times) on export, or I needed to change the alpha handling for the clip in the inspector. Ideally, change this setting on the master clip in the browser so you don’t have to change it all over the timeline after the fact.

I did experience a few oddities immediately following the update, but after I trashed preferences and restarted the machine, things settled down substantially.

Doug Metz

Anode

[Doug Metz]

[Neil Gowan] “•Apple’s Magic Mouse obviously solves 360º scrolling but does not match responsiveness/speed of wired Mighty Mouse.”

Not true. Quite responsive, plus you get gestures (or not, it’s up to you)! The only thing I’m not crazy about is changing batteries. When my original Magic Mouses die (x4), I’ll replace them with the Magic Mouse 2 – but I won’t be crazy about plugging them in… ;^)

Doug Metz

Anode

[Doug Metz]

Hey Jerry,

Keep pushing, you’re well on your way!

I have a slightly different approach, due to the nature of the jobs we get. At the Finder level, I create a job folder for each job, where I keep sub-folders for Music, VO, GFX, etc. related to the specific job, and import my media from these folders. I have FCPX set to Leave Files in Place, so I can always find what I’m looking for.

In some instances, for jobs with a multi-day multicam shoot schedule, I’ll create a new Library for the job itself. For the smaller stuff, I create a single Library at the root of the drive where I create an Event for each of those jobs on the same drive.

I would highly recommend *not* diving into the Library package itself, since it is a database and could create problems down the road.

Doug Metz

Anode

[Doug Metz]

It depends on what kinds of things you’re doing in AE… yes, PPr to AE round-tripping is nice, but you can build your own plugins for FCPX in Motion – titles, effects, transitions, and generators.

Really groovy stuff that could maybe prevent the round trip in the first place.

Doug Metz

Anode

[Doug Metz]

[Dan Bowman] “Looks like I’ll have to transcode. Trouble is, with EditReady the file sizes grow five-fold. Not sure what settings I need in order to closely match the quality and files size of the camera originals.”

It sounds like you’re taking camera source H.264 encoded files, and transcoding with EditReady to ProRes… I don’t have EditReady – is there an option to simply re-wrap instead of transcode? That’ll be as original as you can get.

Doug Metz

Anode

[Doug Metz]

First thing I notice is that you don’t appear to have the entire card structure. I only have older P2 archives, but (and this is a big but) – for FCPX to import this media properly, you need the entire card structure. It looks like you’ve renamed the ‘CONTENTS’ folder, and removed the ‘LASTCLIP.TXT’ file:

*EDIT* It’s difficult to tell in the above screen shot, but the text file is not in the CONTENTS folder, but instead is loose inside the ‘card2’ folder.

It is fairly simple to re-create the LASTCLIP.TXT file, so let us know if it’s missing.

If the text file is actually present in the Finder, then simply renaming the enclosing folder to ‘CONTENTS’ (and putting that with the text file in yet another, descriptive folder, like ‘MalmoP2’) should result in the desired outcome. ;^)

Doug Metz

Anode

[Doug Metz]

Could you post a screen shot of the Import window?

Doug Metz

Anode

[Doug Metz]

[Jeremy Garchow] “I have 3rd party plugins. If I toggle the codec from “source” to anything else and back to “source” the little warning goes away. “

This works for me as well. I’ve been doing a little digging and found that changing the default codec in preferences, restarting FCPX, and changing it back to ProRes 422, I still see the warning triangle but can now ignore it – exports a perfectly compliant file without having to toggle the codec on every export.

Console shows that FCPX kicks the same error on every try:
Apr 18 16:20:33 DMpro Final Cut Pro[532]: assertion failed: 16E195: libxpc.dylib + 74307 [ABC45890-DA23-3A4A-B50B-1384BD4CBBDF]: 0x89

Doug Metz

Anode

[Doug Metz]

Are you on Sierra?

I’m running 10.12.4 / 10.3.3 – had a weird audio issue initially, but trashed prefs and that fixed it. FWIW, all of those plugins are working fine for me.

Doug Metz

Anode

[Doug Metz]

[Lars Hogeus] “The driver did not help me…”

What version of MacOS / FCPX are you running?

Doug Metz

Anode