Thread: [Alsa-user] OPToplay, AudioTRAK
Brought to you by:
perex
From: Song K. <ki...@di...> - 2002-06-26 04:56:35
|
Hello, I have a USB audio interface 24bit 96khz. Since The kernel doen't support that, so I have finded solution, and I know ALSA is the best choice, cause I read alsa web page. My USB Audio Device is OPTOPlay of AutdioTrak(R). The kernel recognizes that, but /dev/dsp doesn't attatched. I downloaded alsa files, and I compiled them. But, What is the correct module which I should load. The information of settings is all concerned with ISA or PCI cards. In case of USB, What Can I do? |
From: Takashi I. <ti...@su...> - 2002-06-26 17:22:28
|
At Wed, 26 Jun 2002 13:47:29 +0900 (KST), Song KiSun wrote: > > Hello, I have a USB audio interface 24bit 96khz. > Since The kernel doen't support that, so I have finded solution, > and I know ALSA is the best choice, cause I read alsa web page. > > My USB Audio Device is OPTOPlay of AutdioTrak(R). > The kernel recognizes that, but /dev/dsp doesn't attatched. > > I downloaded alsa files, and I compiled them. > But, What is the correct module which I should load. the module is snd-usb-audio. please check if "audio" module is not loaded. it's an oss driver, and if you activate hotplug, it might be inserted even automatically. > The information of settings is all concerned with ISA or PCI cards. > > In case of USB, What Can I do? nothing special. i guess you didn't set up /etc/modules.conf for oss compatibilty modules. please check alsa-driver/INSTALL (the section modprobe/kmod support) for more details. alternatively, you can load "snd-pcm-oss" and "snd-mixer-oss" module manually. that's ok, too. btw, 24bit format on usb device is not supported by 0.9.0rc2. it was recently added on cvs. so, please consider to build from the cvs version, too. there is the instruction to download the cvs sources on the web page. to compile cvs version, you need to use cvscompile scrip on the alsa-driver tree. also, you'll need to update both alsa-driver and alsa-lib. Takashi |
From: Song K. <ki...@di...> - 2002-06-27 15:34:33
|
Thanks for your e-mail. First, I downloaed alsa 0.5.12 so I couldn't find usb module. I downloaded CVS version as you told, and I did compile and install. but /dev/dsp doesn't atttched. 'lsmod' says snd-usb-audio is unused. snd-pcm-oss 36836 0 (unused) snd-mixer-oss 8448 0 [snd-pcm-oss] snd-usb-audio 24000 0 (unused) snd-pcm 52544 0 [snd-pcm-oss snd-usb-audio] snd-timer 9728 0 [snd-pcm] snd-hwdep 3392 0 (unused) snd 24008 0 [snd-pcm-oss snd-mixer-oss snd-usb-audio snd-pcm snd-timer snd-hwdep] soundcore 3556 3 (autoclean) [snd] I'll wait your reply, thank you. On Wed, 26 Jun 2002, Takashi Iwai wrote: > At Wed, 26 Jun 2002 13:47:29 +0900 (KST), > Song KiSun wrote: > > > > Hello, I have a USB audio interface 24bit 96khz. > > Since The kernel doen't support that, so I have finded solution, > > and I know ALSA is the best choice, cause I read alsa web page. > > > > My USB Audio Device is OPTOPlay of AutdioTrak(R). > > The kernel recognizes that, but /dev/dsp doesn't attatched. > > > > I downloaded alsa files, and I compiled them. > > But, What is the correct module which I should load. > > the module is snd-usb-audio. > please check if "audio" module is not loaded. > it's an oss driver, and if you activate hotplug, it might be inserted > even automatically. > > > > The information of settings is all concerned with ISA or PCI cards. > > > > In case of USB, What Can I do? > > nothing special. > > i guess you didn't set up /etc/modules.conf for oss compatibilty > modules. > please check alsa-driver/INSTALL (the section modprobe/kmod support) > for more details. > alternatively, you can load "snd-pcm-oss" and "snd-mixer-oss" module > manually. that's ok, too. > > btw, 24bit format on usb device is not supported by 0.9.0rc2. > it was recently added on cvs. > so, please consider to build from the cvs version, too. > there is the instruction to download the cvs sources on the web page. > to compile cvs version, you need to use cvscompile scrip on the > alsa-driver tree. > also, you'll need to update both alsa-driver and alsa-lib. > > > Takashi > > > ------------------------------------------------------- > This sf.net email is sponsored by: Jabber Inc. > Don't miss the IM event of the season | Special offer for OSDN members! > JabberConf 2002, Aug. 20-22, Keystone, CO http://www.jabberconf.com/osdn > _______________________________________________ > Alsa-user mailing list > Als...@li... > https://lists.sourceforge.net/lists/listinfo/alsa-user > |
From: Takashi I. <ti...@su...> - 2002-06-27 15:42:56
|
At Fri, 28 Jun 2002 00:25:22 +0900 (KST), Song KiSun wrote: > > > > Thanks for your e-mail. > > First, I downloaed alsa 0.5.12 so I couldn't find usb module. > I downloaded CVS version as you told, and I did compile and install. then you have to install alsa-lib and alsa-utils together. > but /dev/dsp doesn't atttched. > > 'lsmod' says snd-usb-audio is unused. > > snd-pcm-oss 36836 0 (unused) > snd-mixer-oss 8448 0 [snd-pcm-oss] > snd-usb-audio 24000 0 (unused) > snd-pcm 52544 0 [snd-pcm-oss snd-usb-audio] > snd-timer 9728 0 [snd-pcm] > snd-hwdep 3392 0 (unused) > snd 24008 0 [snd-pcm-oss snd-mixer-oss snd-usb-audio > snd-pcm snd-timer snd-hwdep] > soundcore 3556 3 (autoclean) [snd] please make sure that you already set up usb modules properly before loading snd-usb-audio module. you'll see messages from kernel via dmesg program. also, if you have lsusb program, please run it to get the usb descriptor. if the usb audio driver _really_ doesn't work, this information will help for the further development. Takashi |
From: Song K. <ki...@di...> - 2002-06-27 15:53:17
Attachments:
lsusbinfo
|
I alredy compiled and installed lib and utils. and, I attatched lsusb result. There is no problem on device. I checked in Windows. On Thu, 27 Jun 2002, Takashi Iwai wrote: > At Fri, 28 Jun 2002 00:25:22 +0900 (KST), > Song KiSun wrote: > > > > > > > > Thanks for your e-mail. > > > > First, I downloaed alsa 0.5.12 so I couldn't find usb module. > > I downloaded CVS version as you told, and I did compile and install. > > then you have to install alsa-lib and alsa-utils together. > > > but /dev/dsp doesn't atttched. > > > > 'lsmod' says snd-usb-audio is unused. > > > > snd-pcm-oss 36836 0 (unused) > > snd-mixer-oss 8448 0 [snd-pcm-oss] > > snd-usb-audio 24000 0 (unused) > > snd-pcm 52544 0 [snd-pcm-oss snd-usb-audio] > > snd-timer 9728 0 [snd-pcm] > > snd-hwdep 3392 0 (unused) > > snd 24008 0 [snd-pcm-oss snd-mixer-oss snd-usb-audio > > snd-pcm snd-timer snd-hwdep] > > soundcore 3556 3 (autoclean) [snd] > > please make sure that you already set up usb modules properly before > loading snd-usb-audio module. > you'll see messages from kernel via dmesg program. > > also, if you have lsusb program, please run it to get the usb > descriptor. if the usb audio driver _really_ doesn't work, this > information will help for the further development. > > > Takashi > |
From: Takashi I. <ti...@su...> - 2002-06-27 15:59:05
|
At Fri, 28 Jun 2002 00:44:18 +0900 (KST), Song KiSun wrote: > > I alredy compiled and installed lib and utils. > > and, I attatched lsusb result. > > There is no problem on device. I checked in Windows. ok, the device can be seen from linux, too. (but according to the output of lsusb, apparently this device supports only 24bit format with 44.1/48kHz.) did you check the kernel messages? Takashi |
From: Song K. <ki...@di...> - 2002-06-27 16:39:20
|
You replied so quickly, thanks very much. here is the dmesg. .... hub.c: USB new device connect on bus2/2, assigned device number 2 usb.c: USB device 2 (vend/prod 0xa92/0x51) is not claimed by any active driver ... ... and I load moudule manualy. kernel says. usb.c: registered new driver snd-usb-audio I marked comment about sound module in rc.sysinit and modules.conf and I moved module another pci sound card. On Thu, 27 Jun 2002, Takashi Iwai wrote: > At Fri, 28 Jun 2002 00:44:18 +0900 (KST), > Song KiSun wrote: > > > > I alredy compiled and installed lib and utils. > > > > and, I attatched lsusb result. > > > > There is no problem on device. I checked in Windows. > > ok, the device can be seen from linux, too. > (but according to the output of lsusb, apparently this device supports > only 24bit format with 44.1/48kHz.) > > did you check the kernel messages? > > > Takashi > |
From: Takashi I. <ti...@su...> - 2002-06-28 10:39:21
|
At Fri, 28 Jun 2002 00:57:59 +0900 (KST), Song KiSun wrote: > > > You replied so quickly, thanks very much. > > here is the dmesg. > > .... > hub.c: USB new device connect on bus2/2, assigned device number 2 > usb.c: USB device 2 (vend/prod 0xa92/0x51) is not claimed by any active > driver > > ... > ... > > and I load moudule manualy. > > kernel says. > > usb.c: registered new driver snd-usb-audio and nothing else? one thing i forgot to mention. you'd better to compile the alsa drivers with debug option, i.e. configure --with-debug=detect then the driver will show verbose detection messages. once when it works, then rebuild the driver without this option, so that you don't receive annoying messages. i see that the device support _only_ 24bit format. so, only the cvs version can work on your device. rc2 won't work. Takashi |
From: Song K. <ki...@di...> - 2002-06-28 16:39:25
|
Thanks for your reply, As you did mention, I recompile with debug option. Then I removed esssolo1 module(anther pci sound card), and I moved that module file( esssolo1.o) to some directory to prevent automatic loading. Then, I alsa module manualy. sndcore(oss) -> snd -> snd-timer -> snd-pcm -> snd-usb-audio #lsmod Module Size Used by Not tainted snd-usb-audio 26496 0 (unused) snd-pcm 62400 0 [snd-usb-audio] snd-timer 11680 0 [snd-pcm] snd 31688 0 [snd-usb-audio snd-pcm snd-timer] soundcore 3556 0 [snd] here is the part of dmesg. solo1: unloading hub.c: USB new device connect on bus2/1, assigned device number 2 usb.c: USB device 2 (vend/prod 0xa92/0x51) is not claimed by any active driver. usb.c: registered new driver snd-usb-audio ALSA usbaudio.c:1882: adding an output interface 2:0:1 ALSA usbmixer.c:687: [2] FU [PCM Playback Switch] ch = 2, val = 0/1 ALSA usbmixer.c:687: [2] FU [PCM Playback Volume] ch = 2, val = 0/63 But /dev/dsp doesn't work yet. # cat /dev/dsp <enter> cat: /dev/dsp : No such device. What is the next job I have to do? On Fri, 28 Jun 2002, Takashi Iwai wrote: > At Fri, 28 Jun 2002 00:57:59 +0900 (KST), > Song KiSun wrote: > > > > > > You replied so quickly, thanks very much. > > > > here is the dmesg. > > > > .... > > hub.c: USB new device connect on bus2/2, assigned device number 2 > > usb.c: USB device 2 (vend/prod 0xa92/0x51) is not claimed by any active > > driver > > > > ... > > ... > > > > and I load moudule manualy. > > > > kernel says. > > > > usb.c: registered new driver snd-usb-audio > > and nothing else? > > one thing i forgot to mention. you'd better to compile the alsa > drivers with debug option, i.e. configure --with-debug=detect > then the driver will show verbose detection messages. > once when it works, then rebuild the driver without this option, so > that you don't receive annoying messages. > > i see that the device support _only_ 24bit format. > so, only the cvs version can work on your device. rc2 won't work. > > > Takashi > |
From: Takashi I. <ti...@su...> - 2002-06-28 16:39:20
|
At Sat, 29 Jun 2002 01:16:08 +0900 (KST), Song KiSun wrote: > > > Thanks for your reply, > > As you did mention, I recompile with debug option. > Then I removed esssolo1 module(anther pci sound card), > and I moved that module file( esssolo1.o) to some directory to > prevent automatic loading. > > Then, I alsa module manualy. > sndcore(oss) -> snd -> snd-timer -> snd-pcm -> snd-usb-audio you don't have to do such a way. just load via modprobe like: # modprobe snd-usb-audio then modprobe will load the dependent modules automatically. > #lsmod > Module Size Used by Not tainted > snd-usb-audio 26496 0 (unused) > snd-pcm 62400 0 [snd-usb-audio] > snd-timer 11680 0 [snd-pcm] > snd 31688 0 [snd-usb-audio snd-pcm snd-timer] > soundcore 3556 0 [snd] > > here is the part of dmesg. > > solo1: unloading > hub.c: USB new device connect on bus2/1, assigned device number 2 > usb.c: USB device 2 (vend/prod 0xa92/0x51) is not claimed by any active > driver. > usb.c: registered new driver snd-usb-audio > ALSA usbaudio.c:1882: adding an output interface 2:0:1 > ALSA usbmixer.c:687: [2] FU [PCM Playback Switch] ch = 2, val = 0/1 > ALSA usbmixer.c:687: [2] FU [PCM Playback Volume] ch = 2, val = 0/63 ok, then the device should be now configured. please check /proc/asound/cards and /proc/asound/card0/stream0. > > But /dev/dsp doesn't work yet. you need to load snd-pcm-oss and snd-mixer-oss modules. /dev/dsp is an oss device, so we need the oss emulation layer. Takashi |
From: Song K. <ki...@di...> - 2002-06-28 16:45:34
|
I insterted snd-pcm-oss, snd-mixer-oss, you mentioned. but /dev/dsp doesn't work. here is /proc/asound/card 0 [card0 ]: USB-Audio - USB Audio Driver EGO SYStems Inc. AUDIOTRAK OptoPlay /proc/asound/card0/stream0 EGO SYStems Inc. AUDIOTRAK OptoPlay : USB Audio Playback: Status: Stop Altset 1 Format: S24_3LE Channels: 2 Endpoint: 1 OUT (ADAPTIVE) Rates: 44100, 48000 ---- Hmmm... Do I bother you? ^^ On Fri, 28 Jun 2002, Takashi Iwai wrote: > At Sat, 29 Jun 2002 01:16:08 +0900 (KST), > Song KiSun wrote: > > > > > > Thanks for your reply, > > > > As you did mention, I recompile with debug option. > > Then I removed esssolo1 module(anther pci sound card), > > and I moved that module file( esssolo1.o) to some directory to > > prevent automatic loading. > > > > Then, I alsa module manualy. > > sndcore(oss) -> snd -> snd-timer -> snd-pcm -> snd-usb-audio > > you don't have to do such a way. > just load via modprobe like: > > # modprobe snd-usb-audio > > then modprobe will load the dependent modules automatically. > > > > #lsmod > > Module Size Used by Not tainted > > snd-usb-audio 26496 0 (unused) > > snd-pcm 62400 0 [snd-usb-audio] > > snd-timer 11680 0 [snd-pcm] > > snd 31688 0 [snd-usb-audio snd-pcm snd-timer] > > soundcore 3556 0 [snd] > > > > here is the part of dmesg. > > > > solo1: unloading > > hub.c: USB new device connect on bus2/1, assigned device number 2 > > usb.c: USB device 2 (vend/prod 0xa92/0x51) is not claimed by any active > > driver. > > usb.c: registered new driver snd-usb-audio > > ALSA usbaudio.c:1882: adding an output interface 2:0:1 > > ALSA usbmixer.c:687: [2] FU [PCM Playback Switch] ch = 2, val = 0/1 > > ALSA usbmixer.c:687: [2] FU [PCM Playback Volume] ch = 2, val = 0/63 > > ok, then the device should be now configured. > please check /proc/asound/cards and /proc/asound/card0/stream0. > > > > > > But /dev/dsp doesn't work yet. > > you need to load snd-pcm-oss and snd-mixer-oss modules. > /dev/dsp is an oss device, so we need the oss emulation layer. > > > Takashi > |
From: Takashi I. <ti...@su...> - 2002-06-28 16:52:12
|
At Sat, 29 Jun 2002 01:36:30 +0900 (KST), Song KiSun wrote: > > > I insterted snd-pcm-oss, snd-mixer-oss, you mentioned. > > but /dev/dsp doesn't work. > > here is /proc/asound/card > 0 [card0 ]: USB-Audio - USB Audio Driver > EGO SYStems Inc. AUDIOTRAK OptoPlay > > /proc/asound/card0/stream0 > EGO SYStems Inc. AUDIOTRAK OptoPlay : USB Audio > > Playback: > Status: Stop > Altset 1 > Format: S24_3LE > Channels: 2 > Endpoint: 1 OUT (ADAPTIVE) > Rates: 44100, 48000 oh, sorry, i forgot an important thing: the 24bit-3byte mode doesn't work on kernel oss emulation layer. it's so far supported only by alsa native apps. please try normal alsa applications, not oss applications. or, alternatively you can use user-land oss emulation via aoss wrapper. at first, install alsa-oss. there will be an aoss wrapper script installed. then you can run your favorite oss program like % aoss my-program arguments... there is a man page for aoss, too. however, please remember that it's still a little bit buggy. i never thought that there is a device supporting only 24bit-3byte mode... it's possible to add support if there are requests, but it will take some time. Takashi |
From: Song K. <ki...@di...> - 2002-06-28 17:39:25
|
My desktop environment is KDE, and almost my musio programs use aRts Server( KDE Sound Server like eSound - GNome) so, aoss can't be good solution, though I installed that. xmms, mplayer can't work on that, including mpg123. I'll wait perfect driver, I'll hope you. thanks for your kindness. I'm learning linux kernel and device driver. Someday, I can make that for my self. I will. :) On Fri, 28 Jun 2002, Takashi Iwai wrote: > At Sat, 29 Jun 2002 01:36:30 +0900 (KST), > Song KiSun wrote: > > > > > > I insterted snd-pcm-oss, snd-mixer-oss, you mentioned. > > > > but /dev/dsp doesn't work. > > > > here is /proc/asound/card > > 0 [card0 ]: USB-Audio - USB Audio Driver > > EGO SYStems Inc. AUDIOTRAK OptoPlay > > > > /proc/asound/card0/stream0 > > EGO SYStems Inc. AUDIOTRAK OptoPlay : USB Audio > > > > Playback: > > Status: Stop > > Altset 1 > > Format: S24_3LE > > Channels: 2 > > Endpoint: 1 OUT (ADAPTIVE) > > Rates: 44100, 48000 > > > oh, sorry, i forgot an important thing: > > the 24bit-3byte mode doesn't work on kernel oss emulation layer. > it's so far supported only by alsa native apps. > please try normal alsa applications, not oss applications. > > or, alternatively you can use user-land oss emulation via aoss > wrapper. > at first, install alsa-oss. there will be an aoss wrapper script > installed. then you can run your favorite oss program like > > % aoss my-program arguments... > > there is a man page for aoss, too. > however, please remember that it's still a little bit buggy. > > i never thought that there is a device supporting only 24bit-3byte > mode... it's possible to add support if there are requests, but it > will take some time. > > > Takashi > |
From: Takashi I. <ti...@su...> - 2002-06-28 17:39:30
|
At Sat, 29 Jun 2002 02:17:50 +0900 (KST), Song KiSun wrote: > > > My desktop environment is KDE, and almost my musio programs > use aRts Server( KDE Sound Server like eSound - GNome) the recent arts (at least on kde3) supports also alsa 0.9.0. iirc, you can configure it via kde control center. you need to use the pcm name "plughw:0,0" (or "default"), not "hw:0,0". the former two invoke the conversion plugin inside the alsa-lib, so that applications can use any formats/rates but it's converted to the hardware native one automatically. since arts cannot handle 24bit formats, you have to specify the former pcm name. the latter (hw:0,0) means that you access directly the hardware without any conversion. > so, aoss can't be good solution, though I installed that. > xmms, mplayer can't work on that, including mpg123. xmms has an alsa output plugin but not as default. please search on web. mplayer supports alsa 0.9 as default. there must be an option for that. in addition, as mentioned above, you'll need to specify a certain pcm device name via an option or a config file. mpg123 supports unfortuantely only oss. instead of mpg123, there is mpg321. mpg321 requires libao and libmad. since libao supports alsa 0.9, you can run mpg321 natively on alsa. anyway, at first, try aplay whether the driver works. make sure that arts is not running. it's best to disable it on kde control center before tests. HTH. ciao, Takashi |
From: Song K. <ki...@di...> - 2002-06-28 18:41:03
|
On Fri, 28 Jun 2002, Takashi Iwai wrote: > the recent arts (at least on kde3) supports also alsa 0.9.0. > iirc, you can configure it via kde control center. My KDE version is 3.0, but I can't find alsa option in menu, sound server. There are OSS, non..., Threaded OSS. > > you need to use the pcm name "plughw:0,0" (or "default"), > not "hw:0,0". the former two invoke the conversion plugin inside the > alsa-lib, so that applications can use any formats/rates but it's > converted to the hardware native one automatically. > since arts cannot handle 24bit formats, you have to specify the former > pcm name. the latter (hw:0,0) means that you access directly the > hardware without any conversion. Sorry, What does mean these? Where can I put "plughw:0,0". > > > so, aoss can't be good solution, though I installed that. > > xmms, mplayer can't work on that, including mpg123. > > xmms has an alsa output plugin but not as default. please search on > web. > mplayer supports alsa 0.9 as default. there must be an option for > that. in addition, as mentioned above, you'll need to specify a > certain pcm device name via an option or a config file. > > mpg123 supports unfortuantely only oss. instead of mpg123, there is > mpg321. mpg321 requires libao and libmad. since libao supports alsa > 0.9, you can run mpg321 natively on alsa. > > anyway, at first, try aplay whether the driver works. > make sure that arts is not running. it's best to disable it on kde > control center before tests. I read man page, and I know mpg321 support alsa 0.9 I tried, # mpg321 -o alsa09 <mp3 file> but doesn't work. Did I wrong? > > > HTH. > > ciao, > > Takashi > > > ------------------------------------------------------- > This sf.net email is sponsored by:ThinkGeek > Caffeinated soap. No kidding. > http://thinkgeek.com/sf > _______________________________________________ > Alsa-user mailing list > Als...@li... > https://lists.sourceforge.net/lists/listinfo/alsa-user > |
From: Song K. <ki...@di...> - 2002-06-28 18:42:51
|
And, Sound Server ( arts), When I restart Dialog was pop uped, show message like that. SNDCTL_DSP_SETFMT failed - Invalid argument On Sat, 29 Jun 2002, Song KiSun wrote: > On Fri, 28 Jun 2002, Takashi Iwai wrote: > > > the recent arts (at least on kde3) supports also alsa 0.9.0. > > iirc, you can configure it via kde control center. > > My KDE version is 3.0, but I can't find alsa option in menu, > sound server. There are OSS, non..., Threaded OSS. > > > > > > > you need to use the pcm name "plughw:0,0" (or "default"), > > not "hw:0,0". the former two invoke the conversion plugin inside the > > alsa-lib, so that applications can use any formats/rates but it's > > converted to the hardware native one automatically. > > since arts cannot handle 24bit formats, you have to specify the former > > pcm name. the latter (hw:0,0) means that you access directly the > > hardware without any conversion. > > Sorry, What does mean these? Where can I put "plughw:0,0". > > > > > > > so, aoss can't be good solution, though I installed that. > > > xmms, mplayer can't work on that, including mpg123. > > > > xmms has an alsa output plugin but not as default. please search on > > web. > > mplayer supports alsa 0.9 as default. there must be an option for > > that. in addition, as mentioned above, you'll need to specify a > > certain pcm device name via an option or a config file. > > > > mpg123 supports unfortuantely only oss. instead of mpg123, there is > > mpg321. mpg321 requires libao and libmad. since libao supports alsa > > 0.9, you can run mpg321 natively on alsa. > > > > anyway, at first, try aplay whether the driver works. > > make sure that arts is not running. it's best to disable it on kde > > control center before tests. > > I read man page, and I know mpg321 support alsa 0.9 > > I tried, > # mpg321 -o alsa09 <mp3 file> > > but doesn't work. > > Did I wrong? > > > > > > > > HTH. > > > > ciao, > > > > Takashi > > > > > > ------------------------------------------------------- > > This sf.net email is sponsored by:ThinkGeek > > Caffeinated soap. No kidding. > > http://thinkgeek.com/sf > > _______________________________________________ > > Alsa-user mailing list > > Als...@li... > > https://lists.sourceforge.net/lists/listinfo/alsa-user > > > > |