[Csnd] massign and midi interops
Date | 2017-11-21 20:23 |
From | Arthur Hunkins <000001e1d761dea2-dmarc-request@LISTSERV.HEANET.IE> |
Subject | [Csnd] massign and midi interops |
Is there any reason why commandline options (e.g., --midi-key-cps=N) and MIDI interop opcodes (e.g., midinoteoncps) cannot respond to massign 0, 0 as does midiin - that is, withactual note triggering blocked?
Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here
I'd like to be able to use --midi-key-cps, for example, to change frequency without triggering a new event. Of course MIDI keyboard keys and buttons can always be programmed as are sliders and knobs. However buttons (as well as of course keys) often default to MIDI note numbers. Sliders and knobs *so simply* respond to ctrl7; MIDI notes are by contrast a hassle. It would certainly facilitate my coding if massign 0. 0 had the same effect on --midi-key-cps=N events as it does on midiin. The commandline options and midinoteon series of opcodes are a nice set of options; IMO it is regrettable that they are limited as they are. I appreciate that the rationale behind these MIDI options was quite other than what I am trying to do; I'd simply appreciate their being made available for such usage. (I can't imagine that there'd be any backward-compatibility issues.) Art Hunkins |