Transcoding for Proxy media not working

Question

Level 1

8 points

Transcoding for Proxy media not working

Hello,

I'm trying (and failing) to get FCP to work on my MacBook Air. I've read that converting files to proxy media helps to make it not be so slow. But today when trying to transcode to proxy media, it gets to 72% on one clip and then just stops completely. Here's a screenshot:

As you can see only the first clip has even started, and is just stuck at 72%. What can I do?

Any other general advice for editing on a MacBook Air without a spinning rainbow circle no matter what I click?

MacBook Air 13″, macOS 10.15

Posted on Jun 26, 2021 2:40 PM

Reply

Answer 1

Jun 26, 2021 2:58 PM in response to victoria80

We need more information.

Which MacBook Air? Which version of macOS? Which version of FCP? Where is the media?

Very important: hiw much free space?

Also, in order to give us a good idea of your hardware and software setup please run Etrecheck and post its full report here. Use the additional text button below the message, as the report is too long to post directly in the message.

Reply

Answer 2

Tom Wolsky

Level 10

152,805 points

Jun 26, 2021 5:57 PM in response to victoria80

https://chromeisbad.com/

Delete Chrome and all its pieces like keystone. Window Server should not be the using significant system resources. That’s Chrome and it’s crap.

Reply

Answer 3

victoria80 Author

Level 1

8 points

Jun 26, 2021 5:47 PM in response to Luis Sequeira1

Okay -

MacBook Air: 2019 13 inch with retina display

MacOS version: Catalina 10.15.7

FCP: version 10.5.3

The media and the library are both stored on my external hard drive

Free space on my laptop: 48 gb of 121

Free space on external hard drive: 4.15 TB

Linking the Etrecheck in the additional text.

Etrecheck report

Reply

Answer 4

Jun 26, 2021 7:59 PM in response to victoria80

I have uploaded to YouTube using Safari many times without issues.

If you need a Chrome-like browser try Edge. It uses the Chrome rendering engine but not the keystone stuff and it doesn’t seem to cause the trouble that Chrome does.

Reply