new mac pro & fcpx = slow?!

[Tony West]

[Marcus Moore] “Really, you should only need to use something like this over an entire timeline when something has gone horribly wrong on set.”

I have never used it over an entire timeline myself, (I don’t know if you were responding to the OP or me)

I have only used it on small sections and it’s slow on that. I couldn’t imagine using it on an entire timeline

[Marcus Moore]

Sorry, yes, in reply to OP.

[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]

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]

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…

[Neil Sadwelkar]

I used Neat video in FCP 7 on an old (film-based) feature 3 hrs long. There was a lot of grain in the telecine which we couldn’t redo as the neg wasn’t accessible. Neat video took about 26 hrs to render the 3 hr long timeline in FCP 7.

———————————–
Neil Sadwelkar
neilsadwelkar.blogspot.com
twitter: fcpguru
FCP Editor, Edit systems consultant
Mumbai India

[Walter Soyka]

[Andre van Berlo] “I also noticed neat video is 32bit, I guess the plugin would improve quite a bit if they would make it 64bit…”

64-bit is not automatically faster than 32-bit. The primary difference between 32-bit and 64-bit apps is how high they can count, and that impacts how much RAM they can address.

A 32-bit app can address 4,294,967,296 bytes of data (4 gigabytes).

A 64-bit app can address 18,446,744,073,709,600,000 bytes of data (16 exbibytes). That’s a lot of commas.

A 4K RGBA frame at 32bpc is about 194 MB. You can fit about 84 of those frames inside 4 GB, which is way more than you’d need even for temporal smoothing.

Walter Soyka
Principal & Designer at Keen Live
Motion Graphics, Widescreen Events, Presentation Design, and Consulting
RenderBreak Blog – What I’m thinking when my workstation’s thinking
Creative Cow Forum Host: Live & Stage Events

[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]

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.

[Bret Williams]

I’ve worked before with large amounts of video that was cleaned up by neat video. We worked with the noisy stuff on the edit, while another system cleaned up all the source. At the end we replaced the noisy vids with the clean sources.

Certainly helped if you have an extra machine lying around.