Forum Replies Created

Page 23 of 37
  • Ben Balser

    June 15, 2023 at 3:35 pm in reply to: Color Wheel Uon Saving

    Be sure background rendering is turned off (there’s never a reason to turn it on).

    How much drive space do you have free? What drive are you saving to?

    I’d turn off background rendering, delete all the render files for that Library, restart FCP holding Cmd-Opt do delete pref files. Then go to work, see if that helps. If it doesn’t, there’s a system limitation.

    FCPX only exports one file at a time, so the queue doesn’t slow anything down, it’s just a queue, it does zero work. But it does seem that FCP is eating up memory somewhere. I export in a similar fashion but I am exporting compound clips. I compound every musical performance separately, work on compounds, then throw them together in a final Project when they’re all locked down. That way I’m just exporting whole timelines, easy to keep track of, self contained, fast, easy. Just my personal preference. Not sure it would help with multiple exports. But I’m running on an iMac Pro, and I’m not having slow down issues. I don’t think I ever did, not this bad. I’d be looking at hardware bottleneck, or get a copy of FCP Library Manager and keep all your Libraries cleaned up and tidy, maybe? I dunno, I use it, I like it.

    https://www.arcticwhiteness.com/finalcutlibrarymanager/

  • That’s the way FCPX has always been. It rarely remembers (if ever) your last window layout. What a royal PITA to have to deal with this after 12 years of development.

    Shift-Z is your friend. It is “fit to window” at the macOS level, so it works everywhere, including inside FCPX. Use it in the timeline and browser and viewer. For what you’re doing, it’ll convert the long film strips into thumbnails right away.

  • Ben Balser

    June 15, 2023 at 1:03 pm in reply to: 24p / 23.98 sync problem?

    Normally there shouldn’t be a sync issue based on frame rate, as frame rate has nothing to do with audio. If both audio tracks are the same sample rate, they will sync. Standard video audio rate is 48kHz. Verify they’re both set to that. If one isn’t, Compressor can convert it just fine. So the big question is, what are the sample rates of both audio files? And FYI, that has to be the worst article on frame rates I’ve ever read.

  • Ben Balser

    May 29, 2023 at 9:25 pm in reply to: Missing Audio Filter

    Not a filter I’m familiar with, I’d just use an EQ or low or high shelf filter as needed. I’d suggest learning to use an EQ, it’s pretty easy, don’t be intimidated. But yes, there’s a few audio filters that have been changed or removed.

    https://support.apple.com/guide/logicpro/channel-eq-overview-lgcef1edce5b/mac

  • No really. If Corel can read an XML from Premiere Pro, you can export an XML from FCPX and use X2Pro to convert the XML to something they can read. But it’s also a $149 app.

    https://x2pro.net/

  • Ben Balser

    May 29, 2023 at 9:15 pm in reply to: Voice Over Enhancement plugin is change

    I’d say everyone head over to the FCPX feedback page and let Apple know they screwed you.

    https://www.apple.com/feedback/finalcutpro/

  • “RenderFrameAt returned: 4 for absolute frame 88928”

    This indicates that in your timeline on frame 88928 there’s an issue. Many times this is due to a corrupt render file. No problem, delete them, FCP will create a new one on its own. But if it’s a corrupt frame in the original media (very rare) then we have a major problem.

    In FCPX Settings > General > Time Display, set it to Frames, then find that frame in your timeline. Does it playback OK? My guess is it will. But I’d place a marker there, too, so you can remember where the problem is. Delete render files, export again.

    Now, IF you get an error message, is it the same frame, or a different frame, or an error not relating to corrupted frames?

  • Ben Balser

    May 25, 2023 at 12:10 pm in reply to: Voice Over Enhancement plugin is change

    It seems to be a new plugin. You pick a preset and an amount, pretty simple. Seems to simply be Compressor presets. You’ll have to do it manually. There are better ways to do this with better results.

  • First, turn off background rendering.

    Then delete all render files for that library.

    Then I’d delete FCP’s preference files.

    See if these three (in this order) help.

  • Ben Balser

    May 23, 2023 at 9:42 pm in reply to: Be Careful Updating FCPX!

    Motion and Compressor also got updates today, just FYI.

Page 23 of 37

We use anonymous cookies to give you the best experience we can.
Our Privacy policy | GDPR Policy