FCPX Bugs in the time line render files

Hi,


I am at the end of my tether with FCPX. Every time I edit a project the render files become corrupted within the timeline. This manifests in 1 of 2 ways


1 I get a stray frame from another an unrelated clip insert itself into the clip and display in the time line eg (Image 1 where a talking head shot suddenly has one solitary frame of the proceeding drumming shot show)


2 One frame just becomes corrupted. (Image 2)


The original proxy files are fine. If I find them in the browser and drag them back into the timeline there is no issue.


This has been happening for sometime. I did a clean install of the OS a while ago, which didnt help. OS and software is up-to-date.


Anyone know if there is a solutions to this as it is a huge waste of time or should I just move to Premier or Davinci?



iMac 27″, macOS 12.0

Posted on Feb 1, 2022 1:31 AM

Reply
Question marked as Top-ranking reply

Posted on Feb 1, 2022 2:31 AM

You did NOT make a clean install. You have stuff that was installed in 2014!

You may have erased everything, but if you then migrated all your stuff, you would have in effect just reverted to the previous state.


Uninstall clamxav, for a start.

Then you have stuff that I would not recommend, like torrent stuff - this is a great vehicle for adware.


I would really do a clean install: erase, install and then migrate ONLY the user accounts.

Similar questions

12 replies
Question marked as Top-ranking reply

Feb 1, 2022 2:31 AM in response to ErolGE

You did NOT make a clean install. You have stuff that was installed in 2014!

You may have erased everything, but if you then migrated all your stuff, you would have in effect just reverted to the previous state.


Uninstall clamxav, for a start.

Then you have stuff that I would not recommend, like torrent stuff - this is a great vehicle for adware.


I would really do a clean install: erase, install and then migrate ONLY the user accounts.

Feb 2, 2022 1:19 AM in response to Luis Sequeira1

Indeed. Which is why


[Running] PowerMate (? - installed 2014-01-22)

Application

/Applications/PowerMate.app


is not an indication of the clean install not being done correctly. Simply a login item that has been saved in user preferences, referencing a re-installed piece of software, that has a faulty date stamp.


So beyond the clean install which, again has been done, if anyone has any advice in regards to the FCPX issues I d be grateful.


Thanks


Feb 1, 2022 5:05 AM in response to Luis Sequeira1

I don t have ClamX or any of the other applications installed. Check the image.






Again the drive was deleted and a clean install was completed via a bootable OS disk. The users were migrated which seems to have lead to a bunch of orphan files.


Regardless if there are any third party files that would interfere with FCPX, in my mind they should show up in the report, which they don t. Has anyone experienced this prior?


Doing a clean install every-time FCPx has an issue is not really a practical solution.


Thanks



Feb 1, 2022 5:18 AM in response to ErolGE

We are not discussing a clean install because FCP is having an issue.

We are discussing a clean install because there are badly written, unuseful or damaging software that can make a system not work as intended; or simply stuff that is too old and does not work well in a newer OS.


It is a good idea to do a clean install at least yearly, at the time of a major OS upgrade. That leaves cruft behind and avoids conflicts between old extensions or daemons. Just about every claim about bugs in a new OS are due to the stuff installed before the upgrade.

Feb 1, 2022 11:57 PM in response to Luis Sequeira1

It VERY much is.


I verified my process overnight and following another clean install these orphan files are again visible. Clean install process being erase disk in recovery mode, install Monterey via bootable disk, use migration assistant to migrate "User" data. "Applications", "other files and folders" etc are not migrated.


So there seems to be some genuine confusion over what does and doesn't happen via migration.


And whilst I appreciate the suggestions, in fairness none of this confusion is helping resolve the FCPX issue.


Feb 2, 2022 12:56 AM in response to ErolGE

Let me try to clarify: when you migrate the user accounts, then anything that goes into your own accounts' folders will be migrated. This includes the contents of your users' Library folders. So the contents of "user launch agents" will be restored, but not "launch agents" or "launch daemons", because those are in the overall Library folder.


For the record "user launch agents" are installed in ~/Library/LaunchAgents (the tilde means your home folder)

"launch agents" go into /Library/LaunchAgents (no tilde here; this is the main Library that affects every user)

"launch daemons" go into /Library/LaunchDaemons (again, they affect all users).



This does have the potential for creating "orphan" files: all it takes is for something in your ~/Library/LaunchAgents to try and launch an application or service that was not migrated back. Orphan files just do nothing, hence they typically appear under "clean up" in an Etrecheck report.



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.

FCPX Bugs in the time line render files

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