Final Cut Pro X export fails! Missing RAM vtdecoderxpcservice

FCPX still can't export a project! Whenever I try to export a project the VTDecoderXPCService runs crazy goes up to over 50GB and a "Your System Has Run Out of Application Memory" message comes up and cancels the export. It is so frustrating, I had several sessions with the Apple Support Team and the FCPX Support Team as well, no solution and I can't deliver my project. And just for the records, no AppCleaner, No Chrome, no plug ins at all, I wiped out my complete system (I am still boiling about that). Just installed on my 2021 M1Pro MacBook: macOS Monterey, FCPX and Compressor all in its latest versions, still doesn't work. I just need to export a 18min long FHD timeline with 8k and 4k footage and the the system crashes regardless of what I do. This is now my last attempted to seek for some help, hope someone has at least a workaround???

MacBook Pro 14″, macOS 12.5

Posted on Aug 12, 2022 4:12 AM

Reply
Question marked as Top-ranking reply

Posted on Aug 19, 2022 12:06 AM

I need to correct myself, since I added the Speakers text and Colour Grading in FCP I can't export regardless of what I do. Playing the timeline while you export doesn't help anymore.


In case others have the same problem:

Safe time (I spend 1 week of investigation, Apple support, trial, re-installations, wiped out my mac, end of the day I have a ****** off client because of an extremely fundamental error which makes FCP completely useless.


How I solved it now:

Download Davinci, export your project in FCP via export XML and import the timeline in davinci (XML) and you are good to go, minor tweaks, but in general you can deliver. The H.264 codec plays on a M1 like in FCP, I now need to learn all the shortcuts in Davinci which is annoying, but I did not volunteer.


Activate the FCP mode in Davinci to make the change a bit easier. Actually I am glad, I can now finally buy cheaper Hardware and have a better colour grading tool set. I will not touch FCP ever again it is just an advanced iMovie tool... not suitable for any serious work - I should have listend to the community a couple of years ago, Anyway, good by Apple!

Similar questions

77 replies

Sep 16, 2022 11:16 AM in response to Tom Wolsky

I can guarantee you that it doesn't work, it is a severe bug in FCP which makes the tool unusable. I took my Sony footage to a friends Mac, same problem, it crashes. The only workaround is that you transcode the original 8k 10bit into 4k 8bit footage with Compressor, but that is just a joke... and even then FCP crashes one out of two export attempts. It got slightly better after I downgraded to BigSur, on my brand new MacBook Pro M1Pro it crashes all the time. I am afraid there is no reasonable work around. I will inform all of you as soon as some of the update will fix the problem, 3min. ago it still didn't work

Nov 3, 2022 5:53 AM in response to wil293

What is the main workaround you are doing? I have found out that if I can open up QuickTime and screen record during the export then it will export the file without issues. It will take 2-3 hours which is significantly longer and is extremely frustrating. I use a Sony alpha A7 IV. Shoot in 4K XAVC. I also use a Go pro 10.


This fix has been temporary and is very frustrating for such a long export time, but at least has worked for one of my videos so far.

Aug 15, 2022 9:55 AM in response to KLSetter

More detailed explanation and what I did so far.

Project Footage: Sony A7S3, 4k 4:2:2 10bit 25 and 50fps (H.265) and Sony A1, 8k 10bit, 25fps footage (not sure which codec), duration of the project 18min.

Project: 1920x817px 25fps, no additional Plug-ins, all FCPX latest Version 10.6.4, the project is stored on an external Samsung T5 SSD

Problem: The project and the responses while editing are all fine, the footage can be viewed no lagging, no frame losses, rendering on request (I switched off rendering in the background) runs smoothly and without any problems. If I start exporting "File/export" and select one of the export types "720p, 1080p etc." the process "VTDecoderxpcService" goes memory wise through the roof, it climbs up from 2-3GB to 51GB and more, which then creates a message in Final Cut that the Sharing failed.

In the details of the error message it refers to a particular frame, but that is just the frame where it crashed, every time it is another frame and the footage itself isn't the problem. With MacOS Monterey I was able to just export 3-4min after that it crashed, I thought that the new MacOS was the problem and I downgraded to BigSur. Problem is still there, but the export goes to 16min, sometimes it runs through and is successful, but most of the time the "Sharing failed" messages appears. I wiped out my M1 Mac Mini to test whether something went wrong with the upgrade to Monterey, but the problem remained. I have a 2021 M1 Pro MacBook as well, which I regrettable upgraded to Monterey, that one I can't use at all it crashes after 45 seconds of rendering, the "VTDecoderxpcService" service simply runs much faster into 50-60 GB before it crashes - and I can't wipe out that one...


My guesses so far:

1st Guess: Monterey is the problem -> only partly true, BigSur runs better, but fails also.

2nd Guess: 8k Footage too demanding, not the problem I deleted all 8k clips from the project, same problem

3rd Guess: SSD is too slow, gets to hot or whatsoever -> copied the project files, the source files etc onto the main Mac, same problem, then I read that the SSD should be formatted in APFS, did that with another SSD - same problem

4th Guess: Final Cut not correctly installed or other interference with installed Software, I wiped out and installed from scratch directly from the app store (no installation of a backup), no other software than McOS and FinalCut installed -> same problem

5th Guess: Wrong references in clips or something wrong with the project file, I exported the XML of the project and imported it again into a complete new project -> same problem

6th Guess: Difficulties in FCP having 4k footage but only a 1080p project (too much for FCP while exporting and scaling down the video), if I export in 4k and create a new project in 4k the problem remains


Conclusion, there must be a general problem in FCP and I can't surely be the only person who has those problems with 4k+ and >20min projects and I am sure there is a workaround, but so far no one could help.


Let me know if you need further information and I really appreciate all of your ideas and help


Aug 15, 2022 9:59 AM in response to KLSetter

Thank you very much for this. You are not alone with the problem, which seems to be in M1 machines. What's supposed to happen is when the memory pressure builds up the system is supposed to stop the decode/encode process, release the memory, and continue. That's what I see happen when I run a long export. I experimented with a 60 minute project with a variety of formats and codecs, frame rates and sizes. The VTD memory would run up on some media and codecs more quickly, but release at 35 GB. I have a 32 GB M1 Max. I could crash the system with DNxHD media pretty regularly. The 10-bit H265 pushed the VTD up but it didn't crash. This is in 12.5 with 10.6.4.

Sep 16, 2022 3:54 AM in response to Luis Sequeira1

I'll see if I can get around to testing that later this week -- although to be honest, with the amount of media I'm dealing with I don't see that as a practical work around for myself personally. Optimized media takes a while to make, and then it takes up SO much storage space. One of the biggest reasons I upgraded to the M1 is to stop having to create proxies or optimized media just to edit, and I kind of stubbornly refuse to go back haha. But still, an interesting idea and worth trying if you have this same problem and don't mind creating the optimized media.

Sep 16, 2022 11:50 AM in response to Tom Wolsky

well, for a 18min project in 1080p: Source footage 10bit, 8k and 4k 25fps and 50fps :


Bigsur crashes as soon as there is just one 8k included. With 4k it just works. (I need two to three attempts to render successful)


Monterey all footage crashes, 8k,4k 10bit, 8bit, simply crashes all the time.


BigSur runs on my M1MacMini, Monterey on my brand new full spec M1Pro, which I bought for video editing and which I can’t downgrade to BigSur.


My Cameras: Sony A7SIII and Sony A1.

Sep 19, 2022 2:04 AM in response to MayaElizaB

thanks good to hear that I am not alone, I will cut a very quick video and will send it to the most famous Youtuber, they will hopefully pick it up as they are always keen to find unbelievable FCP or Apple bugs - that will hopefully help to generate a bit more noise - it is really unacceptable and very annoying, in particular if we all consider what we have paid for the apple products… anyway thanks for the tip, what I thought would work as well (but haven’t tried it out) is if you create a couple of compound clips. You can export compound clips separately if you go into the compound clip and then hit export. After exporting all clips one would need to stitch the exported clips together into a new project - a lot of work. The workaround I am using at the moment is a downgrade to BigSur and while exporting you can play the project which resets the service, works not all the time, but you will get there eventually, unfortunately this workaround doesn’t work under Monterey on m1Pro.

Aug 16, 2022 6:40 AM in response to Tom Wolsky

Hurray a bit unconventional, but it works!!! On top of that I figured out that if you export as (Default) and you play the timeline while its exporting then it runs even a bit more stable. Needless to say that such a big bug is extremely annoying. I paid serious money for Apple Hard- and Software, I trusted Apple that I get a functional piece of software, but then starting having more and worse problems then I ever had with Windows and Premiere is more than unacceptable. I am really disappointed. Having said that I am very grateful for the tip!! Thank you very much, it saved my project and I can proceed...

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

Final Cut Pro X export fails! Missing RAM vtdecoderxpcservice

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.