[Colin Anderson]

Hi John,

Thanks for setting me straight on this question. It’s been bugging me for ever. The file Video properties of my footage shows me Data rate and Total bitrate (which number should I care about?). Both are in the range of 16900 to 17340kbps which is slightly higher than 16000kbps. Is that a big enough difference in your opinion? Both .m2ts and .avc renderings produce compliant files when taken into DVDA. Both take around the same amount of time to render. I read somewhere that rendering in video elementary stream (.avc) in Sony Vegas sometimes desaturated the colors. But again, I haven’t been able to compare original footage and rendered footage side by side.

By the way, do you know Magix Video Pro X3 ?
It claims to do smart rendering of AVCHD video.

Thanks

[Colin Anderson]

You know what, your trick works really well! Thanks a lot!

[Colin Anderson]

Actually, I got it to work. Turns out that I can enable de-interlacing in Power DVD 10 and pick the method if I do it before loading the disk.

[Colin Anderson]

I think I understand the reason now. I think. It’s because Power DVD 10 disables all it’s advanced options such as hardware acceleration and de-interlacing when playing Blu-Ray disks because by default it assumes all Blu-Ray disks are progressive scan. In addition, my TV, in PC mode, apparently doesn’t perform any de-interlacing because, once again I assume that it figures there’s no need for de-interlacing.

Does that make sense?

[Colin Anderson]

Ok I get it. This can only work if you have enough footage to spare beyond the frame you want to freeze. Like you couldn’t apply this method if you wanted to freeze at the very last frame of your footage, correct?

[Colin Anderson]

Thanks for the idea Mike. I’m not sure what that procedure is intended to produce. Is that prior to taking a snapshot or to slow down the footage to a point where it’s “frozen”? I tested it out on a footage. I didn’t know what you meant by “Move over the desired freeze length” so I moved the cursor to the right or the first two velocity points and followed the rest of your directions. If I can’t use the save snap shot feature as is, I think I’ll stick with my workaround of rendering the isolated frame as an image sequence.

Thanks.

[Colin Anderson]

I’m currently using Vegas Pro 10 but I had the same issue in Vegas Pro 9. I’m aware that others are having the same issue.

Trust me I’m not that picky in terms of comparison. The difference between video and still is very noticeable, both in the preview and the final render.

I’m doing this as instructed in the manual. Could it handle m2ts files differently? That’s all I’ve been working with since I started working with Vegas.

[Colin Anderson]

The trick is to bring compliant audio and video files into DVDA. Once that’s taken care of, the only elements that will require re-encoding by DVDA are any page that contain buttons and text added withing DVDA.

In the end my project only took DVDA 4:30 hours to complete and not the estimated 122 hours.

Cheers.

[Colin Anderson]

Man, coming back to this old thread and seeing how long my posts are, it’s no wonder only one person other than myself has read them. lol

Anyway, I understand and figured out a few things since my original post.

In the end, after rendering all audio and video to compliant formats prior to bringing them into DVDA, the only elements DVDA had to re-encode were the menu pages because of added buttons and text. And even though as it begins the rendering process it would estimate some 90 hours or so to complete, it really only took 4:30 hours.

Cheers.

[Colin Anderson]

Nevermind,

I’ve figured out that when it comes to the menu pages, set it to whatever space allows. I had enough space left to set the bit rate to 40 000 so that’s what i did.