Ableton Forum

Hey there,

I stumbled across a little but very annoying bug concerning Reaktor and Ableton.
I copied a project over from my studio DAW to my macbook pro (via Collect All + Save)
only to find out that Ableton initializes the Reaktor ensembles in my projects on my macbook with a fresh instance (and the first preset of the Reaktor Player ensemble).

I suppose this has to do something with the Ableton Cache and the preset-management?
Will try to verify this by copying over the ableton cache from my main DAW as soon as I return home.

Any help would be appreciated

Matt

mattadms wrote:Hey there,

I stumbled across a little but very annoying bug concerning Reaktor and Ableton.
I copied a project over from my studio DAW to my macbook pro (via Collect All + Save)
only to find out that Ableton initializes the Reaktor ensembles in my projects on my macbook with a fresh instance (and the first preset of the Reaktor Player ensemble).

I suppose this has to do something with the Ableton Cache and the preset-management?
Will try to verify this by copying over the ableton cache from my main DAW as soon as I return home.

Any help would be appreciated

Matt

I found somewhat similar issues when basically just saving a setup and re loading it only to find that Reaktor is in the slot, but is not actually loaded with the preset used.
Digitalocean

I have got the same issue with Massive...
After saving the project, the preset of Massive is set to the default one.
I tried beta 8.3.X but no change...