From: Martin Dalecki <dalecki@evision-ventures.com>
To: Thomas Gschwind <tom@infosys.tuwien.ac.at>
Cc: Nathan Bryant <nbryant@allegientsystems.com>,
linux-kernel@vger.kernel.org
Subject: Re: [Fwd: i810_audio]
Date: Thu, 03 Jan 2002 16:34:42 +0100 [thread overview]
Message-ID: <3C347A12.3070404@evision-ventures.com> (raw)
In-Reply-To: <3C3382CA.3000503@allegientsystems.com> <3C345493.5040800@evision-ventures.com> <20020103154718.C32419@infosys.tuwien.ac.at>
Thomas Gschwind wrote:
>On Thu, Jan 03, 2002 at 01:54:43PM +0100, Martin Dalecki wrote:
>
>>Nathan Bryant wrote:
>>
>>>Can you have a look at Doug Ledford's 0.13 driver? this incorporates
>>>most or all of the fixes you mentioned, except for SiS support, and
>>>some other fixes; it hasn't been incorporated into the main kernel
>>>quite yet because it needs more testing.
>>>
>>
>>Let me allow for a bit of advertising... Hist SiS changes work fine for
>>me with the exception
>>of recording.,
>>
>
>I did not have the pointer to Doug's latest version of the i810
>driver. I will integrate my patches into his latest version and will
>send it to the list. I will also have another look at recording but
>it would be great if you could be a little bit more specific of your
>recording results.
>
>What happened?
> How did you try to record?
> Did the system crash?
> Did the program you used for recording crash?
> Was the recording trash?
> How did it sound? To fast? To slow? Crackling? Random noise? All of it?
> What hardware do you have? K7S5A or a different MB with a SiS735 chipset?
>
Well my hardware is an Elitegroup, AMI-BIOS, with a SiS735. The AC'97
codec chip, which doesn't
get recognized properly by linux, is a avance logic (AL107) chip. The
whole thing is running
at a fixed 48000 Hz clock, which is derived from the USB host bridge.
XMMS is working fine, since it does understand the issue of fixed
frequency PCM
decoders. mplayer is usable with -ao sdl:esd, aka. piping the output
through esd, since the
esd doesn't have problems with fixed chip codecs. However the sound
frequency
transponder in ESD is really navie. It doesn't do any true filtering
apparently, so
one can hear the overleap frequency from 44.1 kHZ to 48kHz for
example. The artsd from KDE as usuall is failing blatantly and locks the
system hard...
And I don't have neither the time, nor inclination for debuggin it...
(Unless I could compile the whole KDE proerply with some recent gcc-3.x
for RedHat ;-).
Recodring did lockup the system hard as well immediately, no matter what.
However I will certainly try the whole again, since it would be really
nice to have the whole
stuff running properly under KDE. I'm not going to use GNOME in no time ;-).
N'f info?
next prev parent reply other threads:[~2002-01-03 15:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-02 21:59 [Fwd: i810_audio] Nathan Bryant
2002-01-03 12:54 ` Martin Dalecki
2002-01-03 14:47 ` Thomas Gschwind
2002-01-03 15:34 ` Martin Dalecki [this message]
2002-01-03 19:39 ` Nathan Bryant
2002-01-03 22:33 ` Nick Papadonis
2002-01-04 0:37 ` Nathan Bryant
2002-01-04 4:59 ` Doug Ledford
2002-01-04 5:09 ` Nathan Bryant
2002-01-04 5:31 ` Ben Clifford
2002-01-04 15:39 ` Doug Ledford
2002-01-04 19:37 ` Ben Clifford
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=3C347A12.3070404@evision-ventures.com \
--to=dalecki@evision-ventures.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nbryant@allegientsystems.com \
--cc=tom@infosys.tuwien.ac.at \
/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