search for: bitrate_averag

When I run ogginfo on a .ogg file I created with oggenc (RC3), it lists some things that I have questions about: 1. Ogginfo lists bitrate_average and bitrate_nominal. Now, bitrate_average (I assume) would mean the overall bitrate average for the entire file but what does bitrate_nominal mean? 2. How is the serial number created? Can I tell something specific about an .ogg file by looking at it? As a side note, a thank you to those develop...

...reamed ogg and got this: --------------------------------- E:\>ogginfo radio4.ogg filename=radio4.ogg erial=1037942235 header_integrity=pass vendor=Xiphophorus libVorbis I 20011217 version=0 channels=2 rate=44100 bitrate_upper=none bitrate_nominal=96016 bitrate_lower=none stream_integrity=pass bitrate_average=65 length=182692.561270 playtime=3044:52 stream_truncated=true total_length=182692.561270 total_playtime=3044:52 <----------------- what winamp also thinks. E:\> ---------------------------------- While this looks allright, there appears to be some errors: Obvio...

After accidentally ogginfo-ing a WAV file, I'm wondering if there's any reason I shouldn't commit my fix that breaks out of the current file test if header integrity fails. Is there any case where the header integrity will fail but there is still any useful information to get out of the stream? I don't think so... -- Kenneth Arnold <ken@arnoldnet.net> - "Know

...found at approximate offset 3530268 bytes. Corrupted ogg. <p>---------- ogginfo rc3 erial=715851111 header_integrity=pass <snip> vendor=Xiphophorus libVorbis I 20010813 version=0 channels=2 rate=44100 bitrate_upper=none bitrate_nominal=128000 bitrate_lower=none stream_integrity=pass bitrate_average=132758 length=212.240000 playtime=3:32 stream_truncated=false total_length=212.240000 total_playtime=3:32 ----------------- What could cause this? (Other than physical data loss.) This file never went anywhere. Ripped with grip, directly to a local hard drive... possibly a bad sector though, ha...

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