Menu
What's new
By:
Filters

Who's using Reaper and Reaticulate?

robgb said:
I'm not sure this is an accurate characterization of Reaper users. I think the attitude is simply why pay for 3rd party software when the community built version works just fine? I think if Reaper users didn't have a solution to the articulation problem, most would gladly pay for it.
Click to expand...
I think you are missing the point of what we are talking about. We are not talking about another software/plugin to be used instead of Reaticulate. We're talking about sets FOR Reaticulate.

vsthem said:
I personally would be happy to purchase articulation sets. There can be kind of a weird thing among reaper users, that somehow paying money for goods and services within reaper is not in the spirit of reaper. I know that at least some of us would gladly pay though. Have you posted in the thread on the reaper forum? Probably get a good idea over there
Click to expand...
The fact that they would be paying for the sets for an unofficial addon and not for the basic functionality of the DAW, as is the case in other cases, may also play a role.
 
Christianus said:
I think you are missing the point of what we are talking about. We are not talking about another software/plugin to be used instead of Reaticulate. We're talking about sets FOR Reaticulate.
Click to expand...
Okay, same response. Why pay for something that already works all on its own? There are already dozens of Reaticulate articulation maps available on github, covering most of the major libraries, and, frankly, creating one yourself takes about five minutes. So, again, I think most users of Reaper would be happy to pay for it if it weren't available or easy to use, but that isn't the case.
 
I know that @tack is working on making a better, centralized location for reabanks. I think it'll be easier to see the demand for outside articulation maps once that's been implemented
 
robgb said:
frankly, creating one yourself takes about five minutes
Click to expand...
I can assure you it doesn't take anywhere five minutes in my case, so that's why I invested some time to develop that Expression-2-Reaticulate script along with the tool on itch.io. Still it doesn't take 5 minutes since the banks should be built perfectly initially and shouldn't be altered later as they don't save alongside the project, so you improve the bank later only to find out launching a 2-year-old project uses that bank gets f*ed (trust me it happens).

Then I decide to pay for babylonwaves's packs AND Nuendo & learn how to use them because whatever I did for Reaper & Reaticulate didn't helped me for the times I had to come up with lots and lots of music on a tight schedule.

I'm on the team "I would pay for a good articulations library but I'm not confident with relying to Reaticulate for my business (sorry @tack :( ), so Reaper devs should have lay a groundwork for an internal Articulation system that the community can expand upon". You should be on that team, too.
 
Last edited:
Kabraxis said:
I can assure you it doesn't take anywhere five minutes in my case, so that's why I invested some time to develop that Expression-2-Reaticulate script along with the tool on itch.io. Still it doesn't take 5 minutes since the banks should be built perfectly initially and shouldn't be altered later as they don't save alongside the project, so you improve the bank later only to find out launching a 2-year-old project uses that bank gets f*ed (trust me it happens).

Then I decide to pay for babylonwaves's packs AND Nuendo & learn how to use them because whatever I did for Reaper & Reaticulate didn't helped me for the times I had to come up with lots and lots of music on a tight schedule.

I'm on the team "I would pay for a good articulations library but I'm not confident with relying to Reaticulate for my business, so Reaper devs should have lay a groundwork for an internal Articulation system that the community can expand upon". You should be on that team, too.
Click to expand...
Nice!!!
 
Is there any precedence for reaper to take a user generated script and work with the creator to implement it natively? Reaper really needs this, yet assuredly lacks the expertise necessary to build an articulation system that works for orchestral vst composers
 
Well, although the Reaper Devs are pretty cool, it’s extremely rare they do joint work.

And while they are pretty open to suggestions and feedback, they only develop features they’re interested in.
 
vsthem said:
Is there any precedence for reaper to take a user generated script and work with the creator to implement it natively? Reaper really needs this, yet assuredly lacks the expertise necessary to build an articulation system that works for orchestral vst composers
Click to expand...
Why would they need to?
 
I think for security and optics. I understand how composers with tight deadlines would be nervous to switch to a daw that relies on a user generated script. If reaticulate stopped working, I would literally need to switch daws the next day. Also, I think tack has mentioned that there are things he would improve if he could access reaper under the hood, though I don't claim to really know how that works.

I really appreciate that tack takes this very seriously though and would not abandon it without taking some actions, but not everyone knows that.

I really think that reaper could become THE daw for media composers with a little more love to midi and a native articulation system
 
Last edited:
But as it's been pointed out, it doesn't seem to interest them. I'd complain, but then again, there are two devs working hard to make the best daw, and charging $60 for it
 
vsthem said:
I think for security and optics. I understand how composers with tight deadlines would be nervous to switch to a daw that relies on a user generated script. If reaticulate stopped working, I would literally need to switch daws the next day.
Click to expand...
The way Reaper is designed, I think the likelihood of that happening is pretty slim. And Reaticulate has been rock solid throughout several versions of the DAW. I just don't see it as an issue. Are the SWS extensions a formal part of Reaper?
 
Have any of you (except @robgb ) actually used Reaticulate for any length of time? It seems like a theoretical discussion about stability issues. I've been using the system for 3 years and never had an issue.
 
robgb said:
Are the SWS extensions a formal part of Reaper?
Click to expand...
Many features SWS had introduced have been adopted by Reaper devs over time, and some parts of SWS doesn't work properly today since the constant changes happening in Reaper all the time. Maintaining these stuff takes lots of time, and people who lend their leisure time to these projects can just decide it's not worth it, or find themselves in situations they can't keep up.

robgb said:
The way Reaper is designed, I think the likelihood of that happening is pretty slim.
Click to expand...
The way Reaper is designed, things go awry would only took a LUA version update that broke the underlying API. That actually happened with v7.0, and some unmaintained scripts went dead right away, messed up with many people's workflows.
 
Kabraxis said:
some unmaintained scripts went dead right away, messed up with many people's workflows.
Click to expand...
A bit unfair reading here, as that is a prerelease beta thread. They didn't just one day wake up and decide to screw a bunch of people. If you read through the thread, you see exactly the issue the one poster is experiencing due to this, which was a problem with the way his scripts were written (only compatible with a specific LUA version).

Not trying to imply that Reaper is perfect but it's weird constantly reading about how all the scripts have a timebomb attached to them, when I've been using some for like 15 years at this point.

I haven't had any issues with Reaticulate, but a native version would be great too. I've personally been really benefiting from the latest round of big updates (video in background, track lanes) so hopefully that keeps up.
 
I know devs are careful to try and not break sws and other popular scripts. I'm pretty sure there's enough of us that they wouldn't just break it. And you guys make good points about the longitivity of these scripts, especially with the way other popular daws just abandon things regularly. I can't imagine I'd have an easy time opening up my pro tools 7 sessions from back in the day
 
vsthem said:
. I can't imagine I'd have an easy time opening up my pro tools 7 sessions from back in the day
Click to expand...
Yeah Pro Tools is a major offender for backwards compatibility. Apple completely upended everything and end users got mad at third party developers for not updating everything quick enough! It's a no win situation to be sure, but claiming that Reaper is breaking compatibility all the time just isn't true.

To keep this relatively on topic- I think you'll have a bit of a hard time selling Reabanks. Most of the people who write them share them (I shared my Duality Strings), it's a little more part of the "culture" of Reaper, especially when Reaticulate is being developed for free.
 
Pretty much anything that gets broken gets broken in the development, pre-release phase and such concerns are usually addressed by Reaper or by the scripters. It certainly behooves Reaper owners to use Reapack to update their scripts—which literally takes only a few minutes, at most. And if a script breaks, there is bound to be a replacement. If not, you can go to the Reaper forum and will more than likely have one in a short period of time.

For example, I was looking for a way to toggle spacers on a track with a single command and cobbled something together that didn't work quite the way I wanted it to. I posted it on the forum and within minutes not only did a scripter correct it for me, he created multiple scripts that he loaded up on Reapack and Reaper stash.

So the concern that something is somehow going to fail because of an update is a bit overblown. There are usually quick solutions in the rare event that it does, thanks in large part to the Reaper community—which is one of the strongest arguments for using Reaper in the first place.

I've had zero issues with Reaper 7, by the way. All the scripts I use (and I use a ton), are still working fine.
 
I have used Reaticulate in more than 600 projects (rpp) over the years and had not a single issue.
Whereas the REAPER devs don’t have much interest in an articulation system, they usually help out tack pretty quickly when an issue arises. I remember something got changed in the ME regarding loading bank changes and the devs fixed it in the next pre.
 
You must log in or register to reply here.
Top Bottom