Is there a way to make it relative to the chosen channel in group 1 or at least to send it to all channels?
There currently isn't a way to have an output event pass through to the the existing target channels. With the prerelease version I wrote about earlier, it's possible to blast the output event to all channels and not affect future routing. This might be good enough. It would look like this:
Code:
//! c=long-light i=con-sord g=2 o=cc:16@-1,127/cc:16@-2,127/cc:16@-3,127/cc:16@-4,127/cc:16@-5,127/cc:16@-6,127/cc:16@-7,127/cc:16@-8,127/cc:16@-9,127/cc:16@-10,127/cc:16@-11,127/cc:16@-12,127/cc:16@-13,127/cc:16@-14,127/cc:16@-15,127/cc:16@-16,127
7 con sordino on
Yeah, it's not pretty. And it uses the full limit of the number of output events (16). It leverages a new feature in the next version to not affect channel routing by prefixing the target channel with a - sign. So this articulation will fire CC 16 value 127 on all 16 channels but not interfere with any routing that was set up by a previous articulation.
But here's the problem with this approach: Reaper only chases the last program change per channel. So if your "con sordino on" program appears after a spiccato articulation, say, and you manually change the articulation in your patch to long (or whatever), depending on where the edit cursor is, Reaper could chase the con sordino (resending all those CC16-127 messages) but not the spiccato.
It's a limitation of using program changes that we'll just have to live with. This is something that proper articulation map support in Reaper should theoretically address.
such options are good to implement, but it will trougth a big modification of comunication protocol between script and JS as I understand.
Some features would require such an overhaul. It essentially comes down to how much per-track state am I able to store in the JSFX. Currently I have room for about 90 bytes, and there's just only so much you can squeeze into 90 bytes.
Fortunately, the kind of behavior Divico asked for wouldn't depend on that. It actually wouldn't be very difficult to implement I think.
few words about list of articulations appearance - what about autoscroll option? (if list not fit a screen, it needs to manually scroll for see, what articulation is selected - for example, if an instrument has about 50 articulations, like VSL, WarpIV or EW Hollywood).
Do you mean that the list autoscrolls during playback as different articulations are selected?
Also, as idea, a font size option for the list and more than one column list appearance may be a good addition.
Ctrl-mousewheel lets you adjust the zoom level. This affects the entire Reaticulate UI though, icons included, not just font. But maybe it's good enough for you. A couple other users have asked for multiple columns of articulations and I understand the use-case but it's pretty low on my radar.
I think, the better to take selected items at first, then, if nothing is selected - put art on the selected track
But this only makes sense if the currently selected track and the track with the selected MIDI item have the same banks. Otherwise you could easily end up inserting a program change referenced by a bank on the selected track that just doesn't make sense on the track with the selected MIDI item. And I'm not sure I like the idea of an exception here (i.e. if the bank on the selected track is compatible with the track containing the selected MIDI item then insert it into the selected item, otherwise insert at the item under the cursor on the selected track). I think that UX starts to become too confusing.
And something is going on with undo points here
Yes, I've noticed this too. It's on the to-do list to investigate. Might be a regression due to the amount of hacking I've needed to do to prevent Reaticulate from mangling the last touched FX. This is another area where I have to go through some
heroics to work around limitations in Reaper's API.
Hmm. I left click. Does right clicking do something different?
In the prerelease, right clicking an articulation always inserts a program change in the MIDI item under the edit cursor on the selected track. Even if the MIDI editor isn't open. (Or if the MIDI editor is open but step record isn't turned on.)