Re: [pulseaudio-discuss] [pulseaudio-commits] r2495 - /trunk/src/Makefile.am

2008-06-04 Thread Lennart Poettering
On Wed, 04.06.08 09:42, Lennart Poettering ([EMAIL PROTECTED]) wrote:

 On Tue, 03.06.08 19:55, [EMAIL PROTECTED] ([EMAIL PROTECTED]) wrote:
 
  Author: coling
  Date: Tue Jun  3 21:55:01 2008
  New Revision: 2495
  
  URL: 
  http://0pointer.de/cgi-bin/viewcvs.cgi?rev=2495root=pulseaudioview=rev
  Log:
  Also link libpulsecore.la to some libraries (needed for
  logging). Discovered while compiling with --as-needed
 
 No, this is not a good idea. libpulsecore is supposed to be used only
 by the PA server, it should not be linked against the client tools
 where padsp is one example of.

Grrh, forget my complaining please, you seem to have commited the fix
already!

Sorry for the confusion!

Lennart

-- 
Lennart PoetteringRed Hat, Inc.
lennart [at] poettering [dot] net ICQ# 11060553
http://0pointer.net/lennart/   GnuPG 0x1A015CC4
___
pulseaudio-discuss mailing list
pulseaudio-discuss@mail.0pointer.de
https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss


Re: [pulseaudio-discuss] Help in setting up PA... SOLVED

2008-06-04 Thread Juan A Fuentes Bermudez
no me digas que hablas español?

saludos 



  - Original Message - 
  From: Richard Geddes 
  To: General PulseAudio Discussion 
  Sent: Tuesday, June 03, 2008 11:56 PM
  Subject: Re: [pulseaudio-discuss] Help in setting up PA... SOLVED


  de nada... fue un placer... tambien aprendi algo...

  Saludos
  R

  Juan A Fuentes Bermudez wrote: 
hi, very very thank you, 

now i am using the last configuration that you say me, now are 3 cards 
actives, only the HDMI is not working via PA,

i will trying coment and uncoment one to one devices, i am think that HDMI 
device only have output not have input 

very very thank my friend 

you have a spanish jamon fron my :)


- Original Message - 
  From: Richard Geddes 
  To: General PulseAudio Discussion 
  Sent: Tuesday, June 03, 2008 10:24 PM
  Subject: Re: [pulseaudio-discuss] Help in setting up PA... SOLVED


  ok... 

  1) The/var/log/messages indicates that you are running the pa server as 
root (you say as well) and it also says the pa server is not intended to be run 
as root... so you might want to change to a regular user and use sudo for root 
related activities.

  2) I think that the terjeta 3 requires some special parameters ... 
similar to tarjeta 2.  I'm not familiar with ice1724 device driver, but you may 
want to try the same setup for tarjeta 3 as for tarjeta 2.  This is just a 
guess... anyone with knowledge about how to setup an ice1724 source/sink in 
pa... please speak up now... 

  3) Of course, it looks like tarjeta 3 was identified by the 
module-detect/module-hal-detect.  What we've done is disable this and tried to 
set the sources/sinks manually.  module-detect/module-hal-detect seems to be an 
all or nothing proposition...  if anyone knows of a way to auto-detect specific 
devices and manually set others in the same config file... please speak up now. 
  

  Well, you might want to try this (once again, a guess):

  a) re-enable the auto-detect  - we know this will detect tarjeta 0 
and 3, and not tarjeta 1 and 2 
  b) add only the manual configuration for tarjeta 2, after that


  So your default.pa file would contain:


  ### Automatically load driver modules depending on the hardware available
  .ifexists module-hal-detect.so
  load-module module-hal-detect
  .else
  ### Alternatively use the static hardware detection module (for systems 
that
  ### lack HAL support)
  load-module module-detect
  .endif

  # Load the devices:
  #load-module module-alsa-sink sink_name=nvidia_out device=hw:0
  #load-module module-alsa-source source_name=nvidia_in device=hw:0

  #load-module module-alsa-sink sink_name=hdmi_out device=hw:1
  #load-module module-alsa-source source_name=hdmi_in device=hw:1

  load-module module-alsa-sink sink_name=ewx2496_out device=hw:2 
channels=10 channel_map=left,right,aux0,aux1,aux2,aux3,aux4,aux5,aux6,aux7
  load-module module-alsa-source source_name=ewx2496_in device=hw:2 
channels=12 
channel_map=left,right,aux0,aux1,aux2,aux3,aux4,aux5,aux6,aux7,aux8,aux9

  #load-module module-alsa-sink sink_name=e192m_out device=hw:3
  #load-module module-alsa-source source_name=e192m_in device=hw:3

  # Select default device
  #set-default-sink nvidia_out 
  #set-default-source nvidia_in

  Let's see if module-hal-detect/module-detect allows manual loading of 
sources/sinks.


  R

  Juan A Fuentes Bermudez wrote: 
hi, the problem is partial solved

i an coment and paste the module taht you say my

the pa server not start after reboot, 

i am coment and uncoment one to one, to discart waht is the card tthat 
cause problem , 

# Load the devices:
load-module module-alsa-sink sink_name=nvidia_out device=hw:0
load-module module-alsa-source source_name=nvidia_in device=hw:0

#load-module module-alsa-sink sink_name=hdmi_out device=hw:1
#load-module module-alsa-source source_name=hdmi_in device=hw:1

load-module module-alsa-sink sink_name=ewx2496_out device=hw:2 
channels=10 channel_map=left,right,aux0,aux1,aux2,aux3,aux4,aux5,aux6,aux7
load-module module-alsa-source source_name=ewx2496_in device=hw:2 
channels=12 
channel_map=left,right,aux0,aux1,aux2,aux3,aux4,aux5,aux6,aux7,aux8,aux9

#load-module module-alsa-sink sink_name=e192m_out device=hw:3
#load-module module-alsa-source source_name=e192m_in device=hw:3

in this mode, load pa server, and in the padevchooser apear the ewx2496 
card :) very  happy 

when un coment the e192 card, again pa server not start same when 
uncoment hdmi card 

i like active also e192 card, is posible?


i am to paste this info, this is the first mail i want to send to list :

hi, the server not start, always i am login as root

can you test the information?



Re: [pulseaudio-discuss] [pulseaudio-commits] r2495 - /trunk/src/Makefile.am

2008-06-04 Thread Colin Guthrie
Lennart Poettering wrote:
 On Wed, 04.06.08 09:42, Lennart Poettering ([EMAIL PROTECTED]) wrote:
 
 On Tue, 03.06.08 19:55, [EMAIL PROTECTED] ([EMAIL PROTECTED]) wrote:

 Author: coling
 Date: Tue Jun  3 21:55:01 2008
 New Revision: 2495

 URL: 
 http://0pointer.de/cgi-bin/viewcvs.cgi?rev=2495root=pulseaudioview=rev
 Log:
 Also link libpulsecore.la to some libraries (needed for
 logging). Discovered while compiling with --as-needed
 No, this is not a good idea. libpulsecore is supposed to be used only
 by the PA server, it should not be linked against the client tools
 where padsp is one example of.
 
 Grrh, forget my complaining please, you seem to have commited the fix
 already!
 
 Sorry for the confusion!

No it's OK. I did ask on IRC immediately after the commit to ask why 
some link against the library and some the files directly and if I'd 
done this correctly, so I appreciate the response even if I did work it 
out for myself :D

The trouble was I had my systems pulse devel package installed and it 
didn't mess up the build when I tested it. When I submitted a patched 
mdv package to our build cluster (we enable --as-needed by default now) 
it spat out the error and I knew I had a problem and figured it out from 
there :)

Cheers.

Col


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


Re: [pulseaudio-discuss] [pulseaudio-commits] r2495 -/trunk/src/Makefile.am

2008-06-04 Thread Juan A Fuentes Bermudez
hi

can any body tell me how can find data abaut install PA thru svn step by 
step?

thank





- Original Message - 
From: Colin Guthrie [EMAIL PROTECTED]
To: pulseaudio-discuss@mail.0pointer.de
Sent: Wednesday, June 04, 2008 10:14 AM
Subject: Re: [pulseaudio-discuss] [pulseaudio-commits] 
r2495 -/trunk/src/Makefile.am


 Lennart Poettering wrote:
 On Wed, 04.06.08 09:42, Lennart Poettering ([EMAIL PROTECTED]) 
 wrote:

 On Tue, 03.06.08 19:55, [EMAIL PROTECTED] 
 ([EMAIL PROTECTED]) wrote:

 Author: coling
 Date: Tue Jun  3 21:55:01 2008
 New Revision: 2495

 URL: 
 http://0pointer.de/cgi-bin/viewcvs.cgi?rev=2495root=pulseaudioview=rev
 Log:
 Also link libpulsecore.la to some libraries (needed for
 logging). Discovered while compiling with --as-needed
 No, this is not a good idea. libpulsecore is supposed to be used only
 by the PA server, it should not be linked against the client tools
 where padsp is one example of.

 Grrh, forget my complaining please, you seem to have commited the fix
 already!

 Sorry for the confusion!

 No it's OK. I did ask on IRC immediately after the commit to ask why
 some link against the library and some the files directly and if I'd
 done this correctly, so I appreciate the response even if I did work it
 out for myself :D

 The trouble was I had my systems pulse devel package installed and it
 didn't mess up the build when I tested it. When I submitted a patched
 mdv package to our build cluster (we enable --as-needed by default now)
 it spat out the error and I knew I had a problem and figured it out from
 there :)

 Cheers.

 Col


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

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


Re: [pulseaudio-discuss] [pulseaudio-commits] r2495 - /trunk/src/Makefile.am

2008-06-04 Thread Lennart Poettering
On Wed, 04.06.08 09:14, Colin Guthrie ([EMAIL PROTECTED]) wrote:

 The trouble was I had my systems pulse devel package installed and it 
 didn't mess up the build when I tested it. When I submitted a patched 
 mdv package to our build cluster (we enable --as-needed by default now) 
 it spat out the error and I knew I had a problem and figured it out from 
 there :)

/me thinks --as-needed is a bad idea. A really bad idea.

Lennart

-- 
Lennart PoetteringRed Hat, Inc.
lennart [at] poettering [dot] net ICQ# 11060553
http://0pointer.net/lennart/   GnuPG 0x1A015CC4
___
pulseaudio-discuss mailing list
pulseaudio-discuss@mail.0pointer.de
https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss


Re: [pulseaudio-discuss] [pulseaudio-commits] r2495 -/trunk/src/Makefile.am

2008-06-04 Thread Colin Guthrie
Juan A Fuentes Bermudez wrote:
 can any body tell me how can find data abaut install PA thru svn step by 
 step?

Please try not to hijack threads ;)

Basically it's a matter of checking out the svn, running ./bootstrap.sh 
then running make Set your own --prefix if you don't want it to 
interfere with your system packages.

Col

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


Re: [pulseaudio-discuss] [pulseaudio-commits] r2495 - /trunk/src/Makefile.am

2008-06-04 Thread Lennart Poettering
On Wed, 04.06.08 13:17, Colin Guthrie ([EMAIL PROTECTED]) wrote:

 Not to try and go tooo far off topic for this list, but can you 
 elaborate on why?

Because it tapes over bugs. And in times of dso
constructors/destructors and dynamic typing systems such as gtype the
linking rules are not as simple and obvious as some people might
think. As one example it will break PA if you decide to link some of
the modules directly into PA if you do a bit more exotic linking like
i currently do in my dev tree. 

The right fix to for the problem is libtool's Depends.private, not
coming up with some magic thing that eagerly drops deps without
knowing what is really going on.

I think the Debian devs posted a longer explanation of why -as-needed
is bad a while back somewhere.

Lennart

-- 
Lennart PoetteringRed Hat, Inc.
lennart [at] poettering [dot] net ICQ# 11060553
http://0pointer.net/lennart/   GnuPG 0x1A015CC4
___
pulseaudio-discuss mailing list
pulseaudio-discuss@mail.0pointer.de
https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss


Re: [pulseaudio-discuss] [pulseaudio-commits] r2495-/trunk/src/Makefile.am

2008-06-04 Thread Juan A Fuentes Bermudez
thank




- Original Message - 
From: Colin Guthrie [EMAIL PROTECTED]
To: pulseaudio-discuss@mail.0pointer.de
Sent: Wednesday, June 04, 2008 2:18 PM
Subject: Re: [pulseaudio-discuss] [pulseaudio-commits] 
r2495-/trunk/src/Makefile.am


 Juan A Fuentes Bermudez wrote:
 can any body tell me how can find data abaut install PA thru svn step by
 step?

 Please try not to hijack threads ;)

 Basically it's a matter of checking out the svn, running ./bootstrap.sh
 then running make Set your own --prefix if you don't want it to
 interfere with your system packages.

 Col

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

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


[pulseaudio-discuss] [OT] Re: Help in setting up PA... SOLVED

2008-06-04 Thread Richard Geddes
mi madre es peruana y mi padre es escosés pero la mayoría de mi vida he 
pasado en los estados unidos... asi que, para evitar malentendidos, uso 
ingles en discuccioes tecnicas


Saludos
R

Juan A Fuentes Bermudez wrote:

no me digas que hablas español?
 
saludos
 
 
 


- Original Message -
*From:* Richard Geddes mailto:[EMAIL PROTECTED]
*To:* General PulseAudio Discussion
mailto:pulseaudio-discuss@mail.0pointer.de
*Sent:* Tuesday, June 03, 2008 11:56 PM
*Subject:* Re: [pulseaudio-discuss] Help in setting up PA... SOLVED

de nada... fue un placer... tambien aprendi algo...

Saludos
R

Juan A Fuentes Bermudez wrote:

hi, very very thank you,
 
now i am using the last configuration that you say me, now are 3

cards actives, only the HDMI is not working via PA,
 
i will trying coment and uncoment one to one devices, i am think

that HDMI device only have output not have input
 
very very thank my friend
 
you have a spanish jamon fron my :)
 
 
- Original Message -


*From:* Richard Geddes mailto:[EMAIL PROTECTED]
*To:* General PulseAudio Discussion
mailto:pulseaudio-discuss@mail.0pointer.de
*Sent:* Tuesday, June 03, 2008 10:24 PM
*Subject:* Re: [pulseaudio-discuss] Help in setting up PA...
SOLVED

ok...

1) The/var/log/messages indicates that you are running the pa
server as root (you say as well) and it also says the pa
server is not intended to be run as root... so you might want
to change to a regular user and use sudo for root related
activities.

2) I think that the terjeta 3 requires some special
parameters ... similar to tarjeta 2.  I'm not familiar with
ice1724 device driver, but you may want to try the same setup
for tarjeta 3 as for tarjeta 2.  This is just a guess...
anyone with knowledge about how to setup an ice1724
source/sink in pa... please speak up now...

3) Of course, it looks like tarjeta 3 was identified by the
module-detect/module-hal-detect.  What we've done is disable
this and tried to set the sources/sinks manually. 
module-detect/module-hal-detect seems to be an all or nothing

proposition...  if anyone knows of a way to auto-detect
specific devices and manually set others in the same config
file... please speak up now.  


Well, you might want to try this (once again, a guess):

a) re-enable the auto-detect  - we know this will detect
tarjeta 0 and 3, and not tarjeta 1 and 2
b) add only the manual configuration for tarjeta 2, after
that


So your default.pa file would contain:

### Automatically load driver modules depending on the
hardware available
.ifexists module-hal-detect.so
load-module module-hal-detect
.else
### Alternatively use the static hardware detection module
(for systems that
### lack HAL support)
load-module module-detect
.endif
 
# Load the devices:

#load-module module-alsa-sink sink_name=nvidia_out device=hw:0
#load-module module-alsa-source source_name=nvidia_in device=hw:0
 
#load-module module-alsa-sink sink_name=hdmi_out device=hw:1

#load-module module-alsa-source source_name=hdmi_in device=hw:1
 
load-module module-alsa-sink sink_name=ewx2496_out

device=hw:2 channels=10
channel_map=left,right,aux0,aux1,aux2,aux3,aux4,aux5,aux6,aux7
load-module module-alsa-source source_name=ewx2496_in
device=hw:2 channels=12
channel_map=left,right,aux0,aux1,aux2,aux3,aux4,aux5,aux6,aux7,aux8,aux9
 
#load-module module-alsa-sink sink_name=e192m_out device=hw:3

#load-module module-alsa-source source_name=e192m_in device=hw:3
 
# Select default device

#set-default-sink nvidia_out
#set-default-source nvidia_in

Let's see if module-hal-detect/module-detect allows manual
loading of sources/sinks.


R

Juan A Fuentes Bermudez wrote:

hi, the problem is partial solved
 
i an coment and paste the module taht you say my
 
the pa server not start after reboot,
 
i am coment and uncoment one to one, to discart waht is the

card tthat cause problem ,
 
# Load the devices:

load-module module-alsa-sink sink_name=nvidia_out device=hw:0
load-module module-alsa-source source_name=nvidia_in device=hw:0
 
#load-module module-alsa-sink sink_name=hdmi_out device=hw:1

#load-module module-alsa-source source_name=hdmi_in device=hw:1
 
load-module module-alsa-sink sink_name=ewx2496_out

device=hw:2 channels=10
 

Re: [pulseaudio-discuss] [OT] Re: Help in setting up PA... SOLVED

2008-06-04 Thread Lennart Poettering
On Wed, 04.06.08 10:38, Richard Geddes ([EMAIL PROTECTED]) wrote:

 mi madre es peruana y mi padre es escosés pero la mayoría de mi vida he 
 pasado en los estados unidos... asi que, para evitar malentendidos, uso 
 ingles en discuccioes tecnicas

Guys could we stop this please?

What you guys are exchanging here is very much off-topic and marking
it with an [OT] doesn't make that any better.

Then, this is supposed to be an english language mailing list. Don't
post in spanish.

Also, you guys keep sending  40KB emails to a mailing list. This
is very impolite to people with slow internert connections. And I have
to ack every single message over this size limit manually in
mailman -- this one is the last one will accept in your thread.

Finally, please try to format your emails more sensibly in a more, uh,
mailing list compatible way. This includes removing irrelevant text in
replies and not doing stupid top-posting (TOFU).

Let's all help to keep the signal-to-noise ratio on our mailing lists
high, otherwise you are making it very difficult for people who
subscribe to a lot of lists to find the relevant posts in this giant
haystack in their limited time. If you want high quality and friendly
replies to your posts from time to time, then please don't scare the
devs away with lowering the signal-to-noise ratio unecessarily.

Thank you very much for your understanding,

Lennart

-- 
Lennart PoetteringRed Hat, Inc.
lennart [at] poettering [dot] net ICQ# 11060553
http://0pointer.net/lennart/   GnuPG 0x1A015CC4
___
pulseaudio-discuss mailing list
pulseaudio-discuss@mail.0pointer.de
https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss


Re: [pulseaudio-discuss] [OT] Re: Help in setting up PA... SOLVED

2008-06-04 Thread Juan A Fuentes Bermudez
hi, sorry, i am a low vision people, if the rules not want people as my, i 
am go out

bye





- Original Message - 
From: Lennart Poettering [EMAIL PROTECTED]
To: General PulseAudio Discussion pulseaudio-discuss@mail.0pointer.de
Sent: Wednesday, June 04, 2008 9:06 PM
Subject: Re: [pulseaudio-discuss] [OT] Re: Help in setting up PA... SOLVED


On Wed, 04.06.08 10:38, Richard Geddes ([EMAIL PROTECTED]) wrote:

 mi madre es peruana y mi padre es escosés pero la mayoría de mi vida he
 pasado en los estados unidos... asi que, para evitar malentendidos, uso
 ingles en discuccioes tecnicas

Guys could we stop this please?

What you guys are exchanging here is very much off-topic and marking
it with an [OT] doesn't make that any better.

Then, this is supposed to be an english language mailing list. Don't
post in spanish.

Also, you guys keep sending  40KB emails to a mailing list. This
is very impolite to people with slow internert connections. And I have
to ack every single message over this size limit manually in
mailman -- this one is the last one will accept in your thread.

Finally, please try to format your emails more sensibly in a more, uh,
mailing list compatible way. This includes removing irrelevant text in
replies and not doing stupid top-posting (TOFU).

Let's all help to keep the signal-to-noise ratio on our mailing lists
high, otherwise you are making it very difficult for people who
subscribe to a lot of lists to find the relevant posts in this giant
haystack in their limited time. If you want high quality and friendly
replies to your posts from time to time, then please don't scare the
devs away with lowering the signal-to-noise ratio unecessarily.

Thank you very much for your understanding,

Lennart

-- 
Lennart PoetteringRed Hat, Inc.
lennart [at] poettering [dot] net ICQ# 11060553
http://0pointer.net/lennart/   GnuPG 0x1A015CC4
___
pulseaudio-discuss mailing list
pulseaudio-discuss@mail.0pointer.de
https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss 

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


[pulseaudio-discuss] Summary of the PulseAudio/Bluetooth discussions at the BlueZ meeting in Helsinki

2008-06-04 Thread Lennart Poettering
Heya!

(Luiz, please forward this to the bluez ML!)

So, here's my summary of the grand plan to get PA and BT working well
together. This is basically the result of the audio discussions during
the BlueZ Meeting we had in Helsinki that ended today. Especially for
you, João-Paulo, this might be very interesting!

There should be two new PA modules, module-bluetooth-discover and
module-bluetooth-device. The former will use D-Bus to connect to the
BlueZ system services and whenever a new BT audio devices appears load
one m-bt-device instance for it. (as a side node: in contrast to linux
kernel modules, PA modules can be loaded more than once at the same
time). 

The latter, m-bt-device, then connects to the BlueZ audio service via one
BlueZ specific well known unix socket, configures a connection to the
BT device, gets a BT socket fd passed in via the unix socket and then
hands this over to its RT thread. The code for this would actually be
very similar to module-esd-sink which we ship already. m-esd-s is a
sink for PA that hands data to an existing EsounD server. It's basic
structure is very similar: we first configure the ESD connection from
the main thread via exchanging a few simple packets and then hand the
actual communication socket to the RT thread for the actual work. The
big difference in logic is mostly that the BT module needs to encode
the audio data to SBC/SCO first, while the ESD module just spits raw
PCM to the TCP stream. And then, the timing needs to be implemented
differently. 

Neither ESD nor A2DP/SCO provide any reasonable timing
source. However, the TCP socket used by ESD provides flow control
which we misuse for timing estimation. Unfortunately A2DP/SCO doesn't
even provide that, so we need to roll our own timing all the time --
with the exception that for the SCO case we can probably deduce the
remote clock from the time we get the recording packets flowing
in. Since for A2DP we mostly lack recording support we don't have that
clock and we have no other option than just using the raw local clock.
The BT socket uses DGRAM/SEQPACKET as socket type, This should
actually make things much easier than for the m-e-s case, since packet
deserilization is much easier.

Since we only have a single socket for both recording and playback
m-bt-device should register both a sink and a source at the same time
and run it from the same RT thread. This is similar to what module-oss
does, but different from e.g. the alsa modules which run the sink and
the source from seperate threads.

The seperation of m-bt-discover and m-bt-device is very similar to the
seperation between module-hal and module-alsa-{sink,source} or
module-zeroconf-discover and module-tunnel.

To improve the timing estimation, the BlueZ team will add support for
and SIOCOUTQ/SIOCINQ on the BT audio socket. This should tell us how
many bytes are buffered locally. Of course, we still would have no
idea how many bytes are buffered on the receivng side, but it would
help us at least a bit to make our timing more reliable. Also, they
want to add a new sockopt which would allow us to query the BT clock
of the BT device. We can probably assume that the audio clock of the
BT device is dependant or identical to the BT clock. This would allow
us to make sure we stay in sync with the device as much as possible,
even tough we still would have no idea about the actual latency.

The first step to implement is certainly m-bt-device without any fancy
timing. The next step would be m-bt-discover and finally, the fancier
timing estimation should be implemented. And finally the native volume
support should be implemented.

m-bt-device would probably not use D-Bus itself at all. Only
m-bt-discover would.

Eventually the btaudio unix socket should also be used to pass the key
events from the bt head set. I'd need to add a simple subsystem to
pass them on to the application then. Those keypresses would then be
passed to the application inline via the audio API. On one hand I see
that it would be good send the key events inline to make clear to
which audio device they belong. OTOH I have a bad feeling about this
because I don't want to add yet another key event subsystem, in
addtion to XIE, the linux input stuff and even HAL. We need to think
about this a bit more. (It is interesting to note, that having the
sound server forward pause and resume request to applications is
on the todo list anyway, to allow policy modules to request music
playback stopping on imcoming phone calls and suchlike. So doing the
full audio key set of keypresses would be a simple extension of
that.)

Marcel, Johan, Luiz, Marc-André, Claudio, did I miss anything?

Lennart

-- 
Lennart PoetteringRed Hat, Inc.
lennart [at] poettering [dot] net ICQ# 11060553
http://0pointer.net/lennart/   GnuPG 0x1A015CC4
___
pulseaudio-discuss mailing list
pulseaudio-discuss@mail.0pointer.de

[pulseaudio-discuss] Problems with Pulseaudio and Bluetooth Headset

2008-06-04 Thread James Bottomley
I suspect this is some type of resampler problem rather than an actual
connection problem.  The headset is a GN6210H (which is a phone headset,
so mono earpiece and mono mic).  The only other oddity is that apart
from having only one channel, its sample rate is 8000Hz.

I have it all correctly plumbed into alsa using bluez and if I just use
alsa, I can send sound to it with mplayer using

mplayer -ao alsa:device=headset

Since mplayer sees the device directly, it sends the sound stream as

AO: [alsa] 800Hz 1ch s16le (2 bytes per sample)

And everything sounds fine.

When I plug it into pulseaudio with

pactl load-module module-alsa-sink device=headset

It correctly picks up the sample rate and channels.  However, trying to
switch an application to it results in dramatic speed increases and the
output being chopped to pieces.  If I set up pulseaudio only to have
this device and nothing else, mplayer plays the sound file at at least
2x the usual speed.

Since the output has this:

AO: [pulse] 44100Hz 2ch s16le (2 bytes per sample)

I suspect the problem is somewhere in the pulseaudio resampling down
from 2 channels at 44100Hz to a single channel at 8000Hz.  I've tried
forcing different resampling methods with slightly different sounding
results but still playing at at least 2x the speed.

James




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


[pulseaudio-discuss] Sink volume linearity

2008-06-04 Thread Matthew Patterson
Hello everyone,

I have been playing around with the volume control on my whole home 
audio system trying to make it nonlinear so we are able to fine tune the 
volumes we listen at most. Unfortunately it appears that the sink volume 
controls do not allow enough range (I think this would be dynamic range 
in audio terms). Basically, if I set the system up so 100% volume is as 
loud as I want things to go, 1% is not quiet enough. I have tried 
setting the sink volumes using pacmd where the range of volumes is 
1-65535. A value of 0 is muted, but 1 is quite loud.

Any thoughts/experiences on this?

I'm contemplating setting both the stream and sink volumes so I can have 
more granularity of control.

Matt

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