| 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 00000 1.010 1.202 0.000 0 fluidsynth: cc 1 7 100 fluidsynth: noteon 1 64 90 00001 1.010 1.203 0.000 1 fluidsynth: cc 2 7 100 fluidsynth: noteon 2 60 90 00002 1.010 1.203 0.000 2 fluidsynth: cc 3 7 100 fluidsynth: noteon 3 57 90 00003 1.010 1.203 0.000 3
So, yes.
Is there any way for me to suppress these commands or to make my own commands from the init file appear directly after them (but before the first notes are played)? 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?)
However, I did create a file named synth.init and ran
fluidsynth -f synth.init soundfont.sf2 midifile.midi
The strange thing here is that when I write non-valid commands in the init file, such as
poop 1 7 0
, fluitsynth throws an error (which mean that it obviously reads the file). However, when I write valid commands, such as
cc 1 7 0
fluidsynth doesn’t complain, but the command doesn’t take effect either.
I don’t know what the problem is here, but I’m thinking that it’s one of the following
1. fluidsynth doesn’t run my commands.
2. fluidsynth runs my command, but they get overwritten by init procedures in the midi file itself (I don’t know if CC#7 normally is called by a midi file to set the initial levels of the channels).
Theory nr 2 is very easy to verify using the --verbose flag to FluidSynth, and yes, CC#7 is the standard way of setting the channel's level and is almost always used in your random downloaded-from-the-internet midi file. // David _______________________________________________ fluid-dev mailing list address@hiddenhttps://lists.nongnu.org/mailman/listinfo/fluid-dev
|