similar to: minimum processor\ram requirements for decoding vorbis files

Now that FLAC has officionally joined the Xiph family, there are three different free audio codecs, which can be stored/transported using the ogg container. Would it be possible to create an API and/or a library that would cover them all? If my understanding of the situation is correct, if an application wants to support vorbis, speex and flac, it has to use three different interfaces.

Now that FLAC has officionally joined the Xiph family, there are three different free audio codecs, which can be stored/transported using the ogg container. Would it be possible to create an API and/or a library that would cover them all? If my understanding of the situation is correct, if an application wants to support vorbis, speex and flac, it has to use three different interfaces.

Now that FLAC has officionally joined the Xiph family, there are three different free audio codecs, which can be stored/transported using the ogg container. Would it be possible to create an API and/or a library that would cover them all? If my understanding of the situation is correct, if an application wants to support vorbis, speex and flac, it has to use three different interfaces.

Here is patch with manpages for ogg123(1), mp3tovorbis(1) and vorbize(1). Manpages are in pod format, because it is the most readable man source, and are compiled by pod2man. all and clean for man/ work. Install and uninstall for man/ seem to work. Manpages are GPLed of course. <HR NOSHADE> <UL> <LI>text/plain attachment: manpages.diff </UL> -------------- next part

I just moved a bunch of shared code (like 4 copies of getopt) into a share directory within vorbis-tools. I also moved the UTF-8 code from oggenc into the vorbis-tools/share directory as well so that it could be used by all of the tools, since they all need to handle UTF-8 comments correctly. Header files for the shared code are stored in vorbis-tools/include. I have already fixed vorbiscomment

The vorbis FAQ mentions that decoding vorbis should use roughly the same resources as decoding MP3's, but that the current source is not optimized. So what is the current requirement? I have a Pentium 133 with 64 megs and I cannot get .ogg files to play without skipping. I've tried encoding .wav files and downloading .ogg files from www.vorbis.com and playing them on Winamp with

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

Moin, Two questions I have. Actually, the first isn't so much a question. It seems that `ogg123' is not able to play streams from stdin, at least not for me on FreeBSD. It also seems that with the patches way down below, it can play from stdin for me -- I handle stdin like http-transport and return the same values for seeking and the like, to avoid calls that fail, and so it works,

Hi, I have made a small patch for enabling repeating in ogg123. It adds the parameter "--repeat n" or "r n" where n indicates how many times it repeats the playlists. Zero in forever. Apply it if you like, I find it very convenient. -- Regards Niels Sandmann Jabber: sandmann@jabber.dk, Email: sandm@nn.dk -------------- next part -------------- Only in ogg123: .deps Only in

Or rather - the ogg123 seems to run faster than the oggenc. Based on the vorbis toots 1.0_1,3 I've got (on freebsd) a small streaming server which essentially takes the oss/vox audion input; uses the code from oggenc to make a stream and then a bit of apache 2.0 to dole that stream out over TCP to various clients: setup oss /dev/dspW0.0 16 bit stereo 44k1. create ogg/vorbis

I was wondering if there was a way to recompile ogg123 so that it didnt look for "Ogg" at the start of each file. Ie change it so it looked for "Dog" or something. Why you ask? because in theory Im not ment to have any music files on my work computer NFI why but just cant. If I could mask an ogg file to look like another file then I could beat the system. Assuming that they

Installment #3 on my coding binge: The latest CVS version of ogg123 (in vorbis-tools) now plays FLAC and Ogg FLAC files. The FLAC support is optional, so if you don't have FLAC 1.0.4 and the header files, ogg123 will still build without it. Please give it a whirl and let me know how it works for you. --- Stan Seibert <p>--- >8 ---- List archives: http://www.xiph.org/archives/

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

Hi All, For my new file (and thus mp3) server I've decided to switch completely to Ogg Vorbis. This means having to reencode ~30GB worth of 128Kb MP3's, but i figured that it would all be worth the effort. So I downloaded the sources for libogg, libvorbis and vorbis-tools and fired up my trusty old compiler. libogg and libvorbis built and installed like a charm. Not so for

Hi, I noticed there was some discussion on this list about the desire for ogg123 to support output to stdout via Sun's .au file format, so I decided to give implementing an AU driver for libao a shot. Here is my first attempt. To test the driver: * Apply the patch below (against ao in CVS) * Copy the attached ao_au.c into ao/src * Run ao/autogen.sh, compile, and

Daniel: thought you'd like to know that I'm forwarding this to the vorbis-dev mailing list. <p><p>Hey vorbis-dev (after a very long time!), I got the attached message sent to just 3 of the people who have worked on ogg123, and thought it would probably due better good on the mailing list. It seems to concern http://bugs.xiph.org/show_bug.cgi?id=250 by casual search. For

Hello all, I'm glad to announce to you that Vorbis now has full ReplayGain support. If you're not familiar with ReplayGain, take a look at www.replaygain.org. The main features are: a) all songs play back with equal loudness b) removes the need for normalization c) allows for clipping prevention Using it is very simple. Get a compatible decoder (ogg123, XMMS and WinAmp all support it

Hi: Doesn't ogg123 now have speex support? I vaguely recall it being added some months back. Geoff. <p> -- Geoff Shang <gshang@uq.net.au> ICQ number 43634701 Make sure your E-mail can be read by everyone! http://www.betips.net/etc/evilmail.html Please avoid sending me Word or PowerPoint attachments. See http://www.fsf.org/philosophy/no-word-attachments.html <p>---

When using the abx utility that is in LAME's misc dir, trying it on an ogg (with ogg123) gives the following output: Standard Open Source Bug detected, try murksaround ... (ogg123 is decoding to stdout) IIRC this also happened with older mpg123's but no longer with the latest release. Latest ogg123 from CVS still gives it though. Someone stole code but forgot to check for fixes? :)