- #Final cut pro 10.3.4 shuts down mac os
- #Final cut pro 10.3.4 shuts down update
- #Final cut pro 10.3.4 shuts down plus
- #Final cut pro 10.3.4 shuts down windows
Sorry for the rant, but I have projects I need to complete and don't have the time for science projects. I have never been so frustrated and disappointed with Adobe and Nvidia as I am right now. The straw that broke the camels happend todya when I scaled a PNG on a video and the image dissapeared. I have tried everything I can think of based on the forums, chats with Nvidia support and experimentation. I was getting lines and tearing on the mercury transmit monitor that were unacceptable.
#Final cut pro 10.3.4 shuts down windows
This all started last september when Windows updated the machine to version 1903. I have just uninstalled Premiere Pro 2020 and will try to reinstall it. Spent 2 hours on chat with Nvidia this morning to no avial. Is your imported clip MXF 25i, or does the export hang with any clip which you export to MXF? Please Log in to join the conversation.I am soooo frustrated with Adobe Premiere right now that I am about to trash a $10,000 HP workstation PC, cancel my Creative Cloud subscriptions and move back to Apple final cut Pro. It wasn't a crash or hang but how interlacing was handled. We previously had a report of a problem specific to interlaced MXF 25i material on 10.4. As Jonathan said, does it hang when exporting to a ProRes 422 (or higher) master in a non-MXF format? If no can you then convert an exported ProRes master to MXF with Compressor? That's not a long term solution but might help isolate the problem area. MXF is a container format that can include various codecs.
#Final cut pro 10.3.4 shuts down mac os
The Shut Down command turns off your Mac directly, unless it doesnt support soft power (in which case makes it safe for you to turn off your Macintosh) and, in versions of the Macintosh system software and Mac OS between System 7.5 and Mac OS 9.2.2, executes items in the Shutdown Items folder prior to. Is that consistent? Are you certain you've installed the latest Apple Pro Video Formats? Shut Down is a menu command in the Special menu in the Macintosh file system, Finder. You previously said MXF and ProRes above 422. If yes, the next step is evaluating what export codecs it hangs on. If no, we need to examine the original clip characteristics. If you import a non-MXF ProRes clip, or other various H264 clips, does it hang on export to MXF? Does if fail with any clip or just clips using that codec. If it fails with a freshly imported single clip in a test library, then examine the codec of that clip. If it works there's something in your original library causing the problem. If you cannot export even a single clip with no fx, that makes further isolation easier.Į.g, can you import that same clip to a new fresh library, and does export still fail? If so that eliminates the possibility of corrupt data within your existing library. OK, I know this is frustrating but those are all useful tests and help narrow down the problem. I also tried exporting just a single clip with no grade or fx applied and that failed too. Remove those that you no longer need/use, and contact the original vendor if you plan on continuing to use these plugins. Some possible steps:Ģ) Select the "Show FxPlug Plug-Ins in Finder" command under the "Actions” menu:ģ) The Finder will open a folder on your system that contains all legacy plug-ins for Final Cut Pro and Motion.Ĥ) Look at each file in the folder, especially for items like these:
#Final cut pro 10.3.4 shuts down update
If you are using FxFactory run that and update it. If that still fails evaluate what plugins you have, whether applied or not. This could help isolate it to a single clip or at least a small collection of clips.
#Final cut pro 10.3.4 shuts down plus
If the timeline is not fully rendered, then exporting does both render plus encode, so we don't know which phase it crashed in.Ī variation of the above is progressively cut down the project and see at what point the export stops hanging. It's important to determine is it crashing in the render phase or the encode phase.
This copies over just the media for the project, and leaves behind any render, scratch or proxy files. Then try to render the timeline with CTRL+R, if that works then try to export to the problem codec. Can you create a test library on a separate hard drive, copy just the project itself to that library, and answer "no" the dialog about copying render or proxy files? Then consolidate that library, disconnect the other drives and verify the test library will load. If this is a managed library, and you copied that or connected an external hard drive to the MBP, the cache and render files are still there. If you haven't already done it try the Digital Anarchy removal tool, then re-install FCPX.