Cameron Jake wrote: Having downloaded the original file again.
My issue now is the media has dropped back in and is visbile in the time line - i.e. the same file name - however the clips as they were are completely all messed up.. is this the result of whats happened or is there a way to find them again in the exact clip order and section that they were in?
Yes, this indicates you deleted some of your original media. If you re-download the media, and if it has the same filenames you should be able to relink to that, preserving your full-res edits.
FCPX does not show the pathname of each file used in a library. The 3rd-party tool Final Cut Library Manager has an add-on option "Export to CSV" which will make a spreadsheet of all file paths in a given library. This can make it easier to locate your physical media in cases like this, plus may avoid accidentally deleting it in the first place: www.arcticwhiteness.com/finalcutlibrarymanager/
Brave is based on the same underlying Chromium code. If that works for you, OK. If you ever have any performance, stability or reliability issue with FCPX I'd suggest temporarily not running Chrome OR any browser based on Chromium.
ta69 wrote: ...proxy media...created it on the last external hardware I was using. Now it says missing proxy for every clip and relinking doesn't work... I can see it all there in the optimised media folder feel like I'm missing something...
Chrome is poorly behaved and can saturate the MacOS VideoToolBox framework, causing FCPX to unpredictably hang or crash. This is random and unpredictable, so it may work OK for periods then hang, crash or behave oddly.
That is actually a minor problem by Chrome standards. Last year a Chrome installer data corruption bug rendered many Macs unbootable and shut down production of various TV shows: variety.com/2019/digital/news/mac-pro-av...keystone-1203348549/
Is the Chrome VideoToolBox problem fixed on the latest version of Chrome? Does it only affect certain versions of MacOS? If fixed today will a future Chrome regression cause it to happen again? I personally do not intend to find out.
Irishrebel wrote: Symptom #2... I downloaded that Preference Manager app, selected FCP in the menu, and trashed the preferences. Problem solved. That was it!
docsound wrote: ...Does anyone have an idea how to record translator tracks with the Source-TC of the raw material and then create synchronized clips in FCPX from one video file each with the matching original sound and the translator recording?
It would be great to have the translator recordings directly connected to the raw material and have the possibility to log them like regular clips in the browser or create transcripts via the Simonsays plugin, which are then in the notes with the logged range...
Boltman wrote: ...I'm running MacOS, 10.14.6, High-Sierra. RAM is running low. I just bought some RAM but it's asking to upgrad to Catalina and I'm not sure if I should. IF more RAM solves it then I'll just do that...
Examine whether any of your DJI media is HEVC. There are definitely issues with some of that on FCPX 10.4.7 and 10.4.8. 4k HEVC material from our Inspire 2 will crash FCPX almost every time. We normally shoot ProRes but when testing it we shot some HEVC.
Also there may be some image quality issues on certain DJI HEVC variants. We saw banding on the Inspire HEVC and I think on the Phantom 4 Pro HEVC if shooting D-Log. That did not happen if shooting DJI H264. I think newer DJI drones have 10-bit HEVC which might be better.
Due to the current FCPX HEVC reliability issue, any DJI HEVC material should be transcoded to proxy or optimized media. In some cases FCPX may hang or crash during the transcode, so watch for that. If it does your only option is transcode it externally using Handbrake or some other tool, then import to FCPX.
If your HEVC is 10-bit you don't want to externally transcode to 8-bit H264 because you lose bit depth. You could use the free version of Resolve to transcode to ProRes 422, then import that to FCPX.
Re plug-ins, all current FCPX plugins except for Motion templates run within the process address space of FCPX. This means any bug in any plugin can crash or destabilize FCPX. Supposedly this will be improved in the future as plugin vendors move their products to FxPlug 4 which can enable out-of-process plugins, thereby preventing a plugin bug from crashing FCPX: developer.apple.com/documentation/profes..._minor&language=objc
Some plugin vendors have a reputation for producing more reliable products than others. MotionVFX is well regarded, Pixel Film Studios less so.
I suggest you first transcode all media to either optimized or proxy, then edit several days and see if it hangs. If so, then remove all plugins from Pixel Film Studio, delete/rebuild all cache files, then try again.
Do not run Chrome or any browser based on Chrome. It mis-uses the MacOS VideoToolBox framework and this can destabilize or crash FCPX.
Schwalbach wrote: ... I know the alias points to another folder which was probably on other folder on the original HD....I will have to locate this folder...
steve223 wrote: I'm a YouTube creator and shoot a lot of 4wd trips, so new trips every week. A lot of the footage I like to keep for reference .... I really should have no issues Editing on a 12 Core 2020 Mac Pro and Vega 64 but since switching to new MacPro and Catalina FCPX is running just crap slow and buggy (same addons as under Mojave)
DaveF wrote: I had a similar problem recently, in the end, I converted the iPhone footage to ProRes with ff-Works then imported to FCPX and that sorted it.
What version of FCPX? What version of fcpxml are you exporting? Does it crash *during* export of fcpxml, or after that? If afterward, how long after and upon what user action? Can you post the stack trace of the crashing thread?
As previously described, any bug in any 3rd-party plugin developed with the current FxPlug framework can crash FCPX. Can you update to Color Finale v 2.1?
As a standard troubleshooting measure, turn off background rendering in FCPX preferences. Then delete all generated library: Files>Delete Generated Library Files>Delete Render Filess>All. Then do a one-time render of the timeline by selecting it with CMD+A and rendering it with CTRL+R. Then try your fcpxml export. This separates the render phase from the export or encoding phase.
If that still crashes, create a test library, then create a "transfer event" in your current library. Drag/drop your project using OPT key into the transfer library. This does a copy, not a move. Then drag/drop that transfer event to the new library. Answer YES to copy optimized/proxy media (regardless of whether you have any). Do not consolidate media in that new library. Then open that copied project in that new library, render the timeline and try the export the fcpxml from there.
If that still crashes, in that test library, select the project and do the undocumented command OPT+Clip>Verify and Repair Project. See if that makes any difference. Do not try this on your main timeline - it is undocumented.
If that still crashes, can you make a duplicate snapshot of the timeline then strip all Fx with Edit>Remove Effects, render the timeline and see if that crashes? If not then make another snapshot, select 1/2 the timeline and remove Fx from there, re-render and re-export. If that does not crash, repeat the process with the other 1/2, then 1/4, etc until you narrow down the Fx-laden region causing the problem.
Play the original iPhone video in Quicktime Player, then do CMD+I and tell everything in that "Inspector" window. That will help understand the codec characteristics.
Then we need to know the year, model and exact config of your Mac. Just do Apple menu>About This Mac. Type everything on that window except the serial number and post it here.
Max604 wrote: ...is there a quick way for me to sync up the video B roll and have it automatically cut it up and sync it to the A roll? Is this possible in plural eyes or something? Essentially I want the A roll to remain untouched and the program will automatically cut where the overlay video goes on top...