similar to: ogg123, buffering, tag

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,

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

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

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

Bug: vorbis/lib/vorbisfile.c, ov_time_tell. When vf->seekable = 0, link = -1 at the return, thus dividing by vf->vi[-1].rate. Fix should be pretty simple. -- Kenneth Arnold <ken@arnoldnet.net> / kcarnold / Linux user #180115 http://arnoldnet.net/~kcarnold/ <HR NOSHADE> <UL> <LI>application/pgp-signature attachment: stored </UL> -------------- next part

I tried to use ogg123 -b to play from a slow HTTP server, and I realized that ogg123 starts to play immediately even if the buffer isn't full, so if it can't read the ogg fast enough it skips, even with a huge buffer. Is this the way it's supposed to work? It seems to me like the buffer shouldn't start playing until it's full. Am I misunderstanding the purpose of having a

Hi people! I think it would be cool if ogg123 had a mode in which you could conrol it with stdin. pausing, quitting/stopping and seeking would be enough imho. mpg123 already has something like this (I think -e). I'd do it myself but I'm busy. Shouldn't take much time. Bye, Peter Surda (Shurdeek) <surda@bigfoot.com>, ICQ 10236103, +4369910964300 -- The dark ages

Speaking of ogg123 fixes and Solaris... <getopt.h> doesn't appear to exist in Solaris. Hence, ogg123 won't compile on Solaris at all (even with gcc). I originally mentioned this back in November (http://www.xiph.org/archives/vorbis-dev/200011/0291.html). Can this be fixed? {+} Jeff Squyres {+} squyres@cse.nd.edu {+} Perpetual Obsessive Notre Dame Student Craving Utter Madness

Hi all, Browsing through the bug database, I was able to reproduce #14. Briefly, when I run, for example: ogg123 -b 8000 test1.ogg test2.ogg test1.ogg [...] where test1.ogg and test2.ogg have different bitrates or numbers of channels (that is important), ogg123's memory usage continuously increases as each new song is played. I think I've tracked down the bug to the use of

>I've made something. It wasn't done in exactly 10 minutes because I had to >translate the headers to Pascal, but the GUI was certainly done in about >30 minutes. [...] >http://www.xs4all.nl/~walterln/vorbis_play_17apr.zip (259K) would it be hard to add streaming support? a small and simple player, which could also stream vorbis would be cool. also a command line tool for

Every time ogg123 -bXXX is run, it creates another shared memory segment but fails to destroy it on exit. Thus an increasing number of shm segments keeps piling up and eat all the (often rather limited amount of) available shared memory. The patch below corrects this and also fixes the bizarre abuse of stat() permission bits for shmget(). On systems that support it, I'd very much like to

The patch below adds: - acinclude.m4: A new macro A_FUNC_SMMAP to check that sharing pages through mmap() works. This is taken from Joerg Schilling's star. - configure.in: A_FUNC_SMMAP - ogg123/buffer.c: If we have a working mmap(), use it to create a region of shared memory instead of using System V IPC. Works on BSD. Should also work on SVR4 and offspring (Solaris), and Linux.

We have a French translation (and general gettext-ization) of vorbis-tools! Still needs to be merged, though. Perhaps I'll tackle that tomorrow. See below. <p>----- Forwarded message from Fr?d?ric Boiteux <furgarat@free.fr> ----- From: Fr?d?ric Boiteux <furgarat@free.fr> To: "Kenneth C. Arnold" <kcarnold@yahoo.com> Subject: Re: Internationalization of

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:

I know you're tired of hearing me complain about ogg123, but this time I noticed that some of the error messages are a bit inconsistant. Also, I noticed that some things (like "Error connecting to server") are fatal errors that kill ogg123, while I think they should simply go on to the next file in the list like "input not an Ogg Vorbis audio stream" does. Another problem

http://surf.chimie.uqam.ca/~kruus/vorbis/ now contain branch_beta3 and trunk subdirs that are updated daily (until branch_beta3 becomes historical next week, like the other snapshots at that URL). to web-browse the source code, go to http://surf.chimie.uqam.ca/~kruus/vorbis/lxr/http/source erik (back after audio-video sync miniproject. Yay!) --- >8 ---- List archives:

Looking at it, I think this patch is actually better than the one I sent before, mainly because it keeps from adding a bunch of weird parameters to functions at the expense of a single global variable (globals... ick). Aaron Plattner <HR NOSHADE> <UL> <LI>text/plain attachment: ogg123.diff.2 </UL> -------------- next part -------------- A non-text attachment was