Comments

Sunfox wrote on 9/14/2003, 5:26 PM
Hello? Am I the only one to have ever noticed this?
Chienworks wrote on 9/14/2003, 5:32 PM
Probably not the first one to notice it, but possibly the first to be concerned over it. I noticed this and assumed it was a limitation of the format. It never occured to me that i might want to use other rates besides those listed.
Sunfox wrote on 9/14/2003, 9:50 PM
Well, the thing is, at 640x480 resolution there is a *big* difference in quality and file size between 1mbit and 2mbit. So far the best compromise I've found is a VBR average of 1mbit and peak of 2mbit, but the file's still a bit bigger than I want it for web download (I'd like maybe 1.2 average and 1.5 max).

It's certainly not a format limitation - Windows Media Encoder (which has nearly identical options to Vegas' WMV encoder) allows video rate tweaking down to the last bit. But due to long rendering times in Vegas - never mind WME - using it isn't really an option.

I can't see why Vegas would allow me to pick 998 or 999 kbit, but not 1001 or 1002. Silly.
SonyTSW wrote on 9/14/2003, 11:57 PM
If you are using Vegas 4.0d, type in all of the digits for the bitrate value you want to use. For example, type 1572864 for 1.5 Mbs (1.5 * 1024 * 1024). Due to the way it currently handles display of this value, it does not always display it as expected but Vegas 4.0d does properly maintain the value internally (earlier versions do not).

You may find it useful to compare the profiles generated by Vegas and from the Windows Media Encoder 9. These files are in XML format and have a .prx extension.

To have Vegas 4.0d create a Windows Media profile when it renders, you'll need to enable a hidden pref to do this (search for "profile"). Just remember that it will always store a profile for every Windows Media render from Vegas until you turn it off.

Sunfox wrote on 9/15/2003, 3:28 AM
Excellent news! Do you know if this still works if I type in shortcut values, like "1.5 M"?

I prefer to do the WMV render direct from Vegas because I find (with a DV source) that I end up with nicer quality on text overlays, slow-motion effects and certain other effects, compared to rendering the project to a DV AVI and then using WME9 to encode it. Not sure why, perhaps it's how (or when) Vegas does de-interlacing.
SonyTSW wrote on 9/15/2003, 12:49 PM
It will work, as long as the digits before the decimal point are different than how the current value is displayed.

Here's the workaround to make sure it is using the value you want, but it's a little tricky. Let's say you want to use 1.5 M, and it currently displays 1 M:

1. Change this to 2 M
2. Click another tab, such as the Audio tab. This forces the values in the video page to be read. Since the 1 M has changed to 2 M this value is updated internally (to 2 * 1024 * 1024 = 2097152).
3. Click the Video tab
4. Change the 2 M value to 1.5 M.
5. Save the template, click OK, or click another tab. Doing this will read the values and it will update the bit rate value internally to 1.5 * 1024 * 1024. It will display as 1 M though (because it currently uses integer arithmetic for display).

I suggest that you save your modified template, and include 1.5 M in the name and description text for future renders.

I've noted this problem in our bug database.

Addendum: This applies to the Windows Media 9 format only in the custom settings dialog. WM8 does not handle values like 1.5 M properly, it truncates the value after the decimal point.