Why does module-suspend-on-idle.c think this source is idle?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 18-Mar-2016 3:53 PM, "Steven Wawryk" <stevenw at acres.com.au> wrote:
>
>
> Hi,
>
> I'm trying to integrate an ALSA driver I've written for an embedded
platform with PulseAudio 4.0.  The "soundcard" has 32 channels, of which
I'm trying to use 24.  The dummy and loopback ALSA devices come up as cards
0 and 1.  My device comes up as card 2.
>
> My simple loopback of 2 groups of 12 channels (loopback-2x12.pa) works,
though the output is somewhat distorted.
>
> When I input from the card source (alsa_input.2) and try to output with
RTP (rtp-send-2x12.pa, and the simpler precursor rtp-send-2x12 (copy).pa),
there is some initial network traffic then alsa_input.2 suspends due to
being idle, as at the end of pa_output.txt.  I'm having trouble trying to
understand why it thinks alsa_input.2 is idle.
>

You probably need to use the inhibit_auto_suspend module argument on
module-rtp-send.

-- Arun
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/pulseaudio-discuss/attachments/20160318/52c79a59/attachment.html>


[Index of Archives]     [Linux Audio Users]     [AMD Graphics]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux