Summary:ASTERISK-13329: [patch] Asterisk ALSA interface consumes physical input and output regardless of whether or not they are needed...
Reporter:Robert Vincent Krakora (krakorar)Labels:
Date Opened:2009-06-10 14:04:14Date Closed:2009-11-06 10:24:01.000-0600
Versions:Frequency of
Environment:Attachments:( 0) chan_alsa.c
( 1) unified_diff_with_tip
( 2) unified_diff_with_tip2
Description:I have hacked on chan_alsa.c (attached) to allow either ALSA input or
ALSA output or both to be specified.  Previously, Asterisk would
consume a physical ALSA input and physical ALSA output whether it was
going to make use of them or not.  This is problematic when one wants
to make use of a cheap analog microphone to interface to applications
other than Asterisk and there is only one analog input on the
motherboard.  Asterisk would consume the input and it would not be
available for any other application.  Again, this is a hack and
comments and a more elegant solution are desired.
Comments:By: Robert Vincent Krakora (krakorar) 2009-06-15 16:14:00

I signed up for a license, how come I do not have one yet?

By: Leif Madsen (lmadsen) 2009-06-15 16:43:03

The reason is because the status messages are set manually by a bug marshal (primarily me) and I hadn't noticed that your license was approved. I have set this issue back to the appropriate status. Thanks!

By: Leif Madsen (lmadsen) 2009-06-15 16:44:56

It looks like you've attached the entire chan_alsa.c file, where really you just need to attach your changes as a unified diff. Thanks!

By: Robert Vincent Krakora (krakorar) 2009-06-16 09:54:26

I just attached a file called "unified_diff_with_tip".  I did and 'svn update' followed by an 'svn diff > unified_diff_with_tip'.  I hope this is what you need.

By: Leif Madsen (lmadsen) 2009-06-16 14:31:36

Yes this looks much better, thanks!  Marking this as Ready for Testing. If you can, please post to the asterisk-dev list to try and coax some people into testing this out :)  Thanks!

By: Tilghman Lesher (tilghman) 2009-08-24 21:51:43

This code looks like it was written for 1.2, not 1.4, and it really should be against trunk.

By: Tilghman Lesher (tilghman) 2009-09-03 12:12:06

Suspended due to lack of activity. Please request a bug marshal in #asterisk-bugs on the IRC network irc.freenode.net to reopen the issue should you have the additional information requested.

Further information can be found at http://www.asterisk.org/developers/bug-guidelines

By: Robert Vincent Krakora (krakorar) 2009-09-21 12:45:17

This code is from 1.4.25 no 1.2.  I fail to see why this was closed.  The code is directly from the 1.4.25 source tarball.

By: Tilghman Lesher (tilghman) 2009-09-21 14:07:39

The code still needs to be against trunk.

By: Robert Vincent Krakora (krakorar) 2009-09-22 07:18:57

[root@devkrakora asterisk]# svn info
Path: .
URL: http://svn.digium.com/svn/asterisk/trunk
Repository Root: http://svn.digium.com/svn/asterisk
Repository UUID: f38db490-d61c-443f-a65b-d21fe96a405b
Revision: 219800
Node Kind: directory
Schedule: normal
Last Changed Author: dvossel
Last Changed Rev: 219721
Last Changed Date: 2009-09-21 12:59:05 -0400 (Mon, 21 Sep 2009)

By: Robert Vincent Krakora (krakorar) 2009-09-22 07:19:42

It is against the trunk...see my last note.  I uploaded a new "diff" file... ;-)

By: Jason Parker (jparker) 2009-11-06 10:24:00.000-0600

I honestly don't see the benefit of this.  It brings about a whole bunch of ways for things to break.

Having said that..  ALSA has done mixing for several years now.  If you use "default" as the device names, it should not block providing you have a sane ALSA configuration.