[Jeff Feaz]

So here’s some new information:

Converting the file to WAV (with AME) did nothing for me, but changing the file name (of the original MP3) and re-linking fixed it with no system or app restart necessary. Weird, but hopefully you’ll have the same luck.

[Jeff Feaz]

In case anyone is reading this thread 10 years later, I am using CC 2018 and having this exact issue. So doesn’t look like the update did the trick.

[Jeff Feaz]

Sounds like Robin and Tony use the same strategy (compounding). Makes sense. Tony, yeah, the nice thing about the built-in transitions is that they let you avoid keyframing. I do understand that manually animating the transition would be another way around this issue.

Bill – good point about the gray bar. I remember learning about that in a YouTube video. Also good to know that we’re talking about “a” secondary storyline, not “the” secondary storyline. It’s a nice way to avoid having to compound to affect subsequences as a single unit like you would have to do in Premiere (nesting). Too bad it doesn’t protect the primary storyline from transitions though.

Summary: if you’re having the exact same problem as me, use a slide transition instead. But lots of good info in this thread about the workings of X, especially if you’re used to track-based NLEs.

Thanks everyone!

Jeff

[Jeff Feaz]

Thanks!

In my case, I used John’s suggestion above and changed it to a slide transition, which met my needs.

The connected clip indeed was already converted to a secondary storyline like you said, but that didn’t resolve the issue of the push transition also affecting the primary storyline. I guess it’s a question for another day.

Thanks everyone for your help!

[Jeff Feaz]

Very helpful responses – thank you.

Any idea why the “Create Storyline” option is grayed out?

[Jeff Feaz]

Thanks Jeff, good idea on the feedback.

[Jeff Feaz]

I ended up calling Apple earlier and they gave me the same answer as Jeff just did here – thanks Jeff!

The source of my confusion was the fact that in the export dialog, one of the codec choices is “Source – Apple ProRes 422”, which made me think that ProRes 422 was the most original media I could work with.

The Apple rep told me to pretend it doesn’t say “Source” there, which works. But I think now I understand that “Source” is referring to what’s being used in the viewer, rather than the original media source for the export. If you switch the viewer to Proxy, the “Source” codec option will change to 422 Proxy.

He also assured me that unless you choose to make optimized or proxy media, you are editing natively. That’s cool. I didn’t know FCP could do that nowadays.

[Jeff Feaz]

Andy, many thanks!

[Jeff Feaz]

I noticed that even after opening the import dialogue and seeing all the missing media clips come back to life, the camera import still doesn’t complete, resulting in the inability to export.

I solved this by going to File>Import>Reimport from Camera/Archive, but just as with the first import, there’s no progress indicator or any way to know when the import is done. Nor is there any warning when closing the app that this will interrupt an import that won’t resume automatically.

Is anyone aware of any way to actually track the progress of the camera import and get confirmation that it’s done?

[Jeff Feaz]

Andy, this worked for me and also helped me understand FCPX better. Thank you very much!