Problems with Host saving state of Reaktor

Magic Russ

I have a number of projects in Cakewalk on Windows 10 which use Reaktor 6. Recently I was going through some older projects from May 2021. In each of these projects, when I tried to display the plugin window for tracks containing instances of R6, the plugin was in a blank state. In other words, instead of having the ensemble and snapshot loaded that I was using when I saved the project, Reaktor appears as it does when it is initially instantiated.

I looked back through the release notes to find that Reaktor 6 will automatically migrate from VST2 to VST3. Is it possible that that functionality might have caused the problems I am seeing?

Edit: I should note that this is something that seems to affect only older projects. I did create a project recently to see if new projects were recalling project state correctly and did not run into that problem.

Jeremy_NI

So, the answer from our supporters is:

Unfortunately automatic VST2 to VST3 migration is currently not supported for Reaktor within Cakewalk. The development team are aware of this and it works for some DAW's but not all.

 The only way to use the VST3 plug-in would be to open Reaktor with the VST2 as you have previously done, make a note of the presets used, delete the instance of Reaktor VST2 and replace with VST3 then open the preset once more. Unfortunately there is no other way round this at the moment.

Sunborn

VST2 to VST3 migrate has nothing to do with this.

Maybe when you made the old projects, the Reaktor ensembles you used, was on a different folders and/or hard disc?

Magic Russ

I did swap out my d: drive recently, which contains all of my projects, samples, and Native Instruments directory. However, I restored everything to back where it was.

IF swapping out my hard drive was the problem, why am I only having that issue with Reaktor 6 and not other plugins? I have some older projects with instances of Reaktor 5. Why then can R5 find the ensembles and R6 can't?

Sunborn

https://community.native-instruments.com/discussion/comment/78285#Comment_78285

Ok. So, maybe you have both versions installed? VST2 and VST3? And somehow this "confuses" Cakewalk? Logically, you should only have the VST3 version since now Reaktor migrates automatically from VST2 to VST3.

So, do some experiment!:

-If you already have both installed, remove the one and check out with the other. First remove the VST2 (and keep VST3) and if it's not work, do the opposite. Finally, trying all different combinations will solve this.

-If you have VST3 only, install the VST2 also, and vise versa (if you have VST2, also install VST3).

Note: by "remove" i always mean backup, not delete! Just move your .dll or .vst3 file to another directory for a while.

Paule

Do you create backups of your settings? Have a look there, please. If you never create backups, it's a pitty. As a Reaktor builder I ever create backups of my work and take a copy outside into another path on external hdd.

Magic Russ

This is clearly a migration issue.

In Cakewalk, there is an option to automatically load VST3 if both VST2 and VST3 versions are available.

When I load a project where I saved with VST2 and this option is unchecked, it recalls the state of the plugin correctly.

When I load a project with that option checked, it does not recall the state of the plugin correctly.

As far as I know, Reaktor 6 is the only plugin where I have had that problem.

Paule

I don't use projects or midi daws. So there is less experience here.

But you can be on the save page if you save the snapshot first before you save your project.

Jeremy_NI

@Magic Russ I didn't see other reports like this but we would need to look into it, so I contacted you by email and will forward the case to my colleagues.

Jeremy_NI

So, the answer from our supporters is:

Unfortunately automatic VST2 to VST3 migration is currently not supported for Reaktor within Cakewalk. The development team are aware of this and it works for some DAW's but not all.

 The only way to use the VST3 plug-in would be to open Reaktor with the VST2 as you have previously done, make a note of the presets used, delete the instance of Reaktor VST2 and replace with VST3 then open the preset once more. Unfortunately there is no other way round this at the moment.