David,

Thank you for the reply. I should have realized the 16 channel is a midi
limit, not Fluidsynth. In looking through the Fluidsynth on-line
documentation, I see that there are direct "noteon" and "noteoff" commands.
Would it be possible to drive the engine with a config file (instead of a
midi file) containing these commands? I suppose I could just try it, but I
don't see a method to specify when a note is played (or turned off). So I
assume these commands are for real-time devices, not for a file-based
approach.

Regards,
Dave

-----Original Message-----
From: fluid-dev-bounces+dkrinkel=comcast....@nongnu.org
[mailto:fluid-dev-bounces+dkrinkel=comcast....@nongnu.org] On Behalf Of
David Henningsson
Sent: Thursday, November 14, 2013 10:33 PM
To: FluidSynth mailing list
Subject: Re: [fluid-dev] More than 16 instruments?

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
fluid-dev@nongnu.org
https://lists.nongnu.org/mailman/listinfo/fluid-dev


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

Reply via email to