FCPX And El Capitan

Mine's improved. I see I far less often. Seems totaled random.

Xbox is a gaming device, not a 3D authoring device. Apples to onions...

BenB wrote: Xbox is a gaming device, not a 3D authoring device. Apples to onions...

BenB it was a humours joke... :silly:

Though it was a small issue that didn't interfere with my editing process, 10.2.3 brings a very welcomed corrected TC window.. now my clients won't keep pointing it out to me all the time!!! I like the defaults for audio and video effects too!

I can import XVAC footage now! Although after render some glitches will occur. Keep updating Apple you're not finished yet.

So it's not only me?
Using XAVC-L from my Sony X70. Smooth as silk in the timeline but on exports I often get a mashed first frame. No obvious pattern to it and no way to know when it'll happen since it's not visible in the timeline.

No there a lot of people having problems. In my case with original and optimized footage out of a FS5

Thanks for reporting this issue. Please fill in the feedback page with any details you can provide, so they can look into this.

- Ronny

I still have an issue with XAVC files. If I open a project that was using native MXF XAVC files I get blank clips in the timeline on certain clips. No error msg, just a black screen and thumbnail of the clip. The weird thing is when I plug my MacBook that's running Yosemite into the RAID and open the same project it works fine. No issues at all. It's only when I try open those projects on a system running El Capitan that I get the issue...

I thought this latest update would have fixed this but it doesn't. I've been in contact with apple support who are talking about this with engineering at the moment so hopefully they will have a fix soon...

Here's my experience with the XAVC-L clips from the Sony X70 (running El Capitan and 10.2.3):

I have no trouble editing the HD or 4K clips natively on my new top-spec iMac. However, once in a while I get one or two pixellated frames. This never happens on regular footage, but always either just before or just after a transition that I've added. It happens on both third-party transitions and even the built-in cross fade. When this happens, I just do a match frame and replace the clip from the original. That always fixes it, and it stays fixed even on export. It's not the end of the world, but I do wish it didn't happen.

However, when I used to transcode to ProRes, I never saw the problem at all.