Re: [fluid-dev] MIDI commands for reverb/chorus parameters

[Ceresa Jean-Jacques]

Greetings Peter,Element,List

 

> Yes. You might run into other people using the same NRPN for their
> own nefarious purposes, though, so it would be good to have some
> way of ignoring a message that was not one of yours...

 

It seems that using MIDI CC NRPN to change real time parameters (in performance situation)

is more suitable than Sysex that consumes more MIDI bus bandwidth.

As MIDI CC is channel oriented, it easy to have different synths on differents

channels in a manner that a MIDI CC send to one synth(or channel) is ignored by others synths(or channels).

This is possible when synths supports "Basics channels". The recent patch poly-mono offers this

possibility. Anyway we still need a way ("sysex" or other to set ""Basics channels" inside the synths).

 

> > Thinking about this more, I like the idea of having a Sysex
> > interface to the FluidSynth command shell, which would open up
> > a whole world of possibilities.

 

Yes. Using the same bus to communicate with the synth (for real time events et configuration data)

simplfies greatly system architecture.

 

Regards, jjc

 

 

 

> > Message du 10/07/16 01:41
> > De : "Peter Billam" <address@hidden>
> > A : address@hidden
> > Copie à : address@hidden
> > Objet : Re: [fluid-dev] MIDI commands for reverb/chorus parameters
> > 
> > Greetings Element, List, 
> > 
> > > At any rate, it seems like using the NRPN portion of MIDI is OK, 
> > > which could potentially be used for adding reverb and chorus 
> > > parameters (beyond the basics). 
> > 
> > Yes. You might run into other people using the same NRPN for their 
> > own nefarious purposes, though, so it would be good to have some 
> > way of ignoring a message that was not one of yours... 
> > 
> > > Thinking about this more, I like the idea of having a Sysex 
> > > interface to the FluidSynth command shell, which would open up 
> > > a whole world of possibilities. 
> > 
> > Yes yes! You could perhaps use one of the unused text_events ? 
> > There's text_event_08 .. text_event_0f to choose from, and you have 
> > all the length you want so could start with a "fluidsynth" string 
> > to cut down on accidents from other software with similar ideas. 
> > Likewise raw_meta_event, or even sequencer_specific ? 
> > 
> > > In regards to Sysex, I wonder what happens when a company stops paying 
> > > the yearly fee? Beyond the red "suspended" text in the manufacturer's 
> > > ID table online, I can't see what other consequence there would be. 
> > > Not that I'm suggesting anything in particular ;-) 
> > 
> > That thought has occurred to me too, not that I would ever think 
> > such things of course. Especially if the firm is vanished and 
> > their synths are no longer used ... 
> > 
> > Regards, Peter 
> > 
> > http://www.pjb.com.au address@hidden (03) 6278 9410 
> > "Follow the charge, not the particle." -- Richard Feynman 
> > from The Theory of Positrons, Physical Review, 1949 
> > 
> > 
> > _______________________________________________
> > fluid-dev mailing list
> > address@hidden
> > https://lists.nongnu.org/mailman/listinfo/fluid-dev
> >