[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [fluid-dev] Rerouting output
From: |
Pedro Lopez-Cabanillas |
Subject: |
Re: [fluid-dev] Rerouting output |
Date: |
Sat, 5 Mar 2011 21:51:06 +0100 |
User-agent: |
KMail/1.13.5 (Linux/2.6.34.7-0.7-desktop; KDE/4.4.4; i686; ; ) |
Hi,
I assume that you are using Linux because aconnect is an ALSA sequencer
utility, but please note that both FluidSynth and VMPK can be used in Windows
and Mac OSX as well, and while the basics of MIDI and audio are the same other
features may differ.
On Friday 04 March 2011, Nuzhna Pomoshch wrote:
> I hope this doesn't sound like a complete newbie question (even
> though it is), but how do I send the output from fluidsynth to
> another program.
You can't. FluidSynth doesn't have MIDI output ports, only MIDI inputs. You
can't play a MIDI file in fluidsynth to send MIDI events to other programs.
FluidSynth outputs digital audio only.
> I have vmpk installed, and the documentation states:
>
> "You can use the Virtual MIDI Piano Keyboard to display the
> played MIDI notes from another instrument or MIDI file player.
> To do so, connect the other MIDI port to the input port of VMPK."
The other MIDI port should be a MIDI output port, of course. There are several
programs that can be used in Linux to play a MIDI file and provide a MIDI
output port for connection to VMPK. For instance: aplaymidi (from ALSA utils),
KMidimon, drumstick-guiplayer, end even KMid2 (it is the easiest to use, it has
a VMPK keyboard embedded, and can launch and connect FluidSynth at startup).
> I tried connecting Midi Through to the vmpk input, but that
> didn't work.
>
> $ aconnect -l -i
> client 0: 'System' [type=kernel]
> 0 'Timer '
> 1 'Announce '
> Connecting To: 15:0
> client 14: 'Midi Through' [type=kernel]
> 0 'Midi Through Port-0'
> Connecting To: 130:0
> client 129: 'VMPK Output' [type=user]
> 0 'VMPK Output '
> Connecting To: 128:0[real:0]
>
> $ aconnect -l -o
> client 14: 'Midi Through' [type=kernel]
> 0 'Midi Through Port-0'
> Connecting To: 130:0
> client 128: 'FLUID Synth (29527)' [type=user]
> 0 'Synth input port (29527:0)'
> Connected From: 129:0[real:0]
> client 130: 'VMPK Input' [type=user]
> 0 'VMPK Input '
> Connected From: 14:0
>
> Should fluidsynth appear in both the list of input and output
> connections (and if not, why not?)?
Because FS is a synthesizer: It translates MIDI events into digital audio.
FluidSynth input: MIDI.
FluidSynth output: audio.
Regards,
Pedro
- [fluid-dev] Rerouting output, Nuzhna Pomoshch, 2011/03/04
- Re: [fluid-dev] Rerouting output, Dave Serls, 2011/03/04
- Re: [fluid-dev] Rerouting output,
Pedro Lopez-Cabanillas <=
- Re: [fluid-dev] Rerouting output, mike, 2011/03/05
- Re: [fluid-dev] Rerouting output, mike, 2011/03/05
- Re: [fluid-dev] Rerouting output, Pedro Lopez-Cabanillas, 2011/03/05
- fluidsynth on Windows Was: Re: [fluid-dev] Rerouting output, mike, 2011/03/08
- Re: fluidsynth on Windows Was: Re: [fluid-dev] Rerouting output, Graham Goode, 2011/03/08
- Re: fluidsynth on Windows Was: Re: [fluid-dev] Rerouting output, mike, 2011/03/08
- Re: fluidsynth on Windows Was: Re: [fluid-dev] Rerouting output, Graham Goode, 2011/03/08
- Re: fluidsynth on Windows Was: Re: [fluid-dev] Rerouting output, mike, 2011/03/08
- Re: fluidsynth on Windows Was: Re: [fluid-dev] Rerouting output, Graham Goode, 2011/03/08
- Re: fluidsynth on Windows Was: Re: [fluid-dev] Rerouting output, mike, 2011/03/08