What's wrong in VegasPro17 and not in VegasMovieStudio16?

3POINT schrieb am 13.02.2020 um 17:02 Uhr

I'm having following issue:

I made a project in VMS16, just putting a few HDV clips on the timeline and saved that as a project. This VMS16 project I open in VPro17 and stabilize each event (using Vegasaur batchstabilize). Then I render this project, doesn't matter which codec, for testing I use XDCAM. Rendering goes superfast, about 60-70 frames per second.

Now I make a new blanc project in Vpro17 and put the same HDVclips on the timeline as I did in the VMS16 project. Also I stabilize each event and render the project to XDCAM again. Rendering is now terribly slow 6-7 frames a second, there are glitches and sometimes even a total Vegas crash.

What's wrong in VegasPro17 and not in VegasMovieStudio16? Of course I use for both last builds and also videopreferences are exactly the same.

Kommentare

3POINT schrieb am 13.02.2020 um 17:56 Uhr

It becomes even more weird, when I use only an empty VMS16 projecttimeline in VegasPro17 for project building, everything works smooth and fast. Do I start with an empty VegasPro17 timeline, only troubles....

bvideo schrieb am 13.02.2020 um 22:52 Uhr

An obvious possible difference is the default project properties for starting the two programs. After moving the project to VPro, it carries the properties set up in VMS. Are they identical to starting w/ VPro?

3POINT schrieb am 14.02.2020 um 09:52 Uhr

I found the difference and the setting causing the low speed rendering in VegasPro:

Strange thing is that I'm using HDV interlaced and render also to interlaced, so I didn't expect a project deinterlace setting could influence this.

matthias-krutz schrieb am 14.02.2020 um 11:18 Uhr

Yes, Movie Studio does not support the deinterlace method Smart Adaptive. I like to use it, although it slows down the preview and rendering. To make Vegas run stable with Smart Adaptive, I always have to set the dyn RAM to zero. I think this is an underestimated reason for instability. You may also be affected, even though you think you may not be using it.

3POINT schrieb am 14.02.2020 um 17:46 Uhr

Personally I don't like the deinterlace methods in Vegas at all. I leave interlaced, interlaced. My TV handles that perfectly, so I don't deinterlace. Strange that a deinterlace method setting in Vegas has influence when it is not used.

matthias-krutz schrieb am 14.02.2020 um 18:47 Uhr

Since my footage almost always has to be stabilized, I looked for a good workflow. The new video stabilization delivers good results with progressive material, but not good results with interlaced material. So I add 50i footage to a 50p project and use Smart Adaptive. Then the result is perfect if the stabilization happens at event level. If no rework is necessary, you can leave interlaced, interlaced.