problems and questions with creative audixy

problems and questions with creative audixy

[Guenther Sohler]

Hallo List,

I migrated to alsa now. I think its a quite good concept, but I think I have
found some bugs

When I play a midi file to the audixy wavetable synth, and there is a
instrument like a cello which sounds till you switch it off, and you interupt
with CTRL-C it stays hanging. its done with the midi port but
the the port to the audixy synth should do a  "all note off" when it is beeing
closed

With my audixy all the 4 wavetable ports are fine but the midi ports do not work
If I try to access them, there is following error message issued:
alsa ../../alsa-kernel/pci/emu10k1/emumpu401.c:126 cmd 0xff failed at
0xd400(status=0xff, data=0xff)

the same command is repeated with 0x3f isntead of 0xff after 126

There are nice external-midi devices in /dev/snd where you can put raw midi
data to, but there are no devices which go to the wavetable synth of the audixy


Where can i find a description on all the snd midi modules especially not the
pci and the isa but the general ones. snd-virmidi is just an example of a
module i dont know its meaning at all.


thankx in advance

_______________________________________________
Alsa-devel mailing list
Alsa-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/alsa-devel

Re: problems and questions with creative audixy

[Takashi Iwai]

Hi,

At Thu, 07 Feb 2002 17:35:37 +0100 (MET),
Guenther Sohler wrote:
> 
> Hallo List,
> 
> I migrated to alsa now. I think its a quite good concept, but I think I have
> found some bugs
> 
> When I play a midi file to the audixy wavetable synth, and there is a
> instrument like a cello which sounds till you switch it off, and you interupt
> with CTRL-C it stays hanging. its done with the midi port but
> the the port to the audixy synth should do a  "all note off" when it is beeing
> closed
 
It happend on emu10k1, too.  I'll try to find the bug.

> With my audixy all the 4 wavetable ports are fine but the midi ports do not work
> If I try to access them, there is following error message issued:
> alsa ../../alsa-kernel/pci/emu10k1/emumpu401.c:126 cmd 0xff failed at
> 0xd400(status=0xff, data=0xff)
> 
> the same command is repeated with 0x3f isntead of 0xff after 126
 
Aggh, I find one here.  Will be fixed soon.  Thanks.


> There are nice external-midi devices in /dev/snd where you can put raw midi
> data to, but there are no devices which go to the wavetable synth of the audixy
> 
> 
> Where can i find a description on all the snd midi modules especially not the
> pci and the isa but the general ones. snd-virmidi is just an example of a
> module i dont know its meaning at all.

A brief description is found in alsa-kernel/drivers/virmidi.c.
It'd be better to put this info into doc directory..


Takashi

_______________________________________________
Alsa-devel mailing list
Alsa-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/alsa-devel

Re: problems and questions with creative audixy

[Takashi Iwai]

At Thu, 07 Feb 2002 17:49:28 +0100, I wrote:
> 
> > With my audixy all the 4 wavetable ports are fine but the midi ports do not work
> > If I try to access them, there is following error message issued:
> > alsa ../../alsa-kernel/pci/emu10k1/emumpu401.c:126 cmd 0xff failed at
> > 0xd400(status=0xff, data=0xff)
> > 
> > the same command is repeated with 0x3f isntead of 0xff after 126
>  
> Aggh, I find one here.  Will be fixed soon.  Thanks.

ok, now committed to cvs.  hopefully it works now..

BTW, there are two MIDI ports on audigy, the first one
/dev/snd/midiC0D0 is for the gameport and the second one midiC0D1 is
for the connector on external drive.


Takashi

_______________________________________________
Alsa-devel mailing list
Alsa-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/alsa-devel

Re: problems and questions with creative audixy

[Takashi Iwai]

At Thu, 07 Feb 2002 18:27:10 +0100 (MET),
Guenther Sohler wrote:
> 
> > BTW, there are two MIDI ports on audigy, the first one
> > /dev/snd/midiC0D0 is for the gameport and the second one midiC0D1 is
> > for the connector on external drive.
> i dont have an external drive. can i use the midi plug at  the back as a midi
> plug ? i think so ?

yes, then it's the former one, /dev/snd/midiC0D0.

> But I am looking for a device to cat pure midi data to, but it should appear as
> wavetable synth!!! it was possible in oss before
> /dev/midi00 went to the wavetablesynth and /dev/midi01 went to the external
> midi port!

You can feed midi bytes to /dev/snd/midiC0D2 and /dev/snd/midiC0D3 for
playing back on wavetable.
(On SB Live they are midiC0D1 and C0D2.)


Takashi

_______________________________________________
Alsa-devel mailing list
Alsa-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/alsa-devel

stupid question about pcm devices

[Guenther Sohler]

I have seen that alsa provides nice pcm devices in /dev/snd directory

*They are split in playback and capture devices :) nice idea.
In Oss I was able to pipe data from and to them and therfore was
recording/playing back at a certain sample rate.
With alsa this is not possible anymore. it says the descriptor was in a bad
state. Is it possible ???

*Is there something like aconnect for pcm devices ????

when I do a sfxload, it operates on /dev/sequencer, which makes the seq-oss
module automatically to load. Is there a way to load the patches in native alsa
???

rds guenther

_______________________________________________
Alsa-devel mailing list
Alsa-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/alsa-devel

Re: stupid question about pcm devices

[Jaroslav Kysela]

On Fri, 8 Feb 2002, Guenther Sohler wrote:

> I have seen that alsa provides nice pcm devices in /dev/snd directory
>
> *They are split in playback and capture devices :) nice idea.
> In Oss I was able to pipe data from and to them and therfore was
> recording/playing back at a certain sample rate.
> With alsa this is not possible anymore. it says the descriptor was in a bad
> state. Is it possible ???

Yes: arecord | aplay

> *Is there something like aconnect for pcm devices ????

Nope.

> when I do a sfxload, it operates on /dev/sequencer, which makes the seq-oss
> module automatically to load. Is there a way to load the patches in native alsa
> ???

No, it's under slow development.

						Jaroslav

-----
Jaroslav Kysela <perex@suse.cz>
SuSE Linux    http://www.suse.com
ALSA Project  http://www.alsa-project.org


_______________________________________________
Alsa-devel mailing list
Alsa-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/alsa-devel

emu10k1 specification

[Guenther Sohler]

Hallo Takshi Iwai,

is there specification of the emu10k1 chip available describing all its
registers etc ?? or is it nda ?

I am curioius about it

rds guenther



_______________________________________________
Alsa-devel mailing list
Alsa-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/alsa-devel

Re: emu10k1 specification

[Jaroslav Kysela]

On Fri, 8 Feb 2002, Guenther Sohler wrote:

> Hallo Takshi Iwai,
>
> is there specification of the emu10k1 chip available describing all its
> registers etc ?? or is it nda ?

We have it available under NDA.

						Jaroslav

-----
Jaroslav Kysela <perex@suse.cz>
SuSE Linux    http://www.suse.com
ALSA Project  http://www.alsa-project.org



_______________________________________________
Alsa-devel mailing list
Alsa-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/alsa-devel

Re: stupid question about pcm devices

[Paul Davis]

>I have seen that alsa provides nice pcm devices in /dev/snd directory
>
>*They are split in playback and capture devices :) nice idea.
>In Oss I was able to pipe data from and to them and therfore was
>recording/playing back at a certain sample rate.
>With alsa this is not possible anymore. it says the descriptor was in a bad
>state. Is it possible ???

jaroslav answered this in one way. i'd like to add this:

under OSS, most people understand that cat > /dev/dspN requires that
the data match the "default" format for the "dsp" device. any mismatch
will result in noise. the same is true for ALSA.

however, under ALSA, the devices are not that simple. specifically,
OSS required opening+closing devices to reset the parameters, whereas
ALSA instead allows the devices to remain open, but stopped,
reconfigured, then restarted. these are all done by ioctl(2) calls.

this means that, in terms of system calls, there is always at least
one ioctl(2) call required to get the device started after it is
opened. as a result of this, "cat > /dev/snd/pcmC0D0" or equivalent
will never work, since cat merely calls open(2) on the device - it
does not start it (i.e. make the ioctl(2) call).

i suspect that some people in the kernel community will object to this
design, noting that it violates The Unix Way. however, there are many
devices that require ioctl(2)'s to get them set up for use, so ALSA
will not be the first. i doubt, for example, if "cat > /dev/scanner"
will work, and "cat > /dev/modem" normally results in garbage
someplace. 

>*Is there something like aconnect for pcm devices ????
>
>when I do a sfxload, it operates on /dev/sequencer, which makes the seq-oss
>module automatically to load. Is there a way to load the patches in native als
>a
>???

rewrite sfxload.

--p

_______________________________________________
Alsa-devel mailing list
Alsa-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/alsa-devel