The problem is that I need to have my driver work with application that already use
AFMT_AC3 in OSS. I don't need AC3 API for it because AC3 stream will be sent by that
application so what I need is just to handle the AFMT_AC3 just as other AFMT_S16_LE
PCM formats.
Sincerely,
ChenLi Tien
C.L. Tien - ??? wrote:
Hi,
Can ALSA support AFMT_AC3 to enable xine to play AC3 through S/PDIF interface? I check in core/pcm.c and core/oss/pcm_oss.c, neither of them has keywork AC3.
Sincerely,
ChenLi Tien
It works if you use the ALSA API instead of the OSS emulation in the
ALSA driver.
---
Hallo,
David Lloyd hat gesagt: // David Lloyd wrote:
> The thing is, dmix seems to have been around for years
dmix is not around for years. It came to live more or less this year,
and was only fully functional for some cards with version 0.9.7 or .8.
Another thing is, that while dmix works very
Hi,
Can ALSA support AFMT_AC3 to enable xine to play AC3 through S/PDIF interface? I check
in core/pcm.c and core/oss/pcm_oss.c, neither of them has keywork AC3.
Sincerely,
ChenLi Tien
---
This SF.net email is sponsored by: IBM Linux Tutoria
Clemens Ladisch wrote:
Martin Langer wrote:
And there are some other cards (Sonica, ...) which need a firmware download,
but there's no linux loader available.
MobilePre, Sonica, Transit, Ozone (all from M-Audio).
Thanks.
BTW: Patrick, what would be the preferred format for submitting
changed
On Wed, 17 Dec 2003, Peter Kirk wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Am Mittwoch, 17. Dezember 2003 21:11 schrieb David Lloyd:
> > Otherwise, if you all think this is not a worthwhile avenue to pursue, I
> > will try to convince my wife to let me buy a sblive and call it a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am Mittwoch, 17. Dezember 2003 21:11 schrieb David Lloyd:
> After much frustration being stuck on intel8x0 and trying to run teamspeak
> at the same time as a game, I was looking at the dmix implementation and I
> had several questions.
> So I will ma
After much frustration being stuck on intel8x0 and trying to run teamspeak
at the same time as a game, I was looking at the dmix implementation and I
had several questions.
What I want to do is modify dmix to do one of these things, in order of
increasing desirability:
1) When capture stream i
On Wed, 17 Dec 2003, James Courtier-Dutton wrote:
> Jaroslav Kysela wrote:
> > On Wed, 17 Dec 2003, James Courtier-Dutton wrote:
> >
> >
> >>Hi,
> >>
> >>If I use the "front" device name, and select a rate of 48000, I get
> >>sound output. (snd-intel8x0)
> >>If I use the "front" device name, an
Hallo,
James Courtier-Dutton hat gesagt: // James Courtier-Dutton wrote:
> Ooh! Interesting. So it is only a "plug" device, if it has "plug:"
> before it. So the following are all non-plug devices?
> "front", "rear", "center-lfe", "surround40", "surround51" etc.
>
> Plug devices: -
> dmix, dsnoo
Jaroslav Kysela wrote:
On Wed, 17 Dec 2003, James Courtier-Dutton wrote:
Hi,
If I use the "front" device name, and select a rate of 48000, I get
sound output. (snd-intel8x0)
If I use the "front" device name, and select a rate of 44100, It replies
saying 44100 is not availiable, try 48000 inste
On Wed, 17 Dec 2003, James Courtier-Dutton wrote:
> Hi,
>
> If I use the "front" device name, and select a rate of 48000, I get
> sound output. (snd-intel8x0)
> If I use the "front" device name, and select a rate of 44100, It replies
> saying 44100 is not availiable, try 48000 instead!
>
> As
Hi,
If I use the "front" device name, and select a rate of 48000, I get
sound output. (snd-intel8x0)
If I use the "front" device name, and select a rate of 44100, It replies
saying 44100 is not availiable, try 48000 instead!
As the "front" device is a plug device, alsa-lib should automatically
On Wednesday 17 Dec 2003 3:13 pm, Jaroslav Kysela wrote:
> Thanks for insigh to the problem. Can you try the attached patch?
Yes, that's a success. Thank you. It's still not absolutely perfect,
but it's significantly better than the original version. I've seen
one slippage (of about 40ms, und
On Mon, 15 Dec 2003, Chris Cannam wrote:
> On Monday 15 Dec 2003 9:16 am, Chris Cannam wrote:
> > This seems to suggest that the default system-based timer is doing
> > something a bit naive, like assuming it was called back on time
> > without actually checking.
>
> Hmm yes, even this crappy lit
Martin Langer wrote:
> And there are some other cards (Sonica, ...) which need a firmware download,
> but there's no linux loader available.
MobilePre, Sonica, Transit, Ozone (all from M-Audio).
BTW: Patrick, what would be the preferred format for submitting
changed to the soundcard list? (The
Allan Klinbail wrote:
> NOTE: The device must be set to use the Generic USB driver and not
> the "Original" driver (aka FPT)
In theory, ALSA has support for the "Original" setting since version
0.9.0rc8. Could you please send me the output of "lsusb -v" in both
settings?
Regards,
Clemens
--
Hi,
according to martin dausel's posting some weeks ago, I can
confirm, that since alsa-0.9.8 was released, the "old" rme-9652
cards are no longer working.
This is very strange, because the driver was not changed... :(
And: The OSS-kernelmod (rme96xx) works fine!
Here's some output (long lines not
18 matches
Mail list logo
