Re: xmms redirection to stdout

Tim Gruene <[email protected]> Thu, 25 Aug 2005 16:57:31 +0200 (CEST)
Newsgroups gmane.comp.multimedia.xmms.devel
Message-ID <[email protected]>
Hi,

I may have caused some confusion by a typo:
I meant
	xmms -audioout - | a2play <mybdaddress>
instead of
	xmms -audioout - | aplay <mybdaddress>

a2play is a tool that comes from the bluetooth-alse project to redirect
output to a stereo headset.

a2play works with mpg123 --au - file.mp2 | a2play <bdaddress>

but I have not managed to get a2play to work by reading from a device or
file other than stdin, even though the program's help claims it could do
so.

Therefore I would like xmms to send the raw data to stdout so that I can
catch it with a2play.

I've been asked to test a stereo bluetooth headset with linux, and I have
been trying to get it to work for more than the day now. It only works via
this piping from mpg123 to a2play so far.

Any comments and help are GREATLY appreciated.

Thanks a million,

Tim





--
Tim Gruene
Institut fuer anorganische Chemie
Tammannstr. 4
D-37077 Goettingen

GPG Key ID = A46BEE1A


On Wed, 24 Aug 2005, Ben Winslow wrote:

> On Wed, 2005-08-24 at 16:24 +0200, Tim Gruene wrote:
> > Sorry for this non-developer question, but I did not find the answer
> > elsewhere.
> >
> > Is there a way to redirect the sound output of xmms to stdout?
> > I tried using the diskwriter plugin as output and setting it to
> > /dev/pts/3, but that did not work.
> >
> > I would like to use a2play from the bluetooth-alsa project to use xmms
> > with a stereo headset, i.e., I would like to do something like
> > 	xmms -audioout - | aplay <mybdaddress>
>
> Can't you use the ALSA output plugin and select the bluetooth headset in
> its configuration dialog?  (under 'Audio Device'.)
>
> Failing that, having the disk writer plugin write to a fifo (e.g.
> mkfifo /tmp/audio.wav, set wav writer output to /tmp/audio.wav,
> aplay /tmp/audio.wav) might work.
>
> Since WAVE files have a length section in the header, you'll often run
> into undefined behavior when trying to pipe a WAVE somewhere else
> (because the writing application can't seek back to the beginning of the
> pipe to write the length, once it's known.)  Because of this, your best
> bet is to use the ALSA output plugin if it's possible to do so.
>
> --
> Ben Winslow <[email protected]>
>