31 Jan
2003
31 Jan
'03
5:39 p.m.
Hi!
Does anybody know if the Delta 1010's MIDI Ports are supported by the ALSA
drivers?
Regards, Christian
31 Jan
31 Jan
8:08 p.m.
Hi Christian
I have a TerraTec DMX 6Fire 24/96 soundcard, which uses the same chipset as
the Delta 1010. The chipset I am referring to is the Envy24. I am quite
able to use MIDI with my terratec card, so I don't think you will have a
problem.
Luke.
t 08:33 AM 1/02/2003, you wrote:
Hi!
Does anybody know if the Delta 1010's MIDI Ports are supported by the ALSA
drivers?
Regards, Christian
1 Feb
1 Feb
3:59 a.m.
Same for a Terratec EWS 88MT...
Have fun!
KiTaSuMbA
On Saturday 01 February 2003 01:00, Luke Yelavich wrote:
Hi Christian
I have a TerraTec DMX 6Fire 24/96 soundcard, which uses the same chipset as
the Delta 1010. The chipset I am referring to is the Envy24. I am quite
able to use MIDI with my terratec card, so I don't think you will have a
problem.
Luke.
t 08:33 AM 1/02/2003, you wrote:
>Hi!
>
>Does anybody know if the Delta 1010's MIDI Ports are supported by the ALSA
>drivers?
>
>Regards, Christian
6:39 a.m.
Es geschah am Samstag, 1. Februar 2003 01:00 als Luke Yelavich schrieb:
Hi Christian
I have a TerraTec DMX 6Fire 24/96 soundcard, which uses the same chipset as
the Delta 1010. The chipset I am referring to is the Envy24. I am quite
able to use MIDI with my terratec card, so I don't think you will have a
problem.
Actually I do have a problem, but maybe a small one. Audio works now with my
Delta 1010, but I'm missing device /dev/snd/seq.
Should that be simple link to somewhere or have I missed to add a module or
something?
Help greatly appreciated!
P.S. these are my (audio related) modules:
Module Size Used by Tainted: P
snd-pcm-oss 36932 0 (autoclean)
snd-mixer-oss 10680 0 (autoclean) [snd-pcm-oss]
snd-ice1712 34940 0
snd-pcm 56384 0 [snd-pcm-oss snd-ice1712]
snd-timer 10600 0 [snd-pcm]
snd-cs8427 3436 0 [snd-ice1712]
snd-ac97-codec 25828 0 [snd-ice1712]
snd-i2c 2216 0 [snd-ice1712 snd-cs8427]
snd-mpu401-uart 2704 0 [snd-ice1712]
snd-rawmidi 12672 0 [snd-mpu401-uart]
snd-seq-device 3888 0 [snd-rawmidi]
snd 24876 2 [snd-pcm-oss snd-mixer-oss snd-ice1712
snd-pcm snd-timer snd-cs8427 snd-ac97-codec snd-i2c snd-mpu401-uart
snd-rawmidi snd-seq-device]
mpu401 18884 0 (unused)
sound 54540 0 [mpu401]
soundcore 3556 7 [snd sound]
and these my /dev/snd devices:
controlC0 midiC0D0 pcmC0D0c pcmC0D0p timer
3 Feb
3 Feb
4:42 a.m.
Christian Schoenebeck wrote:
Actually I do have a problem, but maybe a small one.
Audio works now with my
Delta 1010, but I'm missing device /dev/snd/seq.
The sequencer modules should be loaded automatically when you try to
access some sequencer device; try "aconnect -o".
P.S. these are my (audio related) modules:
...
mpu401 18884 0 (unused)
This is the OSS driver. As long as it's loaded, the ALSA driver won't be
able to access the MIDI port.
HTH
Clemens
6 Feb
6 Feb
3:30 p.m.
Es geschah am Montag, 3. Februar 2003 09:35 als Clemens Ladisch schrieb:
Christian Schoenebeck wrote:
Ok, at least after a 'modprobe snd-seq-oss' I got the /dev/snd/seq device,
but I have to do that manually everytime I reboot. So why isn't this module
loaded automatically? According to my modules.conf it should:
...
# ALSA portion
alias char-major-116 snd
alias snd-card-0 snd-ice1712
# OSS/Free portion
alias char-major-14 soundcore
alias sound-slot-0 snd-card-0
# card #1
alias sound-service-0-0 snd-mixer-oss
alias sound-service-0-1 snd-seq-oss
alias sound-service-0-3 snd-pcm-oss
alias sound-service-0-8 snd-seq-oss
alias sound-service-0-12 snd-pcm-oss
...
Can somebody give me a hint?
Actually I do have a problem, but maybe a small
one. Audio works now
with my Delta 1010, but I'm missing device /dev/snd/seq.
The sequencer modules should be loaded automatically when you try to
access some sequencer device; try "aconnect -o".
7 Feb
7 Feb
4:30 a.m.
Christian Schoenebeck wrote:
Es geschah am Montag, 3. Februar 2003 09:35 als
Clemens Ladisch schrieb:
/dev/snd/seq is the ALSA sequencer device. The OSS sequencer would be
/dev/sequencer.
Christian Schoenebeck wrote:
Ok, at least after a 'modprobe snd-seq-oss' I got the /dev/snd/seq device,
Actually I do have a problem, but maybe a small
one. Audio works now
with my Delta 1010, but I'm missing device /dev/snd/seq.
The sequencer modules should be loaded automatically when you try to
access some sequencer device; try "aconnect -o". but I have to do that manually everytime I reboot. So
why isn't this module
loaded automatically? According to my modules.conf it should:
...
alias sound-service-0-1 snd-seq-oss
...
Please check that the /dev/sequencer file has major/minor numbers 14, 1.
And when you access /dev/sequencer, the module should be loaded, or there
is an error message written to /var/log/messages.
And if you use programs using the ALSA sequencer the above doesn't matter.
HTH
Clemens
8 Feb
8 Feb
2:46 p.m.
Es geschah am Freitag, 7. Februar 2003 09:23 als Clemens Ladisch schrieb:
I know, sorry, I just typed that to get all in one.
Yes, it is.
Ok, at least
after a 'modprobe snd-seq-oss' I got the /dev/snd/seq
device,
/dev/snd/seq is the ALSA sequencer device. The OSS sequencer would be
/dev/sequencer. but I have to
do that manually everytime I reboot. So why isn't this
module loaded automatically? According to my modules.conf it should:
...
alias sound-service-0-1 snd-seq-oss
...
Please check that the /dev/sequencer file has major/minor numbers 14, 1. And when you access /dev/sequencer, the module should
be loaded, or there
is an error message written to /var/log/messages.
Correct, accessing /dev/sequencer loads the module and /dev/snd/seq appears,
but shouldn't the Alsa seq module be loaded automatically on startup? Alsa
apps won't try to access /dev/sequencer before they actually open
/dev/snd/seq, right? Thus, no Alsa app will work after a reboot without me
having loaded the Alsa seq module manually (or having accessed
/dev/sequencer).
Hope you still have patience to answer me ;)
Regards, Christian
10 Feb
10 Feb
6:30 a.m.
Christian Schoenebeck wrote:
Es geschah am Freitag, 7. Februar 2003 09:23 als
Clemens Ladisch schrieb:
It will be loaded on startup if there is a startup script that loads it.
Creating such a script is the responsibility of the distribution or the
system administrator. >:-)
And when you access /dev/sequencer, the module
should be loaded, or there
is an error message written to /var/log/messages.
Correct, accessing /dev/sequencer loads the module and /dev/snd/seq appears,
but shouldn't the Alsa seq module be loaded automatically on startup? Alsa apps won't try to access /dev/sequencer
before they actually open
/dev/snd/seq, right? Thus, no Alsa app will work after a reboot
without me having loaded the Alsa seq module manually (or having
accessed /dev/sequencer).
The ALSA sequencer is accessed through the ALSA library, and the library
will access /dev/aloadSEQ if /dev/snd/seq isn't found. So, when using ALSA
applications, the sequencer will be loaded transparently.
HTH
Clemens
7740
days inactive
7750
days old
linux-audio-user@lists.linuxaudio.org
8 comments
4 participants
participants (4)
-
Christian Schoenebeck -
Clemens Ladisch -
Gerasimos Grammatikopoulos -
Luke Yelavich