All of lore.kernel.org
 help / color / mirror / Atom feed
From: Friedrich Ewaldt <friedrich.ewaldt@gmx.de>
To: Takashi Iwai <tiwai@suse.de>
Cc: Thierry Vignaud <tvignaud@mandrakesoft.com>,
	alsa-devel@lists.sourceforge.net
Subject: Re: Re: [Alsa-user] fm801 driver status?
Date: Wed, 18 Dec 2002 14:28:09 +0100	[thread overview]
Message-ID: <3E0077E9.9050402@gmx.de> (raw)
In-Reply-To: <s5h8yyowm5s.wl@alsa2.suse.de>

Hi Takashi!

Thank you very much for your work!

The last patch solved the problem. No system hangs anymore. Looking 
back, I must say it was not *that* practical to reboot the system every 
time I used the audio device :-)
The sound quality is ok (I wouldn't expect it any better with this cheap 
card). Using my impulse response program, I also recognized that the 
overall D/A + A/D latency is constant (32 samples) as expected. (I could 
never see this before because using my cs46xx based xfire the latency 
changes in the range of 200 - 258 samples with every run. Bad - the 
xfire has much better sound quality. Is this a hint that pcm_link() 
doesn't work with cs46xx or is this maybe due to the DSP structure of 
the xfire?)

Using aplay, at the end of the audio file the last played samples get 
repeated once. This doesn't happen with 'play', 'cat somefile /dev/dsp' 
or 'artsplay'. But when I cause an error beep in a shell, I first hear 
the beep and then the last samples played back before by any program 
like  aplay, play, xmms,... I can reproduce this as many time as I like, 
i.e. the samples remain in the soundcard buffer all the time.
Another issue regarding aplay: playing back mono wav with a sampling 
frequency below 44k1, the sound get's crackled. This also doesn't happen 
with the other playback programs.
Now I don't know if these small problems result from playing back 
through the alsa device directly or if they are caused by aplay. Sorry 
to say I've no other native alsa app installed at the moment to do tests 
(e.g. alsa output for xmms ...).

Takashi wrote:

>perhaps do you see something out in the kernel messages on console 10
>(alt+f10) when the system hangs?  well, after hang up, you cannot
>switch the console, but you can start aplay on a certain
>console, switch with alt+f10 and wait until the playback is finished.
>  
>
I can switch with alt+f1 .. +f6 to the consoles 1 ..6, alt+f7 is X, but 
alt+f8 and alt+f10 only show a blinking cursor at the top. Does that 
mean that there are no messages or are I'm doing something wrong? (I 
don't see any messages that I can read in /var/log/messages afterwards)

>anyway, could you try the attached patch?
>  
>
of course.

>if you see something on the kernel messages such like kernel panic or
>oops, we can track the point...
>  
>
sorry, but...
... no more kernel problems to report ;-)

>
>ciao,
>
>Takashi
>  
>
cheers
fe



-------------------------------------------------------
This sf.net email is sponsored by:
With Great Power, Comes Great Responsibility 
Learn to use your power at OSDN's High Performance Computing Channel
http://hpc.devchannel.org/

  reply	other threads:[~2002-12-18 13:28 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-12 14:45 fm801 driver status? Friedrich Ewaldt
2002-12-12 15:08 ` [Alsa-user] " Takashi Iwai
2002-12-12 16:27   ` Friedrich Ewaldt
2002-12-12 17:32     ` Takashi Iwai
2002-12-13  9:53       ` Thierry Vignaud
2002-12-13 11:17         ` Friedrich Ewaldt
2002-12-13 16:29           ` Takashi Iwai
2002-12-13 16:33             ` Thierry Vignaud
2002-12-13 16:57             ` Friedrich Ewaldt
2002-12-13 17:02               ` Takashi Iwai
2002-12-13 18:24                 ` Friedrich Ewaldt
2002-12-16 15:12                   ` Takashi Iwai
2002-12-16 20:55                     ` Friedrich Ewaldt
2002-12-17 18:11                       ` Takashi Iwai
2002-12-18 13:28                         ` Friedrich Ewaldt [this message]
2002-12-19 11:31                           ` Takashi Iwai
2002-12-19 20:21                             ` Friedrich Ewaldt
2002-12-13 11:15       ` Friedrich Ewaldt

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=3E0077E9.9050402@gmx.de \
    --to=friedrich.ewaldt@gmx.de \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=tiwai@suse.de \
    --cc=tvignaud@mandrakesoft.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.