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

Some detailed feedback that looks useful. ----- Forwarded message from Michael Semon <wayfarer42@postmaster.co.uk> ----- Delivery-Date: Tue Jul 16 05:29:37 2002 X-Mailer: MIME-tools 5.41 (Entity 5.404) From: "Michael Semon" <wayfarer42@postmaster.co.uk> Subject: CVS: ogg123 rocks! vcut no so much so... To: feedback@vorbis.com Hi! Being impatient for RC4, I downloaded

Below is a diff to vcut.c and its vcut.1 manpage, which - rewrites the manpage in the mdoc(7) markup as offered in my previous message, and while there: - drops the [] around cutpoint as it is _not_ optional - adds the [] around [+] as it _is_ optional - drops the argument name difference between "cutpoint" and "cuttime" - adds the usage sentence about "." output

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

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

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

Hi all, The attached patch for vorbis-tools 1.2.0 fixes vcut so it can handle multiple chained Vorbis streams in the input file. This restructures large parts of the program to avoid duplicating code (e.g., process_first_stream and process_second_stream were very similar). The error handling is still incomplete, but I'd appreciate hearing any comments people have on this version. I think

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

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.

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

Skipped content of type multipart/mixed-------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: Digital signature Url : http://westfish.xiph.org/pipermail/vorbis-dev/attachments/20040618/e7bee431/attachment.pgp

Merry Christmas, Vorbis folks! Here's bunches of cleanups to ogg123. I haven't changed much in the raw code, mostly a few places with broken implementations. I'm also trying to cleanup some places where we assume too much, because ogg123 might eventually be able to safely run suid (or sgid) (to access the audio devices). I think the next thing I'll attack is the buffering. --

Yes it is 2:42 PM, and yes I stayed up finishing ogg123 buffering. But I'm not committing it because I'm really tired now and I'm very, very, very suprised it even worked (the first time!). I see why people use semaphores; I thought select() and a signal could work just as well. The select times out every second, so it keeps the buffer relatively filled without eating up loads of CPU.

I've been doing a ton of work on my branch. CVS log tells a little of the story. For one, the buffer is nearly completely rewriten. That means deadlock cases. I've caught a few, but I need help. Anyone who's computer is faster or slower than my own or perhaps schedules things differently (i.e. everyone) please hit the ogg123 on my branch (kcarnold_work) with the strangest conditions

Hello all, I'm going away on vacation again, so no work on ogg123 from me for a week. This is disappointing because I would have liked to be able to get my branch work into shape for an rc3 release, but there's no way I'll be able to get it done by then. That said, since I have moved the buffer code to pthreads and added libcurl streaming, the new code needs a lot of testing,

I was just about to commit a big buffer overhaul when I realized that it would probably break a lot of stuff and I'd get yelled at, so it's in the kcarnold_work tag (or will be momentarily...). Have a look at it, try to make it deadlock. If I messed up the CVS tagging, also let me know -- I know only enough about CVS to be dangerous :) This should also reduce CPU usage noticably. The

I have been very busy for the last few months with school, during which time Jack and others have taken over ogg123. Now I have a week off for Christmas ("Winter Break" for the politically correct), so I have some free time. And what better place to spend it than at my computer? (heh) So anyway I decided to take a look at (what's left of) ogg123. Yuck. Eeew. Horror. The good news:

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

A feature request that sounds reasonable and a bug report. ----- Forwarded message from Frank Klemm <pfk@fuchs.offl.uni-jena.de> ----- Delivery-Date: Sat Jan 6 06:35:21 2001 Date: Sat, 6 Jan 2001 15:26:43 +0100 From: Frank Klemm <pfk@fuchs.offl.uni-jena.de> To: xiphmont@xiph.org Subject: ogg123 X-Mailer: Mutt 1.0.1i For ogg123 I need the following feature: - Decode one .ogg file

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

I finally managed to compile ogg123 under MacOS X, after creating a PB project for it. Rillian, do you want to include the PB project in cvs? (it needs a LOT of polishing, though). ---------- Ogg123 from PACKAGE VERSION by Kenneth Arnold <kcarnold@arnoldnet.net> and others Usage: ogg123 [<options>] <input file> ... -h, --help this help -V, --version display