10.3 issues

This is your first time posting in the thread.

Can't see a problem dragging clips in a project that's over an hour. Many more video clips but far fewer separate audio clips. Most of the audio is in the clips. Wonder if that's a factor.

yeah, sorry meant from the *linked* thread

It's a "funny" bug though.

Main storyline clips are basically unaffected by this.
Bug occurs on first dragged clip *after* each timeline scroll and/or zoom. Dragging other clips after the first one doesn't exhibit the same drag-lag.

I will link to the vids here as well.
Same system, same project, same timeline, two NLE's doing well. One NLE... not so much.

FCPX 10.3


Resolve


Premiere

Just thought I'd update my input here. As it turned out AJA issued an update a day before I complained about the random crashing. Installed it this morning and was able to go thru the all day edit session with no issues. The lesson learned is, even when you think you're current... check again.

the new admin user trick did the job for me, no more running out of application memory warning and force quit suggestion.
now I have to find a quick and painless way to have all my third-party effects / titles / generators for the new user, as well.
does anyone recommend a specific workflow for migrating these assets or do I have to download them from the vendors' websites again?
thank you!

Thank you for the feedback, very useful for others.

- I have noticed the updates to the AJA drivers, and BM should update their drivers as well. There are still issues with some AJA and BM boxes because of the old drivers. Putting the drivers up to date should do the trick. Nothing to do with FCP X.

- If running a new admin user solves the performance issues, this can indeed mean that you have corrupt plugins. Copying them from the old user into the other is useless because you will copy over the problems. So you will have to reinstall them fresh for the new user. The advantage of this is that you will install the latest versions, and you will be running a lean and clean new user account. This always makes a difference with regard to the performance of your system

As a side note: I have called some friends who are running long and complex timelines - one of them is even working on a 5-hour timeline for a major feature film with close to 500 hours of footage. They are all on Sierra and 10.3, and no-one seems to have any serious performance issues. All of them did wipe-and-clean OS reinstalls.

So before we cry "bug" I think it's worth trying to do the obvious things that are always related to updates: getting external plugins and hardware drivers up to date, and checking if the update has not affected the user account (especially when updating an OS without a clean reinstall). This should fix most of the issues.


- Ronny

well, for me it was the second ”bug” cry, and I use FCPX since it came out, on the same admin account, that underwent all the OS and FCPX updates.
Apart from the footage turning black in timeline (and preview pane) - my first cry, and this ”out of application memory” that would be the 2nd.
never created a new admin account as I didn't have the need to do it; good to know about this solving issues

That makes perfect sense, Lightgale. Thank you for the feedback!

- Ronny

- I have noticed the updates to the AJA drivers, and BM should update their drivers as well. There are still issues with some AJA and BM boxes because of the old drivers. Putting the drivers up to date should do the trick. Nothing to do with FCP X.

That's an understatement.

Someone needs to get to the bottom of why... quite simply FCP X sucks with Blackmagic Video Output devices. I use a Blackmagic Ultrastudio Express and its never been a happy marriage, even with previous X versions...

Last couple of jobs I have done where I need to play out content regularly to clients - I have resorted to using Premiere as it simply doesn't crash the Blackmagic drivers like X does.

Even FCP 7 usually behaves historically well with them.

Since 10.3 - even with Blackmagic's recent device driver set (10.8.2 - released Oct 27) - I couldn't even get Output via SDI!

I see 10.8.3 was released yesterday from BM. I will cross fingers, but will not hold my breath!

Dean...

Hi Deano,

I think that's fair statement. BM video devices have always been pretty problematic with FCP X, while all the AJA Boxes I have work very well. So I think the ball is in the BM camp. Let's hope their latest drivers are better.

- Ronny

ronny courtens wrote: Hi Deano,

I think that's fair statement. BM video devices have always been pretty problematic with FCP X, while all the AJA Boxes I have work very well. So I think the ball is in the BM camp. Let's hope their latest drivers are better.

- Ronny

I will add that I personally have not experienced any issues as such with my BM Ultrastudio 4K*

*except that one time when BM released a driver that froze up FCPX.

Thank you for your input, Chris. Good to know.

- Ronny

My system is far from beefy, a 13 inch retina macbook pro from late 2013, 8GB RAM, so not powerful, but it worked, then I started getting purple flashes on the export, and in the timeline, at first I thought it was heat or bad RAM, or that the video was pro res 6K, so after weeks of experiments, at present Yosemite and 10.2.3 seems to be rock solid.

Is it bad code in Sierra or 10.3 or both? That it would be hardware at first I was convinced it was hardware, but now using Yosemite and 10.2.3, leaves me with no doubt that the two are related, Sierra and 10.3.

I gave my laptop a real hard workout, heavy 6K RED, wifh loads of effects, speed changes, not a single error, yet with Sierra and 10.3, error every time!

So for now I am staying on Yosemite and 10.2.3!

I don't know if this is a bug or not but the Attributes window that used to appear when I pasted effects no longer does so.

Otherwise 10.3 works well on my early 2012 MBP with 16GB RAM.

There are two separate functions, paste attributes and paste effects. Paste attributes has a dialogue window, paste effects does not. It just does it.

Shame, as I don't always want to paste all the effects.

It was particularly annoying when I pasted a multi band compressor onto some clips and it took the fade in from that clip with it as well.

It would have been nice to have the option to untick the fade and just take the comp.

Stereodesign wrote: Shame, as I don't always want to paste all the effects.

It would have been nice to have the option to untick the fade and just take the comp.

And that's why you have Paste Attributes, so you can do exactly that when needed.

ronny courtens wrote: As a side note: I have called some friends who are running long and complex timelines - one of them is even working on a 5-hour timeline for a major feature film with close to 500 hours of footage. They are all on Sierra and 10.3, and no-one seems to have any serious performance issues. All of them did wipe-and-clean OS reinstalls.

I have just tried shortening the timeline from the videos.
Funny thing - the shorter the timeline, the less drag-lag I'm getting, to the point of it being a non-issue.
So far as I can tell, drag-lag increases around the 17-19min mark, and just gets incrementally worse the longer the timeline gets.

I might also add that I'm not experiencing performance issues as such - "just" UI sluggishness when mouse dragging clips in the way described earlier. Perfomance as in rendering and generally working with FCPX 10.3 is not affected.

But I will stand my ground on the drag-lag issue as shown in the video. There's definitely something going on with FCPX the longer the timeline gets - maybe not for everybody, depending on machine (you don't mention what your friends are editing on), but we can't deny that there are at least *two* machine having issues with longer timelines, whether that's from an old OS install or completely fresh OS + FCPX only, on two different macbook pro's.

And yeah, feedback submitted to Apple

"Extremly buggy"

Agree. Moving png files into the timeline .... crash....


System Integrity Protection: enabled

Crashed Thread: 0 Dispatch queue: com.apple.main-thread

Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Exception Note: EXC_CORPSE_NOTIFY

Can anyone reproduce this?

Schnurr wrote: "Extremly buggy"

Agree. Moving png files into the timeline .... crash....


System Integrity Protection: enabled

Crashed Thread: 0 Dispatch queue: com.apple.main-thread

Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Exception Note: EXC_CORPSE_NOTIFY

no problems dragging a .png (screenshot) from the desktop to timeline here.