I'd just like to confirm that the issue is indeed caused by monitoring audio with a Buetooth device. In my case, a pair of Plantronics headphones. Disconnecting the device and monitoring via analog output fixes the problem immediately. This is happening on a Late 2015 27" iMac Retina.
This appears to be a bug that started happening with either a fairly recent OSX or FCPX update. I suspect it might have been the OSX 10.4.5 update. I've been chasing this bug for a while, and it was this thread that tipped me off to the Bluetooth issue:
The only remedy for now is to plug the headphones in to the analog jack and disconnect from Bluetooth. And obviously submit feedback to Apple.
Hey, I think I'm experiencing the same issue. iMac late 2015, OSX 10.14.5, FCPX 10.4.6. When it happens to you, are you unable to click/drag the playback head in the timeline and skimming stops working on the timeline – but still works in the event browser?
Just started happening recently after updating my OS and FCPX one after the other.
Trashed FCPX preferences. Haven't tried a clean re-install of FCPX or the OS yet.
And it looks like an old iMac.
Interesting thought. It would be possible through image analysis to have a plugin guess at a correct horizon adjustment. Some images would be dead simple - images where you can actually see a straight horizon. Otherwise it would have to look for various vertical/horizontal edges in the image and correct for those.
In the mean time, I recommend the FREE Dashwood Level Horizon plugin that is part of their Editor Essentials package in FxFactory. It automatically scales the image up to allow for the horizon shift and includes a handy grid overlay to assist in determining the proper horizon.
This is interesting. Either something is messed up with your system or we're missing some bit of information about how you've got it set up.
I agree with Karsten. This works in FCPX. I do it all the time.
Is your media being copied into the Library location or is it being left in place on import? Is your media managed externally or stored within the Library .fcpbundle? Are you using optimized media and/or proxy media?
The problem with compound clips is that to change anything in them, you have to open the compound clip in the timeline viewer. When you do this, you lose all reference to the other clips that are in the parent timeline and and you cannot see rest of the project - you can only see what's in the compound clip. Often you need to time elements in the compound clip in relation to elements in the parent project.
It would be great to be able to expand the compound clip *within* the parent timeline so you can see the whole picture. I find that compound clips (much like pre-comps in AE) are flawed in this manner.
Maybe I was too distracted by the mechanism noise to notice the fan noise. I disabled the fan on my mini OWC RAID because it's loaded with SSDs and doesn't get hot under load.
You should consider swapping out the stock fan(s) with Noctua fans. They're super quiet. Worth the money, in my opinion. I hate fan noise.
I do remember that my Pegasus R6 was exceptionally quiet all around.
I have two OWC RAIDs and had a Pegasus R6 previously. Performance is on par.
As for noise, I assume people in this thread are talking about disk access noise. That is more a function of the type of mechanisms used in the RAID. My mechanical OWC uses HGST/Toshiba MD04 series drives in my RAID, which are admittedly are a bit too chattery/gronky when reading and writing. But, a Pegasus RAID using the same drives will be just as loud. And you can always load up the OWC enclosure with whatever quiet drives you like (or whatever Promise is using). The fan noise on the OWC is acceptable to me – and can always be improved by swapping out the fan with a premium fan if you're super picky.
My previous Promise R6 was populated with a batch of those horrible Seagate 3TB mechanisms released just after the flood. I had 4 of the 6 of them die on me during the lifespan of that RAID. Remember, the RAID manufacturers are at the mercy of the drive manufacturers.
You're not doing it wrong. You can use 1080p clips without losing resolution as long as you only reframe by moving left/right and you use the full height of the source clip. Even if your default settings require you to "scale up" so that your clip will fit the vertical size of the project, FCPX is still using the full 1080 vertical pixels of your source. If you need to push in further to reframe, of course you will lose some resolution. That only makes sense. But since you're most likely cutting square for social media delivery (i.e. viewing on a phone) – does the slight loss in resolution really matter all that much?
Just bumping this thread with a link to the new announcement from Apple:
Karsten Schlüter wrote: