similar to: oggenc and Encoding with VBR

Hi all, I'm to hit about aprox the same encoding settings (ie bitrate,filesize, quality) with talk radio shows that are currently encoded with Real Producer in 16kbit acelp (maybe cs-acelp). Currently 2 hours of talk radio encoded in a .rm container yields about 16.3 meg file. With speex in wideband vbr I'm getting very good quality results, but with a larger filesize of 19.1 meg.

With this patch, ogginfo will display bitrate information (upper/lower/nominal/average bitrate). It is patched against today's CVS code (main branch). I am also working on true VBR support in oggenc (the user can specify the minimum & maximum bitrate) and will send a patch when it's done. <HR NOSHADE> <UL> <LI>application/x-gzip attachment: ogginfo-diff.gz

I'm sorry if this question has been asked before; I've looked through the archives and haven't seen anything. The problem I'm seeing is that oggenc's VBR encoding doesn't seem to pay attention to any sort of bitrate limitation, either the -m or bitrate_hard_min settings. It isn't that it temporarily dips below the minimum; the average for the whole (in this case,

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?

Hello everybody! Some questions concerning oggenc: 1 why is it called oggenc? (vorbisenc would make more sense) 2 Is it true, that oggenc uses only some predefined codebooks (depending on -q)? 2.1 Are they just "random" books, or were they "optimized" in any way 2.2 Is it possible, that some codebooks are stored in the header, but are never used (even in long (>3min) files)?

>>I realize that I may have unintentionally been misleading you by leaving some information out. That error report from ogginfo keeps going, repeating the same 3 errors (as above) over and over again. It ends after a stream_truncated=true, not giving a final header_integrity=fail. (Perhaps because there's not another packet?) Then it reports a total playtime of 0. > >Yes,

Hi, I have the following config; 4 ices hosts, ices-kh60 2 are streaming to icecast2.1kh5 server. 2 are streaming to icecast2.2kh9 server. The 2 hosts streaming to icecast2.2kh9 are crashing (machine crash...) twice a week. I was thinking of hardware problem, but it think it's not the case. To feed ices, I use: rawrec | ices Which I found very sensitive and may cause machine handup if

--- Hal Vaughan <hal@thresholddigital.com> wrote: > I've been reading the info on Sourceforge about Flac, but there's one > thing > I'm not clear about (and it looks like Flac may not support this > yet). > Before I installed it, I wanted to know if Flac would do what I need. > > I want to be able to record shows on the radio (I have a radio hooked >

This is a bit of a worry. I did not receive either of Michael's e-mails, only this one from Smoerk. I had to read the archives to read the reply. Is it just me? I'm having trouble reading stderr, it just doesn't seem to work in Windows for some reason. I'll wait for progress functionality when a decent DLL is available. Cheers, Ross Levis. moerk wrote: >On Thu, 21

--- vorbiscomment/vorbiscomment.1 | 4 +--- 1 files changed, 1 insertions(+), 3 deletions(-) diff --git a/vorbiscomment/vorbiscomment.1 b/vorbiscomment/vorbiscomment.1 index 0108e78..2bceb83 100644 --- a/vorbiscomment/vorbiscomment.1 +++ b/vorbiscomment/vorbiscomment.1 @@ -39,13 +39,11 @@ Reads, modifies, and appends Ogg Vorbis audio file metadata tags. .IP "-a, --append" Append

Here is a list of current open bugs in debian bts, some of these bugs are probably fixed but I do not know how to test for them properly (like UTF-8) and others may not be important enough to hold up 1.0. bugs.debian.org/(bug num) libao 130816 - WAV device doesn't print error when device is full 150220 - Doesn't open OSS devices with O_NONBLOCK all the time vorbis-tools 128521 -

Dear authors of Vorbis, currently, the manpages that come with vorbistools are written in the traditional man(7) markup language. I am proposing to rewrite them into the semantic markup of the mdoc(7) language. I am willing to do the work. Both the man(7) and mdoc(7) languages have been around for decades, and are supported by the prevalent formatters: groff(1) on most Linuxes and mandoc(1) on

Hello, I just noticed that ogginfo is not properly detecting Ogg FLAC files. To fix the issue I will need to know what is the correct magic for Ogg FLAC and how big are the packet bytes. Please advise. -Ivo

Hello all, I wanted to ask some experienced users some settings about oggenc. 1. How can I setup oggenc so that I can DIRECTLY rip tracks off my audio cd? As we all know, audio cd doens't really have a file format that we can directly use. Do I HAVE to convert them to wav files then convert them to ogg files? 2. The options: -b -m -M with the bitrate of the audio file. If I set something

First let me say that I was absolutely astounded at the sound quality when using oggenc at q = -1 (around 50 kbps). So much so, that I'm anxious to try some of the lower bit rates that were mentioned in the announcement for 1.0: ... audio and music at fixed and variable bitrates from 16 to 128 kbps/channel. But I am having trouble finding how to use either oggdrop or oggenc to get these

Hi All, For my new file (and thus mp3) server I've decided to switch completely to Ogg Vorbis. This means having to reencode ~30GB worth of 128Kb MP3's, but i figured that it would all be worth the effort. So I downloaded the sources for libogg, libvorbis and vorbis-tools and fired up my trusty old compiler. libogg and libvorbis built and installed like a charm. Not so for

I just moved a bunch of shared code (like 4 copies of getopt) into a share directory within vorbis-tools. I also moved the UTF-8 code from oggenc into the vorbis-tools/share directory as well so that it could be used by all of the tools, since they all need to handle UTF-8 comments correctly. Header files for the shared code are stored in vorbis-tools/include. I have already fixed vorbiscomment

Hello folks I am encoding music to ogg vorbis format for the first time. From what i have researched, ogg vorbis is natively a vbr format. Also encoding using the -q switch is encouraged instead of specifying a bitrate through -b. Now, while encoding using -b i get this: Encoding "file.wav" to "file.ogg" at approximate bitrate 224 kbps (VBR encoding enabled) Notice

Hi, I'm trying to record something for about 24 hours but oggenc tells me that I have 203m remaining. Quote: durand at Deuterium ~> arecord -f cd -t wav | oggenc -b 192 -o file.ogg - Recording WAVE 'stdin' : Signed 16 bit Little Endian, Rate 44100 Hz, Stereo Opening with wav module: WAV file reader Encoding standard input to "file.ogg" at approximate bitrate

Hi, Regarding to my previous question, I think I have found out from oggenc source code that the correct way to initialize encoding is: vorbis_encode_init_vbr (or vorbis_encode_setup_managed for cbr etc.) vorbis_encode_ctl (to turn off or use avg bitrate management) vorbis_encode_setup_init By this way, there is no problem with encoded stream. However, there is no documentation of the three