[Jon Cairns]

Kaleigh,

This looks like the same situation I had. Wound up being that an editor I worked with had updated PrP without thinking. So they were running v12.0.1 while I was running v12.0. So I recommend that you double check which versions you’re both running. We are all running Macs.

if this is the case with your situation, the good news is once you update those issues are resolved with no additional work. But it was a tricky one for me to troubleshoot since the other editor hadn’t even remembered updating.

Hope this helps.

Jon

[Jon Cairns]

Dan,
[Dan Wiesjahn] “After this project I’ll see if both of us update at the same time we can get rid of the issue.
“
This sounds like the same situation I came across. We’ve got a team of three editors working on the same projects at various points. Recently we had the same dialog warning about the encoder and what looked like digital dropouts throughout certain (but not all) footage. But we only got that on two of the three machines (all Mac environment). The third machine had no issues with the same projects. Once that third machine opened and saved the projects the other two macs would have the issues.

After troubleshooting it was pinned down to the fact that one person had run the adobe update to the latest version of PrP (12.0.1) while the others were still on the previous version (12.0). Once the other two machines were updated all if the issues we’d seen were gone.

Sounds like you got around the issue by copying and pasting into a new project. But be warned if you pass this project back and forth with the other editor the problem probably rear its ugly head once again.

Hope this helps.

Jon

[Jon Cairns]

Oliver,

I had the same issue, updated Pro Apps several times only to have it appear as an update again. I found this thread on Apple’s discussion board and it seems to have fixed the issue:

https://discussions.apple.com/thread/7006966

Basically, copy all of the files from /Library/Quicktime then run the update again and reboot. I deleted everything from the Quicktime folder before the update just to be sure everything in there was “new”. Then copy any files back to the Quicktime folder that are 3rd party files.

Hope this helps.

Jon

[Jon Cairns]

Sorry to hear that. I just thought it might be worth a try…

[Jon Cairns]

I can’t say one way or the other. The two systems I was working with were a Mac Pro and a MacBook Pro. I haven’t built a hackintosh so I don’t know what would be different.

I did run Carbon Copy Cloner before doing the procedure the first time so I had a fall back plan.

jon

[Jon Cairns]

Jerome,

I didn’t look into it much further. I had two systems that weren’t working properly so I carbon copied my HD on one machine and gave it a shot. It worked so I proceeded to use the same method on the other system. If you read the link that I posted in the earlier thread the author explains what is housed in that directory:

The reason for this is the directory structure that defines the account and its capabilities is stored within the hidden /var/db/dslocal/ directory, unlike other system and user settings that are within preferences folders either in the global or user library folders.

Once it worked I just went back to editing…

jon

[Jon Cairns]

I had a similar situation where oddities and anomalies cropped up while using FCP X. The symptoms were different than what you are experiencing (my issues were things like the skimmer not working, open libraries would be closed and closed libraries would be open on close/relaunch, transform and crop areas in inspector were blank, etc.) I had two separate systems exhibit this same odd behavior but was working on separate drives and libraries. Repairing permissions, trashing preferences had no effect.

Like you, though, the same problematic libraries and FCPX in general, worked fine under a new user. However, like you, I didn’t want to have to go through the tedious process of replicating the User that had been working. What did work for me was to rebuild my user account. This retains your settings, etc. but clears the user files that are stored in /var/db/dslocal/.

I followed the procedure found here:
https://www.cnet.com/how-to/how-to-rebuild-a-user-account-in-os-x/

After doing that on both systems I am back up and running as I was prior to things going sideways in FCP X. No idea if this will solve your issues but I thought I’d throw it out there.

Jon

[Jon Cairns]

There is a demo but the link is in the support section. Here’s the direct link:

https://www.soundness-llc.com/ss_trial.html

I found it in the FAQ’s or something. The plugin is about how I remember SoundSoap 2, decent but not as powerful as RX, IMHO.

jon

[Jon Cairns]

If you open this library in a different User account do you see the same issue?

I had some odd Library behavior (on quite and relaunch open libraries were closed, closed libraries were open, etc.). Same libraries on same drive behaved fine under a new User.

It’s not the same issue you are seeing but worth a try?

Jon

[Jon Cairns]

In the display preferences simply drag the finder bar in the monitor icons to the monitor you’d like to have act as the primary monitor.

Jon