Reaticulate - articulation management for REAPER - 0.5.13 released (2024-02-19)

[Vagalume]

I had a little time last night to test Reaticulate. One of the things that I thought was that if you are using a library with so many articulations, for instance Spitfire Symphonic Strings, and you want to add the whole V1 you will have to scroll a lot. I know this is not really important, but perhaps it would be possible to change the GUI so more articulations are seen. I don’t know how it is the best way to achieve it, anyway I have modified a screenshot in photoshop to make myself understood because my English is poor.




I tried to do the same as you did in your video with chamber Strings V1, but using SSS:
As I said yesterday it worked but this Error message appeared: bank conflict on same channel SSS- V1 Core. Maybe the message has to do with the Kontakt factory banks, in fact SSS V1 Core and V1 Decorative share an articulation (both have Sul Pont) and both patches sound at the same time when selected with this concrete articulation, no idea. Besides Reaticulate doesn’t select V1 Core flautando, of course it is possible to do it with the mouse in the patch itself. Finally, this message appears every time I add a second bank except If I use 2 patches of Spitfire Chamber Strings, with this library the message doesn’t appear. Some screenshots, maybe I did something wrong...

[tack]

Originally Posted by Vagalume

I know this is not really important, but perhaps it would be possible to change the GUI so more articulations are seen. I don’t know how it is the best way to achieve it, anyway I have modified a screenshot in photoshop to make myself understood because my English is poor.

I do understand what you mean. This goes more generally to the point of having the UI adapt better to different widths. I need to give some thought to this, and it'll be a longer term to-do item for sure.

Originally Posted by Vagalume

Maybe the message has to do with the Kontakt factory banks, in fact SSS V1 Core and V1 Decorative share an articulation (both have Sul Pont) and both patches sound at the same time when selected with this concrete articulation, no idea.

This is exactly the reason for the warning. It's safe to ignore in this case. I've committed a fix for that (as it was reported over on The Sound Board) and it'll be in the next release.

As for the Masse conflict, this is expected as these patches definitely do conflict (the patches themselves use the same UACC numbers and so they conflict). The only way to deal with this is to put them on different channels in Kontakt, and use dedicated source and destination channels in the Reaticulate bank configuration.

For example, Strings on source and destination channel 1, and Brass on source and destination channel 2 (with the Kontakt patches assigned accordingly). But then you would need to switch your controller to the appropriate channel as well. (I think perhaps the UX could be improved there.)

The same issue applies with Albion ONE Strings being on the same channel as SSS. The underlying patches themselves conflict and so can't be on the same channel.


Thanks for the feedback!

[swiiscompos]

Hi, this look great but for some reason the Reabank files don't seem to match any of my libraries (all Spitfire), any idea why that would be the case? I'm on mac if that makes any difference (but I don't think it should).

[tack]

Originally Posted by swiiscompos

for some reason the Reabank files don't seem to match any of my libraries (all Spitfire), any idea why that would be the case?

Make sure you set the patches to "Locked to UACC". (The little note field for each of the Spitfire banks says "Set patch to UACC", and in general that message will give patch configuration information if relevant.)

The factory banks using Spitfire send UACC (CC32) events to trigger articulations, not the out-of-box note-based keyswitches.

[Mordi]

I would have liked to see how one uses this in practice, after it's set up. The basic workflow. Do you enter step record-mode and go from there, or is there a way to just place the edit-cursor down where you want an articulation to start and then press one of the given articulations?

[swiiscompos]

Originally Posted by tack

Make sure you set the patches to "Locked to UACC". (The little note field for each of the Spitfire banks says "Set patch to UACC", and in general that message will give patch configuration information if relevant.)

The factory banks using Spitfire send UACC (CC32) events to trigger articulations, not the out-of-box note-based keyswitches.

Thanks, I totally missed that. It sorks perfectly now!

[mikeroephonics]

This looks really interesting! Thanks so much for coming up with this idea and bringing it to life!

I can't seem to get it to work. I ran the Action "Script: Reaticulate_Main.lua", then clicked on the [Add Reaticulate FX] button to add the "JS: Reaticulate" effect to a TCP, but the JS is in offline mode and I can't get it to come online. The FX window reads: "The following effect plug-in could not be loaded."

I'm not sure why.

Aside from that, I have one question regarding Bank/Program Change entry: Can this plug-in let you insert a Bank/Program Change Message at the edit cursor position by clicking on an articulation in Reaticulate's GUI? This would be a very intuitive and fast way to insert articulations note-by-note.

I wrote a Feature Request for faster Bank & Program Change Entry which you might find interesting:

FR: Faster Bank & Program Change Entry & Editing
https://forum.cockos.com/showthread.php?t=158415

[tack]

Originally Posted by Mordi

I would have liked to see how one uses this in practice, after it's set up. The basic workflow. Do you enter step record-mode and go from there, or is there a way to just place the edit-cursor down where you want an articulation to start and then press one of the given articulations?

Workflow will of course vary by individual. You can step record articulation changes in the MIDI editor, or perform them live. (Articulations are activated either by clicking on them, or via one of the actions.)

I'm but a lowly hobbyist, but I find I do some kind of hybrid, where I sketch in something rough by triggering an articulation in the vicinity of what I want (longs for chords, legato, basic shorts, pizzicato), hack away at something live recording, and then go in afterward in the MIDI editor and massage the articulations (and other MIDI events) to be more specific.

Originally Posted by mikeroephonics

I can't seem to get it to work. I ran the Action "Script: Reaticulate_Main.lua", then clicked on the [Add Reaticulate FX] button to add the "JS: Reaticulate" effect to a TCP, but the JS is in offline mode and I can't get it to come online. The FX window reads: "The following effect plug-in could not be loaded."

Wow, I'm afraid I've never seen that before either. What happens if you manually insert the Reaticulate JSFX (and drag it to the top of the chain)? Or what happens if you restart Reaper and try?

Originally Posted by mikeroephonics

Aside from that, I have one question regarding Bank/Program Change entry: Can this plug-in let you insert a Bank/Program Change Message at the edit cursor position by clicking on an articulation in Reaticulate's GUI? This would be a very intuitive and fast way to insert articulations note-by-note.

Yes, but it works by step-input in the MIDI Editor. So you open the MIDI editor, enable step input, and then any activated articulation will be inserted at the edit position.

The exception to that is if a program change is selected: in this case, the activated articulation will replace the selected program change, even if it happens to not be at the edit cursor.

Originally Posted by mikeroephonics

I wrote a Feature Request for faster Bank & Program Change Entry which you might find interesting

Yeah, a bit related to the way Reaticulate works, isn't it. At least in that one aspect of Reaticulate provides a simple GUI to inject program changes into MIDI items. The idea of a most recently used set of articulations being more easily accessible is interesting.

[pcartwright]

Originally Posted by mikeroephonics

I can't seem to get it to work. I ran the Action "Script: Reaticulate_Main.lua", then clicked on the [Add Reaticulate FX] button to add the "JS: Reaticulate" effect to a TCP, but the JS is in offline mode and I can't get it to come online. The FX window reads: "The following effect plug-in could not be loaded."

Not sure if this helps, but...

This happened to me when I tried to use the script immediately after downloading (using ReaPack). I needed to restart Reaper before the JSFX was accessible and usable.

[mikeroephonics]

Originally Posted by tack

Wow, I'm afraid I've never seen that before either. What happens if you manually insert the Reaticulate JSFX (and drag it to the top of the chain)?

I got it to work by manually inserting the JS. Also, I had the offline problem with two machines (my laptop and DAW PC, both on Windows 7, if that matters.)

This is a very cool utility which I'm definitely looking into this weekend! I actually built a .ReaBank for my Vienna Symphonic Library 'Horizon Series' libraries, which is over 10,200 lines long. I'm going to see how Reaticulate can help work with such a daunting amount of articulations.

Thanks for all the work you put into this!

[o_e]

Hi,

After installing via Reapack, when I try to lauch reaticulate_main, I get the following error warning (see screenshot), what am I missing?

[tack]

Originally Posted by o_e

After installing via Reapack, when I try to lauch reaticulate_main, I get the following error warning (see screenshot), what am I missing?

Reaticulate_Main.lua first looks for the source code in .../Scripts/Reaticulate/app/main.lua and if it can't find it, it thinks this must be a binary install and tries to load a different thing. This is dormant code though, part of an experiment to see if precompiled binaries were faster (it was not measurably faster) -- it must mean ReaPack didn't install it properly.

Does Scripts/Reaticulate/app/main.lua exist for you?

Hopi ran into this as well (on Windows) and found that with a fresh profile the problem went away. Hopi did you ever find root cause?

Unfortunately I've not been able to reproduce it.

[o_e]

Originally Posted by tack

Reaticulate_Main.lua first looks for the source code in .../Scripts/Reaticulate/app/main.lua and if it can't find it, it thinks this must be a binary install and tries to load a different thing. This is dormant code though, part of an experiment to see if precompiled binaries were faster (it was not measurably faster) -- it must mean ReaPack didn't install it properly.

Does Scripts/Reaticulate/app/main.lua exist for you?

Hopi ran into this as well (on Windows) and found that with a fresh profile the problem went away. Hopi did you ever find root cause?

Unfortunately I've not been able to reproduce it.

Hi,

Thanks for the quick answer!

I'am on Mac OS 10.9.5 aka Mavericks and in Scripts/Reaticulate is no folder 'app', only one folder 'actions'.
What do you mean with 'a fresh profile'?
Is there a way to get the 'main' folder manually somehow?

Edit: When in browse Reapack and type in 'reaculate' a lot of scripts are shown, a part of them not installed. When I try to install them via rightclick nothing get installed (see screenshot https://imgur.com/NXU9Wun)..

[sfiks]

Originally Posted by o_e

Hi,

Thanks for the quick answer!

I'am on Mac OS 10.9.5 aka Mavericks and in Scripts/Reaticulate is no folder 'app', only one folder 'actions'.
What do you mean with 'a fresh profile'?
Is there a way to get the 'main' folder manually somehow?

Edit: When in browse Reapack and type in 'reaculate' a lot of scripts are shown, a part of them not installed. When I try to install them via rightclick nothing get installed (see screenshot https://imgur.com/NXU9Wun)..

This is how it looks like on my Mac OS 10.8.4

[o_e]

Originally Posted by sfiks

This is how it looks like on my Mac OS 10.8.4

As I said, in my folder ..Scripts/Reaticulate there is only one folder 'actions' the others are missing. How can I get them?
Could this be an OS problem? I can't hardly believe that..

[sfiks]

Originally Posted by tack

I welcome all bug reports, suggestions, and other feedback, either here, or on the GitHub issue tracker.

Thank you for this very helpful tool. I love it!
I noticed insignificant "bug" that doesn't affect the flow and sound,
just irritates a little bit

when i run 1st articulation

//! c=long i=tremolo g=3 o=note-hold:25/note-hold:106
91 Tremolo ordinary Volume - CC1

and change CC1 from 0 to 127 it does what it suppose to do,
but 2nd articulation gets selected on the GUI:

//! c=textured i=pizz g=3 o=note:29/note:106/cc:01,0
96 Pizz. ordinary Volume - VELOCITY

Somehow value 0 of CC1 (volume of 1st articulation) affects the 2nd articulation. The 2nd articulation doesn't get triggered - it's just gets selected on GUI.

Could I code something to get rid of that?

Thank you,
Slava

[tack]

Originally Posted by o_e

As I said, in my folder ..Scripts/Reaticulate there is only one folder 'actions' the others are missing. How can I get them?
Could this be an OS problem? I can't hardly believe that..

I honestly don't know what the root cause is, but it can't be just Mac because Hopi is running Windows and saw the same thing.

Hopi found that when he did a fresh portable install to another location and installed ReaPack and SWS there (all other things being equal -- including OS) he was not able to reproduce the problem and things installed fine.

If you're comfortable, it would be helpful to do a complete backup (Options / Preferences / General) and pass the resulting zip file to me. It'd help me reproduce.

Meanwhile you could install it the old manual way:

1. Download https://github.com/jtackaberry/reati...ve/release.zip
2. Extract the reaticulate-release folder within the zip to your REAPER Scripts/ directory -- %AppData%\REAPER\Scripts on Windows
3. Rename reaticulate-release to Reaticulate
4. Move jsfx/Reaticulate.jsfx up to the Effects/ directory (which exists on the same level as Scripts/) -- %AppData%\REAPER\Effects on Windows
5. In Reaper, open the Actions dialog and click the "Load ..." button in the bottom right
6. Navigate to Scripts/Reaticulate/actions/ and select all files in that directory, and then click the Open button

Originally Posted by sfiks

Somehow value 0 of CC1 (volume of 1st articulation) affects the 2nd articulation. The 2nd articulation doesn't get triggered - it's just gets selected on GUI.

I'm afraid I don't fully understand what you mean. Could you insert a ReaControlMIDI log after Reaticulate and show me what output events are being emitted by each of those two articulations, and then clarify what you actually expect to happen?

Thanks!

[o_e]

Originally Posted by tack

If you're comfortable, it would be helpful to do a complete backup (Options / Preferences / General) and pass the resulting zip file to me. It'd help me reproduce.

What exactly do you need?
The whole ~/Library/Application Support/Reaper folder?
Is it that what you mean? It is about 240mb big..

[tack]

Originally Posted by o_e

What exactly do you need?
The whole ~/Library/Application Support/Reaper folder?
Is it that what you mean? It is about 240mb big..

I was thinking of a configuration export (via the "Export Configuration" option from Preferences | General) but on second thought, since you have a Mac, this won't be quite as thorough as it may need to be, given I'm on PC.

I actually suspect there's a bug with ReaPack.

[cfillion]

Originally Posted by o_e

When I try to install them via rightclick nothing get installed (see screenshot https://imgur.com/NXU9Wun)..

Can you send me a video or gif (http://cockos.com/licecap/) of this not working in action? If there's a bug I'd love to fix it (it works here on macOS 10.10). Does the Transaction Report dialog (shown when installation is finished) lists anything in the Errors tab?

@tack I strongly recommend packaging every required files in a single Reaticulate package. Listing every single file as individual packages begs for partial installs/updates and clutters the package list.

Index example: http://sprunge.us/FLOU (I would have suggested the @provides tag if you used reapack-index but you seem to have built the index yourself! )
Result: https://i.imgur.com/LyaJEZf.gif

[o_e]

Originally Posted by cfillion

Can you send me a video or gif (http://cockos.com/licecap/) of this not working in action? If there's a bug I'd love to fix it (it works here on macOS 10.10). Does the Transaction Report dialog (shown when installation is finished) lists anything in the Errors tab?

Which part exactly do you want to see in the gif?

[cfillion]

Originally Posted by o_e

Which part exactly do you want to see in the gif?

Trying to install the missing packages with right click > Install/update selection and it failing to install everything (with the download progress dialog visible and, at the end, Transaction report).

Like this (except here it works): https://i.imgur.com/gXmuJ9t.gif

[o_e]

Originally Posted by cfillion

Trying to install the missing packages with right click > Install/update selection and it failing to install everything (with the download progress dialog visible and, at the end, Transaction report).

Like this (except here it works): https://i.imgur.com/gXmuJ9t.gif

I tried to make a gif of a fresh install, this time everything goes flawlessly, so sorry for the noise!

[tack]

Originally Posted by cfillion

@tack I strongly recommend packaging every required files in a single Reaticulate package. Listing every single file as individual packages begs for partial installs/updates and clutters the package list.

Oh, yes, this makes much more sense.

The directory structure, maybe less so. I really would like Scripts/Reaticulate/{actions,app,img} but of course everything is nested under the category, so it ends up as Scripts/Reaticulate/MIDI Articulations/{actions,app,img}

I can set the category name to '.' which creates the directory tree I want, even if the ReaPack UX is a little dubious as a result. (You may have noticed that I used this kludge already to get Reaticulate-factory.reabank at the top level.)

Is there a non-kludgy way to accomplish that?

Originally Posted by cfillion

but you seem to have built the index yourself!

I did. I didn't hand-sling it of course, but a trivial python script was all it took. Ultimately it came down to my not being able to make reapack-index behave how I wanted (notably not be dependent on git commits, but also some directory structure aspects), and so I figured it would have been easier just to build my own index.

Thanks for the tip!

Unfortunately the user experience of upgrading isn't all that it might be (on Windows anyway): when I refresh the package, first a "ReaPack Query" dialog pops up warning of obsolete packages, but at the same time, a progress bar pops up over top the query dialog, hanging there at 50%. I had sat there staring at it for a good half minute, thinking ReaPack hung, when I noticed the presence of the ReaPack Query dialog, which is actually modal but yet was initially underneath the progress dialog.

[tack]

I see there is an unintended consequence to setting category name='.' which is that when I bump the version number, ReaPack ends up deleting all the files. :/

Edit: Keeping the category name but prefixing all file paths with ../ seems to work. How much am I tempting fate here?

[rogpfreck]

Great job with the http://reaticulate.com/ website and video. Although haven't quite got through the Custom Bank video part as yet. That needs some serious concentration!

Installed on Mac (OS High Sierra, 10.13.1). Works well with Albion One and CS2.

Thank you!

[daeavelwyn]

OMG ! Thanks so much man for your work ! It's awsome !

A trivial question : How can I change the background color to fit more with my theme ? :-D

[tack]

Originally Posted by daeavelwyn

A trivial question : How can I change the background color to fit more with my theme ? :-D

Hm, it should automatically use your theme's background color. Which theme are you using?

[daeavelwyn]

I'm using cubic pack 2 (https://stash.reaper.fm/theme/2016/CubicPack2.zip)

here is the screenshot : https://imgur.com/a/7NOoh

And whatever is the them i'm using it's brown ...

[_Stevie_]

A question that hasn't been asked yet: tack, where can we donate?

[tack]

Originally Posted by daeavelwyn

And whatever is the them i'm using it's brown ...

Yeah, that was a silly bug. I've fixed it, and it'll land in the next release (I hope tomorrow), but meanwhile hopefully you can live with the horribly ugly UI.

[tack]

Originally Posted by _Stevie_

A question that hasn't been asked yet: tack, where can we donate?

I'm truly humbled that you feel compelled to compensate me for my work! But please take all the money you're inclined to give me and instead donate it to MSF (Doctors Without Borders) [Canada / US] or the EFF.

[daeavelwyn]

Originally Posted by tack

Yeah, that was a silly bug. I've fixed it, and it'll land in the next release (I hope tomorrow), but meanwhile hopefully you can live with the horribly ugly UI.

Not sure I will survive

[_Stevie_]

Originally Posted by tack

I'm truly humbled that you feel compelled to compensate me for my work! But please take all the money you're inclined to give me and instead donate it to MSF (Doctors Without Borders) or the EFF.

Done!
Ah, Jason, you're such a great person! *group hug*

[tack]

Thanks Stevie.

[cfillion]

Originally Posted by tack

I see there is an unintended consequence to setting category name='.' which is that when I bump the version number, ReaPack ends up deleting all the files. :/

Fixed this path parsing bug for the next update, thanks! However, category names should not contain dot, dotdot, or any other special names (such as Windows device names). There will likely be additional validation for this in the future.

Originally Posted by tack

Edit: Keeping the category name but prefixing all file paths with ../ seems to work. How much am I tempting fate here?

This is the correct way. You can go back using .. up to <resource path>/Scripts/<your repo> (type="..." on <source> or <reapack> must be used to write elsewhere than Scripts in the resource directory).

Originally Posted by tack

Unfortunately the user experience of upgrading isn't all that it might be (on Windows anyway): when I refresh the package, first a "ReaPack Query" dialog pops up warning of obsolete packages, but at the same time, a progress bar pops up over top the query dialog, hanging there at 50%. I had sat there staring at it for a good half minute, thinking ReaPack hung, when I noticed the presence of the ReaPack Query dialog, which is actually modal but yet was initially underneath the progress dialog.

This is first time I heard this happens. Is that window shown underneath the progress dialog every time for you, or was it just this one time?

[tack]

Originally Posted by cfillion

This is first time I heard this happens. Is that window shown underneath the progress dialog every time for you, or was it just this one time?

It's consistent:

https://www.youtube.com/watch?v=wMSrQBZkxUk

[sfiks]

Thanks again, Jason!
I don't have 88 keys keyboard and it was always clumsy
to work with XSample library play instruments using key-switches.
Not anymore! I continue working on articulations for those!

Here are 23 out of 48 articulations for
XSample Solo strings score instruments.
(If somebody's interested, let me know and I'll expand it

//----------------XSample/Strings score ----------------

//! g="XSample/strings" n="strings score"
Bank 02 1 Strings score

//! c=legato i=vibrato g=3 o=cc:00,00
00 vibrato cc1

//! c=legato i=legato-vibrato g=3 o=cc:00,01
01 senza vibrato cc1

//! c=default i=vibrato-con-sord g=3 o=cc:00,02
02 vibrato con sord. cc1

//! c=default i=legato-vibrato g=3 o=cc:00,03
03 senza vibrato con sord. cc1

//! c=long i=tremolo g=3 o=cc:00,04
04 tremolo cc1

//! c=long i=harmonics g=3 o=cc:00,05
05 harmonics cc1

//! c=short i=spiccato g=3 o=cc:00,06
06 spiccato velocity

//! c=short i=marcato-quarter g=3 o=cc:00,07
07 marcato velocity

//! c=textured i=pizz g=3 o=cc:00,08
08 pizz. velocity

//! c=textured i=pizz-bartok g=3 o=cc:00,09
09 pizz. bartok velocity

//! c=textured i=col-legno g=3 o=cc:00,10
10 col legno velocity

//! c=fx i=fx g=3 o=cc:00,11
11 finger velocity

//! c=fx i=note-sixteenth g=3 o=cc:00,12
12 sul pont. short velocity (C-b, V-c)

//! c=fx i=sul-pont g=3 o=cc:00,13
13 sul pont. cc1

//! c=fx i=tremolo-sul-pont g=3 o=cc:00,14
14 sul pont. tremolo cc1

//! c=fx i=tremolo-harmonics g=3 o=cc:00,15
15 harmonics tremolo cc1

//! c=fx i=legato-gliss g=3 o=cc:00,16
16 harmonics gliss. cc1

//! c=default i=legato-gliss g=3 o=cc:00,17
17 harmonics gliss. con sord. cc1

//! c=fx i=tremolo-harmonics-a g=3 o=cc:00,18
18 harmonics gliss. tremolo cc1

//! c=default i=tremolo-harmonics-a g=3 o=cc:00,19
19 harmonics gliss. tremolo con sord. cc1 (C-b)

//! c=fx i=legato-gliss g=3 o=cc:00,20
20 harmonics gliss. artificial cc1 (V-no, V-la)

//! c=fx i=run-major g=3 o=cc:00,21
21 glissandi cc1 (V-c)

//! c=default i=run-major g=3 o=cc:00,22
22 glissandi con sord. cc1 (V-c)

//! c=fx i=run-major g=3 o=cc:00,23
23 short gliss. cc1 (C-b)

[cfillion]

Originally Posted by tack

It's consistent:

https://www.youtube.com/watch?v=wMSrQBZkxUk

Ah yes, I see what's causing this (fixed for next update). Thanks for the video! It only happens when downloading the index + finding the obsolete packages is quicker than the progress dialog opening delay (100ms).

(It's less likely to happen when using Synchronize packages.)

[sfiks]

Here is a quick demo with XSample V-no I (play instrument)
Full screen is recommended