What's new

Erae Touch and Studio One 6.5.1

outland

Active Member
I have Erae Touch working (mostly) in Studio One 6.5.1. It should be noted that there is one issue that remains unresolved (very likely from the Studio One side of the problem as there are no issues in Bitwig).

I am on a PC.

One must configure the Erae Touch to "Receive from" both "Erae Touch" and "MIDIIN2 (Erae Touch) in Studio One's External Device window as a "New Keyboard". One or the other alone will not suffice. It does not seem necessary to configure the Erae Touch for "Send to".

The caveats are two:

1) Studio One is only 4/5 compliant with the MPE protocol as "Lift" is ignored in all cases. For whatever reason, Presonus has elected to ignore this dimension of MPE.

2) As of right now, patches with a longer release envelope segment will revert back to the original pitch struck. As an example (read this chronologically, if you will) you play (for this example, think single notes, not chords or intervals): "(Strike) C (Glide to) G (Lift)", expecting to hear: "C, G...", but what you hear is "C, G, C..." as Studio One attempts to return your performance to the original note struck.

Oddly, this same behavior was actually fixed for the Roli keyboards after many months (thanks to Lukas for his bringing the matter up to Presonus.) Hopefully, this bug is addressed by Presonus fully and across all manufacturers' MPE devices at some point.
 
Last edited:
Studio One is only 4/5 compliant with the MPE protocol as "Lift" is ignored in all cases. For whatever reason, Presonus has elected to ignore this dimension of MPE.
I don't think that PreSonus has "elected to ignore" anything. How do you know they are not actively monitoring the demand for this feature?

MPE Lift is Note Off Velocity. Studio One does not support Note Off Velocity (it's hardly ever used). This means that Note Off Velocity would have to be implemented before they could even look at MPE Lift.

There is a feature request in the PreSonus answer base with currently 18 votes:

Other feature requests have had > 1000 votes. So this may be a reason for the somewhat lower priority.
 
Last edited:
I wonder why you think that PreSonus has "elected to ignore" something!? How do you know they are not actively monitoring the demand for this feature? ;)

We had the same conversation last year and I already answered you, if you remember.

MPE Lift is Note Off Velocity. Studio One does not support Note Off Velocity (it's hardly ever used). This means that Note Off Velocity would have to be implemented before they could even look at MPE Lift.

There is a feature request in the PreSonus answer base with currently 18 votes:

Other feature requests have had > 1000 votes. This may be a reason for the somewhat lower priority.
Hi Lukas,

I do remember the conversation, of course; I wasn't writing this post for you so much, but rather for someone who may have the Erae Touch (to be forewarned when "Lift" isn't recognized; if you remember, two of Presonus' techies and I went back and forth for about a month trying to rectify why Lift wasn't being recognized before a programmer informed them that it just wasn't possible due to the reasons you mention above.) So, insofar as Note Off Velocity/Lift is concerned, my use of the word "ignore" does not refer so much to their current decision to evaluate the popularity of Lift as a "feature request" (the way it was described to me by another techie explaining the process by which it might be included later which you recount above,) as their earlier decision to separate off Lift from the other four dimensions of MPE at the beginning of development to address the MPE protocol and the fact that Lift is not recognized currently. Remember, back before MPE was partially embraced by Presonus, polyphonic aftertouch (MPE => "Pressure") was not recognized either, but Presonus made the decision to include that as well when MPE was being considered. And yes, it is clear that release velocity/Lift is rarely used: no argument there. But if it doesn't appear when one knows that a given patch is programmed for it, it can be confusing. This was the case for me and the techies that I mentioned previously. This is the way I am using the word "ignore" and this is why I mentioned it above.

Please understand: my intent was only to warn those who may be trying to use the Erae Touch what to expect as far as the use of MPE with Studio One is concerned. As of this moment, there is a real dearth of information concerning using the two together. It certainly was not an attempt to irritate anyone, much less you, dear sir, as you have been very helpful to so many people (I include myself in this obviously) and I appreciate that fact and thank you, always mentioning you when something pertains to an issue that you've cleared up for me.

But to redirect your attention for a moment, if I may: would you happen to know why Studio One is behaving with the Erae Touch the way it did with my Roli (as I note in my second point in my first post) before you kindly suggested to Presonus that they address this issue? This is exactly the same behavior that I had with my Seaboard Blocks (and Presonus fixed.) How or why is it showing up again with my Erae Touch?

Again, all my thanks to you; it was not my intent at all to upset you and I am deeply sorry if such was the case.
 
Last edited:
👍 I was just trying to explain why there's no MPE Lift in Studio One currently :)
Gotcha.

But, if I could, do you have any idea why Studio One is reacting to the Erae Touch like it did for the Roli Seaboard Block? It's just so weird. I would have thought that the fix for the Roli would have taken care of all similar issues for all the different MPE controllers. Forgive me for asking, but it's incredibly vexing.

OIP (2).jpg
 
FWIW, no, today's update (6.5.2.97444) did not fix the issue I described with Erae Touch, though I initially had hopes when I read the release notes. Notes still attempt to revert to the initial pitch struck.
 
Top Bottom