Just got around to compiling RC3 under beos and came across an anomaly when using managed bitrates. I haven't changed the code for the beos encoder but I now get double the bitrates so vorbis_encode_init(&vi,mediaFormat.u.raw_audio.channel_count,(long)mediaFormat.u.raw_audio.frame_rate , -1, 128000, -1); now gives me vorbis files that average around 325 - 350. Is this now the correct behavior or is it a bugette. I noticed that oggenc still uses bitrate * 1000 but does not say it that is per channel or not. P.S. The beos build is broken from the rc3 tarballs, basically the libtool that gets built now says... "I can't cope with undefined symbol so you can't have a shared library" This means that libogg now only builds a static library in exchange for libvorbisfile sucessfully building (again static only) rather than breaking like before. Dave <p>--- >8 ---- List archives: xiph.org/archives Ogg project homepage: 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.
On Tuesday January 01 2002 9:46 am, you wrote:> > now gives me vorbis files that average around 325 - 350. >I'm getting the same thing when using KDE's audiocd:/ ioslave to encode to vorbis. Here's part of the output from running ogginfo on such a file: vendor=Xiphophorus libVorbis I 20011231 version=0 channels=2 rate=44100 bitrate_upper=none bitrate_nominal=128031 bitrate_lower=none stream_integrity=pass bitrate_average=342080 Strangely enough, I did try to define upper and lower bounds on the bitrate of this file, but it still says none. --- >8 ---- List archives: xiph.org/archives Ogg project homepage: 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.
> P.S. The beos build is broken from the rc3 tarballs, basically the libtool > that gets built now says... > > "I can't cope with undefined symbol so you can't have a shared library" > > This means that libogg now only builds a static library in exchange for > libvorbisfile sucessfully building (again static only) rather than breaking like before.I'm willing to accept patches for BeOS like we always have. Is this the same bug we were running into around beta3? jack. --- >8 ---- List archives: xiph.org/archives Ogg project homepage: 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.
>> This means that libogg now only builds a static library in exchange for >> libvorbisfile sucessfully building (again static only) rather than breaking like before. > >I'm willing to accept patches for BeOS like we always have. Is this the >same bug we were running into around beta3?I'll see what I can do, I ended up creating a BeIDE project in the end to get things working rather than tackling the build process. I wonder if it would be easier to maintain that than trying to sort out the libtool stuff. Its similar to the problem we had for beta3 except that was for libvorbisfile, now it affects libogg too. Dave --- >8 ---- List archives: xiph.org/archives Ogg project homepage: 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.
On Tue, Jan 01, 2002 at 03:46:52PM +0000, David Burnett wrote:> Just got around to compiling RC3 under beos and came across an > anomaly when using managed bitrates. > > I haven't changed the code for the beos encoder but I now get double > the bitrates so > > vorbis_encode_init(&vi,mediaFormat.u.raw_audio.channel_count,(long)mediaFormat.u.raw_audio.frame_rate , -1, 128000, -1); > > now gives me vorbis files that average around 325 - 350.There was an API change; for bitrate managed modes to work (any mode beign set up with vorbis_encode_init is now managed), vorbis_bitrate_addblock and vorbis_bitrate_flushpacket must be used as illustrated in encoder example. Modes set up with vorbis_encode_init_vbr do not require the API change, but using it for those modes as well will also work. Sorry for the surprise, I should have announced this on the development list. Monty --- >8 ---- List archives: xiph.org/archives Ogg project homepage: 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.
>> > now gives me vorbis files that average around 325 - 350. >This is to be expected. API additions mean that correct bitrates require >minor (and very simple) changes to any encoder. For true-VBR encoding, >there's a new init function (vorbis_encode_init_vbr(), I think) to use >instead of vorbis_encode_init(). >I know about the new API but the old API is still there and I would still expect it to work as before, i.e. to quote the *RC3 oggenc code* if(vorbis_encode_init(&vi, opt->channels, opt->rate, opt->max_bitrate>0?opt->max_bitrate*1000:-1, opt->bitrate*1000, opt->min_bitrate>0?opt->min_bitrate*1000:-1)) hould still give an encoded vorbis file with an average of around opt->bitrate if the -q flag is not used. If the new version vorbis_encode_init(...) is not a finished article then fair enough, but if it is then approx_bitrate_to_vbr(...) is way out with its approximations.>For bounded bitrates, things differ a bit more - see encoder_example.c for >what things should be like now.Well bitrates are what its about, most people are used to encoding to a bitrate rather than a 'quality'. For now I'll have to pick a few test pieces and guess a few approximations myself ;-) Dave --- >8 ---- List archives: xiph.org/archives Ogg project homepage: 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.
>There was an API change; for bitrate managed modes to work (any mode >beign set up with vorbis_encode_init is now managed), >vorbis_bitrate_addblock and vorbis_bitrate_flushpacket must be used as >illustrated in encoder example. > >Modes set up with vorbis_encode_init_vbr do not require the API >change, but using it for those modes as well will also work.Thanks Monty that sorted it out. Dave --- >8 ---- List archives: xiph.org/archives Ogg project homepage: 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.