Hi devs, I am developing winLAME, a frontend for LAME, and it also supports Ogg Vorbis decoding and encoding. I've got a question about the new API function vorbis_encode_init_vbr(). Do I have to call vorbis_encode_init() before to set the bitrate(s)? And what is a good default value for the "base_quality" parameter? I read on the mailing list that ABR use in Ogg Vorbis is not so good. Should I disallow the user to set the nominal bitrate in the winLAME UI? And does VBR (setting "max_bitrate" and "min_bitrate") work? btw: good work dev team! I've waited for RC3 for some weeks :-) bye Michael -- http://winlame.sourceforge.net <<-- the only *nice* windows UI for LAME :) http://sourceforge.net/projects/winlame <<-- sf project homepage contact: Michael Fink <vividos@vividos.de> --- >8 ---- List archives: http://www.xiph.org/archives/ Ogg project homepage: http://www.xiph.org/ogg/ To unsubscribe from this list, send a message to 'vorbis-dev-request@xiph.org' containing only the word 'unsubscribe' in the body. No subject is needed. Unsubscribe messages sent to the list will be ignored/filtered.
Hi devs, I am developing winLAME, a frontend for LAME, and it also supports Ogg Vorbis decoding and encoding. I got some questions about the new API functions. What do the new functions in vorbisenc.h do, and in which order do they have to be called? Are there more ways to init encoding? As I have a configuration page for Ogg Vorbis in the winLAME wizard, what options should be on that page? Currenty the user can set the nominal bitrate. Should I only allow the user to adjust the "base_quality" factor? What is a decent default value? thanks for help in advance, and thanks for releasing rc3! bye Michael -- http://winlame.sourceforge.net <<-- the only *nice* windows UI for LAME :) http://sourceforge.net/projects/winlame <<-- sf project homepage contact: Michael Fink <vividos@vividos.de> --- >8 ---- List archives: http://www.xiph.org/archives/ Ogg project homepage: http://www.xiph.org/ogg/ To unsubscribe from this list, send a message to 'vorbis-dev-request@xiph.org' containing only the word 'unsubscribe' in the body. No subject is needed. Unsubscribe messages sent to the list will be ignored/filtered.
> I've got a question about the new API function > vorbis_encode_init_vbr(). Do I have to call vorbis_encode_init() > before to set the bitrate(s)? And what is a good default value for the > "base_quality" parameter?No. Call one of 'vorbis_encode_init_vbr()' or 'vorbis_encode_init()'. These are the high level calls that do encode setup for vbr or bbr in one step. I'm filling in the last pieces of the full interface now. The remaining vorbis_encode_setup_vbr(), vorbis_encode_setup_managed(), vorbis_encode_setup_init(), and vorbis_encode_ctl() are for the fully tweakable interface setup and I'll have them documented later for rc4.> I read on the mailing list that ABR use in Ogg Vorbis is not so good.No, that's not what we meant; ABR forces bitrate management on an encoder that's VBR natively and always has been. The ABR/BBR/CBR is good, but not nearly as good as the VBR. The VBR is so sweet as to make a strong man weep. VBR quality will always beat ABR for a given file size. Bitrate management should only ever be used when there's a reason to do so (like streaming). The only reason I'm adamant about using VBR is that users used to MP3 are, by default, going to latch onto bitrate settings, and end up shooting themselves in the foot by producing ABR files instead of higher quality VBR for no good reason. Those who stream, naturally, have a very good reason to use bitrate management, and they should not be discouraged from doing so. Monty --- >8 ---- List archives: http://www.xiph.org/archives/ Ogg project homepage: http://www.xiph.org/ogg/ To unsubscribe from this list, send a message to 'vorbis-dev-request@xiph.org' containing only the word 'unsubscribe' in the body. No subject is needed. Unsubscribe messages sent to the list will be ignored/filtered.