Go Back   Cockos Incorporated Forums > REAPER Forums > REAPER General Discussion Forum

Reply
 
Thread Tools Display Modes
Old 05-09-2019, 11:55 PM   #401
MrVhek
Human being with feelings
 
Join Date: May 2019
Posts: 2
Default

I just sent you a message !
Thanks a lot for your help
MrVhek is offline   Reply With Quote
Old 05-14-2019, 08:19 AM   #402
Zamyen
Human being with feelings
 
Join Date: Dec 2008
Posts: 51
Default

I just wanted to chime in and thank you for this great solution Reaticulate. It's a very elegant design and solution.

I am looking around for the best place to download (non-factory) banks, for instance for the Metropolis Ark series, Cinematic Studio Brass etc.

Is there a resource / github or similar where these are available?
Zamyen is offline   Reply With Quote
Old 05-19-2019, 01:12 PM   #403
WolfgangAgustus
Human being with feelings
 
Join Date: May 2019
Posts: 4
Default Here's some more Articulations for Spitfire Libraries

Code:
//! g="Spitfire/Harp" n="Harp Main Techniques"
//! m="Set patch to UACC"
Bank 1 1 SH - main techniques
//! c=long i=note-whole o=cc:32,1
1 normale
//! c=long-dark i=harp-pdlt o=cc:32,18
18 pres de la table
//! c=long-light i=note-whole o=cc:32,29
29 flageolet
//! c=legato i=legato o=cc:32,2
2 slid
//! c=long i=tremolo o=cc:32,11
11 bisbigliando
//! c=fx i=fx o=cc:32,90
90 fx

//! g="Spitfire/Harp" n="Harp Glissandi Manual"
//! m="Set patch to UACC"
Bank 1 2 SH - glissandi manual
//! c=legato i=legato-portamento o=cc:32,121
121 whole tone
//! c=legato i=legato-portamento o=cc:32,122
122 minor harmonic
//! c=legato i=legato-portamento o=cc:32,123
123 minor melodic
//! c=legato i=legato-portamento o=cc:32,124
124 major
//! c=legato i=legato-portamento o=cc:32,125
125 pentatonic
//! c=legato i=legato-portamento o=cc:32,126
126 diminished

//! g="Spitfire/Harp" n="Harp Glissandi Legato"
//! m="Set patch to UACC"
Bank 1 3 SH - glissandi legato
//! c=legato i=legato-portamento o=cc:32,118
118 scale gliss
//! c=legato i=legato-portamento o=cc:32,119
119 full gliss & swirls

//! g="Spitfire/Percussion/Pitched" n="Celeste Techinques"
//! m="Make Sure KS is on C0"
Bank 1 4 SP - Celeste
//! c=long i=note-whole o=note:24
24 normal
//! c=long i=note-whole o=note:25
25 expressivo
//! c=short i=short o=note:26
26 tight

//! g="Spitfire/Keyboards/Harpsichord" n="Harpsichord Stops"
//! m="Set globally all stops for C0-F#0 by Keyswitch (CTRL+Click to set Spitfire KS values for this instrument)"
Bank 1 5 SHC - Harpsichord
//! c=long i=note-whole o=note:24
24 low 8'
//! c=long i=note-whole o=note:25
25 hi 8'
//! c=long i=note-whole o=note:26
26 hi & low 8'
//! c=long i=note-whole o=note:27
27 hi and low 8' & hi 4'
//! c=long i=note-whole o=note:28
28 hi 4' & lo 8'
//! c=long i=note-whole o=note:29
29 low 8' buffered (lute)
//! c=long i=note-whole o=note:30
30 hi 8' buffered (lute)

//! g="Spitfire/Percussion/Pitched" n="Glockenspiel Techniques"
//! m="Make Sure KS is on C0"
Bank 1 10 SP - Glockenspiel
//! c=long i=note-whole o=note:24
24 normal
//! c=long-light i=note-whole o=note:25
25 muted
//! c=long-dark i=note-whole o=note:26
26 hard sticks
//! c=long i=tremolo o=note:27
27 roll

//! g="Spitfire/Percussion/Pitched" n="Marimba Techniques"
//! m="Make Sure KS is on C0"
Bank 1 11 SP - Marimba
//! c=long i=note-whole o=note:24
24 normal
//! c=long i=tremolo o=note:25
25 roll

//! g="Spitfire/Percussion/Pitched" n="Timpani Techniques"
//! m="Make Sure KS is on C0"
Bank 1 12 SP - Timpani
//! c=long i=note-whole o=note:24
24 normal
//! c=long-light i=note-whole o=note:25
25 muted
//! c=long i=tremolo o=note:26
26 roll
//! c=long-light i=tremolo o=note:27
27 roll muted
//! c=textured i=cresc-mf-half o=note:28
28 swell mf
//! c=textured i=cresc-f-half o=note:29
29 swell f

//! g="Spitfire/Percussion/Pitched" n="Tubular Bells Techniques"
//! m="Make Sure KS is on C0"
Bank 1 13 SP - Tubular Bells
//! c=long i=note-whole o=note:24
24 normal
//! c=long-light i=note-whole o=note:25
25 muted

//! g="Spitfire/Percussion/Pitched" n="Vibraphone Techniques"
//! m="Make Sure KS is on C0"
Bank 1 14 SP - Vibraphone
//! c=long i=note-whole o=note:24
24 normal
//! c=long i=vibrato o=note:25
25 motor sustain
//! c=long i=tremolo o=note:26
26 roll

//! g="Spitfire/Percussion/Non-Pitched/Drums" n="Snare Position"
//! m="Make Sure KS is on C0"
Bank 1 15 SP - Snares & Field Drm
//! c=textured i=note-whole o=note:24
24 snare on
//! c=textured i=note-whole o=note:25
25 snare off

//! g="Spitfire/Percussion/Non-Pitched/Drums" n="Gong Drum Techniques"
//! m="Make Sure KS is on C0"
Bank 1 16 SP - Gong Drum
//! c=long i=note-whole o=note:24
24 sticks
//! c=long-dark i=note-whole o=note:25
25 wood mallets
Tack, feel free to incorporate the above into the default bank. I will be adding to this as time goes on as I get more sections of my orchestra set up. I will be doing banks for some samples other than Spitfire, so stay tuned for more. I am also interested in using reticulate as a place to toggle organ stops in Spitfire's Union Chapel Organ Library, however I have tried the following for the Swell Division and the previously selected note triggers for the various stops are not being retained until they are selected again to turn off. With this patch, you must reselect the stops simultaneously in order to have multiple stops active. Below is the prototype bank:
Code:
//! g="Spitfire/Keyboards/Organ" n="Swell Division"
//! m="Set patch to unlocked artic. with stop KS moved to C0-F0. Use piano notes in left corner of patch to move."
Bank 1 6 SUCO - Swell Division
//! c=long i=note-whole f=toggle o=note-hold:24
24 Contra Gamba 16'
//! c=long i=note-whole f=toggle o=note-hold:25
25 Open Diapason 8'
//! c=long i=note-whole f=toggle o=note-hold:26
26 Salcional 8'
//! c=long i=note-whole f=toggle o=note-hold:27
27 Vox Angelica 8'
//! c=long i=note-whole f=toggle o=note-hold:28
28 Flote 4'
//! c=long i=note-whole f=toggle o=note-hold:29
29 Mixture

Last edited by WolfgangAgustus; 05-19-2019 at 02:24 PM.
WolfgangAgustus is offline   Reply With Quote
Old 05-19-2019, 06:29 PM   #404
WolfgangAgustus
Human being with feelings
 
Join Date: May 2019
Posts: 4
Default Spitfire Percussion Banks - Toys, Metals & Woods

Code:
//! g="Spitfire/Percussion/Non-Pitched/Toys" n="Guiro Types"
//! m="Make Sure KS is on C0"
Bank 1 17 SP - Guiro
//! c=long i=note-whole o=note:24
24 normal guiro
//! c=long-light i=note-whole o=note:25
25 glass guiro
//! c=long-dark i=note-whole o=note:26
26 reco-reco

//! g="Spitfire/Percussion/Non-Pitched/Metals" n="Cymbal Hi/Low Techniques"
//! m="Make Sure KS is on C0"
Bank 1 18 SP - Cymbal Hi/Lo
//! c=long-light i=note-whole o=note:24
24 soft mallets
//! c=long-dark i=note-whole o=note:25
25 hard mallets
//! c=long i=note-whole o=note:26
26 brushed

//! g="Spitfire/Percussion/Non-Pitched/Metals" n="Cymbal Med Techniques"
//! m="Make Sure KS is on C0"
Bank 1 19 SP - Cymbal Med
//! c=long-light i=note-whole o=note:24
24 soft mallets
//! c=long-dark i=note-whole o=note:25
25 hard mallets

//! g="Spitfire/Percussion/Non-Pitched/Metals" n="Trash Metals Techniques"
//! m="Make Sure KS is on C0"
Bank 1 20 SP - Trash Metals
//! c=long i=note-whole o=note:24
24 metal
//! c=long-light i=note-whole o=note:25
25 plastic

//! g="Spitfire/Percussion/Non-Pitched/Woods" n="Temple Blocks Techniques"
//! m="Make Sure KS is on C0"
Bank 1 21 SP - Temple Blocks
//! c=long-light i=note-whole o=note:24
24 soft mallets
//! c=long-dark i=note-whole o=note:25
25 hard mallets

//! g="Spitfire/Percussion/Non-Pitched/Woods" n="Wood Blocks Techniques"
//! m="Make Sure KS is on C0"
Bank 1 22 SP - Wood Blocks
//! c=long i=note-whole o=note:24
24 sticks
//! c=long-light i=note-whole o=note:25
25 rubber mallets
Again, Tack, feel free to adapt the above banks to the default bank.

Next up is the KS based Reticulate Banks for EastWest RA in cases where the KS patches are superior to the Live Patches. Since the EastWest configuration of KS starting notes is messy, I will use their default locations which are thankfully standardized. I also observed that the Mod wheel dynamics are inverted from the traditional Kontakt layout of higher cc = higher dynamics in Play 5 which is confusing.

I will also consider doing individual banks for the Spitfire Solo Strings Library and extra banks for the newer Performance Legato Patches for Spitfire Symphonic Strings. Also on the table is Articulation Banks for Evolution: World Percussion Series - Taiko, Sonokenetic Carillon and if possible, Embertone Recorders.
WolfgangAgustus is offline   Reply With Quote
Old 05-26-2019, 12:54 PM   #405
WolfgangAgustus
Human being with feelings
 
Join Date: May 2019
Posts: 4
Default EastWest Quantum Leap RA Preset Banks

Just finished this one. It was a nightmare to program and to identify the articulations. EastWest didn't do a good job of labeling their articulations so I had to go through each and every key-switched articulation on every patch to figure out what it was and how to make it easier to identify in the reaticulate GUI. As always Tack, feel free to add it to the next release in the default bank.

I've also decided it would be best in reticulate to make presets for spitfire's union chapel organ until a special toggle mode can be added to reticulate for the unique use case of an organ. Much like pistons on modern organs, the preset approach to this bank library will have a collection of different stop mixes, which are triggered simultaneously, that an organist would use based on volume, expression, and what the majority of organ works call for in the stop list. Being an organist myself, I should be able to choose many useful presets and maybe add coupler articulations in a separate group that will route the midi to multiple tracks including the source.
Attached Files
File Type: txt EastWest RA Bank Files.txt (21.8 KB, 6 views)

Last edited by WolfgangAgustus; 05-26-2019 at 01:06 PM.
WolfgangAgustus is offline   Reply With Quote
Old 05-26-2019, 05:09 PM   #406
WolfgangAgustus
Human being with feelings
 
Join Date: May 2019
Posts: 4
Default Spitfire Union Chapel Organ Bank

Attached is the Union Chapel Organ Sound Banks for Reticulate. Presets are working fine. Track routing for midi was impossible so that portion is not there. Each articulation bank contains the presets and each stop individually if you would like to just have one stop active at a time which is useful for solo stops on different manuals. Some articulation designations had to be abbreviated due to character display limitations of reticulate. Presets are using the default color. Strings are using the legato color code with variance based on middle c pitch within the patch (higher pitches are light, lower pitches are dark). Reeds are using the FX preset color. Flutes are using the Long preset color with variance to middle C pitch and mixtures are using the textured preset.

Tack, Feel free to add it to the default bank.
Attached Files
File Type: txt Spitfire Union Chapel Organ Presets Bank.txt (4.2 KB, 8 views)

Last edited by WolfgangAgustus; 05-26-2019 at 05:17 PM.
WolfgangAgustus is offline   Reply With Quote
Old 05-30-2019, 08:45 AM   #407
12345678
Human being with feelings
 
Join Date: Mar 2019
Posts: 7
Default

Is it possible with this tool to use all the articulations in Symphony Series Brass by SoundIron? Since it has only 8 articulation slots but the library has a lot more.. And i wanna use them in one midi channel? is this possible? Or with some Kontakt script? I struggle with this..
For example Trumpets Sustain has i think 11 articulations available but the patch itself can hold up to 8? I wanna have for example On one midi channel
12345678 is offline   Reply With Quote
Old 05-30-2019, 09:58 AM   #408
tack
Human being with feelings
 
tack's Avatar
 
Join Date: Jan 2014
Location: Ontario, Canada
Posts: 596
Default

Quote:
Originally Posted by 12345678 View Post
Is it possible with this tool to use all the articulations in Symphony Series Brass by SoundIron? Since it has only 8 articulation slots but the library has a lot more.. And i wanna use them in one midi channel? is this possible? Or with some Kontakt script? I struggle with this..
For example Trumpets Sustain has i think 11 articulations available but the patch itself can hold up to 8? I wanna have for example On one midi channel
I guess this is more a question about Symphony Series Brass than of Reaticulate, but worst case you can just load up different patches on different channels, and then create a Reaticulate bank to address all articulations on the appropriate channel (and corresponding keyswitch on that channel).

From a performance perspective, you do everything from the same MIDI channel, and let Reaticulate handle the routing when you activate one of the keyswitches.
tack is offline   Reply With Quote
Old 05-30-2019, 09:59 AM   #409
tack
Human being with feelings
 
tack's Avatar
 
Join Date: Jan 2014
Location: Ontario, Canada
Posts: 596
Default

Quote:
Originally Posted by WolfgangAgustus View Post
Tack, Feel free to add it to the default bank.
Thanks for these submissions, Wolfgang.

I'm going to move away from the notion of factory banks but need to build something for users to swap banks themselves instead. My main challenge, as ever, is free time. But that's the idea.
tack is offline   Reply With Quote
Old 05-30-2019, 12:35 PM   #410
Kitarraman
Human being with feelings
 
Kitarraman's Avatar
 
Join Date: Jun 2018
Location: Italy
Posts: 34
Default

Quote:
Originally Posted by 12345678 View Post
Is it possible with this tool to use all the articulations in Symphony Series Brass by SoundIron? Since it has only 8 articulation slots but the library has a lot more.. And i wanna use them in one midi channel? is this possible? Or with some Kontakt script? I struggle with this..
For example Trumpets Sustain has i think 11 articulations available but the patch itself can hold up to 8? I wanna have for example On one midi channel
Basically what Tack said in his reply. It's a limitation of Symphony.You could work around it though, by loading multiple instances of the same VST (e.g. 3 or 4 instances of French Horns Ensemble) and put a different set of articulation in each instance (careful, each instance has to have a separate MIDI Channel and Reaticulate must send the right output to corresponding channel)
Kitarraman is offline   Reply With Quote
Old 05-30-2019, 01:14 PM   #411
12345678
Human being with feelings
 
Join Date: Mar 2019
Posts: 7
Default

Quote:
Originally Posted by Kitarraman View Post
Basically what Tack said in his reply. It's a limitation of Symphony.You could work around it though, by loading multiple instances of the same VST (e.g. 3 or 4 instances of French Horns Ensemble) and put a different set of articulation in each instance (careful, each instance has to have a separate MIDI Channel and Reaticulate must send the right output to corresponding channel)
I was thinking of this.. But it will be too much work.. I can't really make myself those bank files.. Ok thanks
12345678 is offline   Reply With Quote
Old 05-30-2019, 01:40 PM   #412
Kitarraman
Human being with feelings
 
Kitarraman's Avatar
 
Join Date: Jun 2018
Location: Italy
Posts: 34
Default

Quote:
Originally Posted by 12345678 View Post
I was thinking of this.. But it will be too much work.. I can't really make myself those bank files.. Ok thanks
Look at it this way: anytime you have some spare time, you can program your banks, so that when you have to record, you don't have to play around with keyswitches and such. It's time you invest now to save it later
Kitarraman is offline   Reply With Quote
Old 05-31-2019, 12:47 AM   #413
12345678
Human being with feelings
 
Join Date: Mar 2019
Posts: 7
Default

Quote:
Originally Posted by tack View Post
I guess this is more a question about Symphony Series Brass than of Reaticulate, but worst case you can just load up different patches on different channels, and then create a Reaticulate bank to address all articulations on the appropriate channel (and corresponding keyswitch on that channel).

From a performance perspective, you do everything from the same MIDI channel, and let Reaticulate handle the routing when you activate one of the keyswitches.

How can i do that? It would be awesome if i can do it from one midi channel?
12345678 is offline   Reply With Quote
Old 05-31-2019, 08:18 AM   #414
tack
Human being with feelings
 
tack's Avatar
 
Join Date: Jan 2014
Location: Ontario, Canada
Posts: 596
Default

Quote:
Originally Posted by 12345678 View Post
How can i do that? It would be awesome if i can do it from one midi channel?
This is basically like the multi scenario described here:

http://reaticulate.com/reabank.html#...hannel-routing

The main difference is that instead of straight channel routing, you'll want to send some keyswitch to that channel to activate the articulation.

Adapting the example from the documentation:

Code:
//! c=legato i=legato o=note@1:10
20 legato
//! c=long i=note-whole o=note@2:5
1 sustains
//! c=short i=staccato o=note@3:7
40 staccato
Here each of the articulations routes to a different channel (@2 routes to channel 2) and sends a note to trigger the keyswitch. I just made up the note values 10, 5 and 7, it would be whatever note values are used to activate the articulation on the patches on those channels.

When you add this bank to your track, you choose a source channel. You can put omni there, even if you just intend to only use channel 1, but in that case if all your source MIDI data is on channel 1 (including your program changes to change articulations), Reaticulate takes care of routing to the appropriate destination channel on the VSTis. You just deal with one channel within the Reaper MIDI item.
tack is offline   Reply With Quote
Old 05-31-2019, 09:45 AM   #415
Kitarraman
Human being with feelings
 
Kitarraman's Avatar
 
Join Date: Jun 2018
Location: Italy
Posts: 34
Default

Quote:
Originally Posted by tack View Post
This is basically like the multi scenario described here:

http://reaticulate.com/reabank.html#...hannel-routing

The main difference is that instead of straight channel routing, you'll want to send some keyswitch to that channel to activate the articulation.

Adapting the example from the documentation:

Code:
//! c=legato i=legato o=note@1:10
20 legato
//! c=long i=note-whole o=note@2:5
1 sustains
//! c=short i=staccato o=note@3:7
40 staccato
Here each of the articulations routes to a different channel (@2 routes to channel 2) and sends a note to trigger the keyswitch. I just made up the note values 10, 5 and 7, it would be whatever note values are used to activate the articulation on the patches on those channels.

When you add this bank to your track, you choose a source channel. You can put omni there, even if you just intend to only use channel 1, but in that case if all your source MIDI data is on channel 1 (including your program changes to change articulations), Reaticulate takes care of routing to the appropriate destination channel on the VSTis. You just deal with one channel within the Reaper MIDI item.
Tack, I always wanted to ask you something: I always write my banks this way
//! c=#FF0000 i=note-whole o=note@1:24
24 Sustain All
Using the same number for the note output and the name of the articulation is going to bite me in the ass someday in the future? I hope not, to this day never had an issue (if we don't count Miroslav not receiving the articulation changes... I've given up on that front)
Kitarraman is offline   Reply With Quote
Old 05-31-2019, 09:46 AM   #416
Kitarraman
Human being with feelings
 
Kitarraman's Avatar
 
Join Date: Jun 2018
Location: Italy
Posts: 34
Default

Quote:
Originally Posted by 12345678 View Post
How can i do that? It would be awesome if i can do it from one midi channel?
I'm going to post this. I'm working on my banks and I plan to share them once they're done, but I encourage you to program them yourself, so that if you wanted to use Reaticulate on a library no one has mapped, you'll know how to do it yourself.

//! g="Native Instruments/Symphony Essentials All Articulations Loaded/Brass Ensemble" n="Horns Ensemble"
Bank 12 91 Horns Ensemble
//! c=#FF0000 i=note-whole o=note@1:24
24 Sustain All
//! c=#FF0000 i=note-whole o=note@1:25
25 Sustain Single Tongue
//! c=#FF0000 i=note-whole o=note@1:26
26 Sustain Flutter Tongue
//! c=#FF0000 i=trill o=note@1:27
27 Trill Semi Tone
//! c=#FF0000 i=crescendo o=note@1:28
28 Sust. Crescendo
//! c=#FF0000 i=decrescendo o=note@1:29
29 Sust. Decrescendo
//! c=#FF0000 i=stopped o=note@1:30
30 Sust. Stop Mute
//! c=#40FF00 i=staccato o=note@1:31
31 Staccato
//! c=#40FF00 i=staccato o=note@2:24
32 Staccato Velocity
//! c=#40FF00 i=staccatissimo-stopped o=note@2:25
33 Stac. Stop Mute
//! c=#00BFFF i=crescendo o=note@2:26
34 Crescendo
//! c=#00BFFF i=decrescendo o=note@2:27
35 Decrescendo
//! c=#00BFFF i=sfz o=note@2:28
36 Sforzando
//! c=#00BFFF i=sfz o=note@2:29
37 Sfz Slow
//! c=#00BFFF i=note-whole o=note@2:30
38 Swell
//! c=#00BFFF i=note-whole o=note@2:31
39 Swell Slow
//! c=#00BFFF i=staccatissimo-stopped o=note@3:24
40 Marc Stop Mute
//! c=#00BFFF i=fanfare o=note@3:25
41 Blast
Kitarraman is offline   Reply With Quote
Old 05-31-2019, 11:04 AM   #417
tack
Human being with feelings
 
tack's Avatar
 
Join Date: Jan 2014
Location: Ontario, Canada
Posts: 596
Default

Quote:
Originally Posted by Kitarraman View Post
Tack, I always wanted to ask you something: I always write my banks this way
//! c=#FF0000 i=note-whole o=note@1:24
24 Sustain All
Using the same number for the note output and the name of the articulation is going to bite me in the ass someday in the future? I hope not, to this day never had an issue
Really the only requirement is that program numbers on the same source MIDI channel are unique. Which is to say, program numbers within a given bank must be unique, and across banks assigned to the same track they must not conflict if those banks are mapped to the same source MIDI channel.

So in practice you should be fine, except that you lose the benefit of standardizing articulations between virtual instruments by using a consistent program number for the same articulations (e.g. 1 for long sustains). The main use-case for this is control surfaces were you can trigger common articulations regardless of the track. If that use-case isn't important to you, then it really doesn't matter.

But then as you've noticed, if you've got a multi config with patches on different channels, you'll need to use a different program number on the other channels so at that point they won't match the note numbers anymore. But it really doesn't matter.


Quote:
Originally Posted by Kitarraman View Post
(if we don't count Miroslav not receiving the articulation changes... I've given up on that front)
I'm curious, are you using the prerelease? If not, you might find that works. I made some timing changes that could help. Or maybe not.
tack is offline   Reply With Quote
Old 05-31-2019, 01:36 PM   #418
Kitarraman
Human being with feelings
 
Kitarraman's Avatar
 
Join Date: Jun 2018
Location: Italy
Posts: 34
Default

Quote:
Originally Posted by tack View Post
Really the only requirement is that program numbers on the same source MIDI channel are unique. Which is to say, program numbers within a given bank must be unique, and across banks assigned to the same track they must not conflict if those banks are mapped to the same source MIDI channel.

So in practice you should be fine, except that you lose the benefit of standardizing articulations between virtual instruments by using a consistent program number for the same articulations (e.g. 1 for long sustains). The main use-case for this is control surfaces were you can trigger common articulations regardless of the track. If that use-case isn't important to you, then it really doesn't matter.
Right now, I don't rely on a control surface yet. I'm planning to buy one and use your other piece of work to write MIDI cc, but that'll a problem for future me to deal with.

Quote:
Originally Posted by tack View Post
But then as you've noticed, if you've got a multi config with patches on different channels, you'll need to use a different program number on the other channels so at that point they won't match the note numbers anymore.
Yup, I noticed that when I first started with Reaticulate's Banks, I didn't know what those numbers were for and I had a bank set with the same numbers repeating on multiple articulations. I realised there must've been something wrong in my code because Reaticulate wasn't running as smooth as it should've, so I changed the numbers and that fixed it. Trial and error FTW


Quote:
Originally Posted by tack View Post
I'm curious, are you using the prerelease? If not, you might find that works. I made some timing changes that could help. Or maybe not.
No, I'm using the stable version. I've given up on Miroslav, I don't use it that much anymore and I rely more on Symphony Collection or Chris Hein Libraries. Right now I'm working on a videogame soundtrack and I don't have really all that free time to mess around with Miroslav and why it doesn't receive the MIDI signals as it should. Someday though I'll get to work, but by that time Reaticulate would probably be out of beta

Last edited by Kitarraman; 06-01-2019 at 01:17 AM.
Kitarraman is offline   Reply With Quote
Old 06-01-2019, 12:42 AM   #419
12345678
Human being with feelings
 
Join Date: Mar 2019
Posts: 7
Default

It doesn't really work for me... When i arm record midi channel 1 to control all articulations it switches them but only visually.. It still plays the first 8 in channel 1.. I'm a noob at this and don't know how to fix it..
12345678 is offline   Reply With Quote
Old 06-09-2019, 08:31 AM   #420
Hartley Mays
Human being with feelings
 
Join Date: Sep 2009
Location: Cincinnati, Ohio
Posts: 246
Default Pipe Organs, Hauptwerk

Hi Tack,

Thanks very much for your work on this.

I want to add to the discussion about Reaticulate and pipe organs. There's a software product, Hauptwerk, which can run standalone or as a VSTi. It loads (one at a time) very large sample sets of complete pipe organs, including some of the largest and most famous in Europe. Web site is here:

https://www.hauptwerk.com/

Each sample set has its own set of midi commands to turn stops off and on, and I've got it working from Reaper with Reaticulate. The big problem, as has been mentioned, is that the stops operate independently, not exclusively like other instrument articulations. The Hauptwerk standard is to use a MSB/LSB sequence for each one, specifying ff's for the values to turn the stop on, and 0's for off.

Here's an example from the Inspired Acoustics Palace of Arts Budapest Pipe organ:

//! g="Hauptwerk / PAB Organ" n="PAB Grand Orgue"
Bank 63 127 HW PAB Great

//! c=legato i=legato g=1 o=cc@2:99,16/cc@2:98,53/cc@2:6,127/cc@2:38,127
118 Montre 16 On
//! c=legato i=legato g=1 o=cc@2:99,16/cc@2:98,53/cc@2:6,0/cc@2:38,0
117 Montre 16 Off

As you can see, it takes two entries for each stop, and there can be well more than 100 stops for the large pipe organs.

So it would be great to have an option for these sorts of "binary" articulations to have a syntax available to turn them on/off with one entry. (I would think there may be other situations with VST parameters where something similar could be useful.)

There are a lot of Reaper users of Hauptwerk, and I think Reaticulate could be very useful, but the number of entries required is a big obstacle. Is this something you might consider for an enhancement?

Later,
Hartley
Hartley Mays is offline   Reply With Quote
Old 06-09-2019, 08:49 AM   #421
tack
Human being with feelings
 
tack's Avatar
 
Join Date: Jan 2014
Location: Ontario, Canada
Posts: 596
Default

Quote:
Originally Posted by Hartley Mays View Post
There are a lot of Reaper users of Hauptwerk, and I think Reaticulate could be very useful, but the number of entries required is a big obstacle. Is this something you might consider for an enhancement?
For sure, if we can come up with a sensible UX for it and it's not too invasive to implement.

There was a related exchange in this thread (some pages back) about organs as well. There the context was a different, as it was about being able dynamically create stacks of stops with an organ using note-based keyswitches. I made a suggestion I wasn't overly thrilled about though.

In your case, what if each articulation that describes a stop configuration would reset/disable all prior stops before enabling a new set? Then you wouldn't need a stop-off for each individual group, they would be turned off by virtue of activating another one.

Or if that's too magical and implicit, would it work to have a single "all stops off" articulation that you could use for any grouping/stack/whatever-it's-officially-called?
tack is offline   Reply With Quote
Old 06-09-2019, 10:55 AM   #422
Hartley Mays
Human being with feelings
 
Join Date: Sep 2009
Location: Cincinnati, Ohio
Posts: 246
Default Hauptwerk, pipe organs, stops, into the weeds

Tack,

There's potentially a lot of complexity here. There are different kinds of stops on a pipe organ. We've been discussing the ones which turn off or on a specific rank (set) of pipes, i.e. one voice. These all work independently of each other by design so that the organist can turn each of them off or on during performance. So your suggestion about turning off all of them when sending a new one would not work.

There are also stops (combination stops) which can turn off and on multiple sets of stops, and there are coupler stops which make ranks available on other organ keyboards. But the settings for what these combination stops will do is controlled on the Hauptwerk side.

And I should explain that Hauptwerk runs as a completely independent program from Reaper. To use it as a VST, you enable its VST link from Reaper, but all of the controls for the organ are available independent of Reaper from within Hauptwerk.

The earlier discussion about pipe organs and your proposal here seem to relate to program change chasing but its not clear if or how to worry about that. I don't understand completely what happens, but if the same program change message turned on or off a given stop depending on its state (whether on or off was the last previously sent), then wouldn't resending the same sequence result in the instrument being in the same state? Or is Reaper going to do this without Reaticulate being involved? Hauptwerk is going to handle the state of each stop independently of all the others.

Anyway, great to get the discussion going, thanks for your quick response.

Hartley
Hartley Mays is offline   Reply With Quote
Old 06-09-2019, 02:04 PM   #423
tack
Human being with feelings
 
tack's Avatar
 
Join Date: Jan 2014
Location: Ontario, Canada
Posts: 596
Default

Pushed a couple small prereleases in the past couple days for those of you on the prerelease track:

0.2.93
New Features
  • New action: Track selection follows FX focus
    • When enabled, focusing an FX window will cause the FX's track to become selected.
    • This action requires the js_ReaScriptAPI extension
  • New action: Select last selected track
  • Added a "Behavior" section to the Settings page to control certain behaviors (mainly related to recently added actions)

0.2.92
New Features
  • New action: Toggle track selection follows MIDI editor target item
    • This action is useful when changing tracks via the MIDI Editor track list. It will select the track in the TCP, which causes Reaticulate to show the articulation list for that track.
    • This is most conveniently paired with the "Options: MIDI track list/media item lane selection is linked to editability"

Bug Fixes
  • Improved bidirectional sync between the MIDI Editor's default channel and Reaticulate's default channel.
tack is offline   Reply With Quote
Old 06-09-2019, 03:20 PM   #424
tack
Human being with feelings
 
tack's Avatar
 
Join Date: Jan 2014
Location: Ontario, Canada
Posts: 596
Default

Incidentally, barring bugs, 0.2.93 will be the last prerelease before a proper release (0.3.0) so I'm quite keen to hear feedback, even if it's a "looks good to me!"

And 0.3.0 will be the last version that supports Reaper versions prior to 5.97. I intend to leverage the new gmem_*() functions on the Lua side and these functions were introduced in Reaper 5.97.
tack is offline   Reply With Quote
Old 06-11-2019, 09:39 PM   #425
crd
Human being with feelings
 
Join Date: May 2019
Posts: 11
Default

I am coming from Cubase and absolutely love this script. It's been essential to me moving my work from Cubase to Reaper and has really worked well. I really appreciate you taking the time to make and share it!!!

Is anyone using Reaticulate with Ipad/lemur and could share some tips on how to have the correct bank of articulations follow track selection?
crd is offline   Reply With Quote
Old 06-12-2019, 08:38 AM   #426
_Stevie_
Human being with feelings
 
_Stevie_'s Avatar
 
Join Date: Oct 2017
Posts: 2,344
Default

@Jason, I prefer to use a full screen MIDI editor. It would be so great to be able to dock Reaticulate to the MIDI editor, but I know it's not possible.
However, could you maybe include an "always on top" functionality (from the JS API)? Or are there other ways to have it work nicely along the MIDI editor?
__________________
My Reascripts forum thread | My Reascripts on GitHub | Stephan Römer - film composer
If you wish to donate for my scripts: please consider an organization like: animal shelter, doctors without borders, UNICEF, etc...
_Stevie_ is online now   Reply With Quote
Old 06-12-2019, 09:03 AM   #427
Kitarraman
Human being with feelings
 
Kitarraman's Avatar
 
Join Date: Jun 2018
Location: Italy
Posts: 34
Default

Quote:
Originally Posted by _Stevie_ View Post
@Jason, I prefer to use a full screen MIDI editor. It would be so great to be able to dock Reaticulate to the MIDI editor, but I know it's not possible.
However, could you maybe include an "always on top" functionality (from the JS API)? Or are there other ways to have it work nicely along the MIDI editor?
You could either use a dual screen setup or drag and reduce the midi editor's window size to the point where you can see both the arrange view window and reaticulate's GUI
Kitarraman is offline   Reply With Quote
Old 06-12-2019, 12:48 PM   #428
_Stevie_
Human being with feelings
 
_Stevie_'s Avatar
 
Join Date: Oct 2017
Posts: 2,344
Default

I already got a dual monitor setup. However, the mixer is on the other screen. But that might be a solution, to put Reaticulate just next to the mixer. Will check if that works out. I just wish we could dock windows to the MIDI editor!
__________________
My Reascripts forum thread | My Reascripts on GitHub | Stephan Römer - film composer
If you wish to donate for my scripts: please consider an organization like: animal shelter, doctors without borders, UNICEF, etc...
_Stevie_ is online now   Reply With Quote
Old 06-12-2019, 01:02 PM   #429
Kitarraman
Human being with feelings
 
Kitarraman's Avatar
 
Join Date: Jun 2018
Location: Italy
Posts: 34
Default

Quote:
Originally Posted by _Stevie_ View Post
I already got a dual monitor setup. However, the mixer is on the other screen. But that might be a solution, to put Reaticulate just next to the mixer. Will check if that works out. I just wish we could dock windows to the MIDI editor!
That's how I have things organized. Works well for me.

https://drive.google.com/file/d/1-5Y...ew?usp=sharing
Kitarraman is offline   Reply With Quote
Old 06-12-2019, 01:16 PM   #430
_Stevie_
Human being with feelings
 
_Stevie_'s Avatar
 
Join Date: Oct 2017
Posts: 2,344
Default

Ah, I see, you resize the MIDI editor, so that the docked Reaticulate can peak thru.
__________________
My Reascripts forum thread | My Reascripts on GitHub | Stephan Römer - film composer
If you wish to donate for my scripts: please consider an organization like: animal shelter, doctors without borders, UNICEF, etc...
_Stevie_ is online now   Reply With Quote
Old 06-12-2019, 01:29 PM   #431
Kitarraman
Human being with feelings
 
Kitarraman's Avatar
 
Join Date: Jun 2018
Location: Italy
Posts: 34
Default

Quote:
Originally Posted by _Stevie_ View Post
Ah, I see, you resize the MIDI editor, so that the docked Reaticulate can peak thru.
Yup. And imho, until there's a way to have reaticulate in the MIDI Editor, that's the most comfortable way to use it. If I'm not wrong, Tack uses it the same way (yeah, that's where I got the idea in the first place)
Kitarraman is offline   Reply With Quote
Old 06-12-2019, 01:42 PM   #432
tompad
Human being with feelings
 
Join Date: Jan 2010
Location: Fjugesta, Sweden
Posts: 360
Default

Quote:
Originally Posted by Kitarraman View Post
Yup. And imho, until there's a way to have reaticulate in the MIDI Editor, that's the most comfortable way to use it. If I'm not wrong, Tack uses it the same way (yeah, that's where I got the idea in the first place)
Excuse my interupt - but what theme are you using? Mixer looks realy nice.
__________________
ToDoList Obliques MusicMath Donation Mark4celeste Frid i ditt hjärta Eve & the Fisherman on Spotify
tompad is offline   Reply With Quote
Old 06-12-2019, 01:48 PM   #433
Kitarraman
Human being with feelings
 
Kitarraman's Avatar
 
Join Date: Jun 2018
Location: Italy
Posts: 34
Default

Quote:
Originally Posted by tompad View Post
Excuse my interupt - but what theme are you using? Mixer looks realy nice.
It's the Imperial LCS mod theme. Link here https://stash.reaper.fm/theme/1719/I...LCS-mod_v2.zip
Kitarraman is offline   Reply With Quote
Old 06-12-2019, 04:12 PM   #434
tack
Human being with feelings
 
tack's Avatar
 
Join Date: Jan 2014
Location: Ontario, Canada
Posts: 596
Default

Quote:
Originally Posted by Kitarraman View Post
If I'm not wrong, Tack uses it the same way (yeah, that's where I got the idea in the first place)
Yep, that's what I do.



Quote:
Originally Posted by _Stevie_ View Post
However, could you maybe include an "always on top" functionality (from the JS API)? Or are there other ways to have it work nicely along the MIDI editor?
That capability does exist in the prerelease version (added in 0.2.91 a few months ago).

If you're on the release track you'll get it next week when I release 0.3.0, barring unforeseen circumstances.

Last edited by tack; 06-12-2019 at 04:19 PM.
tack is offline   Reply With Quote
Old 06-12-2019, 04:20 PM   #435
_Stevie_
Human being with feelings
 
_Stevie_'s Avatar
 
Join Date: Oct 2017
Posts: 2,344
Default

Okay, this is strange. I have version 0.2.93 installed. Where should the pin be visible on the title bar of Reaticulate?

I still might use the downsized MIDI editor, but I was just wondering, because I don't see the pin.

Quote:
If you're on the release track you'll get it next week when I release 0.3.0, barring unforeseen circumstances.
Ahh, can't wait, this will be so good
__________________
My Reascripts forum thread | My Reascripts on GitHub | Stephan Römer - film composer
If you wish to donate for my scripts: please consider an organization like: animal shelter, doctors without borders, UNICEF, etc...
_Stevie_ is online now   Reply With Quote
Old 06-12-2019, 04:30 PM   #436
tack
Human being with feelings
 
tack's Avatar
 
Join Date: Jan 2014
Location: Ontario, Canada
Posts: 596
Default

Quote:
Originally Posted by _Stevie_ View Post
Okay, this is strange. I have version 0.2.93 installed. Where should the pin be visible on the title bar of Reaticulate?
Oh, well shit, it's not there. Something must have broken with either my code or js_ReaScriptAPI. Will look into it.


Quote:
Originally Posted by _Stevie_ View Post
Ahh, can't wait, this will be so good
Oh don't get too excited. If you're already on 0.2.93, that's what it's going to be. Just a simple promotion.

The next major release (0.4.0) I'm overhauling some of the guts -- a pretty major redesign of how data is shipped back and forth between the main script and the JSFX (leveraging the new gmem APIs available starting in Reaper 5.97). Among other things, this is a dependency for another major change in which I want to move away from bank MSB/LSB as a way to identify banks. There's a lot of gory detail as to why and how here if you happen to be morbidly curious.

All this makes way for the wwwwaaayyyy overdue GUI bank editor which will come in the major release following (0.5.0). I just realized I had a lot of plumbing to take care of before I could proper deliver that.

Anyway, time to figure out WTF happened to the pin.
tack is offline   Reply With Quote
Old 06-12-2019, 04:50 PM   #437
tack
Human being with feelings
 
tack's Avatar
 
Join Date: Jan 2014
Location: Ontario, Canada
Posts: 596
Default

Quote:
Originally Posted by tack View Post
Anyway, time to figure out WTF happened to the pin.
AFAICT it looks like a js_ReaScriptAPI regression. I've asked on that thread.
tack is offline   Reply With Quote
Old 06-12-2019, 05:09 PM   #438
_Stevie_
Human being with feelings
 
_Stevie_'s Avatar
 
Join Date: Oct 2017
Posts: 2,344
Default

My bad, I thought version 0.3 would already include the graphical editor
Still, can't wait. I really love this script!

Great let's see what Julian says about the pin issue.
__________________
My Reascripts forum thread | My Reascripts on GitHub | Stephan Römer - film composer
If you wish to donate for my scripts: please consider an organization like: animal shelter, doctors without borders, UNICEF, etc...
_Stevie_ is online now   Reply With Quote
Old 06-13-2019, 01:43 AM   #439
Kitarraman
Human being with feelings
 
Kitarraman's Avatar
 
Join Date: Jun 2018
Location: Italy
Posts: 34
Default

Quote:
Originally Posted by tack View Post
Yep, that's what I do.

Tack, what does this buttons do?
https://drive.google.com/file/d/14v8...ew?usp=sharing
Where can I get them? I sense that they can speed my workflow.
Also, which versison of Imperial are you using?
Kitarraman is offline   Reply With Quote
Old 06-13-2019, 05:20 AM   #440
_Stevie_
Human being with feelings
 
_Stevie_'s Avatar
 
Join Date: Oct 2017
Posts: 2,344
Default

The ones with the notes on it are supposedly quantize / grid settings.
And the right ones are the Midi CC scripts from Julian Sader.
__________________
My Reascripts forum thread | My Reascripts on GitHub | Stephan Römer - film composer
If you wish to donate for my scripts: please consider an organization like: animal shelter, doctors without borders, UNICEF, etc...
_Stevie_ is online now   Reply With Quote
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT -7. The time now is 10:42 AM.


Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2019, vBulletin Solutions Inc.