From: Benny Sjostrand <gorm@cucumelo.org>
To: Friedrich Ewaldt <friedrich.ewaldt@gmx.de>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: [PATCH] cs46xx some few corrections
Date: Wed, 11 Dec 2002 22:50:05 +0100 [thread overview]
Message-ID: <3DF7B30D.7000408@cucumelo.org> (raw)
In-Reply-To: 3DF5E870.4040806@gmx.de
> Many thanks for this new patch! Now the xrun problems I reported are
> gone (great!), the SPDIF volume slider works correctly and SPDIF input
> basically works again.
> There seems to remain one problem with SPDIF input that wasn't there
> with rc6: With rc6, SPDIF input got out of sync sometimes.
> Muting+unmuting SPDIF input solved this problem. With the newest
> driver+last 2 patches, the SPDIF input sound is very distorted. After
> loading the alsa driver it sounds very 'robotic' (don't know how to
> describe it :-)) and high frequency components are missing. After
> muting+unmuting SPDIF input approx. 10 times SPDIF input gets into
> another state and there are many high frequency distortions. These
> distortions (not this pure high freq tone, I don't get this anymore)
> remain whenever I switch on SPDIF input. I didn't manage to get
> undistorted SPDIF input (which was possible with rc6).
> Dis-/reconnetcting the SPDIF input cable didn't help either.
> Another issue regarding SPDIF: Digital input works sometimes when I
> reboot, sometimes it doesn't (restarting alsa doesn't help then) and I
> have to reboot once again (I don't see a pattern why it does/-not work
> sometimes). SPDIF input always works when I do a soft reboot from
> win98, i.e. the card seems to be initialized by the win driver somehow
> (would some /proc/asound dumps help solving this problem?). Do you
> have similar problems with your card? Maybe that's terratec xfire
> specific. Anyone out there with a xfire who can report about SPDIF
> input with this card?
The SPDIF input problems are known (at least to me) and not specific to
the xfire card. The main problem is that I dont have enough of technical
info about to implement the SPDIF input part. The only answer I got from
a developer at Cirrus regarding the SPDIF input part was something like:
"yeahh, the SPDIF input needs some special treatments but in this moment
I dont remember exactly what" now several months has passed and I have
not heard a single word from Cirrus (got no responses to my mails at all
anymore ...)
So, so i am afraid that it wont be better than that for the moment ...
/Benny
-------------------------------------------------------
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/
next prev parent reply other threads:[~2002-12-11 21:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-10 8:09 [PATCH] cs46xx some few corrections Benny Sjostrand
2002-12-10 13:13 ` Friedrich Ewaldt
2002-12-11 21:50 ` Benny Sjostrand [this message]
2002-12-12 14:24 ` Friedrich Ewaldt
2002-12-12 21:00 ` Benny Sjostrand
2002-12-10 16:38 ` Takashi Iwai
2002-12-18 14:00 ` Kevin Puetz
2002-12-18 14:25 ` Takashi Iwai
2002-12-18 14:39 ` Jaroslav Kysela
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=3DF7B30D.7000408@cucumelo.org \
--to=gorm@cucumelo.org \
--cc=alsa-devel@lists.sourceforge.net \
--cc=friedrich.ewaldt@gmx.de \
/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