Resizing bug new to Vegas 5d

Laurence wrote on 2/14/2005, 6:53 AM
Well I finallly figured out why I can't change the aspect ratio any more from 4:3 to 16:9 without screwing up and resizing the interlace lines. The latest version of Vegas (5d) doesn't do this properly anymore! I just went back to version 5a and the problem is fixed. Something must have gotten screwed in the SD world when Sony was revamping Vegas for their new HDV cameras! I'm dead sure about this. It wasn't an Ultimate-S problem after all! This is a pretty major bug. Where should I report it?

Comments

BillyBoy wrote on 2/14/2005, 6:57 AM
Interesting, I don't see what you've seen having converted 4:3 to 16:9 on several projects.

Maybe give a step by step what you did so others can try to duplicate it doing the same steps. Its a little harsh to play the "bug" card until its confirmed and can be duplicated. Often, problems are system based or due to source material or work flow.
Laurence wrote on 2/14/2005, 7:17 AM
I'm absolutely sure about this one.

Here's how to see it.

1) Load a 4:3 60i project into vegas, looking at the picture on an external monitor with a 1392 capture/preview device set to Best (Full) resolution.

2) Find a spot where you can see the typical motion interlace jumping back and forth between the two fields.

3) Run Ultimate-S 4:3 to 16:9 conversion (or do the manual steps which do the same thing)

4) With version 5a, I still have the same interlace jumping back and forth between the fields. With version 5d, I have wavy vertical lines where the interlace pattern has been expanded up and down.

5) Render this and you'll see a perfect example of why it is not a good idea to resize interlaced video. It looks absolutly horrible!

The project I was working on run and gun type project with lots of camera movement, fast zooms and pans. It is a real showcase for this bug. It looks horrendous when converted in 5d and fine when converted in 5a. It's a bug all right. What the current version is doing is simply stretching the image vertically, interlace lines and all.
Laurence wrote on 2/14/2005, 7:25 AM
All the way back to "a"! I'm going to start keeping older builds of Vegas from now on.
Laurence wrote on 2/14/2005, 8:49 AM
Does anyone know where I can get a 5b or 5c? 5a won't run scripts like the "snapshot to clipboard". I'm definately going to start keeping Vegas revisions from now on.
jetdv wrote on 2/14/2005, 8:52 AM
There is no reason why 5.0a won't run a "snapshot to clipboard" script.

Sure you're not trying to run a Vegas 4 version of the script???
JJKizak wrote on 2/14/2005, 9:10 AM
My post above (converting 4 x3 to 16 x 9) my have some relavence.

JJK
Laurence wrote on 2/14/2005, 9:23 AM
Yes JJK, I just read your posts. You are describing exactly the same thing as I am. If you can get your hands on an older revision of Vegas 5, you'll see it does exactly what you want.
Laurence wrote on 2/14/2005, 9:32 AM
I had just done a snapshot to clipboard a few minutes before I downgraded to Vegas 5a. When I went back to it after the downgrade it no longer worked. I'm using the script off the VASST site with the references to "Sonic Foundry" changed to "Sony". In Vegas 5d it saves the current state, sets the preview options to maximum quality with an interpolate deinterlace, saves a snapshot to the edit buffer, then returns my preferences back to how they were. In 5a it does the same thing except that it also moves the current frame back to the first frame of the project, thus giving me a beautiful maximum resolution deinterlaced capture of the first black frame in my project! That is a whole lot easier to live with than not being able to convert to 16:9 though! I'll stick with the older version until this is fixed.
Liam_Vegas wrote on 2/14/2005, 9:50 AM
Definitely some scripts that work in 5.0b and above will not work in 5.0a.

Doesn't explain the problem you have with 16:9 vs 4:3 - but at least you can put the script thing behind you.
jetdv wrote on 2/14/2005, 10:10 AM
Definitely some scripts that work in 5.0b and above will not work in 5.0a

This is true. However, taking a snapshot is not one of them.

I do seem to recall a problem taking snapshots if the script used a specific command to take a snapshot at the cursor location. If I remember correctly, the solution was to take the snapshot twice. So, if the script is edited and that line is duplicated, it just might work.
farss wrote on 2/14/2005, 1:05 PM
For what it's worth I've been having much the same dramas with HDV footage going from CF HD 50i footage to SD mpeg-2, going to WMV 9 720p is fine. I'd imagine this can be cured by selecting Reduce Interlace Flicker on the source. While this might 'fix' the problem from what I'm seeing somethings have been screwed up badly, it'd be nice to get some feedback from the Sony guys on just hwat's going on.
Bob.
Laurence wrote on 2/14/2005, 1:28 PM
Yeah that makes sense, if you deinterlace you can't see the problem going from SD 3:4 to 16:9 either since the resizing of the interlace lines is covered up by the deinterlacing. I have reported this Sony already by the way. I sent it in as a "tech support request". In the mean time, the older revision of Vegas is getting me by.
boomhower wrote on 2/14/2005, 1:39 PM
I've seen a few people talking about problems with 5.0d ....does this seem to be isolated to HDV only? I was going to update to D so I could get B but wanted to see what the consensus was.
Jsnkc wrote on 2/14/2005, 1:59 PM
.