5.6.1 Bugs

Hi Sowari,

I had that issue on two windows 7 64 bit machines.
Haven't had any problems in standalone mode, yet. Only within Cubase 32 bit.
Maybe I loaded the 64 bit version of reaktor by mistake and the problem was caused by cubase's vst bridge. I will look into that this weekend and report back as soon as possible.

 

why are you using Cubase in 32 bit Mode?

sowari

 

Until some weeks ago I was using 64 bit mode, but there are still many vst plugins which are written in 32 bit only. Since the Cubase vst bridge lacks of stability I tried jbridger for some time, but that isn't very stable when using many instances, as well.

I just looked up which version of Reaktor I'm using within Cubase 32 bit and it is in fact the 32 bit version. So it is not the problem with Cubase's bridge

When I loaded up a Cubase project today, Reaktor also failed to load an instance of lazerbass. So it seems not to be a problem with Oki only, but with Reaktor itself.

I added some Crashlogs to this post.

 

B-Sides, please report your findings to tech support and include crashlogs.

sowari

 

The Finger is not controlable over the GUI anymore, just with MIDI!

cheers
Mike

 

Please see this thread, may be a bug?

http://www.native-instruments.com/forum/showthread.php?t=151547

 

another snapshot related issue
http://www.native-instruments.com/forum/showthread.php?t=152354
---
I have another major issue i've found, i've already wrote a ticket about this, i can't reproduce that here cause i have discovered it inside an ensemble that i don't want to share yet.
By the way the issue is the following:
I'm working on a very big ensemble where i'm using a lot of modules, i've probably found a cap, i was replacing some knobs to the "Enanched knob" version, http://co.native-instruments.com/index.php?id=userlibrary&type=0&ulbr=1&plview=detail&patchid=10334.
I have many pages, with many knobs, after a certain point "AtoE" and "Event Smoother" (and probably other modules) has stopped working.
They was working fine until the ensemble was opened, but when i have closed reaktor and re-opened the ensemble from a save they doesn't work anymore.
Basically they doesn't output anything, they only output values when i turn on/off reaktor or when i make a new connection with a cable. they acts like a "value" with the trig input unplugged.
If i try removing the latest knobs i've added and then save and re-open, the modules restart working again.
It looks like i've found a limit, and after that limit some modules stop working properly...
too bad!
I hope they will have a look to the ticket i've sent, in the meantime, if anyone has encountered this kind of problem please let me know, at the moment i'm at a dead end and i can't complete my ensemble... i was quite near to finish damnit!
As i do not have received any confirmation about my ticket if someone at NI is actually reading this and wants the ensembles to test please contact me and i'll provide you all the things to reproduce the problem.

 

Just FYI i've found what is causing the modules issue, is the system info module, too many system info modules inside the ensemble causes some modules to stop working properly.
I had more than 100 when the bug has appeared, can't count exactly how many, by the way it can be easily avoided using only 1 and connecting everything to it.
So prblem solved, well, not solved, but workarounded

I've just read reaktor 5.6.2 update info, nice to see that snapshot master will come back, great!
i hope reverting that functionality will eliminate the above issue aswell..
thanks.

 

Playing a tweaked version of CARBON, the "f" key triggers the computer to make its typical beeping sound, which has nothing to do with the Reaktor sounds and ruins my performances. I have no idea how to fix this. Any suggestions will be very, very welcome!

 

the 'f' key does not play a note in reaktor (assuming you mean on a computer keyboard...)
so there's no reason to play it.
also if your soundcard is set up correctly windows will not be able to access it while reaktor is running

 

Quickbus float / integer

not a bug, but a "feature", also in Reaktor 5.6.1:

when changing the source port af a quickbus from integer to float (or vice versa), the quickbus itself doesnt. But in my opinion it should. Normal wires dont have this option. They always behave like their source port.
I thiunk this behavior is not very user friendly. It took me a long time to find this "bug" in my ensemble. :angry:

cheers,
quietschboy

 

Unfortunately i have encountred the same issue also with the "Step Filter" module, so it's not only related to the "system info" module, too bad!
I'm converting as much as i can to core cell in order to avoid bad surprises, i don't know if there are other modules affected by this issue, but at this point probably yes!

 

Mac ensemble recall issues

Bug with how ensembles recall in 5.6.1 when using Reaktor in plugin mode.
When using Reaktor in a host/daw using 5.6.1, the instrument won't recall its saved state properly.

 

I've been seeing this on PC also... I usually have to reload the ens and preset...

 

Sorry to bring up an old sore subject, but I need some help regarding the incompatibility of 5.6.1 files in 5.6.0.

I created a few large ensembles in 5.6.1, and need to be able to downgrade them to work with 5.6.0.

Impossible?

Any copy/paste, or manual editing (decoding) of the .ens file workaround possible?

If not, I IMPLORE NI to have a SAVE AS PREVIOUS option available!

This is madness!

Oh, btw, no bug stickies on 5.7.x? All is well now, or people have given up?

---

 

i am afraid that will not be possible - most likely never, ever.

fwiw, 5.6.2 was the updated version of 5.6, so i am surprised you have not got that?



and sorry, i forgot to create a bug sticky fo 5.7.1 - i have done so now

sowari

 

Oh dear, I was afraid of that. You see I was having a bit of a problem with Logic + Reaktor + Bidule:

http://plogue.com/phpBB3/viewtopic.php?f=10&t=6447

and anyway, I was putting the finishing touches on a system with Reaktor 5.6.1, and lo and behold the snapshot parenting became an issue, so I upgraded to 5.6.2. Voila, but no. Again the cable drop issue, as cited above, reared its ugly head. So I thought, aha by all means back to 5.6.0. And then I got really greedy and started thinking, oh the good old days of 5.1.5, when the plugin window could be minimized with one click. But, but, but, but now that you've ruined that fantasy. :cry:

Btw, what happened to versions 5.2, 5.3, and 5.4 ?

 

unsticking this thread.