"
However, all (audio) applications freeze until my program (which reads
from the pipe) begins to run. This is expected behaviour of named
pipes.
I believe I can solve this by modifying the PCM 'default' dynamically.
"
- well, to me it sounds like your "overall" application should be a
multi-threaded one - one of the threads reads audio stream, waiting for data as
necessary (you call it "freeze") while other threads check the status of the
audio reading thread.
...
Your whole IPC, including over the network part, can be implemented (or, say,
prototyped) using a scripting language and utilities like 'cat', 'netcat' - the
latter for the networking part.
Regards,
Sergei.
Четверг, 7 мая 2015, 8:25 -04:00 от Guru Prasad <gurup...@buffalo.edu>:
>I had some luck with the named pipe setup. I was able to set up
>.asoundrc to write to a named pipe in /tmp and then send this data
>over a socket and play it on another machine.
>However, all (audio) applications freeze until my program (which reads
>from the pipe) begins to run. This is expected behaviour of named
>pipes.
>
>I believe I can solve this by modifying the PCM 'default' dynamically.
>That way, I can modify the PCM at the start of my program to use my
>custom .asoundrc.
>Is it possible to:
> 1) Modify PCM 'default' on the fly?
> 2) Re-initialize ALSA with a new .asoundrc without
>rebooting/restarting the desktop manager?
>
>
>@Anders:
>I tried that approach already with no luck. For some reason when I
>include snd-aloop to my modules, aplay -L does not show any of the
>loopback devices.
>
>
>On Thu, May 7, 2015 at 3:01 AM, Anders Genell < anders.gen...@gmail.com >
>wrote:
>>
>>> 7 maj 2015 kl. 05:23 skrev Guru Prasad < gurup...@buffalo.edu >:
>>>
>>> Could you give me an example of how I can ask the PCM file plugin to
>>> write to a named pipe?
>>> Should i create this manually or can I somehow do this via the PCM
>>> file plugin itself by using the '|' character?
>>>
>>> Also, don't named pipes block until there is a reader? Given that I've
>>> only been able to do this via .asoundrc (and not via the
>>> snd_pcm_file_open), I'm not sure how the blocking behaviour would
>>> interact with ALSA. Would only my file plugin PCM definition block
>>> while others continue?
>>>
>>> Regardless, thank you for the suggestion. I will try this out meanwhile.
>>>
>>> Regards
>>> Guru
>>
>> Maybe this could be a starting point?
>>
>> http://plasmasturm.org/log/soundserverhack/
>>
>> Regards,
>> /Anders
>>
>>
>
>------------------------------------------------------------------------------
>One dashboard for servers and applications across Physical-Virtual-Cloud
>Widest out-of-the-box monitoring support with 50+ applications
>Performance metrics, stats and reports that give you Actionable Insights
>Deep dive visibility with transaction tracing using APM Insight.
>http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
>_______________________________________________
>Alsa-user mailing list
>Alsa-user@lists.sourceforge.net
>https://lists.sourceforge.net/lists/listinfo/alsa-user
------------------------------------------------------------------------------
One dashboard for servers and applications across Physical-Virtual-Cloud
Widest out-of-the-box monitoring support with 50+ applications
Performance metrics, stats and reports that give you Actionable Insights
Deep dive visibility with transaction tracing using APM Insight.
http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
_______________________________________________
Alsa-user mailing list
Alsa-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/alsa-user
