[asterisk-bugs] [JIRA] (ASTERISK-22000) chan_alsa fails to use input_device=plug:dsnoop

[Matt Jordan (JIRA)]

     [ https://issues.asterisk.org/jira/browse/ASTERISK-22000?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Matt Jordan updated ASTERISK-22000:
-----------------------------------

    Assignee: Matt Jordan  (was: Chris Gentle)
      Status: Triage  (was: Waiting for Feedback)
    
> chan_alsa fails to use input_device=plug:dsnoop
> -----------------------------------------------
>
>                 Key: ASTERISK-22000
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-22000
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Channels/chan_alsa
>    Affects Versions: 11.4.0
>         Environment: Asterisk 11.4.0 on Raspberry Pi with Raspbian 2013-05-25-wheezy.  C-Media USB sound card installed.
>            Reporter: Chris Gentle
>            Assignee: Matt Jordan
>            Severity: Minor
>         Attachments: backtrace.txt
>
>
> Trying to get chan_alsa to use ALSA device plug:dsnoop so that it will not block other processes trying to read from ALSA mic input.  (The dsnoop plugin is the opposite of dmix, it's for mic input rather than speaker output.)  My alsa configuration is the distribution's default without anything added to /etc/asound.conf or ~/.asoundrc.
> My goal is to feed an asterisk confbridge with audio from an alsa mic input while simultaneously making a recording of whatever is coming across the microphone jack using arecord with "-f cd" to record it at 44100Hz stereo.
> Running simultaneous arecord sessions with plug:dsnoop works without blocking:
> {noformat}
> for i in `seq 1 5`; do
>   arecord -D plug:dsnoop -f cd -d 10 foobar-$i.wav &
> done
> {noformat}
> but using input_device=plug:dsnoop in /etc/alsa.conf fails.
> {noformat}
> asterisk*CLI> console dial 1001 at conferences
>     -- Executing [1001 at conferences:1] Answer("ALSA/plug:dsnoop", "") in new stack
>  << Console call has been answered >> 
> [2013-07-02 09:32:56] ERROR[5374][C-00000000]: chan_alsa.c:479 alsa_read: Read error: Resource temporarily unavailable
> [2013-07-02 09:32:56] ERROR[5374][C-00000000]: chan_alsa.c:479 alsa_read: Read error: Resource temporarily unavailable
> [2013-07-02 09:32:56] ERROR[5374][C-00000000]: chan_alsa.c:479 alsa_read: Read error: Resource temporarily unavailable
> [2013-07-02 09:32:56] ERROR[5374][C-00000000]: chan_alsa.c:479 alsa_read: Read error: Resource temporarily unavailable
> [2013-07-02 09:32:56] ERROR[5374][C-00000000]: chan_alsa.c:479 alsa_read: Read error: Resource temporarily unavailable
> [2013-07-02 09:32:56] ERROR[5374][C-00000000]: chan_alsa.c:479 alsa_read: Read error: Resource temporarily unavailable
> {noformat}
> I've tested with 11.4.0 on two platforms, one Atom-based and the other was a Raspberry Pi.  On the Atom, a couple of these errors are produced but they are non-fatal and things continue to work as expected.  On the Pi, there are more than two errors (as seen above) and they are fatal resulting in an asterisk crash.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.asterisk.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira