similar to: ogg123 streaming bug

I have vorbis-tools 1.1 (also tested on svn version), I have problem with play any ogg vorbis file as user rmrmg: [rmrmg@slack:~$] ogg123 ./av/lep.ogg Segmentation fault All works fine as _any_ other user. I have not any ~/.libao file. What can be the reason of my problem? Do you have any idea? -- . JID: rmrmg(at)jabberpl(dot)org | Wszystko jest trudne . mail: rmrmg(at)wp(dot)pl | przy

I'm considering patching my copy of ogg123 to support vorbisgain tags. Is there any interest in folding this sort of patch into the main line ogg123? Has anyone done this already (or to another command line ogg player)? John --- >8 ---- List archives: http://www.xiph.org/archives/ Ogg project homepage: http://www.xiph.org/ogg/ To unsubscribe from this list, send a message to

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

I'm having several problems with ogg123 on a FreeBSD-STABLE machine. In each case, ogg123 dumps core complaining about a bus error. 1) ogg123 plays all files at what seems like twice the correct speed. When given a SIGINT, ogg123 dumps core. This is using the program defaults, including the OSS driver. Here's a backtrace from gdb: Core was generated by `ogg123'. Program

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

Has anyone managed to get ogg123 to compile in AIX? I'm got an RS6k with a PPC 604e, running AIX 4.3.3. I can get libogg, libvorbis, libao, oggenc (so, everything _but_ ogg123) to compile just fine. I'm using gcc, thankfully, and not the native IBM compilers. I believe the problem to be with the linker. By default gcc for AIX doesn't use the GNU linker, but the standard AIX

I was just curious about the patch that I sent for ogg123 that implements the --quiet and adds in the --skip option? Also - I would like to know what are the main cvs modules and branches in which development takes place? Specifically, I would like to look at the very latest libao and ogg123 sources. I would also like to know where the main development for libvorbis takes place Regards, Ali

Hi, I have compiled the Vorbis libraries and tools on Solaris 8 using Forte 6 update 2. I am now trying to run ogg123 but nothing happens: $ ogg123 -v Pateras.ogg Audio Device: Sun audio driver output Author: Christian Weisgerber <naddy@openbsd.org> Comments: Outputs to the sun audio system. I have also worked around bug #191 by defining HAVE_SQRTF:

I tried to use the current cvs version of ogg123 with oss output and the ogg just sounds like static. I wanted to document it on the list in case anyone else is having the problem. I can make ogg123 write wav files fine. Also Vakor does not have any trouble playing oggs with ogg123, so I am not certain what the problem is. I have tried compiling all of ogg vorbis (ao,ogg,vorbis,vorbis-tools)

A playback of a mono vorbis track on a system using the i810 audio driver via ogg123 results in a double speed playback (chipmunk sound). It seems that this chipset doesn't support mono and while xmms seems to compensate for it, ogg123 doesn't I have a bugzilla report at redhat.com filed on this with more details https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=90433 Regards, Yusuf

Just as a reminder to our application maintainers. ----- Forwarded message from Ryan Cooley <ryancooley@yahoo.com> ----- Delivery-Date: Sun Jul 22 20:28:06 2001 From: Ryan Cooley <ryancooley@yahoo.com> Subject: Problems with ogg123 on OpenBSD To: feedback@vorbis.com While I hate to send complaints about something that is Free(tm), I really hoped and expected the Ogg Vorbis team to

I am about to commit HTTP streaming code for ogg123. This has no relation to the discussion about "real" steaming Ogg; it just downloads and plays at the same time. But unless you have a direct T3 connection, it'll almost definately break up quite frequently. Solution? Buffer. But I have other things to work on for the rest of the day... Any screaming objections? This has been

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'm using ices2's metadata facility to update the name of a track in a vorbis stream: <input> <module>alsa</module> <param name="rate">44100</param> <param name="channels">2</param> <param name="device">hw:1,0</param> <param name="metadata">1</param>

happy new year. a day off is a day to pick up a new project, so I wrestled my way through making ogg vorbis work on macosx. first, libao (not entirely a proper patch, but 2 source file diffs and a diff of a configure'd Makefile to one that works.): http://bolson.org/pub/libao-0.8.2-diff.tar.gz libogg and libvorbis compiled without incident. vorbis-tools were more complicated. I think

happy new year. a day off is a day to pick up a new project, so I wrestled my way through making ogg vorbis work on macosx. first, libao (not entirely a proper patch, but 2 source file diffs and a diff of a configure'd Makefile to one that works.): http://bolson.org/pub/libao-0.8.2-diff.tar.gz libogg and libvorbis compiled without incident. vorbis-tools were more complicated. I think

Hello, I built the entire Vorbis kit on my PowerMac G4 running OSX 10.4.6. I'm having problems however doing anything with the libao package. Any time I try to use the library to link it errors out with the following message: /usr/bin/ld: Undefined symbols: _dlsym_auto_underscore collect2: ld returned 1 exit status If I try to run the ogg123 application I get this:

Dear developers, I patched ogg123 so that it can use esd (only local socket currently). In order to compile you need to copy esd.h from the esound-devel to the vorbis-tools directory. Usage: ogg123 -e -d something file.ogg the "something" is not important I don't intend to maintain this patch, but perhaps somebody could make it more nicer and incorporate it in the

On 8/16/05, Paul Martin <pm@nowster.zetnet.co.uk> wrote: > > Caught it yesterday, as I was already running level 4: This line: [2005-08-15 04:10:58] EROR stream/ices_instance_stream Send error: No error (Success) is the one that catches my attention. Unfortunately, ices's error logging is somewhat sub-standard. Can you cross reference this against your icecast error.log to see

On Mon, Sep 26, 2005 at 12:41:00PM +0200, Michael Smith wrote: > On 9/23/05, Paul Martin <pm@nowster.zetnet.co.uk> wrote: > > Mike... did you look into this? I posted a waveform from a file > > generated by ogg123 dumping to a wav (so that audio driver problems were > > eliminated). > > > > It looks to me like ices2 is restarting the vorbis encoder in a >