I've been working on a project of still photo montages where an image is blown up and the camera pans and zooms across the stills.
It was frustrating to discover that Vegas seems to limit the resolution of imported still images to the resolution of the video for the project. So when you zoom in on a still, even if the original was a higher res, you get a pixilated image.
i thought that I might be able to solve this problem by setting the project resolution to HD, thinking it would allow for higher res stills, and then rendering to standard res. This didn't seem to work. At least in the preview window the pixilation got worse for some reason when I increased the project resolution.
I did come up with one work around which was a pain, but I did end up using on some images that just looked too bad to leave as is. What I did was, in an external editor, I split the image into multiple image files. and then imported them as separate stills on separate video tracks. then I had to copy position settings across the tracks and compensate for which piece of the image I was working with (top bottom etc.) This connected the two images as the camer pans and zooms.
Vegas seems to limit your imported still image by its longest dimension. For this reason I had a problem with a tall skinny image, so I cut it in half and panned and zoomed around each with the same movement settings, while subtracting the height of the bottom piece from the y position of the top piece.
I think if you had a square image you'd have more of a problem, because if you used my method, you'd have to spit it into 4. One solution that I see here would be if you had a part of an image that you wanted to zoom in on (a face for instance) you could cut out that face and save as a separate high res image in an external editor and them overlay it on a different track in vegas over the full sized image.
One other thing I should note is that I couldn't get this method to work well with the smooth motion setting for key frames, because each piece of the image would be moving at different times and it left gaps. I had to use linear instead.
Has anyone else found a way to get around this limitation? A script maybe?
It was frustrating to discover that Vegas seems to limit the resolution of imported still images to the resolution of the video for the project. So when you zoom in on a still, even if the original was a higher res, you get a pixilated image.
i thought that I might be able to solve this problem by setting the project resolution to HD, thinking it would allow for higher res stills, and then rendering to standard res. This didn't seem to work. At least in the preview window the pixilation got worse for some reason when I increased the project resolution.
I did come up with one work around which was a pain, but I did end up using on some images that just looked too bad to leave as is. What I did was, in an external editor, I split the image into multiple image files. and then imported them as separate stills on separate video tracks. then I had to copy position settings across the tracks and compensate for which piece of the image I was working with (top bottom etc.) This connected the two images as the camer pans and zooms.
Vegas seems to limit your imported still image by its longest dimension. For this reason I had a problem with a tall skinny image, so I cut it in half and panned and zoomed around each with the same movement settings, while subtracting the height of the bottom piece from the y position of the top piece.
I think if you had a square image you'd have more of a problem, because if you used my method, you'd have to spit it into 4. One solution that I see here would be if you had a part of an image that you wanted to zoom in on (a face for instance) you could cut out that face and save as a separate high res image in an external editor and them overlay it on a different track in vegas over the full sized image.
One other thing I should note is that I couldn't get this method to work well with the smooth motion setting for key frames, because each piece of the image would be moving at different times and it left gaps. I had to use linear instead.
Has anyone else found a way to get around this limitation? A script maybe?