Maybe you didn't load the oss compatibility modules? Could you send your alsa-modules configuration and the output of "lsmod | grep snd"?
That might be it. Here's my output:
grisey:/etc/init.d# lsmod | grep snd snd-ali5451 11660 0 snd-pcm 57120 0 [snd-ali5451] snd-timer 11176 0 [snd-pcm] snd-ac97-codec 24804 0 [snd-ali5451] snd 30860 0 [snd-ali5451 snd-pcm snd-timer snd-ac97-codec] soundcore 3556 0 [snd]
With this combination, asound plays o.k. and alsamixer works.
BTW, in my first mail I didn't realize it used an old pd version installed by Debian (0.34).
With the new one (after deinstalling the old one), I get the following error:
couldn't open MIDI output device 1 opened 0 MIDI input device(s) and 0 MIDI output device(s). /dev/dsp (read/write): No such device (now will try write-only...) /dev/dsp (writeonly): No such device error: OSS: SNDCTL_DSP_CHANNELS failed /dev/dsp audio I/O stuck... closing audio
The /dev/dsp exists. (About the MIDI: That's not my problem. That's taken care of as soon as I insmod my midi-driver. I'm just concerned with sound i/o).
Thanx Frank, Orm
Hi, Orm Finnendahl hat gesagt: // Orm Finnendahl wrote:
Maybe you didn't load the oss compatibility modules? Could you send your alsa-modules configuration and the output of "lsmod | grep snd"?
That might be it. Here's my output:
grisey:/etc/init.d# lsmod | grep snd snd-ali5451 11660 0 snd-pcm 57120 0 [snd-ali5451] snd-timer 11176 0 [snd-pcm] snd-ac97-codec 24804 0 [snd-ali5451] snd 30860 0 [snd-ali5451 snd-pcm snd-timer snd-ac97-codec] soundcore 3556 0 [snd]
Yes, there are no OSS-compatibility module. It should have these as well at least: snd-pcm-oss snd-mixer-oss snd-rawmidi. You could try manually modprobing them, but better put them in your alsa-modules configuration under /etc/modutils/ like:
alias sound-slot-0 snd-card-0 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
then run "update-modutils"
With this combination, asound plays o.k. and alsamixer works.
This is only using alsa itself. With the oss-modules loaded, OSS apps should work as well.
BTW, in my first mail I didn't realize it used an old pd version installed by Debian (0.34). With the new one (after deinstalling the old one), I get the following error:
couldn't open MIDI output device 1 opened 0 MIDI input device(s) and 0 MIDI output device(s). /dev/dsp (read/write): No such device (now will try write-only...) /dev/dsp (writeonly): No such device error: OSS: SNDCTL_DSP_CHANNELS failed /dev/dsp audio I/O stuck... closing audio
See above, you seem to miss the OSS-compatibility modules. Are you using ALSA 0.5 or 0.9? If 0.9 you could try my unofficial 0.35 Debian packages on footils.org. It's still test17, I'll put up the latest version the next days.
Frank Barknecht _ ______footils.org__
Hi All,
I'm still using PD 0.34.4 so perhaps this problem has been fixed in 0.35...?
I'm running on Windows 2000.
When I create a subpatch, PD gets confused about the keyboard when in edit mode. It's fine when the subpatch pops up after creation but once closed and reopened, the keyboard doesn't map to the window correctly. The end result is that I will never be able to edit object name/s arguments in the subpatch. Or name new objects etc. The mouse works fine so I can create/delete patch cords and select menu options... even select the text inside the objects.
I've not done any Tcl/tk programming so I'm not sure how to go about finding/fixing the problem myself. Can anyone provide any insight to this?
Many thanks, Daniel
Hi,
This was fixed in 0.35testsomething. I believe the fix was to automatically close and open the subpatch, which makes the keyboard work again.
cheers Juha
Ahah!
A good reason to start playing with the test specimens then.
Thanks. Daniel
-----Original Message----- From: Juha Vehvilainen [mailto:jusu@acoustics.hut.fi] Sent: Monday, 17 June 2002 6:12 PM To: pd-list@iem.kug.ac.at Subject: Re: [PD] 0.34.4 subpatch edit problem
Hi,
This was fixed in 0.35testsomething. I believe the fix was to automatically close and open the subpatch, which makes the keyboard work again.
cheers Juha