Roli: Equator 2 is here !

[Echoes in the Attic]

So who here wants to split up the saving of vst3 presets of equator?

Shame to lose all the attributes and ability to search though. Maybe KK is a better option.

If what I've experienced is any indicator, saving wouldn't help those presets without "partners" that don't load correctly and even saving the partner presets may not wok (at least consistently, I'm sorry to say.) Once one switches to another (non-partnered) preset, it appears that all bets are off as far as loading correctly. At best, there is still much inconsistently. (I was, BTW, going to save all the presets myself and if they offered a fix, share them, but I'm pretty sure that would be a worthless endeavor now.)

OTOH, I received a very pleasant reply from a ROLI tech, apologizing for the loading problem, and stating that they were attempting to fix the issue in Bitwig (and Live?,) while also assuring me that the problem would be fixed before the next update. So, there is hope.

But you were saving as bitwig presets right? As aMUSEd said it seems vst presets and KK presets load ok if saved correctly.

[dlandis]

So who here wants to split up the saving of vst3 presets of equator?

Shame to lose all the attributes and ability to search though. Maybe KK is a better option.

If what I've experienced is any indicator, saving wouldn't help those presets without "partners" that don't load correctly and even saving the partner presets may not wok (at least consistently, I'm sorry to say.) Once one switches to another (non-partnered) preset, it appears that all bets are off as far as loading correctly. At best, there is still much inconsistently. (I was, BTW, going to save all the presets myself and if they offered a fix, share them, but I'm pretty sure that would be a worthless endeavor now.)

OTOH, I received a very pleasant reply from a ROLI tech, apologizing for the loading problem, and stating that they were attempting to fix the issue in Bitwig (and Live?,) while also assuring me that the problem would be fixed before the next update. So, there is hope.

But you were saving as bitwig presets right? As aMUSEd said it seems vst presets and KK presets load ok if saved correctly.

I thought they were. It turned out not to be consistent. I still had to opt for loading (say) a Standard preset and then loading the MPE (or my resaved "BWS" preset.) So, I feel a little better than being at square one, but only a bit.

[Echoes in the Attic]

So who here wants to split up the saving of vst3 presets of equator?

Shame to lose all the attributes and ability to search though. Maybe KK is a better option.

If what I've experienced is any indicator, saving wouldn't help those presets without "partners" that don't load correctly and even saving the partner presets may not wok (at least consistently, I'm sorry to say.) Once one switches to another (non-partnered) preset, it appears that all bets are off as far as loading correctly. At best, there is still much inconsistently. (I was, BTW, going to save all the presets myself and if they offered a fix, share them, but I'm pretty sure that would be a worthless endeavor now.)

OTOH, I received a very pleasant reply from a ROLI tech, apologizing for the loading problem, and stating that they were attempting to fix the issue in Bitwig (and Live?,) while also assuring me that the problem would be fixed before the next update. So, there is hope.

But you were saving as bitwig presets right? As aMUSEd said it seems vst presets and KK presets load ok if saved correctly.

I thought they were. It turned out not to be consistent. I still had to opt for loading (say) a Standard preset and then loading the MPE (or my resaved "BWS" preset.) So, I feel a little better than being at square one, but only a bit.

but what format? bitwig preset right?

[dlandis]

So who here wants to split up the saving of vst3 presets of equator?

Shame to lose all the attributes and ability to search though. Maybe KK is a better option.

If what I've experienced is any indicator, saving wouldn't help those presets without "partners" that don't load correctly and even saving the partner presets may not wok (at least consistently, I'm sorry to say.) Once one switches to another (non-partnered) preset, it appears that all bets are off as far as loading correctly. At best, there is still much inconsistently. (I was, BTW, going to save all the presets myself and if they offered a fix, share them, but I'm pretty sure that would be a worthless endeavor now.)

OTOH, I received a very pleasant reply from a ROLI tech, apologizing for the loading problem, and stating that they were attempting to fix the issue in Bitwig (and Live?,) while also assuring me that the problem would be fixed before the next update. So, there is hope.

But you were saving as bitwig presets right? As aMUSEd said it seems vst presets and KK presets load ok if saved correctly.

I thought they were. It turned out not to be consistent. I still had to opt for loading (say) a Standard preset and then loading the MPE (or my resaved "BWS" preset.) So, I feel a little better than being at square one, but only a bit.

but what format? bitwig preset right?

I was saving them from within Bitwig and using "BWS" as the identifier in the name in order to be able to correctly identify the preset that I had saved; "BWS" wasn't a format, just a way of being able to choose the right preset. Sorry if that wasn't clear. I hope it didn't cause any undue confusion.

[Echoes in the Attic]

So who here wants to split up the saving of vst3 presets of equator?

Shame to lose all the attributes and ability to search though. Maybe KK is a better option.

If what I've experienced is any indicator, saving wouldn't help those presets without "partners" that don't load correctly and even saving the partner presets may not wok (at least consistently, I'm sorry to say.) Once one switches to another (non-partnered) preset, it appears that all bets are off as far as loading correctly. At best, there is still much inconsistently. (I was, BTW, going to save all the presets myself and if they offered a fix, share them, but I'm pretty sure that would be a worthless endeavor now.)

OTOH, I received a very pleasant reply from a ROLI tech, apologizing for the loading problem, and stating that they were attempting to fix the issue in Bitwig (and Live?,) while also assuring me that the problem would be fixed before the next update. So, there is hope.

But you were saving as bitwig presets right? As aMUSEd said it seems vst presets and KK presets load ok if saved correctly.

I thought they were. It turned out not to be consistent. I still had to opt for loading (say) a Standard preset and then loading the MPE (or my resaved "BWS" preset.) So, I feel a little better than being at square one, but only a bit.

but what format? bitwig preset right?

I was saving them from within Bitwig and using "BWS" as the identifier in the name in order to be able to correctly identify the preset that I had saved; "BWS" wasn't a format, just a way of being able to choose the right preset. Sorry if that wasn't clear. I hope it didn't cause any undue confusion.

In Bitwig you can either save a device with it's settings as a bitwig preset (save to library) or as a VST3 preset. I think you're saying you saved as a bitwig preset, not as a vst3 preset from within bitwig. right?

[dlandis]

If what I've experienced is any indicator, saving wouldn't help those presets without "partners" that don't load correctly and even saving the partner presets may not wok (at least consistently, I'm sorry to say.) Once one switches to another (non-partnered) preset, it appears that all bets are off as far as loading correctly. At best, there is still much inconsistently. (I was, BTW, going to save all the presets myself and if they offered a fix, share them, but I'm pretty sure that would be a worthless endeavor now.)

OTOH, I received a very pleasant reply from a ROLI tech, apologizing for the loading problem, and stating that they were attempting to fix the issue in Bitwig (and Live?,) while also assuring me that the problem would be fixed before the next update. So, there is hope.

But you were saving as bitwig presets right? As aMUSEd said it seems vst presets and KK presets load ok if saved correctly.

I thought they were. It turned out not to be consistent. I still had to opt for loading (say) a Standard preset and then loading the MPE (or my resaved "BWS" preset.) So, I feel a little better than being at square one, but only a bit.

but what format? bitwig preset right?

I was saving them from within Bitwig and using "BWS" as the identifier in the name in order to be able to correctly identify the preset that I had saved; "BWS" wasn't a format, just a way of being able to choose the right preset. Sorry if that wasn't clear. I hope it didn't cause any undue confusion.

In Bitwig you can either save a device with it's settings as a bitwig preset (save to library) or as a VST3 preset. I think you're saying you saved as a bitwig preset, not as a vst3 preset from within bitwig. right?

No; again, I apologize for the confusion. I saved as a regular VST3 preset with an identifier of "BWS" within the name (I should have realized that would cause questions.) I did not save it as one would, say, for part of a chain. And just now I did have luck opening a project and having it load the "Additive Elegance BWS" preset I saved yesterday. I'll try to figure out why it worked this time (and didn't revert back to the tiny sounding patch I got yesterday.) Maybe the idea is that when one gets the preset the way one wants it to save it in the project at that point. There's probably more to it, but I'll keep checking.

[aMUSEd]

Just so people know there is an updated version of Equator 2 NKS now in the NKS User Library under Roli (thanks to NI forum member and UL contributor Vagus)

[Examigan]

Windows 10 only, but looks good otherwise...

In their specs they state Windows 10 (x64) or higher.
I assume that means it will also work on Windows 11.

For the Mac they say you'll need macOS 11/12.

[Echoes in the Attic]

I just noticed there was an update to Equator a few days ago (2.5.1) which seems to fix the bug discussed here of corrupting the audio and having messed up presets. The release notes indicate fixes to that effect and it seems to sound much better!

[Echoes in the Attic]

Version 2.5.1 - Release date 10/10/23

Bug Fixes

Corrupted audio when switching presets in VST3.
Parameter values not recalled correctly when saving a preset.
Corrupted samples in Oscar and Orchestral Ensembles soundpacks.
Automatically switching Init MPE preset to Stereo Motion Wavetable Pad preset in VST3.
Global pitch bend not being applied in Standard mode.

[MegaPixel]

Version 2.5.1 - Release date 10/10/23

Bug Fixes

Corrupted audio when switching presets in VST3.
Parameter values not recalled correctly when saving a preset.
Corrupted samples in Oscar and Orchestral Ensembles soundpacks.
Automatically switching Init MPE preset to Stereo Motion Wavetable Pad preset in VST3.
Global pitch bend not being applied in Standard mode.

For me, too little too late... No longer installed...

6+ months to get a critical bug fixed in their software that was so severe that equator 2 was unusable unless I purchased a different DAW.

Can you roll up/down the keys now like a normal keyboard when glide is set to max or was it zero? Or does it still jump and stick to random notes?

[Echoes in the Attic]

Version 2.5.1 - Release date 10/10/23

Bug Fixes

Corrupted audio when switching presets in VST3.
Parameter values not recalled correctly when saving a preset.
Corrupted samples in Oscar and Orchestral Ensembles soundpacks.
Automatically switching Init MPE preset to Stereo Motion Wavetable Pad preset in VST3.
Global pitch bend not being applied in Standard mode.

For me, too little too late... No longer installed...

6+ months to get a critical bug fixed in their software that was so severe that equator 2 was unusable unless I purchased a different DAW.

Can you roll up/down the keys now like a normal keyboard when glide is set to max or was it zero? Or does it still jump and stick to random notes?

Yeah I was about ready to give up on it, but was pleasantly surprised.

Not sure about that question you asked nor how to test.

[dlandis]

Version 2.5.1 - Release date 10/10/23

Bug Fixes

Corrupted audio when switching presets in VST3.
Parameter values not recalled correctly when saving a preset.
Corrupted samples in Oscar and Orchestral Ensembles soundpacks.
Automatically switching Init MPE preset to Stereo Motion Wavetable Pad preset in VST3.
Global pitch bend not being applied in Standard mode.

For me, too little too late... No longer installed...

6+ months to get a critical bug fixed in their software that was so severe that equator 2 was unusable unless I purchased a different DAW.

Can you roll up/down the keys now like a normal keyboard when glide is set to max or was it zero? Or does it still jump and stick to random notes?

It did take a long time to get the bug fixed regarding the preset corruption in Bitwig. To their credit, though it took quite while, Roli never ducked on blame for the issue. The issue in one sense was perhaps a bit more obvious because Bitwig's implementation of MPE may just be the best of any DAW. I am very happy to see it fixed.

As far as the glide issue you mention, I've never seen it in Bitwig. It does, however, still happen in Studio One as this is a recognized Studio One bug (with no scheduled date for rectification, and yes, it does happen similarly in all VSTs that allow for the use of MPE in Studio One.) It is most pronounced on patches with a longer release segment of the ADSR envelope.

[MegaPixel]

As far as the glide issue you mention, I've never seen it in Bitwig. It does, however, still happen in Studio One as this is a recognized Studio One bug (with no scheduled date for rectification, and yes, it does happen similarly in all VSTs that allow for the use of MPE in Studio One.) It is most pronounced on patches with a longer release segment of the ADSR envelope.

It actually stems from their software...

Skip to time 2m 44s

[dlandis]

As far as the glide issue you mention, I've never seen it in Bitwig. It does, however, still happen in Studio One as this is a recognized Studio One bug (with no scheduled date for rectification, and yes, it does happen similarly in all VSTs that allow for the use of MPE in Studio One.) It is most pronounced on patches with a longer release segment of the ADSR envelope.

It actually stems from their software...

Skip to time 2m 44s

Gotcha. Yes, this seems like a different issue than what I am seeing and others have reported in Studio One for sure. For one thing, what you've showed here is much more random sounding. The bug in SO reverts to the original pitch struck. And no, I don't think I've ever seen anything like this in Bitwig (thanks for the clarification, BTW.) Has anyone you know reported similar behavior with Equator 2 in Bitwig? Is it only Equator 2 or are other MPE synths showing the same erratic behavior? Have the techies at Bitwig been of help? Do you get the same behavior with the Arturia turned off (trying to think outside of the box a bit.) BTW, I do not have the Rise 2 as my MPE controller; I have two Seabord Blocks, a Lightpad M, and a Touch Block (FWIW; not sure that's the issue at all, of course.)