Interesting… However, shouldn’t I be able to keep on using midi files with
built-in CC#7 commands and resort to manipulating CC#11 instead (rather than
forcing my midi-files to use CC#11), even if it’s not the “right” way to do it?
I don’t care much for doing things the right way right now; I ju
The "right" way to do what you want would be for you to use CC 7,
channel volume, and the MIDI files to use CC 11, expression controller.
The two values are multiplied together and divided by 128 to get the
final volume of the channel. If the MIDI files use CC 7 for what is
really expression co
Yes, I can confirm that this is the case for my midi files (which are generated
from Lilypond). My CC commands aren’t printed anywhere, but in the list, the
following shows up:
fluidsynth: cc 0 7 100
fluidsynth: noteon 0 64 90 0 1.010 1.202 0.000 0
f
On 01/18/2014 10:27 PM, Martin Larsson wrote:
> Thanks for the answer!
>
> Unfortunately, the server mode doesn’t make much more sense to me since the
> documentation on this is about as sparse as on the load configuration file.
> (Is there a more extensive manual to download anywhere?)
>
> How
Thanks for the answer!
Unfortunately, the server mode doesn’t make much more sense to me since the
documentation on this is about as sparse as on the load configuration file. (Is
there a more extensive manual to download anywhere?)
However, I did create a file named synth.init and ran
flui
On Sat, 18 Jan 2014 15:26:42 +0100
Martin Larsson wrote:
> If I run fluidsynth from the terminal
>
>fluidsynth soundfont.sf2 midifile.midi
>
> I am then able to write control change commands in realtime to alter the
> playback. For example,
>
>cc 1 7 0
>
> sends a CC#7 message (chann
If I run fluidsynth from the terminal
fluidsynth soundfont.sf2 midifile.midi
I am then able to write control change commands in realtime to alter the
playback. For example,
cc 1 7 0
sends a CC#7 message (channel volume) to channel 1 with a value of 0.
Now, I would like to specify a bunc
