Re: [fluid-dev] More than 16 instruments?

[Dave]

Aere,

Thank you for the reply. My use of Fluidsynth is unusual, to say the least.
I use it to convert midi files (hundreds of them) into MP3's. So it is not
in performance, it is a totally automated process. I am not sure how to
combine multiple instances of Fluidsynth into a single raw sound file.

By the way, the description of your "composite voices" is wonderful! Is
there a place to hear some of your performances?

Regards,
Dave

-----Original Message-----
From: address@hidden
[mailto:address@hidden On Behalf Of Aere
Greenway
Sent: Friday, November 15, 2013 8:52 AM
To: FluidSynth mailing list
Subject: Re: [fluid-dev] More than 16 instruments?

On 11/14/2013 11:33 PM, David Henningsson wrote:
> On 11/15/2013 03:14 AM, Dave wrote:
>> I am using FluidSynth to create raw sound files from midi files (LOVE 
>> FluidSynth, works great!). The midi file are generated from an 
>> algorithm, and can contain multiple tracks and channels. The program 
>> also creates a FluidSynth configuration file which links the channels 
>> to soundfonts and instruments (via the "select" command).
>>
>>   
>>
>> Is it possible to have more than 16 instruments? For example, could 
>> two different tracks use channel 0, and somehow assign a different 
>> instrument to each track-channel combination?
> It is possible to have more than 16 instruments within the FluidSynth 
> engine, but you would then have to use the engine directly rather than 
> using midi files. I e, the problem is that the midi file specification 
> allows for 16 channels only (and we have not implemented any 
> non-standard extension that would do what you suggest).
>
> // David
>
>
> _______________________________________________
> fluid-dev mailing list
> address@hidden
> https://lists.nongnu.org/mailman/listinfo/fluid-dev
>
I don't know what environment you're using Fluidsynth in, but I routinely do
what I think you're asking for, using the Qsynth wrapper of Fluidsynth.  In
Qsynth, you just add one (or more) additional 'engines', and route your MIDI
to that other engine (with its own 16 channels).

I'm not as experienced using the command-line interface, but I speculate you
could run (in separate terminal sessions) additional instances of
Fluidsynth, and route your MIDI to each.

I actually use this in performing, to produce what I call "composite
voices", where the main voice is a piano or guitar, and the secondary voice
is String Ensemble 1, or Metallic Pad, at a much lower volume.  
The sound is like a piano with a hint of strings in the background.

I route the same keyboard MIDI performance data to both instances of
Fluidsynth simultaneously.

Depending on the secondary voice you use, it can be useful to have a MIDI
filter in-between to filter-out sustain pedal control signals - useful if
the secondary voice is a type of Pad.

--
Sincerely,
Aere


_______________________________________________
fluid-dev mailing list
address@hidden
https://lists.nongnu.org/mailman/listinfo/fluid-dev