ramman | 15 years ago | 2 comments | 3.0K views
It has been mentioned in a number of places that certain CODECs only handle certain resolutions. I have found, after much playing with BT that if you pick a resolution not supported by a CODEC and then export as movie, when the rendering begins the video screen locks up with garbage on the BT viewer. Sometimes a specific CODEC will work but produce a terrible avi file due to a mismatch. Some time the CODEC will compile when you set it for medium anti allizing quality but fail and lock up the system if you select higher quality. Is what I have just discribed the usual response of BluffTitler or is it my setup? Also has any one compiled a list of the different CODECS and what resolutions they run for and which will crash them?
Welcome to the codec hell :)
First I want to stress that you should only use compression if the video file is the final product. If you are planning to import the BT generated video file into your NLE or other video tool you should never use compression.
Compression should always be postponed to the very end: when you press the BURN TO DVD button, or EXPORT AS FLV button.
Yes, some codecs have weird limitations. Some demand that the horizontal resolution is divisible by 32 (or even 64), some work only with a limited number of resolutions, some have been designed for a specific application, some are buggy (please don't blame BT for a buggy codec),...
BT simply lists all codecs that are installed on your computer. That does not mean that all those codecs should work fine. As long as you don't have the technical documentation for that specific codec there's nothing else you can do than trial and error.
michiel, 15 years ago
Thank you. That worked perfectly. Before knowing the correct settings I could not get it to show transparency so I used the Huff CODEC. It did a reasonable job of compression but nothing like the lagarith CODEC which increased its lossless compression beyond the Huff by a factor of 10. The only downside I find is that it really slows down VEGAS during playback and rendering. The final rendered file works great. I'm guessing that Vegas decompresses real time and that's where the slowdown occurs.
ramman, 15 years ago
