[Andre Van berlo]

26 hours is a very very long render, but it was a 3 hour timeline, mine was only 9 minutes and it already took hours(don’t know how many hours, I went to bed after a while). I do think that having a sharpening effect and stabilizing effect on there at the same time might have been a bit too much to handle at the same time.

[Andre Van berlo]

🙂 That shows how little I know about these things! I always thought more would be better. But I guess that doesn’t even go with a CPU where more cores with some applications will make the application slower than having a CPU with less cores (but higher clockspeed)…

Thank for that bit of knowledge, that is exactly why I’m regularly hangin’ around the cow.

[Andre Van berlo]

Haha, well you caught me there… these are all videos I shot of our daughter when she was just born. Everything was shot early in the morning at home with only very dim light to light the “scene” or “set”. So unfortunately I have a lot of footage like this.

Then again there is no client bothering me about render time so I can have the mac render this stuff over night. But as I only just bought the mac recently I was kind of baffled after seeing all the video’s with the 4k and 6k stuff that my mac is choking on simple HD footage…

I also noticed neat video is 32bit, I guess the plugin would improve quite a bit if they would make it 64bit…

[Andre Van berlo]

Actually I’m happy to read that everyone is experiencing that neat video is slow, it means I don’t have to worry about the hardware…

[Andre Van berlo]

Hi Keith,

thanks for your reply. You could be right, I did notice that the mac pro was getting very very warm on the outside I just couldn’t imagine that it would take so long to render with all that horsepower in the new mac…

[Andre Van berlo]

Hey Darren,

I got this message back from neat video guys:

“protranscodertool is not part of Neat Video, so its behaviour
should not be affected by any adjustments in Neat Video
settings.

protranscodertool is a part of FCPX and I can see other people
reported a similar problem on Apple support website:
https://discussions.apple.com/thread/5808115?start=0&tstart=0”

Personally I’m not convinced that neat video isn’t causing the protranscodertool not responding. Whenever it is enabled fcpx turns into a snail, when I remove it the render is done in a minute…

[Andre Van berlo]

hi Darren,

you were correct about optimization settings not being enabled. However, it didn’t make much difference. Even after enabling both D700’s and all 6 cores the render was as slow as you could get.

Digging in I found that each time when I use neat video I see “protranscodertool not responding” in my activity monitor.

After enabling my gpu’s in optimization settings, still slow renders and stil the “protranscodertool not responding”(25%).

Then I exported a simple project without neat video and it exported fine and “protranscodertool” was working great.

Then applied neat video to a clip within that project and export went bad again, “protranscodertool not responding”.

I just send them an email asking about that beta. There is something about neatvideo that is messing up this “protranscodertool”.

Thanks for letting me know of its existence 🙂

André

[Andre Van berlo]

Thanks Michael Garber, James Culbertson, Marcus Moore, and Darren Roark!

I’ll get that beta for neat video and redo the render.

“In case you didn’t know, go into the hidden optimization settings to enable the GPUs.”

I assume the hidden optimization settings are in neat video right?

In any case I’m going to do the above and report back here. I was pretty scared seeing that beachball time and time again, hopefully we’ve found our culprit… Thanks again!

André

[Andre Van berlo]

actually I think he says that before we all jump on one aspect of the whole process (in this case resolution) we should investigate which of the aspects makes for the biggest improvement. Apparently more companies like the bbc are looking into this and are trying to find out what would yield best results.

I’m not sure but I also think he believes that 4K needs higher framerates.

One thing is certain, many things make up for a better image and i’m sure dynamic range and framerate would do a lot with image quality as well.

disclaimer: I understand some German but he has an accent from the south of Germany which is harder to understand

[Andre Van berlo]

“I, for one, am very grateful for the hole that FCPX plugs for me. Glad I never spent much time learning Premiere.”

I’ve picked up on FCPX very quickly and found it to match my brain more than Premiere Pro, eventhough I started on premiere pro. I was very happily surprised when I tried FCPX.

I am happy X does MTS files natively now as before I would need to transcode.