Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Apostolos Dimitromanolakis <apostolos@aei.ca>
To: Alsa-devel <alsa-devel@lists.sourceforge.net>
Subject: Re: Prodigy 7.1 driver update [snd-ice1724]
Date: Tue, 25 Nov 2003 14:38:39 -0500	[thread overview]
Message-ID: <3FC3AFBF.9040801@aei.ca> (raw)
In-Reply-To: <s5hptfh1url.wl@alsa2.suse.de>

[-- Attachment #1: Type: text/plain, Size: 1788 bytes --]


Hi,

Takashi Iwai wrote:

>> Finally there is some misconception in the aureon & prodigy drivers: 
>>the codec chip does not have a Master control as it appears at the 
>>mixer. Instead the master control just updates the 8 volume controls of 
>>the individual DAC at the same time. Probably the best way is to add a 
>>virtual master control (ie that we update the volumes of the dac with  
>><master attenuation> + <specific channel attenuation> ).
>>    
>>
>
>well, such a thing should be done on user-space rather than on
>kernel.  let's postpone this until the new highlevel mixer functions
>become available.
>  
>
   That's fine if it can be done in user space but this creates a problem
with the mixer right now. Changing the master volume does not update all
the DAC volumes as it should and you can be in the situation where
Master is100% and all other volumes are 0, yet the playback is done in
maximum volume at all channels. Maybe the driver should update all
channel volumes on a master update.

>>As I wrote some days ago, the default buffer/period rates that 
>>alsarecord uses at 44.1KHz and lower sampling , locks hard the kernel. 
>>Have no idea what is it/how to fix it whatsoever.
>>    
>>
>
>hmm, could be the mismatch of cristal rate?
>i don't find out the critical path in the driver yet.
>  
>

No idea about that and how to debug it.. The driver still locks the
kernel using arecord and default parameters at 44.1Khz but not at higher
sample rates. I attached the PCM setup that locks the machine hard. It
seems that the driver manages to record a few periods and then locks.
Maybe the reason is the funny period buffer sizes (5513??) that appear
at the pcm setup. As I understand the situation it is a (minor) problem
with the ice1724 driver.

Apostolis





[-- Attachment #2: log --]
[-- Type: text/plain, Size: 662 bytes --]

Recording WAVE '/dev/null' : Signed 32 bit Little Endian, Rate 44000 Hz, Stereo
Hardware PCM card 0 'Audiotrak Prodigy 7.1' device 0 subdevice 0

Its setup is:
stream       : CAPTURE
access       : RW_INTERLEAVED
format       : S32_LE
subformat    : STD
channels     : 2
rate         : 44100
exact rate   : 44100 (44100/1)
msbits       : 24
buffer_size  : 22050
period_size  : 5513
period_time  : 125011
tick_time    : 10000
tstamp_mode  : NONE
period_step  : 1
sleep_min    : 0
avail_min    : 5513
xfer_align   : 5513
start_threshold  : 1
stop_threshold   : 22050
silence_threshold: 0
silence_size : 0
boundary     : 1445068800
Aborted by signal Interrupt...



      reply	other threads:[~2003-11-25 19:38 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-24 17:53 Prodigy 7.1 driver update [snd-ice1724] Apostolos Dimitromanolakis
2003-11-24 18:33 ` Takashi Iwai
2003-11-25 19:38   ` Apostolos Dimitromanolakis [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3FC3AFBF.9040801@aei.ca \
    --to=apostolos@aei.ca \
    --cc=alsa-devel@lists.sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox