[alsa-devel] Testers wanted: New SB X-Fi driver
Hi,
after some communications with Creative, I finally got a mergeable version of their X-Fi driver. It's not my crappy hack but by genuine Creative :)
The patch is now merged into sound-unstable GIT tree topic/ctxfi branch: git://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound-unstable-2.6.git
The corresponding alsa-driver snapshot tarball is: ftp://ftp.kernel.org/pub/linux/kernel/people/tiwai/snapshot/alsa-driver-unstable-snapshot.tar.gz
The driver module is named as snd-ctxfi.
I tested only the driver builds with recent kernels, but unfortunately I have no test hardware now, so it'd be helpful if anyone can test it with a real hardware.
Note that the ctxfi driver might conflict with the HD-audio driver. So it'd be nice if you save the output of lspci before loading the drivers and let me know if any problem happens. Also, at testing, please check the kernel message. If this conflict really happens, try to build without hd-audio, that is, run configure with --with-cards=ctxfi option in addition to others, and test whether it works with this workaround (better after reboot to reset the board info by BIOS).
Once after I get positive feedbacks (or fix after negative ones), I'm going to merge it to the main tree so that it'll be in the next kernel. So, a quick test report would be greatly appreciated.
thanks,
Takashi
Takashi Iwai wrote:
Hi,
after some communications with Creative, I finally got a mergeable version of their X-Fi driver. It's not my crappy hack but by genuine Creative :)
The patch is now merged into sound-unstable GIT tree topic/ctxfi branch: git://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound-unstable-2.6.git
The corresponding alsa-driver snapshot tarball is: ftp://ftp.kernel.org/pub/linux/kernel/people/tiwai/snapshot/alsa-driver-unstable-snapshot.tar.gz
Woo, worked first go! :)
I have a "Titanium fata1ity Pro" (1102:000b/1102:0043), and compiled against Intrepid's current kernel (2.6.28-11).
I have only recently subscribed to the list and was just about to ask what the deal was with the X-Fi driver.
So mplayer, aplay and audacious all play things. Clearly works perfectly then :)
Does alsa have some sort of test suite or similar that I can run the card through?
Mick.
At Thu, 14 May 2009 22:07:33 +1000, Michael (Micksa) Slade wrote:
Takashi Iwai wrote:
Hi,
after some communications with Creative, I finally got a mergeable version of their X-Fi driver. It's not my crappy hack but by genuine Creative :)
The patch is now merged into sound-unstable GIT tree topic/ctxfi branch: git://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound-unstable-2.6.git
The corresponding alsa-driver snapshot tarball is: ftp://ftp.kernel.org/pub/linux/kernel/people/tiwai/snapshot/alsa-driver-unstable-snapshot.tar.gz
Woo, worked first go! :)
I have a "Titanium fata1ity Pro" (1102:000b/1102:0043), and compiled against Intrepid's current kernel (2.6.28-11).
I have only recently subscribed to the list and was just about to ask what the deal was with the X-Fi driver.
So mplayer, aplay and audacious all play things. Clearly works perfectly then :)
Great.
Does alsa have some sort of test suite or similar that I can run the card through?
The way you tested should suffice as primary tests. You can also try speaker-test for multi-channels.
Thanks!
Takashi
Michael (Micksa) Slade wrote:
Takashi Iwai wrote:
Hi,
after some communications with Creative, I finally got a mergeable version of their X-Fi driver. It's not my crappy hack but by genuine Creative :)
The patch is now merged into sound-unstable GIT tree topic/ctxfi branch: git://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound-unstable-2.6.git
The corresponding alsa-driver snapshot tarball is: ftp://ftp.kernel.org/pub/linux/kernel/people/tiwai/snapshot/alsa-driver-unstable-snapshot.tar.gz
Woo, worked first go! :)
I have a "Titanium fata1ity Pro" (1102:000b/1102:0043), and compiled against Intrepid's current kernel (2.6.28-11).
I have only recently subscribed to the list and was just about to ask what the deal was with the X-Fi driver.
So mplayer, aplay and audacious all play things. Clearly works perfectly then :)
Does alsa have some sort of test suite or similar that I can run the card through?
Oh, doesn't survive suspend/resume, and doesn't appear to work at 24bit.
Mick.
At Thu, 14 May 2009 22:22:11 +1000, Michael (Micksa) Slade wrote:
Michael (Micksa) Slade wrote:
Takashi Iwai wrote: Hi, after some communications with Creative, I finally got a mergeable version of their X-Fi driver. It's not my crappy hack but by genuine Creative :) The patch is now merged into sound-unstable GIT tree topic/ctxfi branch: git://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound-unstable-2.6.git The corresponding alsa-driver snapshot tarball is: ftp://ftp.kernel.org/pub/linux/kernel/people/tiwai/snapshot/alsa-driver-unstable-snapshot.tar.gz Woo, worked first go! :) I have a "Titanium fata1ity Pro" (1102:000b/1102:0043), and compiled against Intrepid's current kernel (2.6.28-11). I have only recently subscribed to the list and was just about to ask what the deal was with the X-Fi driver. So mplayer, aplay and audacious all play things. Clearly works perfectly then :) Does alsa have some sort of test suite or similar that I can run the card through?Oh, doesn't survive suspend/resume,
It's expected. PM isn't supported yet with this driver.
and doesn't appear to work at 24bit.
That's bad. How did you test it?
thanks,
Takashi
Takashi Iwai wrote:
At Thu, 14 May 2009 22:22:11 +1000, Michael (Micksa) Slade wrote:
Woo, worked first go! :) I have a "Titanium fata1ity Pro" (1102:000b/1102:0043), and compiled against Intrepid's current kernel (2.6.28-11). I have only recently subscribed to the list and was just about to ask what the deal was with the X-Fi driver. So mplayer, aplay and audacious all play things. Clearly works perfectly then :) Does alsa have some sort of test suite or similar that I can run the card through?Oh, doesn't survive suspend/resume,
It's expected. PM isn't supported yet with this driver.
and doesn't appear to work at 24bit.
That's bad. How did you test it?
Swtiched audacious to 24bit. It very quietly plays a badly distorted version of the song :)
How might I get a copy of the specs? I want to try my hand at kernel coding. I hear it gets you chicks.
Mick.
At Thu, 14 May 2009 22:34:09 +1000, Michael (Micksa) Slade wrote:
Takashi Iwai wrote:
At Thu, 14 May 2009 22:22:11 +1000, Michael (Micksa) Slade wrote: Woo, worked first go! :) I have a "Titanium fata1ity Pro" (1102:000b/1102:0043), and compiled against Intrepid's current kernel (2.6.28-11). I have only recently subscribed to the list and was just about to ask what the deal was with the X-Fi driver. So mplayer, aplay and audacious all play things. Clearly works perfectly then :) Does alsa have some sort of test suite or similar that I can run the card through? Oh, doesn't survive suspend/resume, It's expected. PM isn't supported yet with this driver. and doesn't appear to work at 24bit. That's bad. How did you test it?Swtiched audacious to 24bit. It very quietly plays a badly distorted version of the song :)
What about aplay with 32bit samples?
How might I get a copy of the specs?
Unfortunately I have no spec, too. I just got source codes and contact with guys.
thanks,
Takashi
Takashi Iwai wrote:
At Thu, 14 May 2009 22:34:09 +1000, Michael (Micksa) Slade wrote:
Swtiched audacious to 24bit. It very quietly plays a badly distorted version of the song :)
What about aplay with 32bit samples?
Seems to work fine. Also 24bit. Guess it's audacious' fault. Probably.
I'm going to play around with all this stuff more in my spare time so hopefully in a while I'll start sounding like I know what I'm doing.
Mick.
At Thu, 14 May 2009 23:07:59 +1000, Michael (Micksa) Slade wrote:
Takashi Iwai wrote:
At Thu, 14 May 2009 22:34:09 +1000, Michael (Micksa) Slade wrote: Swtiched audacious to 24bit. It very quietly plays a badly distorted version of the song :) What about aplay with 32bit samples?Seems to work fine. Also 24bit. Guess it's audacious' fault. Probably.
It's possible that audacious tries to access 24bit, not 32bit format, and ctxfi driver has a bug around that.
Could you try the patch below?
Takashi
=== diff --git a/sound/pci/ctxfi/ctpcm.c b/sound/pci/ctxfi/ctpcm.c index a64cb0e..aae9eb1 100644 --- a/sound/pci/ctxfi/ctpcm.c +++ b/sound/pci/ctxfi/ctpcm.c @@ -30,7 +30,6 @@ static struct snd_pcm_hardware ct_pcm_playback_hw = { SNDRV_PCM_FMTBIT_S16_LE | SNDRV_PCM_FMTBIT_U16_LE | SNDRV_PCM_FMTBIT_S24_3LE | - SNDRV_PCM_FMTBIT_S24_LE | SNDRV_PCM_FMTBIT_S32_LE), .rates = (SNDRV_PCM_RATE_CONTINUOUS | SNDRV_PCM_RATE_8000_192000), @@ -81,7 +80,6 @@ static struct snd_pcm_hardware ct_pcm_capture_hw = { SNDRV_PCM_FMTBIT_S16_LE | SNDRV_PCM_FMTBIT_U16_LE | SNDRV_PCM_FMTBIT_S24_3LE | - SNDRV_PCM_FMTBIT_S24_LE | SNDRV_PCM_FMTBIT_S32_LE), .rates = (SNDRV_PCM_RATE_CONTINUOUS | SNDRV_PCM_RATE_8000_96000),
Takashi Iwai wrote:
At Thu, 14 May 2009 23:07:59 +1000, Michael (Micksa) Slade wrote:
Takashi Iwai wrote:
At Thu, 14 May 2009 22:34:09 +1000, Michael (Micksa) Slade wrote: Swtiched audacious to 24bit. It very quietly plays a badly distorted version of the song :) What about aplay with 32bit samples?Seems to work fine. Also 24bit. Guess it's audacious' fault. Probably.
It's possible that audacious tries to access 24bit, not 32bit format, and ctxfi driver has a bug around that.
Could you try the patch below?
[snip]
aplay still works in 24 and 32bit, audacious freezes (but you can still switch back to 16bit and it will play without having to kill and restart it)
What does that mean? :)
Mick.
At Thu, 14 May 2009 23:37:20 +1000, Michael (Micksa) Slade wrote:
Takashi Iwai wrote:
At Thu, 14 May 2009 23:07:59 +1000, Michael (Micksa) Slade wrote: Takashi Iwai wrote: At Thu, 14 May 2009 22:34:09 +1000, Michael (Micksa) Slade wrote: Swtiched audacious to 24bit. It very quietly plays a badly distorted version of the song :) What about aplay with 32bit samples? Seems to work fine. Also 24bit. Guess it's audacious' fault. Probably. It's possible that audacious tries to access 24bit, not 32bit format, and ctxfi driver has a bug around that. Could you try the patch below?[snip]
aplay still works in 24 and 32bit, audacious freezes (but you can still switch back to 16bit and it will play without having to kill and restart it)
What does that mean? :)
Hrm, I don't know what it's doing exactly... Or, removing S24_3LE there might help?
I don't know exactly that audacious is doing. Anyway, it's no critical bug as a showstopper :)
thanks,
Takashi
Hi,
On Thu, 2009-05-14 at 15:28 +0200, Takashi Iwai wrote:
At Thu, 14 May 2009 23:07:59 +1000, Michael (Micksa) Slade wrote:
Takashi Iwai wrote:
At Thu, 14 May 2009 22:34:09 +1000, Michael (Micksa) Slade wrote: Swtiched audacious to 24bit. It very quietly plays a badly distorted version of the song :) What about aplay with 32bit samples?Seems to work fine. Also 24bit. Guess it's audacious' fault. Probably.
It's possible that audacious tries to access 24bit, not 32bit format, and ctxfi driver has a bug around that.
Audacious indeed uses 24bit formats. We will add proper 32bit support in the 2.1 merge window.
William
At Mon, 18 May 2009 21:38:52 -0500, William Pitcock wrote:
Hi,
On Thu, 2009-05-14 at 15:28 +0200, Takashi Iwai wrote:
At Thu, 14 May 2009 23:07:59 +1000, Michael (Micksa) Slade wrote:
Takashi Iwai wrote:
At Thu, 14 May 2009 22:34:09 +1000, Michael (Micksa) Slade wrote: Swtiched audacious to 24bit. It very quietly plays a badly distorted version of the song :) What about aplay with 32bit samples?Seems to work fine. Also 24bit. Guess it's audacious' fault. Probably.
It's possible that audacious tries to access 24bit, not 32bit format, and ctxfi driver has a bug around that.
Audacious indeed uses 24bit formats.
OK, thanks. Is it 24bit 3-bytes format, or 24bit in 4bytes format?
Takashi
On Tue, 2009-05-19 at 07:34 +0200, Takashi Iwai wrote:
At Mon, 18 May 2009 21:38:52 -0500, William Pitcock wrote:
Hi,
On Thu, 2009-05-14 at 15:28 +0200, Takashi Iwai wrote:
At Thu, 14 May 2009 23:07:59 +1000, Michael (Micksa) Slade wrote:
Takashi Iwai wrote:
At Thu, 14 May 2009 22:34:09 +1000, Michael (Micksa) Slade wrote: Swtiched audacious to 24bit. It very quietly plays a badly distorted version of the song :) What about aplay with 32bit samples?Seems to work fine. Also 24bit. Guess it's audacious' fault. Probably.
It's possible that audacious tries to access 24bit, not 32bit format, and ctxfi driver has a bug around that.
Audacious indeed uses 24bit formats.
OK, thanks. Is it 24bit 3-bytes format, or 24bit in 4bytes format?
24bit 3-bytes format.
This is a table of supported formats:
static alsaplug_format_mapping_t alsaplug_format_conv_tbl[] = { {FMT_S24_LE, SND_PCM_FORMAT_S24_LE}, {FMT_S24_BE, SND_PCM_FORMAT_S24_BE}, {FMT_S24_NE, SND_PCM_FORMAT_S24}, {FMT_U24_LE, SND_PCM_FORMAT_U24_LE}, {FMT_U24_BE, SND_PCM_FORMAT_U24_BE}, {FMT_U24_NE, SND_PCM_FORMAT_U24}, {FMT_S16_LE, SND_PCM_FORMAT_S16_LE}, {FMT_S16_BE, SND_PCM_FORMAT_S16_BE}, {FMT_S16_NE, SND_PCM_FORMAT_S16}, {FMT_U16_LE, SND_PCM_FORMAT_U16_LE}, {FMT_U16_BE, SND_PCM_FORMAT_U16_BE}, {FMT_U16_NE, SND_PCM_FORMAT_U16}, {FMT_U8, SND_PCM_FORMAT_U8}, {FMT_S8, SND_PCM_FORMAT_S8}, };
William
2009/5/14 Takashi Iwai tiwai@suse.de:
Hi,
after some communications with Creative, I finally got a mergeable version of their X-Fi driver. It's not my crappy hack but by genuine Creative :)
It is good news that you managed to have productive communications with Creative. I did have a very good relationship with Creative and EMU until all my contacts left the company. It took me years to build up the relationship, but I did not have the time to start again from scratch. If you manage to get the open source NDA signed with them, ask them to contact me, informing me of such, and I can then pass all the datasheets I have on to you. I do need direct contact from them before I can do this though. The datasheets cover almost all Creative and EMU sound cards.
Kind Regards
James
At Thu, 14 May 2009 14:05:06 +0100, James Courtier-Dutton wrote:
2009/5/14 Takashi Iwai tiwai@suse.de:
Hi,
after some communications with Creative, I finally got a mergeable version of their X-Fi driver. It's not my crappy hack but by genuine Creative :)
It is good news that you managed to have productive communications with Creative. I did have a very good relationship with Creative and EMU until all my contacts left the company. It took me years to build up the relationship, but I did not have the time to start again from scratch. If you manage to get the open source NDA signed with them, ask them to contact me, informing me of such, and I can then pass all the datasheets I have on to you. I do need direct contact from them before I can do this though. The datasheets cover almost all Creative and EMU sound cards.
Thanks. I still don't sign any NDA for Creative, so I've been just a bridge between them and us. But, if I do, certainly I'll ask you to gather all stuff ;)
Takashi
At Thu, 14 May 2009 12:52:17 +0200, I wrote:
Hi,
after some communications with Creative, I finally got a mergeable version of their X-Fi driver. It's not my crappy hack but by genuine Creative :)
The patch is now merged into sound-unstable GIT tree topic/ctxfi branch: git://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound-unstable-2.6.git
The corresponding alsa-driver snapshot tarball is: ftp://ftp.kernel.org/pub/linux/kernel/people/tiwai/snapshot/alsa-driver-unstable-snapshot.tar.gz
The driver module is named as snd-ctxfi.
I tested only the driver builds with recent kernels, but unfortunately I have no test hardware now, so it'd be helpful if anyone can test it with a real hardware.
Note that the ctxfi driver might conflict with the HD-audio driver. So it'd be nice if you save the output of lspci before loading the drivers and let me know if any problem happens. Also, at testing, please check the kernel message. If this conflict really happens, try to build without hd-audio, that is, run configure with --with-cards=ctxfi option in addition to others, and test whether it works with this workaround (better after reboot to reset the board info by BIOS).
Once after I get positive feedbacks (or fix after negative ones), I'm going to merge it to the main tree so that it'll be in the next kernel. So, a quick test report would be greatly appreciated.
It seems that there is no critical issues, so far. Thus I merged X-fi patch to sound GIT tree. It'll appear in the normal alsa-driver snapshot below, too. ftp://ftp.kernel.org/pub/linux/kernel/people/tiwai/snapshot/alsa-driver-snapshot.tar.gz
Any positive / negative feedback reports are still appreciated.
thanks,
Takashi
Takashi Iwai wrote:
It seems that there is no critical issues, so far. Thus I merged X-fi patch to sound GIT tree. It'll appear in the normal alsa-driver snapshot below, too. ftp://ftp.kernel.org/pub/linux/kernel/people/tiwai/snapshot/alsa-driver-snapshot.tar.gz
Should the hda driver still have the X-fi PCI ids?
Mick.
At Sat, 16 May 2009 19:34:28 +1000, Michael (Micksa) Slade wrote:
Takashi Iwai wrote:
It seems that there is no critical issues, so far. Thus I merged X-fi patch to sound GIT tree. It'll appear in the normal alsa-driver snapshot below, too. ftp://ftp.kernel.org/pub/linux/kernel/people/tiwai/snapshot/alsa-driver-snapshot.tar.gz
Should the hda driver still have the X-fi PCI ids?
Yes, it looks like that not all models are supported by ctxfi driver.
The question is whether we get real conflicts. If any, let me know.
Takashi
Takashi Iwai wrote:
At Sat, 16 May 2009 19:34:28 +1000, Michael (Micksa) Slade wrote:
Takashi Iwai wrote:
It seems that there is no critical issues, so far. Thus I merged X-fi patch to sound GIT tree. It'll appear in the normal alsa-driver snapshot below, too. ftp://ftp.kernel.org/pub/linux/kernel/people/tiwai/snapshot/alsa-driver-snapshot.tar.gz
Should the hda driver still have the X-fi PCI ids?
Yes, it looks like that not all models are supported by ctxfi driver.
The question is whether we get real conflicts. If any, let me know.
Well on my box snd-hda-intel, as-is, stole my card before snd-ctxfi could get to it. Does that count as a conflict?
Mick.
At Mon, 18 May 2009 13:43:36 +1000, Michael (Micksa) Slade wrote:
Takashi Iwai wrote:
At Sat, 16 May 2009 19:34:28 +1000, Michael (Micksa) Slade wrote: Takashi Iwai wrote: It seems that there is no critical issues, so far. Thus I merged X-fi patch to sound GIT tree. It'll appear in the normal alsa-driver snapshot below, too. ftp://ftp.kernel.org/pub/linux/kernel/people/tiwai/snapshot/alsa-driver-snapshot.tar.gz Should the hda driver still have the X-fi PCI ids? Yes, it looks like that not all models are supported by ctxfi driver. The question is whether we get real conflicts. If any, let me know.Well on my box snd-hda-intel, as-is, stole my card before snd-ctxfi could get to it. Does that count as a conflict?
Yes. That's what I mentioned as a "conflict".
Could you run alsa-info.sh with --no-upload option, and attach the generated file? The script is found at http://www.alsa-project.org/alsa-info.sh
thanks,
Takashi
Hi,
When this driver will support USB X-Fi Surround 5.1 ?
best regards, Patryk Kowalczyk
At Mon, 18 May 2009 13:43:36 +1000, Michael (Micksa) Slade wrote:
Takashi Iwai wrote:
At Sat, 16 May 2009 19:34:28 +1000, Michael (Micksa) Slade wrote: Takashi Iwai wrote: It seems that there is no critical issues, so far. Thus I merged X-fi patch to sound GIT tree. It'll appear inthe normal alsa-driver snapshot below, too. ftp://ftp.kernel.org/pub/linux/kernel/people/tiwai/snapshot/alsa-driver-snapshot.tar.gz
Should the hda driver still have the X-fi PCI ids? Yes, it looks like that not all models are supported by ctxfidriver.
The question is whether we get real conflicts. If any, let me know.Well on my box snd-hda-intel, as-is, stole my card before snd-ctxfi could get to it. Does that count as a conflict?
Yes. That's what I mentioned as a "conflict".
Could you run alsa-info.sh with --no-upload option, and attach the generated file? The script is found at http://www.alsa-project.org/alsa-info.sh
thanks,
Takashi _______________________________________________ Alsa-devel mailing list Alsa-devel@alsa-project.org http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
At Mon, 18 May 2009 08:06:27 +0200 (CEST), wodor@wodor.org wrote:
Hi,
When this driver will support USB X-Fi Surround 5.1 ?
USB is a completely different device and has nothing to do with PCI X-Fi. Don't be fooled by marketing :)
Takashi
best regards, Patryk Kowalczyk
At Mon, 18 May 2009 13:43:36 +1000, Michael (Micksa) Slade wrote:
Takashi Iwai wrote:
At Sat, 16 May 2009 19:34:28 +1000, Michael (Micksa) Slade wrote: Takashi Iwai wrote: It seems that there is no critical issues, so far. Thus I merged X-fi patch to sound GIT tree. It'll appear inthe normal alsa-driver snapshot below, too. ftp://ftp.kernel.org/pub/linux/kernel/people/tiwai/snapshot/alsa-driver-snapshot.tar.gz
Should the hda driver still have the X-fi PCI ids? Yes, it looks like that not all models are supported by ctxfidriver.
The question is whether we get real conflicts. If any, let me know.Well on my box snd-hda-intel, as-is, stole my card before snd-ctxfi could get to it. Does that count as a conflict?
Yes. That's what I mentioned as a "conflict".
Could you run alsa-info.sh with --no-upload option, and attach the generated file? The script is found at http://www.alsa-project.org/alsa-info.sh
thanks,
Takashi _______________________________________________ Alsa-devel mailing list Alsa-devel@alsa-project.org http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
-- Patryk Kowalczyk jid/email: wodor@wodor.org
Alsa-devel mailing list Alsa-devel@alsa-project.org http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
On Mon, 18 May 2009 21:42:45 -0500 William Pitcock nenolod@sacredspiral.co.uk wrote:
Hi,
On Mon, 2009-05-18 at 08:06 +0200, wodor@wodor.org wrote:
Hi,
When this driver will support USB X-Fi Surround 5.1 ?
Never. That would be supported by snd-usb-audio.
William
Hi,
So. When will snd-usb-audio support channels clonning or some mixer for this sound card? Now I`m clonning channels by alsa plugins but it`s taking much CPU time.
best regards, Patryk Kowalczyk
-- jid / email : wodor at wodor dot org homepage: wodor dot org
At Tue, 19 May 2009 17:09:05 +0200, Patryk Kowalczyk wrote:
On Mon, 18 May 2009 21:42:45 -0500 William Pitcock nenolod@sacredspiral.co.uk wrote:
Hi,
On Mon, 2009-05-18 at 08:06 +0200, wodor@wodor.org wrote:
Hi,
When this driver will support USB X-Fi Surround 5.1 ?
Never. That would be supported by snd-usb-audio.
William
Hi,
So. When will snd-usb-audio support channels clonning or some mixer for this sound card? Now I`m clonning channels by alsa plugins but it`s taking much CPU time.
I don't think the hardware does such a thing. Almost all usb-audio devices don't do any fancy effects or channel setups. They are mostly a dumb playback / recording device. All other effects are implemented in software secretly.
Takashi
Takashi Iwai wrote:
Could you run alsa-info.sh with --no-upload option, and attach the generated file? The script is found at http://www.alsa-project.org/alsa-info.sh
Attached.
Mick.
upload=true&script=true&cardinfo= !!################################ !!ALSA Information Script v 0.4.56 !!################################
!!Script ran on: Mon May 18 10:07:32 UTC 2009
!!Linux Distribution !!------------------
Ubuntu 9.04 \n \l DISTRIB_ID=Ubuntu DISTRIB_DESCRIPTION="Ubuntu 9.04"
!!Kernel Information !!------------------
Kernel release: 2.6.28-11-generic Operating System: GNU/Linux Architecture: x86_64 Processor: unknown SMP Enabled: Yes
!!ALSA Version !!------------
Driver version: 1.0.20 Library version: 1.0.18 Utilities version: 1.0.18
!!Loaded ALSA modules !!-------------------
snd_ctxfi snd_usb_audio snd_usb_audio
!!Sound Servers on this system !!----------------------------
Pulseaudio: Installed - Yes (/usr/bin/pulseaudio) Running - Yes
ESound Daemon: Installed - Yes (/usr/bin/esd) Running - No
Jack: Installed - Yes (/usr/bin/jackd) Running - No
!!Soundcards recognised by ALSA !!-----------------------------
0 [XFi ]: SB-XFi - Creative X-Fi Creative ALSA Driver X-Fi 1 [Cable ]: USB-Audio - USB Midi Cable USB Midi Cable at usb-0000:00:12.2-3.1, full speed 2 [PCR ]: USB-Audio - PCR EDIROL PCR at usb-0000:00:12.2-3.2, full speed
!!PCI Soundcards installed in the system !!--------------------------------------
00:14.2 Audio device: ATI Technologies Inc SBx00 Azalia (Intel HDA) 02:00.0 Audio device: Creative Labs [X-Fi Titanium series] EMU20k2 (rev 03)
!!Advanced information - PCI Vendor/Device/Susbsystem ID's !!--------------------------------------------------------
00:14.2 0403: 1002:4383 Subsystem: 1458:a022 -- 02:00.0 0403: 1102:000b (rev 03) Subsystem: 1102:0043
!!Modprobe options (Sound related) !!--------------------------------
snd-atiixp-modem: index=-2 snd-intel8x0m: index=-2 snd-via82xx-modem: index=-2 snd-usb-audio: index=-2 snd-usb-us122l: index=-2 snd-usb-usx2y: index=-2 snd-usb-caiaq: index=-2 snd-cmipci: mpu_port=0x330 fm_port=0x388 snd-pcsp: index=-2
!!Loaded sound module options !!--------------------------
!!Module: snd_ctxfi multiple : 2 reference_rate : 48000
!!Module: snd_usb_audio async_unlink : Y device_setup : 0,0,0,0,0,0,0,0 devpath : <NULL>,<NULL>,<NULL>,<NULL>,<NULL>,<NULL>,<NULL>,<NULL> enable : Y,Y,Y,Y,Y,Y,Y,Y id : <NULL>,<NULL>,<NULL>,<NULL>,<NULL>,<NULL>,<NULL>,<NULL> ignore_ctl_error : N index : -2,-1,-1,-1,-1,-1,-1,-1 nrpacks : 8 pid : -1,-1,-1,-1,-1,-1,-1,-1 vid : -1,-1,-1,-1,-1,-1,-1,-1
!!Module: snd_usb_audio async_unlink : Y device_setup : 0,0,0,0,0,0,0,0 devpath : <NULL>,<NULL>,<NULL>,<NULL>,<NULL>,<NULL>,<NULL>,<NULL> enable : Y,Y,Y,Y,Y,Y,Y,Y id : <NULL>,<NULL>,<NULL>,<NULL>,<NULL>,<NULL>,<NULL>,<NULL> ignore_ctl_error : N index : -2,-1,-1,-1,-1,-1,-1,-1 nrpacks : 8 pid : -1,-1,-1,-1,-1,-1,-1,-1 vid : -1,-1,-1,-1,-1,-1,-1,-1
!!ALSA Device nodes !!-----------------
crw-rw----+ 1 root audio 116, 0 May 18 20:03 /dev/snd/controlC0 crw-rw----+ 1 root audio 116, 32 May 16 16:27 /dev/snd/controlC1 crw-rw----+ 1 root audio 116, 64 May 15 19:36 /dev/snd/controlC2 crw-rw----+ 1 root audio 116, 40 May 16 16:27 /dev/snd/midiC1D0 crw-rw----+ 1 root audio 116, 72 May 15 19:36 /dev/snd/midiC2D0 crw-rw----+ 1 root audio 116, 24 May 18 20:03 /dev/snd/pcmC0D0c crw-rw----+ 1 root audio 116, 16 May 18 20:04 /dev/snd/pcmC0D0p crw-rw----+ 1 root audio 116, 17 May 18 20:03 /dev/snd/pcmC0D1p crw-rw----+ 1 root audio 116, 18 May 18 20:03 /dev/snd/pcmC0D2p crw-rw----+ 1 root audio 116, 19 May 18 20:03 /dev/snd/pcmC0D3p crw-rw----+ 1 root audio 116, 20 May 18 20:03 /dev/snd/pcmC0D4p crw-rw----+ 1 root audio 116, 1 May 15 19:36 /dev/snd/seq crw-rw----+ 1 root audio 116, 33 May 15 19:36 /dev/snd/timer
!!Aplay/Arecord output !!------------
APLAY
**** List of PLAYBACK Hardware Devices **** card 0: XFi [Creative X-Fi], device 0: Front/WaveIn [Front/WaveIn] Subdevices: 8/8 Subdevice #0: subdevice #0 Subdevice #1: subdevice #1 Subdevice #2: subdevice #2 Subdevice #3: subdevice #3 Subdevice #4: subdevice #4 Subdevice #5: subdevice #5 Subdevice #6: subdevice #6 Subdevice #7: subdevice #7 card 0: XFi [Creative X-Fi], device 1: Rear [Rear] Subdevices: 8/8 Subdevice #0: subdevice #0 Subdevice #1: subdevice #1 Subdevice #2: subdevice #2 Subdevice #3: subdevice #3 Subdevice #4: subdevice #4 Subdevice #5: subdevice #5 Subdevice #6: subdevice #6 Subdevice #7: subdevice #7 card 0: XFi [Creative X-Fi], device 2: Center/LFE [Center/LFE] Subdevices: 8/8 Subdevice #0: subdevice #0 Subdevice #1: subdevice #1 Subdevice #2: subdevice #2 Subdevice #3: subdevice #3 Subdevice #4: subdevice #4 Subdevice #5: subdevice #5 Subdevice #6: subdevice #6 Subdevice #7: subdevice #7 card 0: XFi [Creative X-Fi], device 3: Surround [Surround] Subdevices: 8/8 Subdevice #0: subdevice #0 Subdevice #1: subdevice #1 Subdevice #2: subdevice #2 Subdevice #3: subdevice #3 Subdevice #4: subdevice #4 Subdevice #5: subdevice #5 Subdevice #6: subdevice #6 Subdevice #7: subdevice #7 card 0: XFi [Creative X-Fi], device 4: IEC958 Non-audio [IEC958 Non-audio] Subdevices: 1/1 Subdevice #0: subdevice #0
ARECORD
**** List of CAPTURE Hardware Devices **** card 0: XFi [Creative X-Fi], device 0: Front/WaveIn [Front/WaveIn] Subdevices: 1/1 Subdevice #0: subdevice #0
!!Amixer output !!-------------
!!-------Mixer controls for card 0 [XFi]
Card hw:0 'XFi'/'Creative ALSA Driver X-Fi' Mixer name : '20K2' Components : '' Controls : 29 Simple ctrls : 10 Simple mixer control 'Master',0 Capabilities: pvolume cvolume Playback channels: Front Left - Front Right Capture channels: Front Left - Front Right Limits: Playback 0 - 43690 Capture 0 - 43690 Front Left: Playback 21845 [50%] Capture 34913 [80%] Front Right: Playback 21845 [50%] Capture 34913 [80%] Simple mixer control 'PCM',0 Capabilities: pvolume cvolume cswitch cswitch-joined Playback channels: Front Left - Front Right Capture channels: Front Left - Front Right Limits: Playback 0 - 43690 Capture 0 - 43690 Front Left: Playback 34461 [79%] Capture 34913 [80%] [on] Front Right: Playback 34461 [79%] Capture 34913 [80%] [on] Simple mixer control 'Front',0 Capabilities: pvolume pswitch pswitch-joined Playback channels: Front Left - Front Right Limits: Playback 0 - 43690 Mono: Front Left: Playback 34913 [80%] [on] Front Right: Playback 34913 [80%] [on] Simple mixer control 'Surround',0 Capabilities: pvolume pswitch pswitch-joined Playback channels: Front Left - Front Right Limits: Playback 0 - 43690 Mono: Front Left: Playback 32525 [74%] [off] Front Right: Playback 32525 [74%] [off] Simple mixer control 'Center/LFE',0 Capabilities: pvolume pswitch pswitch-joined Playback channels: Front Left - Front Right Limits: Playback 0 - 43690 Mono: Front Left: Playback 32525 [74%] [off] Front Right: Playback 32525 [74%] [off] Simple mixer control 'Line-in',0 Capabilities: pvolume cvolume pswitch pswitch-joined cswitch cswitch-joined Playback channels: Front Left - Front Right Capture channels: Front Left - Front Right Limits: Playback 0 - 43690 Capture 0 - 43690 Front Left: Playback 32525 [74%] [off] Capture 32525 [74%] [on] Front Right: Playback 32525 [74%] [off] Capture 32525 [74%] [on] Simple mixer control 'Mic',0 Capabilities: pvolume cvolume cswitch cswitch-joined Playback channels: Front Left - Front Right Capture channels: Front Left - Front Right Limits: Playback 0 - 43690 Capture 0 - 43690 Front Left: Playback 0 [0%] Capture 0 [0%] [off] Front Right: Playback 0 [0%] Capture 0 [0%] [off] Simple mixer control 'Rear',0 Capabilities: pvolume pswitch pswitch-joined Playback channels: Front Left - Front Right Limits: Playback 0 - 43690 Mono: Front Left: Playback 32525 [74%] [off] Front Right: Playback 32525 [74%] [off] Simple mixer control 'S/PDIF-in',0 Capabilities: pvolume cvolume pswitch pswitch-joined cswitch cswitch-joined Playback channels: Front Left - Front Right Capture channels: Front Left - Front Right Limits: Playback 0 - 43690 Capture 0 - 43690 Front Left: Playback 32525 [74%] [off] Capture 32525 [74%] [on] Front Right: Playback 32525 [74%] [off] Capture 32525 [74%] [on] Simple mixer control 'S/PDIF-out',0 Capabilities: pvolume pswitch pswitch-joined Playback channels: Front Left - Front Right Limits: Playback 0 - 43690 Mono: Front Left: Playback 32525 [74%] [off] Front Right: Playback 32525 [74%] [off]
!!-------Mixer controls for card 1 [Cable]
Card hw:1 'Cable'/'USB Midi Cable at usb-0000:00:12.2-3.1, full speed' Mixer name : 'USB Mixer' Components : 'USB15ca:0101' Controls : 0 Simple ctrls : 0
!!-------Mixer controls for card 2 [PCR]
Card hw:2 'PCR'/'EDIROL PCR at usb-0000:00:12.2-3.2, full speed' Mixer name : '' Components : 'USB0582:0033' Controls : 0 Simple ctrls : 0
!!Alsactl output !!-------------
--startcollapse-- state.XFi { control.1 { comment.access 'read write' comment.type INTEGER comment.count 2 comment.range '0 - 43690 (step 128)' iface MIXER device 5 name 'Master Playback Volume' value.0 21845 value.1 21845 } control.2 { comment.access 'read write' comment.type INTEGER comment.count 2 comment.range '0 - 43690 (step 128)' iface MIXER device 5 name 'PCM Playback Volume' value.0 34461 value.1 34461 } control.3 { comment.access 'read write' comment.type INTEGER comment.count 2 comment.range '0 - 43690 (step 128)' iface MIXER device 5 name 'Line-in Playback Volume' value.0 32525 value.1 32525 } control.4 { comment.access 'read write' comment.type INTEGER comment.count 2 comment.range '0 - 43690 (step 128)' iface MIXER device 5 name 'Mic Playback Volume' value.0 0 value.1 0 } control.5 { comment.access 'read write' comment.type INTEGER comment.count 2 comment.range '0 - 43690 (step 128)' iface MIXER device 5 name 'S/PDIF-in Playback Volume' value.0 32525 value.1 32525 } control.6 { comment.access 'read write' comment.type INTEGER comment.count 2 comment.range '0 - 43690 (step 128)' iface MIXER device 5 name 'S/PDIF-out Playback Volume' value.0 32525 value.1 32525 } control.7 { comment.access 'read write' comment.type INTEGER comment.count 2 comment.range '0 - 43690 (step 128)' iface MIXER device 5 name 'Front Playback Volume' value.0 34913 value.1 34913 } control.8 { comment.access 'read write' comment.type INTEGER comment.count 2 comment.range '0 - 43690 (step 128)' iface MIXER device 5 name 'Rear Playback Volume' value.0 32525 value.1 32525 } control.9 { comment.access 'read write' comment.type INTEGER comment.count 2 comment.range '0 - 43690 (step 128)' iface MIXER device 5 name 'Center/LFE Playback Volume' value.0 32525 value.1 32525 } control.10 { comment.access 'read write' comment.type INTEGER comment.count 2 comment.range '0 - 43690 (step 128)' iface MIXER device 5 name 'Surround Playback Volume' value.0 32525 value.1 32525 } control.11 { comment.access 'read write' comment.type INTEGER comment.count 2 comment.range '0 - 43690 (step 128)' iface MIXER device 5 name 'Master Capture Volume' value.0 34913 value.1 34913 } control.12 { comment.access 'read write' comment.type INTEGER comment.count 2 comment.range '0 - 43690 (step 128)' iface MIXER device 5 name 'PCM Capture Volume' value.0 34913 value.1 34913 } control.13 { comment.access 'read write' comment.type INTEGER comment.count 2 comment.range '0 - 43690 (step 128)' iface MIXER device 5 name 'Line-in Capture Volume' value.0 32525 value.1 32525 } control.14 { comment.access 'read write' comment.type INTEGER comment.count 2 comment.range '0 - 43690 (step 128)' iface MIXER device 5 name 'Mic Capture Volume' value.0 0 value.1 0 } control.15 { comment.access 'read write' comment.type INTEGER comment.count 2 comment.range '0 - 43690 (step 128)' iface MIXER device 5 name 'S/PDIF-in Capture Volume' value.0 32525 value.1 32525 } control.16 { comment.access 'read write' comment.type BOOLEAN comment.count 1 iface MIXER device 5 name 'PCM Capture Switch' value true } control.17 { comment.access 'read write' comment.type BOOLEAN comment.count 1 iface MIXER device 5 name 'Line-in Capture Switch' value true } control.18 { comment.access 'read write' comment.type BOOLEAN comment.count 1 iface MIXER device 5 name 'Mic Capture Switch' value false } control.19 { comment.access 'read write' comment.type BOOLEAN comment.count 1 iface MIXER device 5 name 'S/PDIF-in Capture Switch' value true } control.20 { comment.access 'read write' comment.type BOOLEAN comment.count 1 iface MIXER device 5 name 'Line-in Playback Switch' value false } control.21 { comment.access 'read write' comment.type BOOLEAN comment.count 1 iface MIXER device 5 name 'S/PDIF-out Playback Switch' value false } control.22 { comment.access 'read write' comment.type BOOLEAN comment.count 1 iface MIXER device 5 name 'S/PDIF-in Playback Switch' value false } control.23 { comment.access 'read write' comment.type BOOLEAN comment.count 1 iface MIXER device 5 name 'Front Playback Switch' value true } control.24 { comment.access 'read write' comment.type BOOLEAN comment.count 1 iface MIXER device 5 name 'Rear Playback Switch' value false } control.25 { comment.access 'read write' comment.type BOOLEAN comment.count 1 iface MIXER device 5 name 'Center/LFE Playback Switch' value false } control.26 { comment.access 'read write' comment.type BOOLEAN comment.count 1 iface MIXER device 5 name 'Surround Playback Switch' value false } control.27 { comment.access read comment.type IEC958 comment.count 1 iface PCM device 4 name 'IEC958 Playback Mask' value ffffffff00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000 } control.28 { comment.access 'read write' comment.type IEC958 comment.count 1 iface PCM device 4 name 'IEC958 Playback Default' value '0082000200000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000' } control.29 { comment.access 'read write' comment.type IEC958 comment.count 1 iface PCM device 4 name 'IEC958 Playback PCM Stream' value '0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000' } } state.Cable { control { } } state.PCR { control { } } --endcollapse--
!!All Loaded Modules !!------------------
Module snd_ctxfi isofs udf crc_itu_t nfs lockd nfs_acl sunrpc binfmt_misc bridge stp bnep video output input_polldev nls_iso8859_1 nls_cp437 vfat fat lp snd_hda_codec_ca0110 snd_hda_codec_realtek snd_usb_audio snd_usb_lib snd_seq_dummy snd_seq_oss snd_hda_codec snd_pcm_oss snd_mixer_oss snd_seq_midi snd_rawmidi snd_seq_midi_event ppdev snd_seq snd_hwdep snd_pcm parport_pc i2c_piix4 pcspkr snd_timer snd_seq_device snd_page_alloc parport psmouse k8temp nvidia serio_raw snd soundcore ohci1394 ieee1394 r8169 mii fbcon tileblit font bitblit softcursor
At Mon, 18 May 2009 20:10:46 +1000, Michael (Micksa) Slade wrote:
Takashi Iwai wrote:
Could you run alsa-info.sh with --no-upload option, and attach the generated file? The script is found at http://www.alsa-project.org/alsa-info.sh
Attached.
Thanks. Fixed now.
Takashi
On Thu, 14 May 2009 12:52:17 +0200 Takashi Iwai tiwai@suse.de wrote:
Once after I get positive feedbacks (or fix after negative ones), I'm going to merge it to the main tree so that it'll be in the next kernel. So, a quick test report would be greatly appreciated.
As for me:
aplay works fine with 16bit samples (doesn't tested 24bit)
mplayer plays first open stream glitchy, but if i open one more mplayer, and then close the first - it plays fine but prints error: [AO_ALSA] alsa-lib: pcm_hw.c:1321:(snd_pcm_hw_open) open /dev/snd/pcmC0D0p failed: Invalid argument [AO_ALSA] alsa-lib: pcm_dmix.c:1058:(snd_pcm_dmix_open) unable to open slave [AO_ALSA] Playback open error: Invalid argument
Also ac3-passthrough works with this driver (finally!), but prints errors too: mplayer -ac hwac3 -ao alsa:device=hw=0.4 test.ac3 [AO_ALSA] alsa-lib: conf.c:3843:(parse_args) Unknown parameter AES0 [AO_ALSA] alsa-lib: conf.c:3969:(snd_config_expand) Parse arguments error: No such file or directory [AO_ALSA] alsa-lib: pcm.c:2196:(snd_pcm_open_noupdate) Unknown PCM hw:0,4,AES0=6
On Sun, 17 May 2009 00:52:51 +0400 Alexey Bazhin baz@irc.msk.ru wrote:
mplayer plays first open stream glitchy, but if i open one more mplayer, and then close the first - it plays fine but prints error: [AO_ALSA] alsa-lib: pcm_hw.c:1321:(snd_pcm_hw_open) open /dev/snd/pcmC0D0p failed: Invalid argument [AO_ALSA] alsa-lib: pcm_dmix.c:1058:(snd_pcm_dmix_open) unable to open slave [AO_ALSA] Playback open error: Invalid argument
disregard this part - buggy dmix configuration was left from previous experiments...
On Sun, 17 May 2009 00:52:51 +0400 Alexey Bazhin baz@irc.msk.ru wrote:
On Thu, 14 May 2009 12:52:17 +0200 Takashi Iwai tiwai@suse.de wrote:
Once after I get positive feedbacks (or fix after negative ones), I'm going to merge it to the main tree so that it'll be in the next kernel. So, a quick test report would be greatly appreciated.
As for me:
One more thing - using digital output (with maximum volume in mixer) resulting volume of sound is much higher than with my other cards, so some additional processing added so even playing sound sample with native card rate is not bit accurate. Is it how it's supposed to be?
participants (8)
-
Alexey Bazhin -
James Courtier-Dutton -
Michael (Micksa) Slade -
Michael (Micksa) Slade -
Patryk Kowalczyk -
Takashi Iwai -
William Pitcock -
wodor＠wodor.org