Routing API
To: Martin Grimme martin.gri...@gmail.com
Cc: maemo-developers@maemo.org
Message-ID:
l2le3a9904f1005012013q167658ccre8a0d368ff6b3...@mail.gmail.com
Content-Type: text/plain; charset=iso-8859-1
Thanks Martin, I have a feeling that I should be able to set those flags
in
alsa
backend.
Regards,
Chitti
--- On Sun, 5/2/10, maemo-developers-requ...@maemo.org
maemo-developers-requ...@maemo.org wrote:
Message: 8
Date: Sun, 2 May 2010 08:43:04 +0530
From: saurabh aggarwal aggarwal.saur...@gmail.com
Subject: Re: Audio Routing API
To: Martin Grimme martin.gri
-requ...@maemo.org
maemo-developers-requ...@maemo.org wrote:
Message: 8
Date: Sun, 2 May 2010 08:43:04 +0530
From: saurabh aggarwal aggarwal.saur...@gmail.com
Subject: Re: Audio Routing API
To: Martin Grimme martin.gri...@gmail.com
Cc: maemo-developers@maemo.org
Message-ID
Thanks Martin, I have a feeling that I should be able to set those flags in
alsa using the gstreamer APIs and pulsesink.
The pulsesink object does accept a propllist, and using pactl if you look at
the pulsesink, there seem to be properties that should be able to switch
between headset and
Hi,
alsamixer -c0
reveals a switch to route audio to the earpiece (I don't remember it's
exact name). I don't think you can route sound to the earpiece any
other way. Somebody please correct me if I'm wrong.
Martin
2010/4/28, saurabh aggarwal aggarwal.saur...@gmail.com:
We are developing a
We are developing a VoIP application, and have it running for Maemo5 (using
gstreamer/pulseaudio).
The problem now is that the output being used is the speaker, and not the
headphone/earpiece.
I have tried a couple of things (which haven't worked) like -
gst-launch pulsesrc device=source.voice !
