Vegas Pro's method of working with still images is leaving me a little confused. I'm doing little slide show thingies to be turned into HTML5 video.
I want an oddball video output size: 950 wide by 310 high.
I've got my project settings in Vegas set to those dimensions, and I'm careful to set the output render ALSO to those dimensions. A quicktime 7 mov is the target.
I have carefully set the Project properties to NOT resize the media. But it seems to be happening anyway. I have all sorts of oddball size PNG files as input images, but they are ALL bigger than 950 X 310, so I would expect that they would all MORE than fill the preview screen and, barring some event pan/crops or suchlike, the output render image should be filled COMPLETELY with leftover image borders hanging off the plate out of frame. Nope.
If I do load a pan/crop on one of the stills just to see what it says about the still image (don't actually make any changes, mind you), the x-y size does claim to be the original size of the image, e.g., 1280 X 844, but the images DON'T take up the whole preview screen and they DON'T take up the whole final rendering. I have Windows utilities that simply inform me of the sizes of any windows on the screen, and the final rendered video is showing up in VLC as being exactly 950 X 310, but the 1280 X 844 input still is only taking up about half the video's on-screen real estate. It's a little rectangle floating in a big black void, only taking up about a third of the 950 X 310 space.
I was more or less expecting a one-to-one correspondance of pixel dimensions between my input stills and the output rendering (which, by the way, OUGHT to be pretty laser sharp video since I THOUGHT no pixel interpolating would be happening to introduce any blurring).
I assumed no adjustments to the scaling would happen unless I started changing scale in pan/crop, but nope, I'm scaled all OVER the place and can't make it stop.
What am I not getting about the relationships between input image pixel dimensions and output rendering pixel dimensions?
Thanks in advance.
Steve
I want an oddball video output size: 950 wide by 310 high.
I've got my project settings in Vegas set to those dimensions, and I'm careful to set the output render ALSO to those dimensions. A quicktime 7 mov is the target.
I have carefully set the Project properties to NOT resize the media. But it seems to be happening anyway. I have all sorts of oddball size PNG files as input images, but they are ALL bigger than 950 X 310, so I would expect that they would all MORE than fill the preview screen and, barring some event pan/crops or suchlike, the output render image should be filled COMPLETELY with leftover image borders hanging off the plate out of frame. Nope.
If I do load a pan/crop on one of the stills just to see what it says about the still image (don't actually make any changes, mind you), the x-y size does claim to be the original size of the image, e.g., 1280 X 844, but the images DON'T take up the whole preview screen and they DON'T take up the whole final rendering. I have Windows utilities that simply inform me of the sizes of any windows on the screen, and the final rendered video is showing up in VLC as being exactly 950 X 310, but the 1280 X 844 input still is only taking up about half the video's on-screen real estate. It's a little rectangle floating in a big black void, only taking up about a third of the 950 X 310 space.
I was more or less expecting a one-to-one correspondance of pixel dimensions between my input stills and the output rendering (which, by the way, OUGHT to be pretty laser sharp video since I THOUGHT no pixel interpolating would be happening to introduce any blurring).
I assumed no adjustments to the scaling would happen unless I started changing scale in pan/crop, but nope, I'm scaled all OVER the place and can't make it stop.
What am I not getting about the relationships between input image pixel dimensions and output rendering pixel dimensions?
Thanks in advance.
Steve