[pulseaudio-discuss] Disabling monitor sources in Pulse

2010-01-11 Thread Jeremy Visser
Hey,

I have a webcam with a built-in microphone (that appears as a USB
soundcard without only a single capture interface) that works fine,
except when I first log on, my internal sound card's microphone is
always selected by default, even though I don't want it to be.

So in gnome-volume-control, I have changed my internal audio card from
Analog Stereo Duplex to Analog Stereo Output, to force my USB
microphone to be the only USB microphone.

But now all that happens is that my Monitor of Internal Analog Stereo
is now the default microphone for all applications, despite my selecting
of the USB microphone as the default.

So, for some reason, PulseAudio hates my USB microphone, and refuses to
assign applications to it, even though it is the default.

So, I need a solution that does either or both of the following:

* Makes gnome-volume-control actually assign an application to the
microphone that is selected in the Input tab (*gasp* how logical).

* Removes and prevents the Monitor sources from ever appearing.

I'm fine with jumping through hoops and workarounds for 5 minutes prior
to ever using a microphone, but I am an extraordinary type.

I am actually asking this on behalf of a non-technical friend who got
into this exact situation today, and any form of workaround like what I
have to do for my situation is unacceptable. I need a solution that will
work for him, because until then, he is unable to use his microphone due
to (Pulse/GNOME/some app)'s poor logic.

Any ideas on how to get to the bottom of this?

Jeremy.

___
pulseaudio-discuss mailing list
pulseaudio-discuss@mail.0pointer.de
https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss


[pulseaudio-discuss] How to implement CS-call module in PA?

2010-01-11 Thread tieg
Hi, all:

I'd like to implement a CS-Call module in pule audio. That is to say
voice call data will be handled at user space. Such mechanism is
different from traditional H/W voice call solution. Its pros points is
voice data can be rendered specially. For example, you can add
echo/noise cancellation.

Is there any examples or guide I can refer to?

BR
tieg

___
pulseaudio-discuss mailing list
pulseaudio-discuss@mail.0pointer.de
https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss


Re: [pulseaudio-discuss] How to implement CS-call module in PA?

2010-01-11 Thread Rémi Denis-Courmont

Hello,

On Mon, 11 Jan 2010 18:57:56 +0800, tieg tie...@access-company.com wrote:
 I'd like to implement a CS-Call module in pule audio.
 That is to say voice call data will be handled at user space.
 Such mechanism is different from traditional H/W voice call solution.
 Its pros points is voice data can be rendered specially.
 For example, you can add echo/noise cancellation.
 Is there any examples or guide I can refer to? 

I am not aware of any commonly used standard to get circuit-switched voice
data out of a voice modem. You can typically dial and answer with AT
commands. But as you seem to imply, voice audio is often routed directly in
the hardware to the speakers.

The Nokia N900 does route CS audio through PulseAudio. This is done using a
dedicated kernel driver for Nokia modems talking to a Nokia-specific
PulseAudio plugin. My point is, it's entirely dependent on the specific
hardware whether and if so, how CS audio can be routed from/to user-space
(and PulseAudio in particular). So a generic example wouldn't make much
sense IMHO.

-- 
Rémi Denis-Courmont
http://www.remlab.net
http://fi.linkedin.com/in/remidenis 

___
pulseaudio-discuss mailing list
pulseaudio-discuss@mail.0pointer.de
https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss


[pulseaudio-discuss] Metronome

2010-01-11 Thread Stéphane List

Hi list,

I've just wrote a metronome in QT for pulseaudio :
http://slist.lilotux.net/linux/qmetronome/index_en.html

Basicaly, the following pactl commands are used :


pactl upload-sample tick.wav tick


Every x ms,

pactl play-sample tick


pactl remove-sample tick


It works well if my PC is already playing a MP3. But if my PC is silent, 
the 3 first ticks don't look very accurate.

Any hint ?


Regards


Stephane



___
pulseaudio-discuss mailing list
pulseaudio-discuss@mail.0pointer.de
https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss


Re: [pulseaudio-discuss] Metronome

2010-01-11 Thread Arun Raghavan
On Mon, 2010-01-11 at 13:33 +0100, Stéphane List wrote:
[...]
 It works well if my PC is already playing a MP3. But if my PC is silent, 
 the 3 first ticks don't look very accurate.
 Any hint ?

Sounds like this might be your problem:

https://tango.0pointer.de/pipermail/pulseaudio-discuss/2009-December/005893.html

Cheers,
Arun

___
pulseaudio-discuss mailing list
pulseaudio-discuss@mail.0pointer.de
https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss


[pulseaudio-discuss] Pull request: Autospawn fix

2010-01-11 Thread Tanu Kaskinen
Hi Lennart,

I have modified the daemon so that if --start is used, the start-up is
aborted if there's a server address configured in client.conf, the X11
properties or the PULSE_SERVER environment variable. The fix is in the
fixes branch of my gitorious repo
(http://gitorious.org/~tanuk/pulseaudio/tanuk-clone/commits/fixes). The
branch is rebased against the current master, and contains two purely
cosmetic fixes also.

I already notified you about this in irc a couple of days ago, but that
may have gone unnoticed, so I thought maybe the mailing list is a more
appropriate channel.

-- 
Tanu Kaskinen

___
pulseaudio-discuss mailing list
pulseaudio-discuss@mail.0pointer.de
https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss


Re: [pulseaudio-discuss] Pull request: Autospawn fix

2010-01-11 Thread Colin Guthrie
'Twas brillig, and Tanu Kaskinen at 11/01/10 14:03 did gyre and gimble:
 Hi Lennart,
 
 I have modified the daemon so that if --start is used, the start-up is
 aborted if there's a server address configured in client.conf, the X11
 properties or the PULSE_SERVER environment variable. The fix is in the
 fixes branch of my gitorious repo
 (http://gitorious.org/~tanuk/pulseaudio/tanuk-clone/commits/fixes). The
 branch is rebased against the current master, and contains two purely
 cosmetic fixes also.
 
 I already notified you about this in irc a couple of days ago, but that
 may have gone unnoticed, so I thought maybe the mailing list is a more
 appropriate channel.

Nicely done :) I'll leave it to Lennart to pull to avoid confusion.

On a (semi) related note, I opened this yesterday:
http://pulseaudio.org/ticket/773

If a muli-user system allows one user to setup network support so he can
ssh to another machine, if a second user logs in, the current connection
code will try and connect to localhost via tcp prior to auto-spawning.

Sadly this connection will fail due to a permission problem (e.g. user b
is not allowed to access user a's PA) and this failure ends the
connection loop prior to the point autospawning would kick in thus
failing to load PA for poor user b.


So there is a problem here which can be solved in several ways.

 1. Do not attempt to connect to localhost via tcp at all during normal
startup.
 2. Do attempt to connect but do not fail on an unauthorised connection
(which would also cover the case of a random app which is not PA
listening on that socket effectively DoS'ing autospawn) thus allowing
autospawn.
 3. Do not have a default pulseaudio TCP port and thus do not try and
connect (like 1. but more far reaching). Currently only one user on a
system can load TCP, but if multiple users want to use it to SSH out and
run applications this is bad. The networking module should load and try
to listen on a pool of TCP ports (e.g. a range of numbers for
firewalling ease) As the TCP port number is put into the x11
PULSE_SERVER property, it doesn't actually matter that the number is
standard. The module should randomly pick numbers from the pool (or
count up) until it finds one it can use (e.g. not already bound).


Personally, with a longer term view for networking support etc, I think
1 or 3 are more appropriate. If we implement 2, if someone turns on
anonymous access + tcp it can effectively DoS another user from
autospawning PA too and can hang applications as by virtue of the other
user being in active (on a single seat system) they wont have permission
to output the sound and the streams will be corked).

WDYT?

Col


-- 

Colin Guthrie
gmane(at)colin.guthr.ie
http://colin.guthr.ie/

Day Job:
  Tribalogic Limited [http://www.tribalogic.net/]
Open Source:
  Mandriva Linux Contributor [http://www.mandriva.com/]
  PulseAudio Hacker [http://www.pulseaudio.org/]
  Trac Hacker [http://trac.edgewall.org/]

___
pulseaudio-discuss mailing list
pulseaudio-discuss@mail.0pointer.de
https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss