Rift 2.0.1 - Bug Fixes and Optimization

#1

Hey everyone,

We’ve got a Rift update that fixes some issues that came up since the 2.0 release.

We’d super appreciate it if you could install 2.0.1 and let us know how it works for you and what OS/DAW you tested on.

Changes:

  • Complete overhaul of graphics rendering to better work on all OSs but particularly M1 Macs.
  • Improved modulator timeline syncing in some less common situations.
  • Fixed some crashes that were reported in Logic and Ableton.
  • Fixed an issue with VST3 not recalling UI size.
  • Some more optimizations

If you notice anything off about the graphics or timeline sync, please let us know!

Download Rift 2.0.1

Thanks :pray:

3 Likes
Remember window size
Ableton Live -> Saving Clips with Rift causes crash
#2

Hi @jake.minimal and @ben.minimal , I am not sure where this comes from, but I have the weirdest of issues with this new Rift version.

I was just working on a track and put Rift onto a drum buss track. So far so good. Sometimes when I played back the project in Live, there occurred some kind of unpleasant distortion, sounding like some bit-crushing, out of the blue. If I stopped and re-started playback, the effect was gone and stayed away. I kind of thought it was due to some buffer underrun, so I ignored it more or less, as it went away again.
But, when I now export the whole track off Ableton Live (11.1.1 or current 11.5b2 Beta), it produces these distortion burps in the mixdown, at the same places all the time. It’s not on the whole track, just in certain places. Disabling Rift, or replacing it with the older 2.0.0r4 version I still had lying around, actually solves this.

I’m on Windows 11, latest updates, Live as described above, using the VST3 version of Rift 2.0.1. I can send you the two exports if needed, or the preset I created, though I assume the problem is probably hard to recreate reliably. Let me know if you need anything!

Edit: Probably not extremely relevant, but my CPU and/or RAM haven’t even nearly been maxed out, as I have a beast of a machine. Changing buffer size for my audio interface didn’t help therefore.

#3

Hey @ratzekind – thanks so much for letting us know about this issue. Is it reproducible if you duplicate you ableton session and remove all the channels but Rift? If you can send us the project file where it’s occurring, that is super helpful for us to recreate the issue.

#4

Preset is good too! ----

#5

Hi @jake.minimal, okay, so I went with what you proposed, stripped everything off my set, even bounced the audio of my drum machine and left everything else outside. So no other effects, just Rift on a grouped track. You’ll find the download here, including a vst3preset for Rift (I used one of the presets and tweaked it afterwards). Also included is a bounce of the set as you find it here. Starting at about 14 seconds, you’ll hear the bit-crushing effect I was talking about, in case you cannot get that when you export my set.

1 Like
#6

Amazing!

Thanks so much we’re reviewing this now.

1 Like
#7

Awesome – just want to share publicly here that we’ve found and resolved this issue, and will be posting another set of installers and doing another round of testing before we make this fully public on the website and update users

#8

Thanks @ratzekind!

We’re pretty sure we’ve fixed the issue. Can you please update Rift using this installer and let us know if it’s fixed?

https://drive.google.com/drive/folders/1SsLYu9tl3yAL7VEO96nYA8HMjWG5pe2U?usp=sharing

Really appreciate you sharing your files. It made tracking it down easy.

1 Like
#9

@ben.minimal @jake.minimal I can confirm the problem is gone with the latest installer. Yeeha! Jake explained the problem with Ableton Live in a private message in detail, so I have a notion of the trouble you went through. And I’m glad you found it. Keep on keeping on :blush:!

2 Likes