You could configure the MIDI router to only filter CC 7 on certain channels.
As for command line commands for the MIDI player, yes, sounds useful. Someone just needs to program it ;-) Element On Fri, Feb 3, 2012 at 5:32 PM, James Ong <yanlile...@gmail.com> wrote: > I see, true it will be sounds awful with all at the same levels, seem like > having 2 fluidsynth will do the job. > > However, not sure if you remember, in the FluidSynth command shell, do you > still find it feasible to implement a playback controls > which we could load, pause, play, stop, change tempo Midi song. This will be > useful for someone without C/C++ background to get start quickly. > > > On Sat, Feb 4, 2012 at 8:20 AM, Element Green <jgr...@users.sourceforge.net> > wrote: >> >> If your MIDI song itself contains a CC7 event you could perhaps filter >> it with the FluidSynth MIDI router: >> router_begin cc >> router_par1 7 7 1 0 >> router_par2 0 127 0 127 >> router_end >> >> I think that would cause all CC 7 events received to set the volume to >> 100% (127). >> >> If the MIDI song has a MIDI reset command in it, then I'm not real >> sure how to handle that off hand. Might be able to also use the MIDI >> router, but I'm not sure. >> >> Element >> >> On Fri, Feb 3, 2012 at 3:58 AM, James Ong <yanlile...@gmail.com> wrote: >> > Hi, >> > >> > What does player.reset-synth does? It seem, everytime the song is load, >> > the >> > engine will >> > still get reset by MIDI song? Is there a way to retain CC7 value? >> > >> > fluidsynth.exe" -g 1 -o "player.reset-synth=false" >> > >> > Apply CC#7 to 10% >> > cc 0 7 10 >> > >> > Load midi songs which contain CC7 event will set to 100%. >> > >> > _______________________________________________ >> > 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 > > > > _______________________________________________ > 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