Re: [pulseaudio-discuss] [PATCHv3 0/4] Read and store UCM data as proplist
On May 17, 2011, at 8:56 AM, Lu Guanqun wrote: On Thu, May 12, 2011 at 02:56:04AM +0800, Jorge Eduardo Candelaria wrote: Ok, I'll copy the jack code we have into module-alsa-card. This will allow for simple jack removal/insertion events to be propagated to pulseaudio. We won't be able to do the complicated stuff mentioned above, but should at least be able to do simple speaker/headphone switching. Hi Jorge, I'm interested in your jack detection code, when do you decide to send it out? :-) Don't worry, I haven't forgotten about it :). I plan to send the new patches tomorrow if all goes well with testing. Regards, Jorge -- guanqun ___ pulseaudio-discuss mailing list pulseaudio-discuss@mail.0pointer.de https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss
[pulseaudio-discuss] build error
Hello All,
This is first mail to the list, Hello to evreyone in the list,
I am new to pulseaudio and I am trying to build the pulseaudio using make
and get the following build errors:
{standard input}: Assembler messages:
{standard input}:64: Error: selected processor does not support ARM mode
`ssat r0,#16,r0'
{standard input}:79: Error: selected processor does not support ARM mode
`ssat r2,#16,r2'
{standard input}:80: Error: selected processor does not support ARM mode
`ssat r3,#16,r3'
{standard input}:81: Error: selected processor does not support ARM mode
`pkhbt r0,r3,r2,LSL#16'
{standard input}:98: Error: selected processor does not support ARM mode
`ssat r2,#16,r2'
{standard input}:99: Error: selected processor does not support ARM mode
`ssat r3,#16,r3'
{standard input}:100: Error: selected processor does not support ARM mode
`ssat r4,#16,r4'
{standard input}:101: Error: selected processor does not support ARM mode
`ssat r5,#16,r5'
{standard input}:102: Error: selected processor does not support ARM mode
`pkhbt r0,r3,r2,LSL#16'
{standard input}:103: Error: selected processor does not support ARM mode
`pkhbt r1,r5,r4,LSL#16'
make[3]: *** [libpulsecore_0.9.21_la-svolume_arm.lo] Error 1
make[3]: Leaving directory `/home/himanshu/pulse_new/src'
make[2]: *** [all] Error 2
make[2]: Leaving directory `/home/himanshu/pulse_new/src'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/himanshu/pulse_new'
make: *** [all] Error 2
can someone help me to resolve these errors. Thanks in advance
BR,
Himanshu
___
pulseaudio-discuss mailing list
pulseaudio-discuss@mail.0pointer.de
https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss
Re: [pulseaudio-discuss] [PATCHv3 0/4] Read and store UCM data as proplist
On Wed, May 18, 2011 at 02:22:06PM +0800, Jorge Eduardo Candelaria wrote: On May 17, 2011, at 8:56 AM, Lu Guanqun wrote: On Thu, May 12, 2011 at 02:56:04AM +0800, Jorge Eduardo Candelaria wrote: Ok, I'll copy the jack code we have into module-alsa-card. This will allow for simple jack removal/insertion events to be propagated to pulseaudio. We won't be able to do the complicated stuff mentioned above, but should at least be able to do simple speaker/headphone switching. Hi Jorge, I'm interested in your jack detection code, when do you decide to send it out? :-) Don't worry, I haven't forgotten about it :). I plan to send the new patches tomorrow if all goes well with testing. Thanks for the update :) Regards, Jorge -- guanqun -- guanqun ___ pulseaudio-discuss mailing list pulseaudio-discuss@mail.0pointer.de https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss
Re: [pulseaudio-discuss] Receiving RTP streams with pulseaudio
On Tue, 17 May 2011 21:51:35 +0200, Michael Trunner mich...@trunner.de
wrote:
I'm trying to setup Pulseaudio to receive RTP/Multicast steams. Sender
should be vlc, (and receiver should be pulseaudio). I activated
module-rtp-recv (and module-rtp-send) with papref, but I can't get it
work. Can some one explain me what I have to do? Or how to debug it.
First you need to make sure that VLC uses an RTP payload format that
PulseAudio understands, typically L16/44100/2 (signed big endian 16-bits
stereo at 44100 Hz). By default, VLC will not decode the audio. Also make
sure SAP is enabled.
For example:
# IP=224.0.0.42
# vlc --sout-keep --no-sout-video --no-sout-spu \
--sout
#transcode{acodec=s16b,samplerate=44100}:gather:rtp{sap,dst=$IP}
Then you need to configure PulseAudio to use the standard SAP address as
specified in IETF RFC2974 §3, corresponding to the multicast scope that VLC
is configured to use, in particular:
- 224.2.127.254 (SAP.MCAST.NET) for global IPv4,
- ff0e::2:7ffe for global IPv6,
- 224.0.0.255 for link-local IPv4,
- ff02::2:7ffe for link-local IPv6.
By default, PulseAudio uses a proprietary non-standard SAP group, namely
224.0.0.56. This cannot interoperate with VLC.
--
Rémi Denis-Courmont
http://www.remlab.net/
___
pulseaudio-discuss mailing list
pulseaudio-discuss@mail.0pointer.de
https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss
[pulseaudio-discuss] my paulseaudio is not running as daemon
Hi, I need developing PA client App,so I download pulseaudio-0.9.22 and run ./configure,make,make install.After install finished,I run pacmd,but display No pulseaudio daemon running,or not running as session daemon.Then,I run ps aux | grep pulse,but display pulseaudio -start. Pls help me how can I do. Thanks zhen ___ pulseaudio-discuss mailing list pulseaudio-discuss@mail.0pointer.de https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss
Re: [pulseaudio-discuss] How to find the latest created bluetooth sink/source via event hook?
Hi, 'Twas brillig, and Lin, Mengdong at 18/05/11 04:43 did gyre and gimble: I’m developing an routing module to automatically set a new created Bluetooth sink as the default sink when a Bluetooth headset is connected. Please note that there already exists a module called module-switch-on-connect which does this task, but for all new sinks, not just BT sinks. I suspect it would be trivial to modify it to accept arguments which control things (e.g. device_types=all|bluetooth|usb|network - or a combination of those i.e. device_types=bluetooth,usb) rather than create a whole new module. If you want your work upstreamed, I would personally take this approach as I'd rather not get too much duplication of code in different modules. So I need to get the new BT sink when it’s created. Just so you know, I will am intending on shaking up the routing system in PA after v1 is released which will hopefully make this kind of thing easier to implement and manage. Feel free to ask if you want more details, but essentially the routing will be based on priority lists of devices rather than just setting a single device to use. But when I hook event “ PA_CORE_HOOK_SINK_NEW”, I found that the sink pointer for the callback function is **not** the real sink pointer value. Correct. This hook is fired before the sink is created to allow you to modify critical details about the sink before it is created. If you want a hook that informs you *after* the sink is created, then you can use PA_CORE_HOOK_SINK_PUT as shown in module-switch-on-connect.c code. So could anyone share some hint on how to find the new created sink/source? Shall I iterate the core’s sink/source list and compare pointers in sink/source state change callback function? I suspect the *_PUT hook is what you want :) Cheers Col -- Colin Guthrie gmane(at)colin.guthr.ie http://colin.guthr.ie/ Day Job: Tribalogic Limited [http://www.tribalogic.net/] Open Source: Mageia Contributor [http://www.mageia.org/] 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
[pulseaudio-discuss] my paulseaudio is not running as daemon
Hi, I need developing PA client App,so I download pulseaudio-0.9.22 and run ./configure,make,make install.After install finished,I run pacmd,but display No pulseaudio daemon running,or not running as session daemon.Then,I run ps aux | grep pulse,but display pulseaudio -start. Pls help me how can I do. Thanks zhen ___ pulseaudio-discuss mailing list pulseaudio-discuss@mail.0pointer.de https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss
Re: [pulseaudio-discuss] build error
On Wed, 2011-05-18 at 12:00 +0530, Himanshu Chug wrote:
Hello All,
This is first mail to the list, Hello to evreyone in the list,
Hello. :)
I am new to pulseaudio and I am trying to build the pulseaudio using
make and get the following build errors:
{standard input}: Assembler messages:
{standard input}:64: Error: selected processor does not support ARM
mode `ssat r0,#16,r0'
{standard input}:79: Error: selected processor does not support ARM
[...]
can someone help me to resolve these errors. Thanks in advance
This problem has been fixed in the master and in stable-queue branches,
so it'll be resolved in the next release (which should hopefully happen
before too long). Patch is at here if you want to apply it yourself:
http://git.0pointer.de/?p=pulseaudio.git;a=commitdiff;h=12b900858ae82d435c100d6eb94cb7bb22fe5e29
Cheers,
Arun
___
pulseaudio-discuss mailing list
pulseaudio-discuss@mail.0pointer.de
https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss
Re: [pulseaudio-discuss] [PATCHv3 0/4] Read and store UCM data as proplist
'Twas brillig, and Jorge Eduardo Candelaria at 18/05/11 07:22 did gyre and gimble: On May 17, 2011, at 8:56 AM, Lu Guanqun wrote: On Thu, May 12, 2011 at 02:56:04AM +0800, Jorge Eduardo Candelaria wrote: Ok, I'll copy the jack code we have into module-alsa-card. This will allow for simple jack removal/insertion events to be propagated to pulseaudio. We won't be able to do the complicated stuff mentioned above, but should at least be able to do simple speaker/headphone switching. Hi Jorge, I'm interested in your jack detection code, when do you decide to send it out? :-) Don't worry, I haven't forgotten about it :). I plan to send the new patches tomorrow if all goes well with testing. Have you spoken with David about this off-list by any chance? As I mentioned previously, we have quite specific needs for jack detection for it to be accepted so I hope further discussions have happened or that you have managed to be super awesome and make it all just work as we want it, otherwise more tweaks will be ultimately be needed :) Take care Col -- Colin Guthrie gmane(at)colin.guthr.ie http://colin.guthr.ie/ Day Job: Tribalogic Limited [http://www.tribalogic.net/] Open Source: Mageia Contributor [http://www.mageia.org/] 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
Re: [pulseaudio-discuss] my paulseaudio is not running as daemon
I running this a regular user.I download pulseaudio-0.9.22 in www.pulseaudio.org,it is now install /usr/local/. -Original Message- From: pulseaudio-discuss-boun...@mail.0pointer.de [mailto:pulseaudio-discuss-boun...@mail.0pointer.de] On Behalf Of Colin Guthrie Sent: Wednesday, May 18, 2011 2:59 PM To: pulseaudio-discuss@mail.0pointer.de Subject: Re: [pulseaudio-discuss] my paulseaudio is not running as daemon 'Twas brillig, and Fu, Zhen at 18/05/11 07:50 did gyre and gimble: I need developing PA client App,so I download pulseaudio-0.9.22 and run “./configure,make,make install”.After install finished,I run “pacmd”,but display “No pulseaudio daemon running,or not running as session daemon”.Then,I run “ps aux | grep pulse”,but display “pulseaudio –start”. Are you running this as root or a regular user. What does (as a regular user) pulseaudio - say (I suspect daemon already running or pid file already exists or similar)? Are you using a distro? If so what version does your distro include and did you overwrite you distro version with your self build version or is it now installed into /usr/local instead? Also, I would suggest the stable-queue git branch rather than 0.9.22 as this contains several bugfixes on top of 0.9.22. Col -- Colin Guthrie gmane(at)colin.guthr.ie http://colin.guthr.ie/ Day Job: Tribalogic Limited [http://www.tribalogic.net/] Open Source: Mageia Contributor [http://www.mageia.org/] 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 ___ pulseaudio-discuss mailing list pulseaudio-discuss@mail.0pointer.de https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss
Re: [pulseaudio-discuss] build error
'Twas brillig, and Colin Guthrie at 18/05/11 07:53 did gyre and gimble: Hiya, 'Twas brillig, and Himanshu Chug at 18/05/11 07:30 did gyre and gimble: This is first mail to the list, Hello to evreyone in the list, Hello, welcome to the list :) I am new to pulseaudio and I am trying to build the pulseaudio using make and get the following build errors: I don't personally know much about ARM stuff, but it would help if you share which version of PA you are building. e.g. Is it v0.9.22 or the git master or stable-queue branches? That info will be useful to people who can (hopefully!) help more than me :) Ahh well, it seem Arun is learned enough to spot the problem without this info, so you can ignore me :D Cheers Col -- Colin Guthrie gmane(at)colin.guthr.ie http://colin.guthr.ie/ Day Job: Tribalogic Limited [http://www.tribalogic.net/] Open Source: Mageia Contributor [http://www.mageia.org/] 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
Re: [pulseaudio-discuss] Receiving RTP streams with pulseaudio
thanks for that informations, i will try it Today. But it Looks like that i can
fix my Problem now.
Am 18.05.2011 um 08:37 schrieb Rémi Denis-Courmont r...@remlab.net:
On Tue, 17 May 2011 21:51:35 +0200, Michael Trunner mich...@trunner.de
wrote:
I'm trying to setup Pulseaudio to receive RTP/Multicast steams. Sender
should be vlc, (and receiver should be pulseaudio). I activated
module-rtp-recv (and module-rtp-send) with papref, but I can't get it
work. Can some one explain me what I have to do? Or how to debug it.
First you need to make sure that VLC uses an RTP payload format that
PulseAudio understands, typically L16/44100/2 (signed big endian 16-bits
stereo at 44100 Hz). By default, VLC will not decode the audio. Also make
sure SAP is enabled.
For example:
# IP=224.0.0.42
# vlc --sout-keep --no-sout-video --no-sout-spu \
--sout
#transcode{acodec=s16b,samplerate=44100}:gather:rtp{sap,dst=$IP}
Then you need to configure PulseAudio to use the standard SAP address as
specified in IETF RFC2974 §3, corresponding to the multicast scope that VLC
is configured to use, in particular:
- 224.2.127.254 (SAP.MCAST.NET) for global IPv4,
- ff0e::2:7ffe for global IPv6,
- 224.0.0.255 for link-local IPv4,
- ff02::2:7ffe for link-local IPv6.
By default, PulseAudio uses a proprietary non-standard SAP group, namely
224.0.0.56. This cannot interoperate with VLC.
--
Rémi Denis-Courmont
http://www.remlab.net/
___
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] my paulseaudio is not running as daemon
[Please try to avoid top-posting. It's considered bad netiquitte on most mailing lists as it disrupts the flow of reading] 'Twas brillig, and Fu, Zhen at 18/05/11 08:05 did gyre and gimble: 'Twas brillig, and Fu, Zhen at 18/05/11 07:50 did gyre and gimble: I need developing PA client App,so I download pulseaudio-0.9.22 and run “./configure,make,make install”.After install finished,I run “pacmd”,but display “No pulseaudio daemon running,or not running as session daemon”.Then,I run “ps aux | grep pulse”,but display “pulseaudio –start”. Are you running this as root or a regular user. What does (as a regular user) pulseaudio - say (I suspect daemon already running or pid file already exists or similar)? Are you using a distro? If so what version does your distro include and did you overwrite you distro version with your self build version or is it now installed into /usr/local instead? Also, I would suggest the stable-queue git branch rather than 0.9.22 as this contains several bugfixes on top of 0.9.22. I running this a regular user.I download pulseaudio-0.9.22 in www.pulseaudio.org, it is now install /usr/local/. OK, so is the version that is running the distro provided one or your new one? Chances are it's your distro version and your self compiled version of PA are in some way conflicting. Can I ask specifically why you need to build your own version of PA and not use your distro version? You said originally you are developing a client application for PA. Is this the case or are you hacking on PA code itself? If the latter then you should really use git so that you can track your changes. If the former (you are just developing a PA client app), then just install your distros development package for PA and you should be good to go, avoiding any hassle. If you really do want to run PA and don't want to over write your distro version, I wrote a guide some time ago about running PA from git: http://colin.guthr.ie/2010/09/compiling-and-running-pulseaudio-from-git/ You also did not supply the pulseaudio - output that would have aided debugging, but hopefully we can short circuit all that if you are just developing a client app as you don't need to build your own PA for that :) Col -- Colin Guthrie gmane(at)colin.guthr.ie http://colin.guthr.ie/ Day Job: Tribalogic Limited [http://www.tribalogic.net/] Open Source: Mageia Contributor [http://www.mageia.org/] 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
Re: [pulseaudio-discuss] build error
Thanks much Arun, the patch is perfectly working fine for me. Thanks *Colin
for initiating the discussion and replying back.. seems our group is *active
and we are
going to enjoy working here. Thanks guys once again :-)
*
Best Regards,
Himanshu
*
On Wed, May 18, 2011 at 12:00 PM, Himanshu Chug himanshu.c...@gmail.comwrote:
Hello All,
This is first mail to the list, Hello to evreyone in the list,
I am new to pulseaudio and I am trying to build the pulseaudio using make
and get the following build errors:
{standard input}: Assembler messages:
{standard input}:64: Error: selected processor does not support ARM mode
`ssat r0,#16,r0'
{standard input}:79: Error: selected processor does not support ARM mode
`ssat r2,#16,r2'
{standard input}:80: Error: selected processor does not support ARM mode
`ssat r3,#16,r3'
{standard input}:81: Error: selected processor does not support ARM mode
`pkhbt r0,r3,r2,LSL#16'
{standard input}:98: Error: selected processor does not support ARM mode
`ssat r2,#16,r2'
{standard input}:99: Error: selected processor does not support ARM mode
`ssat r3,#16,r3'
{standard input}:100: Error: selected processor does not support ARM mode
`ssat r4,#16,r4'
{standard input}:101: Error: selected processor does not support ARM mode
`ssat r5,#16,r5'
{standard input}:102: Error: selected processor does not support ARM mode
`pkhbt r0,r3,r2,LSL#16'
{standard input}:103: Error: selected processor does not support ARM mode
`pkhbt r1,r5,r4,LSL#16'
make[3]: *** [libpulsecore_0.9.21_la-svolume_arm.lo] Error 1
make[3]: Leaving directory `/home/himanshu/pulse_new/src'
make[2]: *** [all] Error 2
make[2]: Leaving directory `/home/himanshu/pulse_new/src'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/himanshu/pulse_new'
make: *** [all] Error 2
can someone help me to resolve these errors. Thanks in advance
BR,
Himanshu
___
pulseaudio-discuss mailing list
pulseaudio-discuss@mail.0pointer.de
https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss
Re: [pulseaudio-discuss] Receiving RTP streams with pulseaudio
'Twas brillig, and Rémi Denis-Courmont at 18/05/11 07:37 did gyre and
gimble:
On Tue, 17 May 2011 21:51:35 +0200, Michael Trunner mich...@trunner.de
wrote:
I'm trying to setup Pulseaudio to receive RTP/Multicast steams. Sender
should be vlc, (and receiver should be pulseaudio). I activated
module-rtp-recv (and module-rtp-send) with papref, but I can't get it
work. Can some one explain me what I have to do? Or how to debug it.
First you need to make sure that VLC uses an RTP payload format that
PulseAudio understands, typically L16/44100/2 (signed big endian 16-bits
stereo at 44100 Hz). By default, VLC will not decode the audio. Also make
sure SAP is enabled.
For example:
# IP=224.0.0.42
# vlc --sout-keep --no-sout-video --no-sout-spu \
--sout
#transcode{acodec=s16b,samplerate=44100}:gather:rtp{sap,dst=$IP}
Then you need to configure PulseAudio to use the standard SAP address as
specified in IETF RFC2974 §3, corresponding to the multicast scope that VLC
is configured to use, in particular:
- 224.2.127.254 (SAP.MCAST.NET) for global IPv4,
- ff0e::2:7ffe for global IPv6,
- 224.0.0.255 for link-local IPv4,
- ff02::2:7ffe for link-local IPv6.
Many thanks for the info Rémi :)
By default, PulseAudio uses a proprietary non-standard SAP group, namely
224.0.0.56. This cannot interoperate with VLC.
Interesting. I see from the history:
commit e1887b552ceb324f70732c85c7458119e03718b7
Author: Lennart Poettering lenn...@poettering.net
Date: Sun Apr 16 11:13:20 2006 +
change default mcast address once again, to make sure our traffic
doesn't leave the network by default
Previously the address was 224.0.1.3
The change before that is:
commit c999fe40b841b035c7d0c873b4a4875e12e9c9a4
Author: Lennart Poettering lenn...@poettering.net
Date: Sun Apr 16 09:15:51 2006 +
* deal properly with underruns, overflows and packet losses
* change default mcast address
* detect RTP loops
Which had the address as 224.0.1.2. This was the address used when the
module was committed.
This default can be overridden in the module-rtp-recv module with the
sap_address= argument. And with the module-rtp-send module with the
destination= argument.
Hope that helps.
If you have any recommendations for the defaults, please feel free to
suggest them, but I guess the intention was to keep the traffic in house
by default. We should likely expose via paprefs the ability to choose a
public mutlicast group or something. WDYT?
Col
--
Colin Guthrie
gmane(at)colin.guthr.ie
http://colin.guthr.ie/
Day Job:
Tribalogic Limited [http://www.tribalogic.net/]
Open Source:
Mageia Contributor [http://www.mageia.org/]
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
Re: [pulseaudio-discuss] Receiving RTP streams with pulseaudio
On Wed, 18 May 2011 10:40:48 +0100, Colin Guthrie gm...@colin.guthr.ie wrote: If you have any recommendations for the defaults, please feel free to suggest them, but I guess the intention was to keep the traffic in house by default. We should likely expose via paprefs the ability to choose a public mutlicast group or something. WDYT? There is almost everything you need to know in the already referenced RFC. To summarize, the standard for SAP group address is: - 224.2.127.254 for global IPv4 multicast, - the last address in the netmask for non-global IPv4 multicast: SAP group = scope prefix | scope mask - ff0X::2:7ffe for IPv6 multicast where X is the multicast scope: SAP group = ff00::2:7ffe | (scope identifier 120) Link-local IPv4 multicast is 224.0.0.0/8, so the corresponding standard SAP group is 224.0.0.255. VLC always selects the SAP group with the same address family and scope as the advertized RTP multicast stream. This is not required by the standard, but it only makes sense... -- Rémi Denis-Courmont http://www.remlab.net/ ___ pulseaudio-discuss mailing list pulseaudio-discuss@mail.0pointer.de https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss
Re: [pulseaudio-discuss] Receiving RTP streams with pulseaudio
2011/5/18 Colin Guthrie gm...@colin.guthr.ie:
'Twas brillig, and Rémi Denis-Courmont at 18/05/11 07:37 did gyre and
gimble:
On Tue, 17 May 2011 21:51:35 +0200, Michael Trunner mich...@trunner.de
wrote:
I'm trying to setup Pulseaudio to receive RTP/Multicast steams. Sender
should be vlc, (and receiver should be pulseaudio). I activated
module-rtp-recv (and module-rtp-send) with papref, but I can't get it
work. Can some one explain me what I have to do? Or how to debug it.
First you need to make sure that VLC uses an RTP payload format that
PulseAudio understands, typically L16/44100/2 (signed big endian 16-bits
stereo at 44100 Hz). By default, VLC will not decode the audio. Also make
sure SAP is enabled.
For example:
# IP=224.0.0.42
# vlc --sout-keep --no-sout-video --no-sout-spu \
--sout
#transcode{acodec=s16b,samplerate=44100}:gather:rtp{sap,dst=$IP}
Then you need to configure PulseAudio to use the standard SAP address as
specified in IETF RFC2974 §3, corresponding to the multicast scope that VLC
is configured to use, in particular:
- 224.2.127.254 (SAP.MCAST.NET) for global IPv4,
- ff0e::2:7ffe for global IPv6,
- 224.0.0.255 for link-local IPv4,
- ff02::2:7ffe for link-local IPv6.
Many thanks for the info Rémi :)
By default, PulseAudio uses a proprietary non-standard SAP group, namely
224.0.0.56. This cannot interoperate with VLC.
Interesting. I see from the history:
Then there is also http://www.pulseaudio.org/ticket/436
Can we decide now what to change the default to?
commit e1887b552ceb324f70732c85c7458119e03718b7
Author: Lennart Poettering lenn...@poettering.net
Date: Sun Apr 16 11:13:20 2006 +
change default mcast address once again, to make sure our traffic
doesn't leave the network by default
Previously the address was 224.0.1.3
The change before that is:
commit c999fe40b841b035c7d0c873b4a4875e12e9c9a4
Author: Lennart Poettering lenn...@poettering.net
Date: Sun Apr 16 09:15:51 2006 +
* deal properly with underruns, overflows and packet losses
* change default mcast address
* detect RTP loops
Which had the address as 224.0.1.2. This was the address used when the
module was committed.
This default can be overridden in the module-rtp-recv module with the
sap_address= argument. And with the module-rtp-send module with the
destination= argument.
Hope that helps.
If you have any recommendations for the defaults, please feel free to
suggest them, but I guess the intention was to keep the traffic in house
by default. We should likely expose via paprefs the ability to choose a
public mutlicast group or something. WDYT?
Col
--
Colin Guthrie
gmane(at)colin.guthr.ie
http://colin.guthr.ie/
Day Job:
Tribalogic Limited [http://www.tribalogic.net/]
Open Source:
Mageia Contributor [http://www.mageia.org/]
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
___
pulseaudio-discuss mailing list
pulseaudio-discuss@mail.0pointer.de
https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss
Re: [pulseaudio-discuss] Assertion '(size_t) decoded == a2dp-frame_length' failed at modules/bluetooth/module-bluetooth-device
My audio.conf looks as below. Configuration file for the audio service # This section contains options which are not specific to any # particular interface [General] Enable=Source # Switch to master role for incoming connections (defaults to true) #Master=true # If we want to disable support for specific services # Defaults to supporting all implemented services #Disable=Control,Source # SCO routing. Either PCM or HCI (in which case audio is routed to/from ALSA) # Defaults to HCI #SCORouting=PCM # Automatically connect both A2DP and HFP/HSP profiles for incoming # connections. Some headsets that support both profiles will only connect the # other one automatically so the default setting of true is usually a good # idea. #AutoConnect=true # Headset interface specific options (i.e. options which affect how the audio # service interacts with remote headset devices) [Headset] # Set to true to support HFP, false means only HSP is supported # Defaults to true HFP=true # Maximum number of connected HSP/HFP devices per adapter. Defaults to 1 MaxConnected=1 # Just an example of potential config options for the other interfaces #[A2DP] #SBCSources=1 #MPEG12Sources=0 Regards, patil -Original Message- From: Patil, H. Sent: Wednesday, May 18, 2011 4:04 PM To: 'General PulseAudio Discussion' Subject: RE: [pulseaudio-discuss] Assertion '(size_t) decoded == a2dp-frame_length' failed at modules/bluetooth/module-bluetooth-device Hi Luiz Augusto, Thanks a lot for your reply Please find the attached logs for --We are able to run pulseaudio and establish service connection for A2DP (BlueZ). Once the mobile phone starts streaming the audio, pulse audio encounters following error module-bluetooth-device.c: Received error condition: Input/output error.. Please suggest. Thanks Patil -Original Message- From: pulseaudio-discuss-boun...@mail.0pointer.de [mailto:pulseaudio-discuss-boun...@mail.0pointer.de] On Behalf Of Luiz Augusto von Dentz Sent: Sunday, May 15, 2011 1:43 PM To: General PulseAudio Discussion Subject: Re: [pulseaudio-discuss] Assertion '(size_t) decoded == a2dp-frame_length' failed at modules/bluetooth/module-bluetooth-device Hi, On Thu, May 12, 2011 at 5:17 PM, h.pa...@accenture.com wrote: Hello Becker, Thanks for the reply. I am getting the following error if I remove --system ~ # pulseaudio -n -F /etc/pulse/default.pa W: main.c: Couldn't canonicalize binary path, cannot self execute. W: main.c: This program is not intended to be run as root (unless --system is specified). W: main.c: Unable to contact D-Bus: org.freedesktop.DBus.Error.Spawn.ExecFailed: /bin/dbus-launch terminated abnormally with the following error: Autolaunch error: X11 initialization failed. Are you sure you are running Pulseaudio optimized for an ARM target? SBC code should already have the necessary optimization for ARM, BlueZ should take care of a2dp signalling. For ARM: I have cross compiled PulseAudio for arm. Is there any specific optimization needs to be done for PulseAudio for ARM? Is there any configuration needs to be done for PulseAudio for ARM? We are able to run pulseaudio and establish service connection for A2DP (BlueZ). Once the mobile phone starts streaming the audio, pulse audio encounters following error module-bluetooth-device.c: Received error condition: Input/output error This is probably endpoint configuration problem, could you please have bluetoothd run with debug and send us the output? You can enable debug by either do killall -USR2 bluetoothd or start it using -d. Also what API are you using in the system, how your audio.conf looks like? -- Luiz Augusto von Dentz Computer Engineer ___ pulseaudio-discuss mailing list pulseaudio-discuss@mail.0pointer.de https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss This message is for the designated recipient only and may contain privileged, proprietary, or otherwise private information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the email by you is prohibited. ___ pulseaudio-discuss mailing list pulseaudio-discuss@mail.0pointer.de https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss
Re: [pulseaudio-discuss] [PACKAGERS] New dep on json-c
Dear Colin, Am Montag, den 16.05.2011, 11:56 +0100 schrieb Colin Guthrie: I've just pushed Arun's (mostly, Pierre-Louis also had a hand!) passthrough work to master. This carries with it a new dependency: json-c We may yet remove this and write our own parser for the simple subset of JSON formatting we use but there may ultimately be other reasons to keep this longer term. But in the interests of simplicity, I'd certainly not be against any native implementation patches that came along provided they were simple and clean. Please test these changes. I'm sure Arun will post more details and test requests in due course. looking at the XBMC commit log [1] they seem to move from JsonCpp [2] to YAJL [3]. Thanks, Paul [1] https://github.com/xbmc/xbmc/commit/56ac2a40cc3d721d428f026bfe11173b27596fe3/ [2] http://lloyd.github.com/yajl/ [3] http://jsoncpp.sourceforge.net/ signature.asc Description: This is a digitally signed message part ___ pulseaudio-discuss mailing list pulseaudio-discuss@mail.0pointer.de https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss
[pulseaudio-discuss] Debugging Pulse Audio
Hi All I am trying to debug pulse audio v0.9.21 code (on Ubuntu desktop) by running some test playback .pcm stream. I guess to check the code logs I need to start the pulse audio daemon in debug mode. 1. How can I Stop the existing PA daemon? when I try to KILL the daemon it automatically started again (may be due to some configuration.?) 2. How to again Start the daemon in Debug mode? 3. How and where to check for PA code logs ? Thanks Regards, Himanshu ___ pulseaudio-discuss mailing list pulseaudio-discuss@mail.0pointer.de https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss
Re: [pulseaudio-discuss] Debugging Pulse Audio
Hiya 'Twas brillig, and Himanshu Chug at 18/05/11 13:40 did gyre and gimble: I am trying to debug pulse audio v0.9.21 code (on Ubuntu desktop) by running some test playback .pcm stream. I guess to check the code logs I need to start the pulse audio daemon in debug mode. 1. How can I Stop the existing PA daemon? when I try to KILL the daemon it automatically started again (may be due to some configuration.?) Typically you can: echo autospawn=no ~/.pulse/client.conf to prevent autospawning. (man pulse-client.conf) PA will likely still start at login to X11 due to XDG scripts triggered at login, but it will not autospawn and thus some apps that start during the early login may actually flip over to a non-PA mode due to this change, so I'd recommend reverting the change when you are done or accepting the consequences (I turn off autospawn generally and accept that some login items might misbehave a bit) 2. How to again Start the daemon in Debug mode? Generally I run it manually: pulseaudio -v 3. How and where to check for PA code logs ? You can configure the log target and level in daemon.conf (man pulse-daemon.conf) or just use the console output from the above command. HTHs Col -- Colin Guthrie gmane(at)colin.guthr.ie http://colin.guthr.ie/ Day Job: Tribalogic Limited [http://www.tribalogic.net/] Open Source: Mageia Contributor [http://www.mageia.org/] 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
Re: [pulseaudio-discuss] How to find the latest created bluetooth sink/source via event hook?
Great thanks for your advice, Col! Please note that there already exists a module called module-switch-on-connect which does this task, but for all new sinks, not just BT sinks. ... I found module-switch-on-connect.c is not in 0.9.22 tar ball but in git. When will this module be released? My work is still based on 0.9.22 and need upgrade to use this module. Just so you know, I will am intending on shaking up the routing system in PA after v1 is released which will hopefully make this kind of thing easier to implement and manage. ... but essentially the routing will be based on priority lists of devices rather than just setting a single device to use. It sounds great! Could you share more information on this new design, maybe in a new thread? Thanks Amanda ___ pulseaudio-discuss mailing list pulseaudio-discuss@mail.0pointer.de https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss
Re: [pulseaudio-discuss] How to find the latest created bluetooth sink/source via event hook?
On Thu, 2011-05-19 at 10:09 +0800, Lin, Mengdong wrote: Great thanks for your advice, Col! Please note that there already exists a module called module-switch-on-connect which does this task, but for all new sinks, not just BT sinks. ... I found module-switch-on-connect.c is not in 0.9.22 tar ball but in git. When will this module be released? My work is still based on 0.9.22 and need upgrade to use this module. Just so you know, I will am intending on shaking up the routing system in PA after v1 is released which will hopefully make this kind of thing easier to implement and manage. ... but essentially the routing will be based on priority lists of devices rather than just setting a single device to use. It sounds great! Could you share more information on this new design, maybe in a new thread? http://colin.guthr.ie/2010/02/this-is-the-route-to-hell/ Cheers, Arun ___ pulseaudio-discuss mailing list pulseaudio-discuss@mail.0pointer.de https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss
