similar to: Manpages

Displaying 20 results from an estimated 6000 matches similar to: "Manpages"

2000 Jun 18
3
Makefile dependencies in vorbis-tools
I've been trying to tackle the vorbis source. I ran across what I think is a missing dependency in the vorbis-tools directory. Since ogg123 and vorbize are staticly linked to libvorbis and vorbisfile, when those file change, the executables should be rebuilt. Below I've attached a patch. (I hope it works. I am sort of new to patch and diff.) BTW, I've been trying to find a good
2001 Nov 04
5
ogg123 running under MacOS X
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
2000 Jun 16
2
Description of commits
Tonight's commits so far: I finally wrote up the result of the comment header specification discussion. It's in the doc/ directory now. I plan on doing work in the libvorbis comment handling tonight to bring it up to date and make the interface more useful. gif->png conversion of the images in the docs Monty --- >8 ---- List archives: http://www.xiph.org/archives/ Ogg
2000 Jul 13
1
Patch: ogg123 -> esd
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
2000 Jun 20
3
Kenneth's Second Commit
I've fixed a heck of a lot of stuff in the time frame of just over ten minutes. And you all care... right. I actually ran Vorbize, and discovered some stupid bugs (e.g., segfault???). Fixed. Both Vorbize and Ogg123 should now speak fluently in Monty's comment-eese. I'll be working on getting both to implement all the comment tags; I'm seriously considering dropping all comment
2000 Nov 11
1
esd bug in ogg123
I've run into two problems with ogg123 that appears only when using the esound driver. Case 1: pops in output Audible pops, especially at low volume. Original mp3 file does not exhibit these pops, nor does oss output from ogg123, nor does esd output from mpg123. Things ruled out: disk speed - the HD is ATA/33 with DMA on. It's a single user
2000 Aug 14
0
OggEnc manpage
Attached is the manual page for OggEnc. Please proofread it and commit to CVS. Also remember to edit Makefile.in to install the man page to the appropriate location. Thanks. --- Stan Seibert .\" Process this file with .\" groff -man -Tascii oggenc.1 .\" .TH oggenc 1 "August 13, 2000" "" "Vorbis Tools" .SH NAME oggenc \- encode audio into
2002 Jan 01
2
RC3: ogg123 dumps core at end of file
1.0rc3, OpenBSD/i386 & FreeBSD/alpha. ogg123 segfaults after playing a file. This will not happen if I specify multiple songs and skip (^C) to the next one. Seems to be independent of buffering (-b) and output device (oss, esd, raw). -- Christian "naddy" Weisgerber naddy@mips.inka.de --- >8 ---- List archives: http://www.xiph.org/archives/ Ogg
2000 Sep 02
1
libao endian fix (attempt 2)
Okay, here's the patch that should fix byte-ordering madness. The basic rule with libao is that samples have to be in native byte order. All of the drivers will assume this, and libao provides a ao_is_big_endian() function for library clients (and sometimes drivers) to test their byte ordering. I would appreciate it if someone on a big endian platform test ogg123 and make sure that it works
2006 Oct 04
3
problem using libao on OSX 10.4
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:
2003 Jan 16
1
Several problems with ogg123
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
2013 May 28
5
[PATCH 1/6] Remove the --quiet (-q) option from vorbiscomment.1 man page.
--- 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
2000 Jun 18
3
Compile error
Here's the error I get when trying to compile: gcc -O20 -ffast-math -D_REENTRANT -D__NO_MATH_INLINES -fsigned-char -I. -I../include -c ogg123.c ogg123.c: In function `main': ogg123.c:260: `AFMT_S16_NE' undeclared (first use this function) ogg123.c:260: (Each undeclared identifier is reported only once ogg123.c:260: for each function it appears in.) make[2]: *** [ogg123.o] Error 1
2006 Oct 06
1
problem using libao on OSX 10.4
I installed fink and now I have the /sw/lib, however that didn't fix my problem. I went as far as to take out the - Ddlsym=dlsym_auto_underscore out of the configuration files. Now however the libao package won't build at all and yips about this: [ukiel:/MP3/OGG/libao-0.8.6] wind% make Making all in src Making all in plugins Making all in oss make[3]: Nothing to be done for
2008 May 30
3
regarding vorbis tool
hi, i am trying to load vorbis tool on to my arm board EDB9302 , till now i have cross compiled libao, libogg, libvorbis, flac, speex and vorbis tool. when i run the command line arm-linux-ogg123 with some sample ogg format file on my arm board it gave *"Could not load default driver and no driver specified in config file : Exiting"* , please help me to over come this error.
2000 Aug 16
1
YALCSF (Yet Another Libao Configure Script Fix)
This patch fixes three problems with the current configure script: 1. Manual exclusion of drivers: Now you will be able to force drivers NOT to be compiled, even if they are detected. This was specifically requested with so that ALSA could be disabled. 2. Selecting the default device: Now you can override the default driver chosen by the script with your own preference. Again, this enhancement
2000 Jul 26
3
Alpha
I'm going to gather that no work has been done to make the vorbis stuff work on Alpha, I've got an XL366 on which I will donate an account if anyone would like to attempt to get it working. --- >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 'vorbis-request@xiph.org' containing
2000 Jul 26
3
Alpha
I'm going to gather that no work has been done to make the vorbis stuff work on Alpha, I've got an XL366 on which I will donate an account if anyone would like to attempt to get it working. --- >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 'vorbis-request@xiph.org' containing
2003 May 08
2
ogg123/libao needs to factor non support for mono in i810 driver
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
2003 Jul 10
2
optimization to libao audio output autodetection code
Ok, this patch replaces the old patch I sent, and it does a bit more. For one, it sorts the linked list of drivers based on the priority values, highest valued ones coming first. That allows the _find_default_driver_id code to stop looping (break) immediately when it finds a driver that works, because it already knows it's the working driver with the highest priority (what it normally