![]() | |||||||||||||
Messages in this thread |
On Mon, 20 Aug 2007, Clemens Ladisch wrote: > David Griffith wrote: > > On Fri, 17 Aug 2007, Clemens Ladisch wrote: > > > David Griffith wrote: > > > > On Thu, 16 Aug 2007, Clemens Ladisch wrote: > > > > > Please try "amidi -d -p virtual" and playing a .mid file to this port with > > > > > aplaymidi. > > > > > > > > $ aplaymidi -p "virtual" castle2.mid > > > > Invalid port virtual - No such file or directory > > > > > > Sorry, the name of the correspondig sequencer port is different, > > > probably "128:0"; see the output of "aplaymidi -l". > > > > $ aplaymidi -l > > Port Client name Port name > > 14:0 Midi Through Midi Through Port-0 > > 16:0 Ensoniq AudioPCI ES1371 > > 20:0 Fastlane Fastlane MIDI A > > 20:1 Fastlane Fastlane MIDI B > > > > $ aplaymidi -p 20:0 casablan.mid > > > > Nothing is written to the Fastlane. No lights. Nothing. > > Please run "amidi -d -p virtual" and then play to the virtual port > created by amidi, to see if MIDI playback works even without hardware. $ amidi -d -p virtual $ aplaymidi -l Port Client name Port name 14:0 Midi Through Midi Through Port-0 16:0 Ensoniq AudioPCI ES1371 128:0 Client-128 Virtual RawMIDI $ aplaymidi -p 128:0 casablan.mid At this point, MIDI data flew by in the xterm in which amidi was running. -- David Griffith dgriffi@cs.csubak.edu - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ | ||||||||||||
| Last update: 2007-08-20 07:47 [W:0.812 / U:0.990 seconds] ©2003-2008 Jasper Spaans | |||||||||||||