similar to: [fwd] CVS: ogg123 rocks! vcut no so much so... (from: wayfarer42@postmaster.co.uk)

For some reason this didn't make the list and I got no approval message... this time I'll force the From to be my subscribed address. Bug in Monty's new filtering system? Anyway, here goes again. ----- Forwarded message from ----- Date: Thu, 1 Aug 2002 10:24:46 -0400 To: vorbis-dev@xiph.org Subject: Re: [vorbis-dev] [fwd] CVS: ogg123 rocks! vcut no so much so... (from:

Hello, I am trying build vorbis-tools-1.1.1 in the framework of my tool (see signature). The essence of the tools is that it builds and install everything locally, and, of course, it uses the available mechanisms to specify search paths for both headers and libraries; the tool first builds dependencies abd then the target itself. So, for example, 'configure' for vorbis-tools-1.1.1 is

Hi every body , ( Please forgive my dumb poor english ) I got many tracks in ogg/vorbis format . I would like to make a "preview" of them . I mean : I have a track : foo.ogg ( wich is 3:00 minutes long ) i want to have : preview_foo.ogg ( wich is foo.ogg but from 1:00 -> 1:15 ) I read man oggdec , man ogg123 , man oggenc but i did not see what suits me . I use zsh shell , on a

I looked through the archives and I didn't really seem to find the answer to what my question. I used wget to get an audio stream from a site and now I would like to be able to split up the stream into the individual songs. The site is nice enough to encode the artist and track name in each new song. This info is displayed in Winamp when the song plays. Doing an xxd dump of the file I can

Hi, I've got alot of long 1-2hr files which I'd like to split up into 5-10 minute chunks. ?I think this should be possible using a small shell script and vcut, but my scripting abilities are lacking. ?Does anyone know of the existence of a script which would do this, or know how I'd go about making one? So say I had a 60 min file (60mins.ogg) I'd like to issue a command

Hello I have experienced some problems with vcut (media-sound/vorbis-tools-1.0-r1 package from Gentoo/Linux). I have a long live record I have encoded in OGG (maybe it would have been easier to cut the WAV file and encode the parts, but still). The file was encoded with oggenc from the same package as vcut. I have therefore tried to use vcut to split the long OGG file in several smaller files.

While testing the new vcut, some of the early results had badly framed headers. I actually didn't notice it at first, because I was testing with oggz-validate, but ogginfo does identify the problem: "WARNING: Vorbis stream X does not have headers correctly framed. Terminal header page contains additional packets or has non-zero granulepos" Conrad (or someone else) may want to

Hi, I have a question regarding vcut. In the man page, it says: DESCRIPTION vcut reads an Ogg Vorbis audio file and splits it at the given cutpoint, which is a sample number. <p>What I want to do, is to cut an Ogg Vorbis file at a given time. Say, I have an Ogg Vorbis file, which is 1 hour long, and I want to cut it into two half hour parts. With a fixed bitrate

Dear vorbis-dev I tried to split an ogg file which was downloaded as a part of a stream with mplayer -dumpstream -dumpfile file.ogg http://..../stream.ogg. The metadata or headers or what it is is then of course in error. (I hate this problem.) Both vcut (I'd post version if vcut supported a --version or -V option) and oggsplt (= mp3splt (same about version)) (according to this page, they

Andrew Williams <andrew.s.williams@adelaide.edu.au> has tipped me off that vorbis-tools uses a format specifier "%Ld" in vcut/vcut.c and ogginfo/ogginfo2.c. This is plain wrong. The L modifier only applies to floating point. The modifier corresponding to "long long" is ll, e.g. "%lld". -- Christian "naddy" Weisgerber

This patch cleans up the vorbis-tools Makefile.am files so they work with both automake 1.4 and 1.6. Some changes to configure.in were also needed in order to get things to work (and to fix some ac 2.50 issues). Please remove config.h from cvs as it is a generated file and empty anyway. automake 1.6 isn't really incompatable with 1.4, it's just more picky about you sticking to the rules:

Here's an updated version of my last vcut patch, which adds support for chained streams. The patch is against vorbis-tools 1.3.0b1 and fixes all issues that were identified by TODO and XXX comments in the preliminary patch. It also fixes a false positive for the "bad GP range" error and avoids using stderr for messages that aren't errors or warnings. I believe this version is

hi, I am recording a continuous 24/7 broadcast using ecasound, oggenc and cronolog. because the broadcast is continuous and to not lose any data, I split up the recorded stream into a file for every 30 minutes using cronolog (http://www.cronolog.org). o the chain looks like the following: ecasound | oggenc | cronolog the problem is the following, because the oggfiles are split, they lack a

Dear vorbis-dev lurkers, I bring you the first beta release of vorbis-tools 1.3.0. It has quite a few new features and the final version will have even more, so I am sure it is to everyone's benefit that it gets as much tested as possible so we can do a quick release. Here's the changelog so far: * Fixed an error in configure.ac; --with-speex/flac work again (#1319) * Corrected

How does one use the vcut from Vorbis-tools package? I tried to enter samples, miliseconds, seconds, h:mm:ss as cut point, but nothing worked (I even tried to enter 1 as cutpoint, but I always got "Cutpoint not within stream." message)... I'm doing this on Windows, if it matters... -- Jernej Simoncic, jernej.simoncic@guest.arnes.si http://www2.arnes.si/~sopjsimo/ ICQ: 26266467

The ogginfo tool writes its errors to stdout instead of stderr. Shouldn't that change? (Warnings also go to stdout, but that's more of a gray area.) The other vorbis-tools don't have this problem, with the possible exception of vcut, which writes the usage message to stdout, another edge case.

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

module. The file may be corrupted. Message-ID: <Pine.LNX.4.43.0406081110070.26162-100000@pilchuck.reedmedia.net> I am unable to pipe to ogg123 with cat, but redirecting with < works fine. rainier:~$ cat ~/audio/acdc-who_made_who.ogg | ogg123 -v - Audio Device: OSS audio driver output Author: Aaron Holtzman <aholtzma@ess.engr.uvic.ca> Comments: Outputs audio to the Open Sound

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

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