I normally render my timelines due to number of effects applied to get a correct preview - I assume this is fully rendered data on my HDD.

If I export timeline to CFHD - why does Cinemform take so long rendering it again? When I used to have a Matrox if did not re-render unless I changed something.

Will Cineform address this? It will save everyone hours and hours.

No, as Adobe removed the feature in the next release. You could also find an external tool to do an AVI join.

David

I'm using NEO Scene. I captured to CFI in High quality with "enable smart render" turned on, then did simple cuts and sound sweetening in Vegas 8c, then rendered in High quality CFI. It took a long time, and was obviously re-rendering the video. Isn't NEO Scene supposed to smart render in this instance? I seem to remember NEO HDV doing so in the past.

Yes that should have worked. I can only guess there was a setting mismatch some where. Load the source into VirtualDub to confirm that every frame is a key frame, if so then the file is set up for smart rendering. If not report a bug to support.

I downloaded virtualdub and loaded a source clip. Never having used virtualdub, I don't know how to use it to determine that every frame of the source clip is an I frame?

Thanks for your help.

The frame number on the bottom of the display will show "Frame 8 (0:00:00.334) [K]" for a key frame and "Frame 9 (0:00:00.375) []" for a non-key-frame (or 'p' frame.) If you only see [K], you have a smart renderable file.

If I read the posts in this thread correctly (and there is hopefully a good chance that I have not) when the new, modified (?rebuilt) Cineform Prospect 4k finally (soon, we ALL hope) comes out, we will not be able to use it to render from the time line in Adobe Premiere CS4. Specifically what I have in mind is using Prospect 4k to render from Premiere
CS4 timeline at 1920x1080 30p to 720x480 30p for using Adobe Encore CS4 to render MPEG2 for DVDs. Will this be possible, or in order to do this, must we use some other application?

Yes that should have worked. I can only guess there was a setting mismatch some where. Load the source into VirtualDub to confirm that every frame is a key frame, if so then the file is set up for smart rendering. If not report a bug to support.

Virtualdub shows it to be NOT smart renderable--frames alternate as [K] [] [K] [] ...
I've submitted a ticket to support.

Cineform tech support advised that they have found the bug and will release a new build with a fix next week.