SB 128 ES1370 tip for dual dsp

[GNU]

heres a possibly obvious tip for some, but it helped me

the SB128 PCI card, running the older chip with the ES1370 (note: not 1371) modules from alsa, can run 2 dsp's

the easy way (only way ?) is to use *** /dev/adsp ***

i run teamspeak on /dev/adsp and games(and everything else) on /dev/dsp


might help some people out there, spent a day getting this going, but all's well now.






btw: about this problem of key capture. surely just make a command (as in unix command) to transmit, and use xbindkeys(the program) to bind it to a key. sorted.

[N. Werensteijn]

Thanks for the tip with the soundcard.

As for the push-to-talk. Thats not all we want to keybind :)
And the method xbindkeys uses is not realy good with
more exotic combos like "shift-a-F3".

But suggestions are welcome, I am new to X11 programming

[woutur]

Doesn't work here.
Got same card, kernel 2.4.19 alsa rc6, tried with OSS too.
There just isn't any other device than dsp for me. dsp1 or 2 or 0 or adsp don't work.
Can't i just let esd or something mix the stuff?

[GNU]

snd-ens1370 module. es1370 is poop mate. Youll prob have some problems getting snd-ens1370 to run, but once it is, dont go back :-)

[ztoon]

You can do multiplexing on ens1371 with alsa 0.9 too. adsp seems to work fine

[Uranus]

btw, I got the same card, thanks for the tip, I didnt know that... anyway, I tried to use /dev/adsp with TeamSpeak, but if I do, TeamSpeak always puts input & output muted, and I can't un-mute, but it works on other software, so I use adsp for quake3 and /dev/dsp for TeamSpeak

[ztoon]

If have a similar problem, I can't use TeamSpeak on adsp, but I can't use quake3 on adsp, cause it didn't produce sound.. (don't know why because I can use xmms on adsp)

[woutur]

I think there is a problem with those 2 devices since only one can record and playback simultaneously (at least.. thats what my feeling says). So basically have a look at the links of adsp and dsp that are made in the /dev/ directory and try to figure out which one can record and playback and which one can only playback. Use last one for games. That's the crucial point if you ask me :)

Have a look at this topic. I posted my links there:
http://www.teamspeak.org/forums/showthread.php?s=&threadid=2494

[ztoon]

So i can't use TeamSpeak on adsp (adsl is only for playback), so I'll use Teamspeak on dsp0, but I can't use quake3 on adsp too, cause I have no sound with quake3 on adsp (it says "could not open /dev/adsp") but adsp works cause i can use XMMS on adsp...

I don't know what is this problem.
Changing any order of dsp links doesn't change anythink...

Is it possible to force playback and callback only for adsp, and let dsp0 only for playback ?

[GNU]

adsp is a play back only device.

hence, you need to make games use it, and teamspeak to use the playback and record one.

how i hear you cry ? -- do a symlink from
/dev/dsp --> /dev/sound/adsp
and
/dev/adsp --> /dev/sound/dsp

job done.

[ztoon]

You didn't understood the problem..

This is not symlinks problem.

Quake3 is the ONLY app that doesn't produce sound on /dev/adsp. ESD apps like XMMS works fine on adsp. THIS is THE strange problem. Having quake3 that doesn't work on adsp saying "could not open /dev/adsp"

I have no /dev/sound/* directory, I only have /dev/snd that is a link to /proc/asound/dev

/dev/adsp is a link to /dev/adsp0 in my system.

And changing links like /dev/dsp --> /dev/adsp0 and /dev/adsp --> /dev/sound/dsp0 doesn't change anythink

So, if quake3 doesn't want to work on adsp, and I can't use TeamSpeak on adsp too, I have a big problem.

[GNU]

run quake on dsp, linked to adsp, how you do it is your fun :-)

if your using snd-ens1370 and not es1370 you should have a /sound afaik

gentoo 1.2 / 1.4 / mandrake 8.2 / debian woody works here.
TS newest (any works to be honest)
SB 128 PCI

[ztoon]

I am doing all this with ens1371 in alsa 0.9 (read this 6 replies highter). cause I never managed to load the ens1370 with my SB 128 (ct5880 chip)

this is very incredble that some apps doesn't find adsp device, and some other works fine with it :)

thnx for trying to help me GNU

[GNU]

to run snd-ens1370 youll have to follow the alsa directions exactly, otherwise only es1370 will load. i normally re-emerge (recompile) alsa to get snd-ens1370 running. and this is because ive gone to a new kernel normally.

of course youll have to have the Creative 128 **es1370** module loaded into kernel as a module for this to work, at default only the 1371 is loaded as a module and the 1370 isent loaded at all. This is prob why you couldnt get that module to load.

all this shouldnt matter to you anyhow, as the Ct5880 chip needs a diffrent module anyhow, i run an older 128 card which needs the 1370 module, SB released the 128 with 2 diffrent chips at diffrent dates, you see.

http://www.alsa-project.org/alsa-doc/
http://www.alsa-project.org/alsa-doc/doc-php/template.php3?company=Creative+Labs&card=Soundblaster+PCI+128&chip=ES1373&module=ens1371