11 Dec
2003
11 Dec
'03
2:43 p.m.
Hi,
I posted on this list a while ago, but still couldn't resolve one of my
problems. I have a Dela 1010LT card, which works nice with the envy24
ALSA driver. What I want to achieve is to record from this soundcard
through the OSS interface. I've been experimenting with /etc/asound.conf
and the aoss utility, but to no avail.
Basically what I want to achieve is to have a two channel /dev/dsp
device, which corresponds to adc 3&4 on the Delta card. in
/etc/asound.conf I have:
# adcdac 3&4
pcm.channel2 {
type plug
ttable.0.2 1
ttable.0.3 1
slave.pcm ice1712
}
which works nice when I use arecord -D channel2 ...
now, what I want to work is something following:
aoss sox -t ossdsp -r 44100 -c 2 -w /dev/dsp0 -t wav tmp.wav
but no matter how I try to generate a pcm.dsp0 section in
/etc/asound.conf, what I record is total silence :(
as far as I understand, I need a pcm.dsp0 section, which would describe
the /dev/dsp0 features. what I tried, among others is:
pcm.dsp0 {
type plug
slave.pcm "channel2"
}
but this doesn't work. (it may be a problem that there is actually an
OSS-driven /dev/dsp0 in the system. but setting pcm.dsp1 didn't work, it
gave me non-existent device errors) can someone give me hints on setting
up a proper pcm.dsp0 section?
11 Dec
11 Dec
3:31 p.m.
Hi!
Which alsa do you use?
What do you want to do? - If it is automated or just textbased recording and
effect processing, then it might be quicker to use ecasound. If you are
interested in this possibility, mail me directly and I'll tell you a bit about
it and I may give you some basic ways to use it for your purpose.
Otherwise: Did you compile the oss-emulation for alsa? You said there might
be an oss-driver loaded? Do you have more cards? Can't those cards be used via
alsa?
Generally I think, that the asound.conf isn't the right place to create a
/dev/dsp-device. This is a real device, as I understand it. It can be accessed
like a real (or close to real) oss device. What you've been doing sounds like
just creating alsaplugins. Those are - as I understand it - completely
different. They are just for alsa-programs and are based on different
mechanism.
Kindest regards
Julien
Julien Patrick Claassen
jclaassen(a)gmx.de
julien(a)c-lab.de
http://www.geocities.com/jjs_home
SBS C-LAB
Fuerstenallee 11
33102 Paderborn
Phone: (+49) 5251 60 6060
Fax: (+49) 5251 60 6065
www.c-lab.de
12 Dec
12 Dec
5:41 a.m.
Julien Claassen wrote:
Hi!
Which alsa do you use?
1.0.0rc2
What do you want to do? - If it is automated or just
textbased recording and
what I wrote: have the possibility to record from an ALSA device by
using a program that only know about the OSS interface.
Otherwise: Did you compile the oss-emulation for
alsa? You said there might
yes, I did
be an oss-driver loaded? Do you have more cards?
Can't those cards be used via
alsa?
might be, but currently they are not.
Generally I think, that the asound.conf isn't
the right place to create a
/dev/dsp-device. This is a real device, as I understand it. It can be accessed
like a real (or close to real) oss device. What you've been doing sounds like
just creating alsaplugins. Those are - as I understand it - completely
different. They are just for alsa-programs and are based on different
mechanism.
yes, but this is what I found regarding using aoss and the alsa-oss
package...
6:11 a.m.
Hallo,
Julien Claassen hat gesagt: // Julien Claassen wrote:
Generally I think, that the asound.conf isn't
the right place to create a
/dev/dsp-device. This is a real device, as I understand it. It can be accessed
like a real (or close to real) oss device. What you've been doing sounds like
just creating alsaplugins. Those are - as I understand it - completely
different. They are just for alsa-programs and are based on different
mechanism.
Well, Akos is trying to use the aoss library, which is designed to do
exactly that: map OSS devices to ALSA devices, that are normally out
of reach of OSS applications, which among others are those defined in
asoundrc-configuration files.
I don't think, it is possible to use channel 3+4 of a Delta card
directly through ALSA's OSS emulation, so aoss might be the only way
indeed. But I never used aoss for anything besides playback, so I have
no idea if it should work, sorry.
ciao
--
Frank Barknecht _ ______footils.org__
9:55 a.m.
On Fri, 12 Dec 2003, Frank Barknecht wrote:
Hallo,
Julien Claassen hat gesagt: // Julien Claassen wrote:
It isn't, or at least I was never able to get it to work. I built Audacity
with native ALSA support which was a much better solution anyway, but not
what you're looking for. The OSS emulation layer gives 2 channels, I
think.
// John Bleichert
// syborg(a)earthlink.net
Generally I think, that the asound.conf
isn't the right place to create a
/dev/dsp-device. This is a real device, as I understand it. It can be accessed
like a real (or close to real) oss device. What you've been doing sounds like
just creating alsaplugins. Those are - as I understand it - completely
different. They are just for alsa-programs and are based on different
mechanism.
Well, Akos is trying to use the aoss library, which is designed to do
exactly that: map OSS devices to ALSA devices, that are normally out
of reach of OSS applications, which among others are those defined in
asoundrc-configuration files.
I don't think, it is possible to use channel 3+4 of a Delta card
directly through ALSA's OSS emulation, so aoss might be the only way
indeed. But I never used aoss for anything besides playback, so I have
no idea if it should work, sorry.
10:21 a.m.
John Bleichert wrote:
It isn't, or at least I was never able to get it
to work. I built Audacity
with native ALSA support which was a much better solution anyway, but not
what you're looking for. The OSS emulation layer gives 2 channels, I
think.
thanks for clearing up this limitation...
1:03 p.m.
On Fri, 12 Dec 2003, Akos Maroy wrote:
Subject: Re: [linux-audio-user] ALSA -> OSS DSP
question
John Bleichert wrote:
Actually, I think OSS itself only provides 2 channels, and the alss-oss
emulation layer passes this limitation on...
// John Bleichert
// syborg(a)earthlink.net
It isn't, or at least I was never able to get
it to work. I built Audacity
with native ALSA support which was a much better solution anyway, but not
what you're looking for. The OSS emulation layer gives 2 channels, I
think.
thanks for clearing up this limitation...
10:23 a.m.
The OSS emulation layer gives 2 channels, I
think.
Actually, using Audacity/OSS with OSS emulation over ALSA we've
recorded with 8 inputs and 2 outputs using a Delta 1010. (Audacity
doesn't support more than 2 outputs in version 1.1.3, but it does
support up to 16 inputs in theory.)
Cheers
Daniel
10:50 a.m.
Daniel James wrote:
Actually, using Audacity/OSS with OSS emulation over
ALSA we've
recorded with 8 inputs and 2 outputs using a Delta 1010. (Audacity
doesn't support more than 2 outputs in version 1.1.3, but it does
support up to 16 inputs in theory.)
and how did you manage to set it up?
11:25 a.m.
Actually,
using Audacity/OSS with OSS emulation over ALSA we've
recorded with 8 inputs and 2 outputs using a Delta 1010.
(Audacity doesn't support more than 2 outputs in version 1.1.3,
but it does support up to 16 inputs in theory.)
and how did you manage to set it up? 
6:17 a.m.
Hi,
are the snd-*-oss modules configured and loaded correctly?
Do you load oss and alsa modules in parallel? (Is that possible??)
What does /sbin/lsmod say?
Please post your /etc/modules.conf.
You shouldn't have to edit asound.conf to achieve what you want.
You can pass the snd-pcm-oss module parameters which determine how to
map alsa pcm to oss devices.
Jan
Am Don, den 11.12.2003 schrieb Akos Maroy um 19:41:
Hi,
I posted on this list a while ago, but still couldn't resolve one of my
problems. I have a Dela 1010LT card, which works nice with the envy24
ALSA driver. What I want to achieve is to record from this soundcard
through the OSS interface. I've been experimenting with /etc/asound.conf
and the aoss utility, but to no avail.
6:40 a.m.
Jan Weil wrote:
are the snd-*-oss modules configured and loaded
correctly?
yes
Do you load oss and alsa modules in parallel? (Is that
possible??)
yes
What does /sbin/lsmod say?
# /sbin/lsmod
Module Size Used by Tainted: P
snd-pcm-oss 43876 0 (unused)
snd-mixer-oss 15952 0 [snd-pcm-oss]
snd-ice1712 50124 1
snd-pcm 85056 0 [snd-pcm-oss snd-ice1712]
snd-page-alloc 9748 0 [snd-pcm]
snd-timer 19812 0 [snd-pcm]
snd-ac97-codec 58412 0 [snd-ice1712]
snd-mpu401-uart 5136 0 [snd-ice1712]
snd-rawmidi 18656 0 [snd-mpu401-uart]
snd-seq-device 6236 0 [snd-rawmidi]
snd-ice17xx-ak4xxx 2588 0 [snd-ice1712]
snd-ak4xxx-adda 5460 0 [snd-ice1712 snd-ice17xx-ak4xxx]
snd-cs8427 9032 0 [snd-ice1712]
snd-i2c 4644 0 [snd-ice1712 snd-cs8427]
snd 46564 1 [snd-pcm-oss snd-mixer-oss snd-ice1712
snd-pcm snd-timer snd-ac97-codec snd-mpu401-uart snd-rawmidi
snd-seq-device snd-ak4xxx-adda snd-cs8427 snd-i2c]
tuner 12384 1 (autoclean)
tvaudio 15580 1 (autoclean)
bttv 81856 0 (autoclean)
i2c-algo-bit 8776 1 (autoclean) [bttv]
i2c-core 19108 0 (autoclean) [tuner tvaudio bttv
i2c-algo-bit]
videodev 8288 3 (autoclean) [bttv]
agpgart 47968 3 (autoclean)
nvidia 1676800 10 (autoclean)
via82cxxx_audio 24248 2 (autoclean)
uart401 8356 0 (autoclean) [via82cxxx_audio]
ac97_codec 14536 0 (autoclean) [via82cxxx_audio]
sound 73492 0 (autoclean) [via82cxxx_audio uart401]
soundcore 6468 6 (autoclean) [snd bttv via82cxxx_audio
sound]
parport_pc 18788 1 (autoclean)
lp 8804 0 (autoclean)
parport 36800 1 (autoclean) [parport_pc lp]
autofs 13108 0 (autoclean) (unused)
ppp_synctty 7776 0 (unused)
ppp_async 9312 1
ppp_generic 24188 3 [ppp_synctty ppp_async]
slhc 6660 0 [ppp_generic]
8139too 18120 1
mii 3976 0 [8139too]
ipt_REJECT 3992 6 (autoclean)
iptable_filter 2412 1 (autoclean)
ip_tables 14648 2 [ipt_REJECT iptable_filter]
sg 35852 0 (autoclean)
sr_mod 17720 0 (autoclean)
ide-scsi 11984 0
scsi_mod 106520 3 [sg sr_mod ide-scsi]
ide-cd 35424 0
cdrom 33216 0 [sr_mod ide-cd]
ohci1394 19880 0 (unused)
ieee1394 48780 0 [ohci1394]
nls_iso8859-1 3548 2 (autoclean)
nls_cp437 5180 2 (autoclean)
vfat 12780 2 (autoclean)
fat 38488 0 (autoclean) [vfat]
keybdev 2912 0 (unused)
mousedev 5428 1
hid 21892 0 (unused)
input 5792 0 [keybdev mousedev hid]
usb-uhci 25996 0 (unused)
usbcore 78272 1 [hid usb-uhci]
ext3 69984 2
jbd 51508 2 [ext3]
Please post your /etc/modules.conf.
# cat /etc/modules.conf
alias eth0 8139too
alias char-major-81 bttv
alias usb-controller usb-uhci
alias ieee1394-controller ohci1394
alias char-major-195 nvidia
alias sound-slot-0 via82cxxx_audio
post-install sound-slot-0 /bin/aumix-minimal -f /etc/.aumixrc -L
/dev/null 2>&1 || :
pre-remove
sound-slot-0 /bin/aumix-minimal -f /etc/.aumixrc -S
/dev/null 2>&1 || :
# ALSA portion
alias char-major-116 snd
alias snd-card-0 snd-ice1712
# module options should go here
# OSS/Free portion
alias char-major-14 soundcore
alias sound-slot-1 snd-card-0
# card #1
alias sound-service-1-0 snd-mixer-oss
alias sound-service-1-1 snd-seq-oss
alias sound-service-1-3 snd-pcm-oss
alias sound-service-1-8 snd-seq-oss
alias sound-service-1-12 snd-pcm-oss
You shouldn't have to edit asound.conf to achieve
what you want.
well, this is what I read earlier, that I'd have to define an ALSA
device named dsp0 or dsp1
You can pass the snd-pcm-oss module parameters which
determine how to
map alsa pcm to oss devices.
and what are those parameters?
8:56 a.m.
Akos Maroy wrote:
[...]
device
named
/sbin/modinfo snd-pcm-oss
filename: /lib/modules/2.4.20-8/kernel/sound/acore/oss/snd-pcm-oss.o
description: "PCM OSS emulation for ALSA."
author: "Jaroslav Kysela <perex(a)suse.cz>cz>, Abramo Bagnara
<abramo(a)alsa-project.org>"
license: "GPL"
parm: dsp_map int array (min = 1, max = 8), description "PCM device number
assigned to 1st OSS device."
parm: adsp_map int array (min = 1, max = 8), description "PCM device number
assigned to 2nd OSS device."
parm: nonblock_open int, description "Don't block opening busy PCM
devices."
Good luck,
Jan
# cat /etc/modules.conf
alias eth0 8139too
alias char-major-81 bttv
alias usb-controller usb-uhci
alias ieee1394-controller ohci1394
alias char-major-195 nvidia
alias sound-slot-0 via82cxxx_audio
post-install sound-slot-0 /bin/aumix-minimal -f /etc/.aumixrc -L
Hmmm, I have no experience with an OSS/ALSA mixed system.
At first glance I would say your modules.conf looks correct.
What does 'cat /proc/asound/oss/sndstat' say?
/dev/null 2>&1 || :
pre-remove
sound-slot-0 /bin/aumix-minimal -f /etc/.aumixrc -S
/dev/null 2>&1 || :
# ALSA portion
alias char-major-116 snd
alias snd-card-0 snd-ice1712
# module options should go here
# OSS/Free portion
alias char-major-14 soundcore
alias sound-slot-1 snd-card-0
# card #1
alias sound-service-1-0 snd-mixer-oss
alias sound-service-1-1 snd-seq-oss
alias sound-service-1-3 snd-pcm-oss
alias sound-service-1-8 snd-seq-oss
alias sound-service-1-12 snd-pcm-oss
You
shouldn't have to edit asound.conf to achieve what you want.
well, this is what I read earlier, that I'd have to define an ALSA dsp0 or dsp1
Generally, there are two ways to achieve OSS compatibility.
1) You can load snd-*-oss kernel modules which will generate /dev/dsp* and friends.
This is what you obviously did.
2) You can make an app believe that there is a /dev/dspX by preloading the aoss
library. This is what you did in addition to 1).
So currently you have a native OSS device, some emulated devices and you try to use
aoss.
Are you sure you need both of the latters?
Have you any reason for using aoss in favour of the kernel level emulation?
Assuming your snd-*-oss modules are setup correctly you should be able to access
your alsa card through /dev/dsp1, leading to
sox -t ossdsp -r 44100 -c 2 -w /dev/dsp1 -t wav tmp.wav
If /dev/dsp1 is mapped to the wrong channels of your card use the module parameters
listed below to adjust the mapping.
For further information see the OSS-Emulation.txt file contained in the alsa-driver
documentation.
> You can pass the snd-pcm-oss module parameters
which determine how to
map alsa
pcm to oss
devices.
and what are those parameters?
9:24 a.m.
Jan Weil wrote:
Generally, there are two ways to achieve OSS
compatibility.
1) You can load snd-*-oss kernel modules which will generate /dev/dsp* and friends.
This is what you obviously did.
2) You can make an app believe that there is a /dev/dspX by preloading the aoss
library. This is what you did in addition to 1).
So currently you have a native OSS device, some emulated devices and you try to use
aoss.
Are you sure you need both of the latters?
no, I'm not sure :)
Have you any reason for using aoss in favour of the
kernel level emulation?
no, I don't, I just don't know enough about the ALSA OSS emulation...
Assuming your snd-*-oss modules are setup correctly
you should be able to access
your alsa card through /dev/dsp1, leading to
sox -t ossdsp -r 44100 -c 2 -w /dev/dsp1 -t wav tmp.wav
well, I tried, and it doesn't work:
$ sox -t ossdsp -r 44100 -c 2 -w /dev/dsp1 -t wav tmp.wav
sox: Can't open input file '/dev/dsp1': No such device
even though:
$ ls -l /dev/dsp1
crw------- 1 darkeye root 14, 19 Dec 11 17:25 /dev/dsp1
For further information see the OSS-Emulation.txt file
contained in the alsa-driver
documentation.
thanks, I will consult that...
Akos
9:09 a.m.
On Fri, Dec 12, 2003 at 11:38:36AM +0100, Akos Maroy wrote:
http://www.alsa-project.org/~iwai/OSS-Emulation.html
(2 minutes of googling, which you could have done by yourself)
You can pass
the snd-pcm-oss module parameters which determine how to
map alsa pcm to oss devices.
and what are those parameters? 
2:32 p.m.
--- Claudio Mettler <linux-audio-user(a)singularity.ch>
wrote: > On Fri, Dec 12, 2003 at 11:38:36AM +0100,
Akos Maroy
wrote:
http://www.alsa-project.org/~iwai/OSS-Emulation.html
(2 minutes of googling, which you could have done by
yourself)
right, and did anyone actually read this? on the above
page you will read:
"Unsupported Features
MMAP on ICE1712 driver
ICE1712 supports only the unconventional format,
interleaved 10-channels 24bit (packed in 32bit)
format. Therefore you cannot mmap the buffer as the
conventional (mono or 2-channels, 8 or 16bit) format
on OSS."
also, Akos posted the following information:
"Basically what I want to achieve is to have a two
channel /dev/dsp device, which corresponds to adc 3&4
on the Delta card."
and he uses driver:
snd-ice1712
my CONCLUSION => it *will not* work for this card!?
greets, ALEX
________________________________________________________________________
Want to chat instantly with your online friends? Get the FREE Yahoo!
Messenger http://mail.messenger.yahoo.co.uk
>You can pass the snd-pcm-oss module
parameters
which determine how to
map alsa
pcm to oss devices.
and what are those parameters?
7705
days inactive
7706
days old
linux-audio-user@lists.linuxaudio.org
15 comments
8 participants
participants (8)
-
Akos Maroy -
Alex Timmer -
Claudio Mettler -
Daniel James -
Frank Barknecht -
Jan Weil -
John Bleichert -
Julien Claassen