I'm running with -nosound. That shouldn't make a difference (should it?)
Well, I tried it and I get the same results. Darn.
alfonso acosta wrote:
jfm3 wrote:
So I have this laptop hooked up to a MIDI timepiece AV. I'm running ALSA 0.9-beta3. The beta4 card-mtpav.c file is the same as the beta3 one. I run pd-0.33-TEST5 and see the following.
# pd -midiindev 2 -midioutdev 2 -nosound Pd: system call timed out Pd: system call timed out couldn't open MIDI output device 2 opened 1 MIDI input device(s) and 0 MIDI output device(s).
[...]
Try running pd -frags <value> (try different values)
Hmm, the "system call timed out" messages mean that Pd was trying to open something (MIDI output I bet) and the open() call was just sitting there. This can happen if something else on the system already has MIDI open for output. There might also be other reasons I don't know about...
cheers Miller
On Mon, Jun 04, 2001 at 06:52:08PM -0400, jfm3 wrote:
I'm running with -nosound. That shouldn't make a difference (should it?)
Well, I tried it and I get the same results. Darn.
alfonso acosta wrote:
jfm3 wrote:
So I have this laptop hooked up to a MIDI timepiece AV. I'm running ALSA 0.9-beta3. The beta4 card-mtpav.c file is the same as the beta3 one. I run pd-0.33-TEST5 and see the following.
# pd -midiindev 2 -midioutdev 2 -nosound Pd: system call timed out Pd: system call timed out couldn't open MIDI output device 2 opened 1 MIDI input device(s) and 0 MIDI output device(s).
[...]
Try running pd -frags <value> (try different values)
-
jfm3 -
Miller Puckette