gene heskett wrote: > # aplaymidi -l > Port Client name Port name > 14:0 Midi Through Midi Through Port-0 > 16:0 SB Audigy 2 Value [SB0400] Audigy MPU-401 (UART) > 16:32 SB Audigy 2 Value [SB0400] Audigy MPU-401 #2 > 17:0 Emu10k1 WaveTable Emu10k1 Port 0 > 17:1 Emu10k1 WaveTable Emu10k1 Port 1 > 17:2 Emu10k1 WaveTable Emu10k1 Port 2 > 17:3 Emu10k1 WaveTable Emu10k1 Port 3 > > Can I make the inference that a .mid file sent to 14:0 should find its way > to one of the 17:n ports?
Only if you have connected the output of 14:0 to one of the 17:n ports. > Java, by its scanning methods, finds a huge list of ports, but only the > semi-broken, internal to java, synth actually makes a noise. But does it find those sequencer ports? > If I switch to amidi -l, the list is a bit shorter: > Dir Device Name > IO hw:0,0 Audigy MPU-401 (UART) > IO hw:0,1 Audigy MPU-401 #2 > IO hw:0,2 Emu10k1 Synth MIDI (16 subdevices) > IO hw:0,3 Emu10k1 Synth MIDI (16 subdevices) > > but sending a midi file to the latter pair, while taking the normal play > time for the file, is also silent. How are you trying to send a midi file to a raw MIDI port? > From the lengthy output of amixer contents: > numid=7,iface=MIXER,name='Synth Playback Volume' > ; type=INTEGER,access=rw---R--,values=2,min=0,max=100,step=0 > : values=72,72 > | dBscale-min=-40.00dB,step=0.40dB,mute=1 > > does mute=1 mean it is live, not off? In the dBscale line, it means that the minimum value would mute. Regards, Clemens _______________________________________________ Linux-audio-dev mailing list [email protected] http://lists.linuxaudio.org/listinfo/linux-audio-dev
