Yuan, Hang | 1 Aug 2005 05:06
Picon
Favicon

RE: 2.6.12 sound problem

 

-----Original Message-----
From: Stephen Clark [mailto:stephen.clark <at> earthlink.net] 
Sent: 2005年7月30日 11:05
To: sclark46 <at> earthlink.net
Cc: Yuan, Hang; alsa-devel <at> lists.sourceforge.net
Subject: Re: [Alsa-devel] 2.6.12 sound problem

Stephen Clark wrote:

>Yuan, Hang wrote:
>
>  
>
>>-----Original Message-----
>>From: alsa-devel-admin <at> lists.sourceforge.net
[mailto:alsa-devel-admin <at> lists.sourceforge.net] On Behalf Of Stephen Clark
>>Sent: 2005Äê7ÔÂ28ÈÕ 22:12
>>To: alsa-devel <at> lists.sourceforge.net
>>Subject: Re: [Alsa-devel] 2.6.12 sound problem
>>
>>Stephen Clark wrote:
>>
>> 
>>
>>    
>>
>>>Hello List,
>>>
(Continue reading)

bugtrack | 1 Aug 2005 08:09
Favicon

[ALSA - liboss 0001278]: fails to read volume for software volume control


A NOTE has been added to this issue.
======================================================================
<https://bugtrack.alsa-project.org/alsa-bug/view.php?id=1278> 
======================================================================
Reported By:                jdthood
Assigned To:                
======================================================================
Project:                    ALSA - liboss
Issue ID:                   1278
Category:                   
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     new
======================================================================
Date Submitted:             07-23-2005 18:23 CEST
Last Modified:              08-01-2005 08:09 CEST
======================================================================
Summary:                    fails to read volume for software volume control
Description: 
From: http://bugs.debian.org/319628:

Package: alsa-oss
Version: 1.0.8-1

Hi,

My MacMini's audio chip seems to have no hardware volume control (or it 
is unsupported in the kernel I use), so I use software volume control, 
(Continue reading)

thomas schorpp | 1 Aug 2005 09:37
Picon
Picon

Re: snd-usb-audio hangs modprobe if switching dv camera betw. webcam / usb mass storage mode

thomas schorpp wrote:
> thomas schorpp wrote:
> 
>>hello,
>>
>>this bug is in conjunction with the older
>>"usb disconnect hangs keyboard" bug on lkml.
>>
>>module-init-tools / hotplug hangs with snd-usb-audio if i switch/remove
>>usb camera as stated above, if  a client like kmix is attached.
>>(strange, since this device has no mixers here).
>>
>>if its not unavoidable, pls fix soon, thx. vanilla kernel 2.6.12.0.
>>
>>Jul 31 10:35:58 tom1 kernel: usb 1-2: USB disconnect, address 3
>>...
>>killall kmix
>>...
>>
>>Jul 31 10:42:08 tom1 kernel: usb 1-2: new full speed USB device using
>>uhci_hcd and address 4
>>Jul 31 10:42:08 tom1 kernel:
>>/usr/src/spca5xx-20050701/drivers/usb/spca5xx.c: USB SPCA5XX camera
>>found. Aiptek DV3500 Mpeg4
>>Jul 31 10:42:08 tom1 kernel:
>>/usr/src/spca5xx-20050701/drivers/usb/spca5xx.c: [spca5xx_probe:8652]
>>Camera type JPEG
>>Jul 31 10:42:08 tom1 kernel: ALSA sound/usb/usbaudio.c:2570: 4:3:1: add
>>audio endpoint 0x86
>>
(Continue reading)

Jaroslav Kysela | 1 Aug 2005 10:09
Picon

Re: The different STATES of ALSA

On Sun, 31 Jul 2005, James Courtier-Dutton wrote:

> Once the hw_params and sw_params have been set, you cannot change them. You
> have to close and then reopen the device.

It's not true. You must call snd_pcm_hw_free() before applying of new 
hardware parameters. Software parameters can be changed at any time.

						Jaroslav

-----
Jaroslav Kysela <perex <at> suse.cz>
Linux Kernel Sound Maintainer
ALSA Project, SUSE Labs

-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
Jaroslav Kysela | 1 Aug 2005 10:11
Picon

Re: The different STATES of ALSA

On Sun, 31 Jul 2005, Hynek Hanke wrote:

> > >>>	d) snd_pcm_drop and _drain
> > >Calling the function in every other state is considered an error?
> > I don't know. But in any other state, it won't actually do anything.
> 
> Can someone please clarify this?

drain function can be called at any time except immediately after open 
(the hardware parameters must be set)...

						Jaroslav

-----
Jaroslav Kysela <perex <at> suse.cz>
Linux Kernel Sound Maintainer
ALSA Project, SUSE Labs

-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
bugtrack | 1 Aug 2005 10:20
Favicon

[ALSA - driver 0001224]: artsd-like style


A NOTE has been added to this issue.
======================================================================
<https://bugtrack.alsa-project.org/alsa-bug/view.php?id=1224> 
======================================================================
Reported By:                Hetfield
Assigned To:                
======================================================================
Project:                    ALSA - driver
Issue ID:                   1224
Category:                   PCI - ens1370
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     new
Distribution:               
Kernel Version:             2.6.x
======================================================================
Date Submitted:             07-01-2005 14:49 CEST
Last Modified:              08-01-2005 10:20 CEST
======================================================================
Summary:                    artsd-like style
Description: 
i'd like to know if that's a roadmap to let alsa drivers have a artsd (or
windows) style, i mean, multiple streams at once.

that could be very important for example using skype voip and listening
music at the same time.
======================================================================

(Continue reading)

Takashi Iwai | 1 Aug 2005 10:58
Picon

Re: via82xx dxs_support=5 OK

At Sat, 30 Jul 2005 13:23:44 +0200,
Voluspa wrote:
> 
> 
> Typo, should be WLMi not WMLi, ie:
> 
> Acer Aspire 1524 WLMi
> 
> Doesn't matter since it's just a comment in your code, but confusion
> leads to doubt, leads to extra work.

Too late, already committed :)
Will fix it later.

thanks,

Takashi

-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
Takashi Iwai | 1 Aug 2005 11:22
Picon

Re: Re: Volume per voices [Feature Request]

At Mon, 01 Aug 2005 00:37:26 +0800,
Raymond wrote:
> 
> Jaroslav Kysela wrote:
> > On Thu, 28 Jul 2005, Raymond wrote:
> > 
> > 
> >>In theory, and sound cards with hardware mixing can support this kind of
> >>volume control.
> >>
> > 
> > Nope. Please, define the controls at the driver initialization phase and 
> > make them inactive when the stream is not open. See emu10k1 or trident 
> > driver for hints. You must also map the voice volume with substream 
> > number.
> > 
> 
> Beside volume control, Is it feasible to bind other controls (e.g.
> Interaural Time Difference, Interaural Level Difference and SAMPLE RATE 
> CONVERTOR - Doppler Effect ) to the substream ?

I think yes.  Whatever directly bound to a PCM substream should be
handled as IFACE_PCM with a certain subdevice number.

> How can the alsa application access those controls
> (SNDRV_CTL_ELEM_IFACE_PCM) using the handle return by snd_pcm_open() ?

By defining a new API for that purpose :)

Takashi
(Continue reading)

Takashi Iwai | 1 Aug 2005 11:25
Picon

Re: How to fix "Invalid type for PCM iec958:"?

At Sat, 30 Jul 2005 13:53:38 -0600,
Philip A. Prindeville wrote:
> 
> I've been seeing:
> 
> alsa-init: 1 soundcard found, using: iec958:{CARD 0 AES0 0x02 AES1 0x82 
> AES2 0x00 AES3 0x02}
> ALSA lib pcm.c:1851:(snd_pcm_open_conf) Invalid type for PCM 
> iec958:{CARD 0 AES0 0x02 AES1 0x82 AES2 0x00 AES3 0x02} definition (id: 
> iec958, value: cards.pcm.iec958)
> alsa-init: playback open error: Invalid argument
> 
> 
> And went looking via Google if this is anything obvious.  I saw several
> other postings about having the same issue, but no clear replies about
> what causes it, or how to fix it.
> 
> Should this be a FAQ question?  BTW:  What *is* the fix?

This depends on the hardware and driver you use.
Most likely, the SPDIF I/O is not supported or defined in the system
configuration.

Takashi

-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
(Continue reading)

Takashi Iwai | 1 Aug 2005 12:02
Picon

Re: Re: ALSA memory allocator rants

At Sun, 31 Jul 2005 16:46:44 +0100,
James Courtier-Dutton wrote:
> 
> Hi,
> 
> Here is a email I received as a result of talks I had at KS.
> The general point is that they want the memory alloc function calls in 
> alsa-kernel to not be calls to wrappers, but instead be proper kernel 
> 2.6 function calls.
> The other general point is that some of the code we use should be 
> generalised so that other non-audio drivers can reuse it.
> 
> Comments please,
> 
> James
> 
> 
> Christoph Hellwig wrote:
> > At KS I promised you to send you my rants about ALSA memory allocations,
> > so here we go finally.
> > 
> > First stance from me is that a subsystem needing it's own memory
> > allocation helpers is always a bug, either in the subsystem or in the
> > generic allocators.  In the ALSA case we have both..
> > 
> > sound/core/memalloc.c:
> > 
> >  - snd_dma_hack_alloc_coherent shouldn't exist, instead the arch
> >    dma_alloc_coherent should do hacks similar to it.  The
> >    kmalloc_dev/kmalloc_mask as proposed at KS should fix this
(Continue reading)


Gmane