Made a comment: https://github.com/grame-cncm/faust/pull/1381#issuecomment-6692707938
Excited for this, though...will report back on the testing results. Aaron Krister Johnson Music, etc.: https://soundcloud.com/aaron-krister-johnson https://soundcloud.com/filtercreed https://www.youtube.com/channel/UC_utjGYbSizWE0dNyr0Vdmg https://aaronkristerjohnson.bandcamp.com/ http://www.untwelve.org Code: https://github.com/akjmicro <http://www.untwelve.org> On Fri, Nov 6, 2026 at 11:19 AM Aaron Krister Johnson <[email protected]> wrote: > Absolutely! Thanks for doing this! > > Aaron Krister Johnson > Music, etc.: > https://soundcloud.com/aaron-krister-johnson > https://soundcloud.com/filtercreed > https://www.youtube.com/channel/UC_utjGYbSizWE0dNyr0Vdmg > https://aaronkristerjohnson.bandcamp.com/ > http://www.untwelve.org > Code: > https://github.com/akjmicro <http://www.untwelve.org> > > > On Fri, Nov 6, 2026 at 11:10 AM Stéphane Letz <[email protected]> wrote: > >> Hi Aaron, >> >> A Claude Opus made branch to test + PR to explain how it works, see: >> https://github.com/grame-cncm/faust/pull/1381 >> >> Can you test and report ? >> >> Thanks. >> >> Stéphane >> >> > Le 6 nov. 2026 à 17:35, Aaron Krister Johnson <[email protected]> a >> écrit : >> > >> > Hi there, Faust devs! >> > >> > I'm wondering if you'd be welcoming of a commit/pull-request to solve >> an itch I have for Faust: the ability to build the ability to take >> > a `-mchan` parameter on the command line for any built app that reads >> midi, such that it behaves by only responding to a certain MIDI channel. >> > >> > I'm frankly amazed that no-one has requested this prior, but I find for >> my workflow, at least, this is the biggest cause of friction I have working >> with Faust >> > executables. The default out-of-box behavior of a synth responding to >> all channels for MIDI_NOTE_ON, MIDI_NOTE_OFF, MIDI_PITCH_BEND etc. >> > is killing me! I end up having to use Faust to produce a C++ file, then >> manually add something like: >> > >> > if (status == MIDI_NOTE_ON & channel == 1) {. // channel == 1 means >> midi channel 2, i.e. only respond to channel 2 >> > ... >> > } >> > >> > ... in the resulting code. >> > >> > As you can see, that's a bit annoying. Better would be able to take the >> executable, and when running, dynamically decide I want to respond only to >> a certain channel: >> > >> > ./my_synth -mchan 2 -port 5514 >> > >> > I suppose even better would be to have the special keywords `freq` and >> `mkey` be able to take params that filter by MIDI channel, too. But for >> now, the above calling convention, >> > I think, would suffice. >> > >> > LMK your thoughts. I'd hate to make changes for a PR branch and then >> not have be welcome into the codebase. >> > >> > Thanks, >> > >> > Aaron Krister Johnson >> > Music, etc.: >> > https://soundcloud.com/aaron-krister-johnson >> > https://soundcloud.com/filtercreed >> > https://www.youtube.com/channel/UC_utjGYbSizWE0dNyr0Vdmg >> > https://aaronkristerjohnson.bandcamp.com/ >> > http://www.untwelve.org >> > Code: >> > https://github.com/akjmicro >> > _______________________________________________ >> > Faudiostream-users mailing list >> > [email protected] >> > https://lists.sourceforge.net/lists/listinfo/faudiostream-users >> >>
_______________________________________________ Faudiostream-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/faudiostream-users
