Jeff,

Oh, that's about right on, depending on your computer.

Some of the is the deartifacting, some is the deinterlacing. I am using MB only for deartifacting. I have a P4 2.8 GHz with 1 GB of RAM, and it takes about 24 hours to deartifact 5 minutes of footage.

The long processing times are the reason I do a rough edit prior to deartifacting. You have to toss out as much footage as possible, so cut the render times.

Usually I get it set up, and come back the next day when it's done (OK, usually I sit there mezmerized as it processes frame by frame, but who doesn't?).

What's confusing about all of this is that the latest MB for Editors added Deartifacting within NLE's, and supposedly real-time with the right setup. I'm not sure if the deart is RT, or just the Look Suite, or even if it's the same algorithm shared between MB Suite and MB for Editors.

Josh

Ouff, that is a lot of render time. I have bulleted a 77 minute project from 30i to 30p and that took almost 200 hours. I recently exported a 35 minute piece doing a 30i to 24p conversion and it took 80 hours. This was on an intel 3.2EE cpu platform with 2GB of ram. Fast, but really fast by today's standards.

I also deartifact my DV footage and leave the sliders alone. Sliding them to left would actually increase the render times so sliding to the right probably helped a little.

If the Huffy codec is installed, when you choose your render output module settings it would be Video for Windows and choose the Format Options button. If you have it installed it will show up in the compressor list.

Fieldskit by RE:vision is much faster render-wise, but you have de-interlace to 60p first and then to 24p using Twixtor for best results.

It would be nice to know how the cheaper MB for editors differs, I don't know either and have always used the AE version. The new MB 2.1 I think uses open GL support, but that may only help with previews...