iMac Late 2015 FCPx Issue

[jrmilt]

Hi there!
I've recently upgraded my computer to a late 2015 iMac (4ghz,32gb ram, 4gb 395x) and having trouble rendering while neat video is activated. Final it will get to around 30% export before it either says sharing failed or makes the computer freeze and instantly restart.

It's a 30 minute timeline which involves multi camera secquences.

Any help would be appreciated

I'm running mac sierra, fcpx 10.3.1 and neat video v4 pro

[NVTeam]

Please try to disable use of GPU in Neat Video Preferences (GPU Troubleshooting dialog in Performance page) and check if the problem is still reproducible.

Thank you,
Vlad

[jrmilt]

Thank you for your reply. I have disabled the GPU, however the issue still exists

[NVTeam]

Can you trace it back to a specific part of your project/timeline that has a specific combination of effects, clips, transitions, etc., that always fails in the same spot?

Vlad

[jrmilt]

I'll have a check when I get home. It renders fine with neat video turned off. Just crashes when it's enabled. I have saved the crash log from final cut which I'll email to you

[NVTeam]

Thank you, that can help. Still, please try to identify the spot in your project where it stops.

Thank you,
Vlad

[jrmilt]

I wasn't able to identify where in the project where it stops.

Ive tried an old project with Neat Video applied that rendered perfectly on my MBP mid 2012, which also failed around the 40% complete mark on my new iMac. It froze the computer forcing a restart which a crash report wasn't generated.

I tried applying to a single clip of around 11 minutes which rendered fine. I then split that same clip into 4 with the blade tool and applied neat video which when rendered resulted in the computer crashing, forcing a restart.

So its fine applying it on a single clip, its just crashing when there is more clips in a single timeline with neat video applied.

[NVTeam]

Ive tried an old project with Neat Video applied that rendered perfectly on my MBP mid 2012, which also failed around the 40% complete mark on my new iMac. It froze the computer forcing a restart which a crash report wasn't generated.

That may indicate a hardware problem with the new machine. It may be overheating because of heavy rendering.
There may also be a problem with the GPU driver. That could also lead to a restart of the whole machine.

Do you see any notes about the crash in the system logs of OSX after that?

I tried applying to a single clip of around 11 minutes which rendered fine. I then split that same clip into 4 with the blade tool and applied neat video which when rendered resulted in the computer crashing, forcing a restart.

So its fine applying it on a single clip, its just crashing when there is more clips in a single timeline with neat video applied.

Was the use of GPU enabled in Neat Video in that test?
When it crashed, was it only FCPX or OSX too?

Could you try to render the same test project (with bladed clips) on MBP for a test? Will it work without issues there?


Also, thank you for sending the hang log to our e-mail. We will check it too.
Could you just clarify, when did you receive that log? When doing what in FCPX? Did FCPX hang and not respond, but OSX continued to work without restart?

Please also check the system logs using Console to see if OSX logged any specific causes of the restart (perhaps a kernel panic).

Thank you,
Vlad

[jrmilt]

That may indicate a hardware problem with the new machine. It may be overheating because of heavy rendering.
There may also be a problem with the GPU driver. That could also lead to a restart of the whole machine.

I rendered the bladed clip test project with the fan setting turned all the way up which rendered fine, however The other, longer projects still either crash Final cut or force restart the computer. It doesn’t matter if I render with gpu. It will still crash with cpu only setting enabled.

Do you see any notes about the crash in the system logs of OSX after that?

Im not too sure what I am looking for there, so I sent you a couple of logs I copied and pasted from the console from where final cut crashed and where the whole computer crashed. I hope its of help

So its fine applying it on a single clip, its just crashing when there is more clips in a single timeline with neat video applied.

Thats what I thought until the bladed clips test project rendered fine. now Im thinking its something to do with the size of the project

When it crashed, was it only FCPX or OSX too?

Sometimes it locks the system forcing a restart, sometimes fcpx stops responding allowing me to force quit the application (Which I am Able to generate the crash reports from, Doesn't prompt me to send report to apple after the computer restarts from the crash)

Could you try to render the same test project (with bladed clips) on MBP for a test? Will it work without issues there?.

I have tried it and is rendering fine. I would try the bigger project on it, but neat video applied takes more than 30 hours on it with previous projects, hence the upgrade to this machine.

[NVTeam]

That may indicate a hardware problem with the new machine. It may be overheating because of heavy rendering.
There may also be a problem with the GPU driver. That could also lead to a restart of the whole machine.

I rendered the bladed clip test project with the fan setting turned all the way up which rendered fine, however The other, longer projects still either crash Final cut or force restart the computer. It doesn’t matter if I render with gpu. It will still crash with cpu only setting enabled.

That may still indicate overheating but in another component (for example, in CPU itself or in RAM modules).

Please try to reduce the number of cores that Neat Video uses and see if this helps to avoid crashes.
Also monitor the temperatures of the CPU/GPU during render to see if any of those temperatures goes too high.

Do you see any notes about the crash in the system logs of OSX after that?

Im not too sure what I am looking for there, so I sent you a couple of logs I copied and pasted from the console from where final cut crashed and where the whole computer crashed. I hope its of help

Thank you for the logs. There are some errors there but it is not clear if any of those are related to the crashes.

I recommend to collect such logs after reproducing a crash of FCPX and/or OSX so that you knew the approximate time of the crash
and we could then use it to find the relevant records in the logs.

Could you try to render the same test project (with bladed clips) on MBP for a test? Will it work without issues there?.

I have tried it and is rendering fine. I would try the bigger project on it, but neat video applied takes more than 30 hours on it with previous projects, hence the upgrade to this machine.

That is another indication of overheating of the other machine. I would expect it to be more stable if you limited the number of CPU cores. Perhaps using GPU instead of CPU could help too.

Vlad

[tiloprobst]

Final it will get to around 30% export before it either says sharing failed or makes the computer freeze and instantly restart.

This sounds kinda familiar. My computer is freezing and restarting too, when I use NeatVideo during a final export. Here, here and here people maybe have the same problem. When you google a bit, you also find stuff like this where people get kernel panics with NeatVideo on original Apple hardware.

FCPX 10.3.3, macOS X.12.6. The hardware is a hackintosh with a Gigabyte H270N-Wifi, a 7700K and a Gigabyte GTX 1070 (8GB, ITX format). The whole setup is very fresh, so the drivers are up to date. Initially Neat Video did not recognize the GPU, but forcing the settings worked.

The project is a movie of around 100 min. The source material is 4k. At first I thought it would be overheating problems or the 550W PSU not delivering enough watts. The CPU is aroung 70 deg C during rendering (Corsair H60 compact water cooler), but that also happens when I render with Handbrake. NeatVideo is pretty much the only CUDA app I use. It crashes no matter if I use CPU-only, GPU-only or CPU/GPU, sometimes at around 20%, 40% or 90% (CPU only). What gets me is that the entire computer just shuts down. But to my knowledge there are no real Kernel Panics on hackintoshes since there is no Apple BIOS. I also don't think there's a crash report for FCPX.

When I use CPU-only it crashes later, with the export about 90% done after 30 hours. In this case the 1070 is only warm, whereas with CUDA it gets quite hot. I can't say how hot though since on hackintoshes the GPU temp sensors kernel extensions currently causes crashes under Sierra and there's no update in sight.

With CUDA the export is around 3x times faster, which is why I want to use it. And yes, I am sure the problems are related to NeatVideo, CUDA or whatever. I have used FCPX for years and my projects are often very similiar. With my current testing project NeatVideo is the only complex effect. The timeline is very simple. Deactivating NeatVideo drops the render time to almost nothing and the export finishes normally.

I have already talked to support about this. I will try and test VirtualDub under Windows, as Vlad suggested, but that will take time. Usually I don't work under Windows.

Right now I am rendering with CUDA to reproduce the crash and then I will try to find something in the system logs.

I will also try to install another fan, even though I doubt it makes a difference.

[tiloprobst]

I have done more testing since then. On the MBP 2015 (Intel iGPU) I never had a crash no matter what. On the main machine I pretty much always get a crash when rendering longer timelines (like 60+ min). I get a crash maybe one in three times by rendering short clips (like, 10 min).

But, I can also rule out hardware/heat issues on my main machine, since I also had a kernel panic / hard reset once just from pressing the Auto Profile button. At this point I had just quit FCPX (to get a clean start before a rendering test, as I always do), the machine was on low temps, but just pressing the Auto Profile button produced a KP. So my thinking right now is that the problem lies within Neat Video or NVidias custom 10xx driver (which is to be differentiated from their CUDA driver). Might be also CUDA, can't rule that out yet. I also had crashes in CPU-only mode, but then again FCPX generally uses CUDA too.

[NVTeam]

Please reduce the number of used cores in Neat Video Preferences, set it to use the CPU only and disable GPU in the GPU Troubleshooting dialog, then restart FCPX and see if you can reproduce a hard reset by doing Auto Profile many times over.

Thank you,
Vlad