similar to: wishlist for ogg123 += Non-blocking verbose messages

Does this look okay? : Time: 1:15.50 of 4:13.73, Bitrate: 133.3 How about? : <snip from=ogg123.c> info.u_time = ov_time_total (&vf, -1); /* Seconds with double precision */ gettimeofday (&start_time, NULL); t_min = (long) info.u_time / (long) 60; t_sec = info.u_time - 60 * t_min; while (! eos) { gettimeofday (&cur_time, NULL); c_min = (long)

Hi, I just added an "archive" mbox namespace to my dovecot setup, so that people can put their old mail into a slightly more inode-friendly box. When querying the STATUS on one of these boxes, I got a sigsegv: Program received signal SIGSEGV, Segmentation fault. 0x0000000000454d24 in message_parse_header_next (ctx=0x59e500, hdr_r=0x7fbffff420) at message-parser.c:759 759

In the vorbis-tools of the 20010710 version of CVS snapshot, ogg123/ogg123.c causes error on FreeBSD: <sys/types.h> is required. This *HAS NOT BEEN FIXED SINCE THE 20010601 VERSION*. I would appreciate if you just add an #include line - or let me know why you do not want to do so. // Kenji Rikitake *** ogg123.c.FCS Sun Apr 8 11:33:08 2001 --- ogg123.c Sat Jun 2 00:40:08 2001

P { margin-bottom: 0.08in; }A:link { } Hi Ogg Fans, I have a puzzle. When I'm getting ready to plan a larger program, I often do some little experiments to see whether what I'm thinking is going to be able to happen in the way that I anticipate. My next project involves some playing .ogg files in a random order. I have three brief files which I have used in this experiment. I am

Hi, Regarding ticket 523 "ogg123 can no longer play from stdin": http://trac.xiph.org/cgi-bin/trac.cgi/ticket/523 It seems that 'cat sample.ogg | ogg123 -' works for me, for ogg123 from svn. Can anyone verify that code has been committed to fix this bug, or is there a different usage that triggers the bug? Conrad.

Ulrich Windl wrote: > Hi! > > Recently I made some recordings (44.1kH/24bit WAV), and after > post-processing (normalization, noide reduction) I saved them as flac (still > 44.1kHz/24bit). > I noticed that ogg123 can decode these, but it will output 24 bit only. > Specifically there's no option to transform the output to 16bit. > When trying to pipe the 24bit WAV output

Hi. I'm trying to get plugger to work with ogg123 and it does - sort of. No matter what the song is, it plays 24 seconds of the song and then dies. Same spot every time - I've tried with a short song (Janis Joplin Mercedes Benz) and a long song (Cracker Eurotrash Girl). I have this as the mime identification in the plugger rc file: audio/ogg: ogg: Vorbis Ogg audio application/x-ogg: ogg:

MoiN ogg123 does not exit after playing a file but starts to eat all available cpu time, trying to read past the end of the file. Please apply the following patch to ogg123.c in vorbis-tools: --- vorbis-tools/ogg123/ogg123.c.orig Thu Oct 26 22:37:05 2000 +++ vorbis-tools/ogg123/ogg123.c Thu Oct 26 22:37:29 2000 @@ -461,9 +461,9 @@ while (!eos) {

Hey When playing an http ogg stream served by icecast, ogg123 (vorbis-tools-1.0.1) seems to detect replaygain metadata because it displays it in a nice way, but does ogg123 actually alter the playback volume according to the replaygain variables? I can notice no effect. I did some googling on this but didn't find much help. I discovered a vgplay patch for vorbis-tools 1.0.1 but after

A small patch (attached) to the ogg123 source (dec 15 nightly build from CVS) that implements ranged playback a la: ogg123 -r 12:10-13:00 file.ogg to playback 12m:10s-13m:00s fragment from the file.ogg soundfile. Usage: ogg123 -r hours:minutes:seconds.fraction-hours:minutes:seconds.fraction anything can be pretty much omitted (within reason) [although it does not support hh:mm:ss.hh- ]

Hi There is a good thing with ogg123. When playing multiple files, like ogg123 a.ogg b.ogg Ctrl-C will skip to next file. However, if I first do a cat a.ogg b.ogg > c.ogg and then ogg123 c.ogg Ctrl-C will simple skip the and not just jump to chapter two. Is it a big change to ogg123 to just let it jump to next block when pressing Ctrl-C ? best regards/hans -- Hamletsgade 4 - 201,

I just used ogg123 to play back a file encoded from a 22.5 KHz WAV, and it played twice too fast. Looking at the source, it seems that the sampling rate and number of channels are hard-coded into it. What´s the best way of fixing this? I quickly hacked together something that closes and reopens the devices before each file (diff attached). Is there a better solution? Aaron Plattner <HR

Below is a patch for vorbis-tools-1.0beta4 ogg123. It adds support for using the rc file (like /etc/ogg123.rc) for configuring the device-options. In addition, comments can be used (when they start a line). My ~/.ogg123rc: default_device=oss default_options=dsp:/dev/audio Please share your comments. Jeremy C. Reed http://www.reedmedia.net/ diff -u

Hello I'm following this up to the vorbis-dev mailing list (and bcc to you). Thanks for your repsonses. At 15:09 Uhr -0500 07.08.2005, Graham Mitchell wrote: > > b) concerning oggdec and ogg123: > > - neither is able to read from a pipe nor a fifo, as it seems. > >Yes, the "ogg123" from a pipe bug was actually just fixed in CVS during the >last week, so try

Halo vorbis devel team, I have a question concerning remote control interface in ogg123. I have searched this forum and Internet and found that in 2002 there was a patch made adding remote control interface to ogg123. My question is, if this will be included in the main trunk some day? Because this way whenever I upgrade ogg123 I have to adjust the patch and then patch it.... Thanks for answers

In order to get ogg123 to compile under FreeBSD, I had to change the include order: Index: ogg123.c =================================================================== RCS file: /usr/local/cvsroot/vorbis/vorbis-tools/ogg123.c,v retrieving revision 1.17 diff -u -r1.17 ogg123.c --- ogg123.c 2000/08/30 06:09:22 1.17 +++ ogg123.c 2000/09/19 17:18:12 @@ -27,8 +27,8 @@ #include

Hi all, Ralph Giles pointed me here for my ogg123 patch. I had mail'd the authors (listed in ogg123.1) and Xiph about this but I recieved no response - and here is probably a better place for it. I decided to work on ogg123 when I wanted to work on Ogg Vorbis support in Nautilus (if you don't know what it is, it is the new Graphical File Manager for GNOME). Currently Nautilus has mp3

As I have mentioned here before, ogg123 from 1.0rc3 segfaults after playing a file on FreeBSD and OpenBSD. This happens with both the native pthread and with GNU pth. I have finally managed to isolate the problem. ogg123 crashes inside pthread_cond_wait(), specifically in the COND_WAIT() call in buffer_wait_for_empty(). *If* I understand the control flow correctly, the decoder thread waits on

Hi, I need to adjust the output volume from ogg123 the same way that mpg123 has the "-f n change scalefactor [32768]" option. I need to do this within ogg123, instead of alternatives that involve pipes, such as piping the output to sox. I do not believe that this is currently possible in ogg123, and I'm looking for some suggestions as to how it can be accomplished by modifying

Hi, I need to adjust the output volume from ogg123 the same way that mpg123 has the "-f n change scalefactor [32768]" option. I need to do this within ogg123, instead of alternatives that involve pipes, such as piping the output to sox. I do not believe that this is currently possible in ogg123, and I'm looking for some suggestions as to how it can be accomplished by modifying