Instruments breaking in Razor

Just bought Razor and installed Reaktor. When I close and restart Logic, the Razor instruments stop working?
I own other instruments like Sylenth and Absynthe 4 which work fine. For some reason, when I restart Logic only the instruments out of Razor stop working. They dont disconnect, they just become a weird super quiet synth and I have to create an entirely new track, select that instrument and move the notes down to that track to even get it to work again. Is there a fix to this?

 

Yes this happens to me too, but not with other Reaktor ensembles, only Razor. They need to bring out an update to fix it. It sux. Hard.

 

same thing here... I reopen Razor in Reaktor and reselect the preset and I'm back to working, it is still very annoying though.

 

Wow...
I bought Razor over the weekend and I signed up to this forum to see if anyone was having the same problem as me and I found this.

My situation is almost identical to the OPs.

I have a project with 3 Razor instances and whenever I reopen the project one of them stops working. It's always the same one.

I don't own any other Reaktor synths but it does seem like it's likely to be a problem with Razor as opposed to that as I find I can make it start working again if I reopen Razor within the same instance of Reaktor (I used to just remake the whole track and shift the notes down.

I'm also using Logic Pro.

This is so frustrating, I love the synth but this bug is really getting to me.

 

Turn Reaktor off and on again with the icon in the top right hand corner and it starts working again, no need for any other workaround

 

my problem is the same, i use razor in maschine, i save, but when i close then re open what ive been working on razor reverts back to normal, so all my changes dont get saved. sometimes one will not work.

 

I'm getting this problem too. I'm using it in Reaper 4.10 x64.

 

I'm not sure what icon your talking about. If you mean the NI logo in the top right I can't get that to work. Can you be more specific? Thanks!
---
Also, just FYI. Someone from NI mailed me and asked me if I had the latest version of Reaktor installed. I told him of course I did, I just bought the program. He then mailed me back and told me they were aware of the issue and were working on an update for it. Hopefully they get it done soon because I frankly think it's incredibly embarrassing to let an issue of this magnitude go on for so long.

 

I just wanted to clarify this. I add an instance of Razor as an insert on a track and use any supplied patch/snapshot from razor's library. Fine everything works no issues. However when the project is opened again the instance of Razor loads with the right patch but doesn't run (ie -- no sound).

Clicking on the "on/off" button twice somehow solves the issue and then all is OK....

until you open the project again... then no sound.

 

Same problem here with Razor.
DAW: Win 7 64bit (all fixes), Cubase 6.0.3 64bit, Reaktor 5.6.1 x64, Razor 1.2.0

Cubase Project with 6 instances of Reaktor (VST instruments) each with a Razor ensemble (each with different factory snapshot).

After loading Cubase project, 3 of 6 Razor ensembles work (the analyzer shows) but no output, CPU-consumption in Reaktor (top right) shows approx. 11%. Clicking the CPU button in Reaktor (top-right), reduces the CPU consumption (to approx. 2-3%) and the output is working.

... annoying to restart several Reaktor instances every time loading a cubase project.

 

Having the same problem with Razor in Pro Tools 10 on Mac OS X 10.7.2. Just opened up a session and one of the Razor instances wasn't playing the right sound. Had to reload the patch to get it right again.

 

please send a report to tech support.

sowari

 

ive found if you save it as a preset in reactor then when you open it back up, and the knob settings have reverted, or the patch dont work, then you can go into ur user section and click em... its a pain to do all this, but atleast i can close my songs now without fear of everything changing... this needs to be fixed soon!:S

 

I did, they said they were aware of the problem and were working on an update.