similar to: piping vorbize's stdout/stderr

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

Hi! The version of ogg123 (or perhaps libao I think) says that the wav output can't go to STDOUT. Is this feature supported already in the current CVS? Bye, Peter Surda (Shurdeek) <surda@bigfoot.com>, ICQ 10236103, +436505122023 -- The three Rs of Microsoft support: Retry, Reboot, Reinstall. <HR NOSHADE> <UL> <LI>application/pgp-signature attachment: stored

Hi! - what is the mime type for ogg? - does the current implementation (xmms/winamp plugin) support http streaming? Bye, Peter Surda (Shurdeek) <surda@bigfoot.com>, ICQ 10236103, +4369910964300 -- Press every key to continue. --- >8 ---- List archives: http://www.xiph.org/archives/ Ogg project homepage: http://www.xiph.org/ogg/

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

Hello ppl! I asked some time ago how about adding the option to control ogg123 interactively from command line, similar to mpg123. So I got fed up waiting and added it myself today. The code initially comes from mpg123, I already adapted it to work with aviplay and vlc so it's proven and shouldn't introduce many problems. The only problems I see now: - in order to compile ogg123 now

Hello! I was wondering if someone took a look at my patch I posted on tuesday. I just checked and it applies to current cvs too. Anyone has comments about functionality, idea or whether it should/should not be commited? Sorry if this looks like I'm impatient but I just want to be assured someone responsible will eventually take a look and then give me a yes or a no so I can stop worrying and

Hi! I've been wondering, is there a tool (preferably under linux) that allows me simple audio editing of ogg+vorbis file? Say I have a song that takes 2:00 and the last 20 seconds is silence and I want to get rid of it without reencoding. Or could this be done simply in 10 lines in C? Bye, Peter Surda (Shurdeek) <shurdeek@panorama.sth.ac.at>, ICQ 10236103, +436505122023 --

Hi! Sorry for being somewhat offtopic but I'm hoping someone can help me. I need to download some music I can use in a one-time non-commercial multimedia presentation (technically speaking I'll be demo-ing ogg123 :-)). I don't care what it is, only it musn't suck and be somewhat suitable for general audience. RMS's speeches simply don't cut :-) So far all music I found on

Are there any attempts currently being worked on to make Vorbize Visual C++ compatable? Or for that matter non-GNU compatiable? I guess I never realized that getopt.h was a GNU thing. What would be the suggested course of action to get vorbize to cross compile on VC++ or other non-GNU platforms? If not I can certainly do this because I'd like to be able to run this on Windows but I

Hey. Last night I hacked grip so that it'd allow me to use vorbize and comments with grip. It's very ugly because grip'd need a bit of rearrangement in order to facilitate the way the vorbis comments work (that is, the comments are not added in after the encoded file has been written). Any one who wants to use it should patch grip-2.94 (http://www.nostatic.org/grip), and make sure you

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

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

Howdy.. I've got a couple little patches here. 1. vorbis-tools needs getopt. Since it's already sitting in the source tree for cmdline I set up cmdline to make a getopt.a that gets used for both. Also, since mp3tovorbis is a shell script, it needs to be installed 755 not 711 (unless I'm missing something). 2. I've found that both tru64 and irix 5.3 won't give int64_t

Hello, I've been trying to compile some things but have run into some problems. I've have the vorbis directory inside of /usr/src. I have compiled vorbis itself with no problems. I've also copied the results to their respective directories as per the README file. I've also compiled the XMMS plugin with no problem. However when it is installed in the

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 finally got around to getting this to a more-or-less working state. Right now, it does most of what vorbize does, plus support for encoding multiple files (this works, but needs some additions to sanely handle titles, etc. for multiple files). The name is temporary, until I think of something better. http://www.labyrinth.net.au/~msmith/oggenc-0.1.tar.gz Hopefully, it's mostly portable,

Hi all, As I read into the forum, NATting (SNAT) is expensive, using iptables to translate IP sucks the performance of the system. I just want to know if IProute2 can handle NATting and if it handels NATting can it performed faster than iptables? thanks, Wennie

It looked like ogg123 was expecting an out-of-date set of headers. I've updated the printout section to expect the canonical set from docs/v-comment.html. I also found vorbize's use of "track" for the title tag confusing. The second patch is just a rename in the code and ui. Cheers, -ralph -- giles@ashlu.bc.ca <HR NOSHADE> <UL> <LI>TEXT/PLAIN attachment:

------- Forwarded Message The following patches should fix vorbis-tools to build on NetBSD. I'm not including the diff to the configure scripts, so you'll need to rerun autoconf in the toplevel and libao directory after applying these patches to the configure.in files. It also appears that vorbis-tools/libao/ao_libs.inc is automatically generated by a configure script but checked into

I just commited my modifications: vorbis-tools is back in the main build, but ogg123 is out of the vorbis-tools build. I am investigating the cross-platform libraries suggested. ogg123 silences "Clipping in frame x", can now play multiple files at once, and has a new stream handling format (resolves the get_stream() bug mentioned earlier). Vorbize has options for no comment and