similar to: File Info Question

>>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,

I have a CD ripped with RC2, ogginfo from 1.0 claims they are all "broken". ogg123 also goes a little wild with them. I'll experiment a little more, maybe play with xmms, etc. RC3's ogginfo do not see anything wrong with them... an example: ---------- ogginfo 1.0 New logical stream (#1, serial: 2aab0567): type vorbis Vorbis headers parsed for stream 1, information follows...

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

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

Hello everybody, I've put some functions/modifications into the Ogg Vorbis encoder source. (The new functions are in the first 500 lines of the oggenc.c, some definitions are in the oggenc.h) I hope, you can use it. Here is the full source (same source on 3 locations): http://www.geocities.com/mpxplay/oggenc.zip http://www.tar.hu/mpxplay/oggenc.zip http://www.extra.hu/galileog/oggenc.zip

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 hope that this is the appropriate venue for this question. If it's not, let me know and I'll take it elsewhere (perhaps vorbis-dev). Saved streams are great - it lets this norteamericano get his fill of BBC Radio 1's Essential Mix. Unfortunately, saved streams aren't seekable. Running ogginfo on the stream data gives: erial=1626603590 header_integrity=pass vendor=Xiphophorus

I hope that this is the appropriate venue for this question. If it's not, let me know and I'll take it elsewhere (perhaps vorbis-dev). Saved streams are great - it lets this norteamericano get his fill of BBC Radio 1's Essential Mix. Unfortunately, saved streams aren't seekable. Running ogginfo on the stream data gives: erial=1626603590 header_integrity=pass vendor=Xiphophorus

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

--- 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

Are there plans to incorporate aoTuV mode into vorbis, perhaps a commandline switch to make optionally available the aoTuV tunings? The abx results from aoTuV are impressive... http://www.hydrogenaudio.org/index.php?showtopic=21916&st=50&&#entry215109 -Dan

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,

hi guys, first of all, i'd like to ask if there any crossplatform software/service ( gui is also better, an online application like firefogg is great, or at least a command line tools for any platform) to combine theora videos, other than oggcat... i am doing some art projects that people should be able to remix featured theora videos and i find oggcat very usefull in theory but not in

Apologies if this is know. But I've spent most of today Googling for a way to get this working, and to me, something is wrong here. But it might well be me. Anyway... I've been trying to record direct from the soundcard into an ogg file. I came up with rawrec -t 10 | oggenc -r -Q -q 5 - > foo.ogg which partially works. ogg123 will play it, but ogginfo reports Warning: Hole in

Hi all, I've got a question on regarding how to find out the duration of an ogg vorbis file. Sorry if it should already be mentioned somewhere in the docs, but I couldn't find out how to do it the best way. So, I can read the [bitrate_nominal] field from the identification header (if it is set), find out the size of the audio data (by subtracting the size of the three headers from the

I found I have ripped the same CD twice with different machines. Cannot remember when, why, or how, but anyway. I've been using jack, here is relevant output: first one: 01/|\enc/|\128/|\[coding @0.67× done,129kbit] 02/|\enc/|\128/|\[coding @0.69× done,124kbit] 03/|\enc/|\128/|\[coding @0.66× done,124kbit] <etc> econd one: 01/|\enc/|\128/|\[coding @5.50× done,116kbit]

Thank you, ogginfo returned: ----- Note: Stream 1 has serial number 0, which is legal but may cause problems with some tools. New logical stream (#1, serial: 00000000): type vorbis Vorbis headers parsed for stream 1, information follows... Version: 0 Vendor: ffmpeg Channels: 1 Rate: 22050 Nominal bitrate: 35.333000 kb/s Upper bitrate not set Lower bitrate not set Vorbis stream 1: Total data

Hey guys, currently wrapping my head around the vorbisfile API. The stream callback interface is really nice ! Great work. I'm running into two snags using it though. a) getting ov_bitrate on a seakable stream returns a long. When I print it as %ld, I get Bitstream is 2 channel, 44100 Hz, 0 version, -2147483648 bitrate I get this same number for any vorbis file. I checked them with

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 -

I'm tentatively creating a Windows .dll file using the Vorbis tools demos as a base for it. I've taken oggenc and simply converted it into a .dll file, with some minor changes purely to pass parameters to it (the original uses the command line). I have it working as far as it goes, but there seems to be something going wrong deep inside that I don't understand. The line at fault