Reaticulate - articulation management for REAPER - 0.4.0 now available

Vadium

Active Member
Hi @tack ,
I reached the limitation of 16 midi ports. But VePro provides 48 and I use almost all (for example, 42 ports needs to use HS 1st violins in MPE mode) - is it possible to increase this limit to 48?

hm.. I think it's an internal Reaper limitation, yes? I can bypass it by opening Vepro inside Plogue Bidule inside Reaper, but it means that I should use additional soft anyway, instead of a pure combination of Reaper+Reaticulate, yes?

Also feature request, maybe in the distant future - multiple CC remapper. there are many instruments with different hard-preassigned CC to controls, like EW Play instruments, where users often want to reassign CC11 to CC7, CC2 to CC1 and CC1 to CC11 on the fly. As variant, graphically it can be realized as popup menus in Bidule (see att.pic.)
 

Attachments

Last edited:
OP
tack

tack

Damned Dirty Ape
hm.. I think it's an internal Reaper limitation, yes?
Yep. Reaper only allows up to 16 buses. You would first have to lobby to the Reaper Gods to extend this. :)

Also feature request, maybe in the distant future - multiple CC remapper.
Why wouldn't the stock MIDI CC Mapper JSFX work here? Do you mean per articulation CC remapping?

I can see that different instruments would necessitate different mappings, but with a track-per-instrument approach wouldn't track-level CC remapping be ok?
 

Vadium

Active Member
You would first have to lobby to the Reaper Gods to extend this.
Yes, I started to do it on September 23) but, as I see, only 2 people want it - it's a very quiet request for Gods ))


but with a track-per-instrument approach wouldn't track-level CC remapping be ok?
in most cases - yes, it will enough. but for such crazy people as me - no, because if in one bank there are different instruments placed on different MIDI buses (all articulations routed to VSL sync strings, but legato - to HS strings) - different mapping required for different buses..:cool:
 
Last edited:

Vadium

Active Member
if anyone does not know, it's possible to change the articulation by double-clicking on the event (or set a mouse modifier on your taste (Midi editor/double click on MIDI CC event) :

Articulation changing.gifScreen Shot 2019-10-17 at 05.15.43.JPEG
 
Last edited:
OP
tack

tack

Damned Dirty Ape
0.3.91 is now available via the pre-release ReaPack:

Code:
https://reaticulate.com/prerelease.xml
See here for more detailed download instructions. Those of you already on the pre-release track should automatically receive it (provided you haven't pinned to a specific version).

These are the changes since the last prerelease (0.3.90):

New Features

  • Allow user-configurable background color (in Settings page)

Minor Enhangements

  • Improved text entry widget behavior
  • Add bus number to output event description in status bar
  • Clean up after deleted/deactivated Reaticulate JSFX instances (#77)
  • Minor robustness improvements

Bug Fixes

  • Fix regression from 0.3.90 where output events' destination channels would be ignored
  • Fix unreadable status bar text on light themes
 
OP
tack

tack

Damned Dirty Ape
0.3.92 is now available via the pre-release ReaPack:

Code:
https://reaticulate.com/prerelease.xml
See here for more detailed download instructions. Those of you already on the pre-release track should automatically receive it (provided you haven't pinned to a specific version).

Your Help Needed!

Bug reports for the 0.4.x pre-release cycle has been suspiciously few given the magnitude of change in this release. If you use the pre-release I'm interested to hear about your experience even if you haven't encountered any problems. If you haven't, I'd be grateful if you could take it out for a spin and test out some of your existing projects.


These are the changes since the last prerelease (0.3.91):

New Features

  • Add option for undocked windows to be borderless (requires a fairly recent version of the js_ReaScript_API extension)
  • When the MIDI editor is open and notes are selected, articulations will insert just ahead of the first selected note rather than at the edit cursor. (Right- or double-clicking articulations are still used for insertion.)
  • Much better support for light themes

Minor Enhancements

  • Minor cosmetic enhancements, especially on Mac

Bug Fixes

  • Fix regression from 0.3.90 where output events may not be sent to the proper channel. (The fix for this in 0.3.91 was incomplete.)
 

Vadium

Active Member
Double clicking an articulation or invoking any of the activate articulation actions twice within 500ms will force insert the articulation in the MIDI item at the edit cursor. (This is equivalent to right clicking, which behavior still exists.)
Hi Tack,
this manner works only in 5% for me on macOS - strange. I have tried as very quick double-clicks (completely not work), as close to 499ms (work in 5% cases, after placing a cursor to the new timeline place)

Update: it's work ok, if the MIDI editor is closed, but if I place a cursor inside MIDI Editor open - 5%
 
Last edited:
OP
tack

tack

Damned Dirty Ape
this manner works only in 5% for me on macOS - strange. I have tried as very quick double-clicks, as close to 499ms)
Hm, I'm not able to reproduce on OS X. Is right-clicking working consistently or is it also intermittent? Is the behavior the same in these scenarios?
  1. MIDI editor open with notes selected (relevant if using 0.3.92)
  2. MIDI editor open with notes unselected
  3. MIDI editor closed but track selected and edit cursor over a MIDI item
Also, when you double click is the button drawing as depressed for both clicks?

Like this:
2xclick.gif
 
Last edited:

Vadium

Active Member
right-clicking working OK

MIDI editor open with notes selected or unselected - 5%

MIDI editor closed but track selected and edit cursor over a MIDI item - working OK


when you double click is the button drawing as depressed for both clicks?
only 1 time for 2 clicks at all
 

Vadium

Active Member
All introduced features of 0.3.90-92 except a double click are work for me on macOS 10.13.6, thanks a lot!

It may be useful mode of pitchrange=60-72 - to mute notes, that out of range
 
Last edited:
OP
tack

tack

Damned Dirty Ape
All introduced features of 0.3.90-92 except a double click are work for me on macOS 10.13.6, thanks a lot!
Great! Thanks for the feedback.
It may be useful mode of pitchrange=60-72 - to mute notes, that out of range
I did offer that as a possibility (behavior #2) but you seemed more interested in the clamping behavior. ;)

Will consider it for a future release. It's should be possible without too much effort.
 
OP
tack

tack

Damned Dirty Ape
but it's not as relevant as the ability to send to all channels at once to avoid such a nightmare))
Yikes, I see what you mean. And that won't even actually work, because the maximum output events you can have is 16.
 
OP
tack

tack

Damned Dirty Ape
0.3.93 is now available via the pre-release ReaPack:

Code:
https://reaticulate.com/prerelease.xml
See here for more detailed download instructions. Those of you already on the pre-release track should automatically receive it (provided you haven't pinned to a specific version).

Your Help Needed!

Barring reported bugs, this version will be promoted from pre-release to 0.4.0. Any time you are able to spend testing and providing feedback about issues (or lack thereof!) is most appreciated.


These are the changes since the last prerelease (0.3.92):

Minor Enhancements

  • More intelligent articulation insertion logic when notes are selected. Program changes will now be inserted at gaps in the selection, and the channel of the note will be used for the program change rather than the default channel.
  • Delay refocusing the MIDI editor (if open) when double clicking articulations to reduce window focus flicker

Bug Fixes

  • Fix minor text cropping bug when the window is a certain width
 
OP
tack

tack

Damned Dirty Ape
Reaticulate 0.4.0 is now available!

Thanks to everyone who helped with testing during the pre-release cycle. Your feedback was invaluable.

You can read much more in the release notes on the website which expands on the highlights of this release.


Installing

If you're a new user (not upgrading), just follow these installation instructions.


Upgrading

For those of you on the release track, you should eventually receive the update, but you can force it by following the updating instructions. Those using the prerelease track will receive this update as well, plus of course all the prereleases leading up to 0.5.0.


Here are the changes since 0.3.2:


New Features
  • This release introduces support for multiple MIDI buses. Anywhere previously involving a destination MIDI channel can now optionally include a MIDI bus number as well. Among other things, this allows for better integration with Vienna Ensemble Pro. (#73)
  • Articulation insertion now optionally respects selected notes when the MIDI editor is open. Program changes will be inserted intelligently based on the nature of the selection.
  • Articulations can now define transformations to incoming notes after the articulation is activated. These include transposing the notes, a velocity multiplier, and pitch and velocity range clamping. (#72)
  • Output events can now be routed to destination channels set up by the previous articulation by using `-` as the channel (#42)
  • Output events can now send pitch bend MIDI messages (#60)
  • Double clicking an articulation or invoking any of the "activate articulation" actions twice within 500ms will force-insert the articulation in the MIDI item. (This is equivalent to right clicking, which behavior still exists.)
    • The old behavior of always inserting when step record is enabled has been removed in favor of this consistent approach.
  • Much better support for light themes (#6)
  • Added option for undocked windows to be borderless (requires a fairly recent version of the js_ReaScript_API extension)
  • Allow user-configurable background color (in Settings page) (#78)


Minor Enhancements
  • Added a new 'spacer' articulation attribute which adds visual padding above the articulation when shown in Reaticulate's UI (#66)
  • Bank messages (set with the 'm' attribute in the bank definition) can now be viewed from Reaticulate's main articulation list screen (#68)
  • Improved text entry widget behavior with text selection, copy/paste, etc.
  • Errors and other problems with banks or track configuration are now more visible in the articulation list screen
  • Linux: preliminary support
  • Added tremolo-180-con-sord icon
  • Many other small GUI refinements, especially on Mac

Bug Fixes
  • Fixed problem where insertion of articulations could not be undone by Reaper's undo action (#47)
  • Fixed bug where 'art' type output events combined with filter programs could hang Reaper (infinite loop) (#44)
  • Fixed bug where activating an articulation that acts as a filter to another articulation's 'art' output events could activate the wrong child program
  • Fixed bug when MIDI controller feedback was enabled where Reaticulate would sometimes install sends to the wrong track when a new project was opened
  • Avoid reloading all other track FX when Reaticulate is installed on a track (#1)
  • Mac: use the Reaper theme background color for Reaticulate's window
  • Fixed bug when opening the Reabank file editor on Windows when the path contained spaces
  • Fixed rare crash when last touch fx becomes invalid
  • Factory banks: Fixed trills and tongued legato for the Herring Clarinet
  • Do not clear serialized variables in @init per JSFX docs (#65)
 

Vadium

Active Member
That's by design. Only one articulation per group per source channel can be active at a time.
After creating a bank for a next complex instrument, I want to return to my old (impossible?) request for more overall groups.. :) I remember, that Cubase has 4 groups, but it's not enough too - there are a couple of instruments with a lot of independent switchable options (for this bass 8 groups needed, see att.pic) - is it very hard limit to programming? If make 10 groups, it will be enough for a many-many years.Screen Shot 2019-11-05 at 02.10.48.JPEG
 

Attachments