First Sony Vegas Slide Show

[mlong30]

Hi,

I just purchase a new digital camera. Canon 20D.

I'm trying to create a slide show using pictures from my new camera in Sony Vegas 6.

Can some tell me why my movie look like there is a heat wave going across the screen, when I pan and zoom in the video?

I de-interlaced the pics in photoshop, I added blur, still looks like a heat wave going across the screen.

Is there something I'm missing that needs to be done to the pic?
I don't have this problem if I use ProShow Gold.

This file is 10mb, I'm trying to make it smaller. It only has two pics in the slide for an example.

http://home.comcast.net/~mlong219/SonyVegas_None_Interpolitefield.wmv

Thanks.


Matt

[jtoolman2000]

You are deinterlazing images???? WHY!
Just load then onto the time line as they come from the camera. Throw your transitions, pans and zooms, music track and render. I do that all the time with vegas. You do not need to do anything in PS execpt maybe correct color, contrast ect.

[mlong30]

<< Just load then onto the time line as they come from the camera. Throw your transitions, pans and zooms, music track and render. >>

I've tried that, and I still get the same results.



Matt

[Cornucopia]

I agree, DON'T deinterlace. In fact, how are you outputting this? 'Cuz you may want to be using a 24P project and outputting to the Mainconcept MPEG2 encoder(with a 24P profile/template selected). This would keep it as progressive (with pulldown added).

What is the resolution of these pix? Maybe Vegas isn't doing the best job of resizing them. You could batch resize them in Photoshop 1st (e.g. 4Kx2K --> crop to nearest 4:3 or 16:9 --> 720x480 --> SaveAs). Then load the results into Vegas. Vegas would have less of a job to do. However, it may have been making use of the hirez for subpixel shifting during a pan (Like AfterEffects. I would hope), so this is just something to test...

Scott

[mlong30]

<< I agree, DON'T deinterlace. >>

I never do, I just tried it to see if that would make a difference. Just getting desperate.


<< In fact, how are you outputting this? 'Cuz you may want to be using a 24P project and outputting to the Mainconcept MPEG2 encoder(with a 24P profile/template selected). This would keep it as progressive (with pulldown added). >>

I've been using 29fps using Frameserver to Procoder and Cinema SP. I'll try using 24p.


<< What is the resolution of these pix? Maybe Vegas isn't doing the best job of resizing them. You could batch resize them in Photoshop 1st (e.g. 4Kx2K --> crop to nearest 4:3 or 16:9 --> 720x480 --> SaveAs). >>

The pics were taken at 3504 x 2336 then I crop them down to 720X480 in PhotoShop. I've tried JPG, and TIF files.


I'll try to post a couple of pictures to see if anyone else can duplicate the same problem.

Thanks.

Matt

[hech54]

I've used pics from my Nikon D70 at full size(1504 x 1000) with no problems with my OLD Ulead Movie Factory 2SE to create slideshows. You may want to try that as well.
Unless you are cropping the originals to frame them better of course.

[mlong30]

<< I've used pics from my Nikon D70 at full size(1504 x 1000) with no problems with my OLD Ulead Movie Factory 2SE to create slideshows. >>

I still have a copy of that, I never had an issue with either. I just didn't like being limited, so I moved up to Sony Vegas.

Matt

[hech54]

No...I meant don't resize them...sorry...

[trossin]

I started using Vegas Studio 6 (the cheap $60 version) and noticed horrible roping when doing pan and zoom. I'm using the highest quality and it just looks like junk. It also takes an hour to render a 2 minute slide show (my 0.6 GHz machine is showing it's age). I just got a free version of Ulead Video something with my new DVD drive and it renders pan and zoom slide shows much faster and the results look way better.

I think the cheap Vegas is junk. Not to mention the cheap authoring tool that came with it sucks as it only does PCM audio which is totally useless as the audio eats up all the disk space. Of course the trial version disables all MPEG support so I didn't find this out till I sent them money which I'll never do again. I'll stick with Ulead in the future (I sent them money in the past and have always been happy with the speed and quality of their tools).

[mlong30]

Here is a sample pic. Only the levels were adjusted to correct exporsure.

I'd appreciated if some one could drop this pic into Sony Vegas, and tell me if they have the same problem.

http://home.comcast.net/~mlong219/Bike1.jpg


Thanks.

Matt

[mlong30]

Here is a sample pic. Only the levels were adjusted to correct exporsure.

I'd appreciated if some one could drop this pic into Sony Vegas, and tell me if they have the same problem.

http://home.comcast.net/~mlong219/Bike1.jpg


Thanks.

Matt

[mikiem]

"I'd appreciated if some one could drop this pic into Sony Vegas, and tell me if they have the same problem. "

Supersampling & motion blur help but won't eliminate the prob in Vegas. My suggestion would be to try some of the image based slide show prog., including the Microsoft slide show applet, or photostory, or going back to proshow. Rendering separate video clips you can import into Vegas should let you use various transitions &/or FX & get around what I feel is Vegas' biggest limitation -- resize stinks. Haven't used it for some time but prem used to be the same way.

I *Think* the problem is Vegas insists on dealing with the images line by line as video rather then dealing with them on a pixel by pixel basis as an image editor would. That said, don't know that any way you do it it'll look good on a CRT TV because of interlace flicker on thin, sharp, highlights for engine. That may be one reason some folks use morphing for a similar zooming effect?

[dipstick]

Nice Bike. Nice camera. Nice picture considering you used 800 ISO setting. The problem I see is that you used Flash. This really highlights the crome wich contrasts greatly with the blacked out engine cases. It makes it tough to pan becouse of the high contrasts.

I don't use Vegas, so I can't coment directly on it. With shots like this, it may be better to do all your pans at close range to keep the edges as large as posible. If you zoom out too much, the edges become very small and create image flicker problems.

I did this pan and zoom using Wax2 (free), I imported the image at full size. I used a lot of compression to get the file under the 2 mb limit, so the quality isn't as good as I'd like, but you can get the effect:

bike.m2v