A few minor R5 bugs I've discovered

I'm extremely happy with my R5 update, but I have discovered a few small bugs(I've already installed the hotfix BTW):

1. When switching views within a stacked macro while audio output is being generated, it creates artifacts(as if possibly the midi gate signal is being resent?)

2. Sometimes Nuendo 2 takes an unusually long time to open or save a project containing instances of R5(much longer than R4). This could just be that it is compiling the core modules, but sometimes it really takes a very long time.

3. Rarely, instances of R5 will open in a Nuendo project at double the internal samplerate they were saved at(for example, when the project was saved and Nuendo was closed, the .ens was set to 96000 hz, when the project was reopened it was set to 192000. This affected all instances of Reaktor 5 in that project).

My setup:
Athon64 3200+
1gb DDR 400
Asus Mobo
Nuendo 2.2
M-Audio Audiophile 192 soundcard

 

Oh, and Windows XP home

 

And another bug that I forgot to mention(which was also an R4 bug):

If the control rate is changed at the ensemble level, the LFO modules(event rate) do not adjust their internal timing, so if the rate is increased, the lfo will oscillate faster than what the "F" input specifies. Deleting the LFO module and inserting a new one, or closing and reopening the ensemble does fix the problem.

 

They really have done an outstanding job with the initial 5.0.0 release.

 

well there IS a bug

unfortunately, :

R5 replaces lamps with internal connections with a

AtoE(mono)-> StpFilter(poly) -> Send structure

but this replace has a bug, and gets messed up in
some case, see attached image

in this case, the send input doesnt work
it works, when the StpFilter is set to mono,

In other ensembles this seems to work fine
there is no obvious reason, why the send doesnt work here

 

Re: well there IS a bug

That's no bug - NI has changed the behavior of internal connections. In R4 you can use a lamp with internal connections to switch a receive modul. In R5 you have to use IC Send to have the same behaviour.
ciao herw

 

Re: well there IS a bug

the bug is, that the auto-replacement doesnt work as intended - just see the image
the in port of the send is "X"ed and doesnt send anything
untill you change the structure - which means that some user lib r4 ensembles do not work in r5

 

Re: well there IS a bug

yes - auto-replacement is difficult i think because you don't know in which way the author put its intention to work.
The combination of a step-filter and a ICSend is not usefull because the ICSend never sends same events - you can delete the step filter.
ciao herw

 

Re: well there IS a bug

well I can but someone who just downloaded this ens doesnt know whats going on - and the ensemble doesnt work as expected any more

and I still dont see why the send doesnt work here
or rather - I dont see why it does work in other cases - arent sends always mono anyway ? how can they be fed by a poly stepfilter ?

 

Re: well there IS a bug

the older and new Receive-module has two options: it gets Audio- or Event- data from a SEND-Module and works like a switcher; you could in R4 connect an internal connection from f.i. a meter to change the switch (RECEIVE).
The new SEND- and RECEIVE-Module are working in the same way. But the meters don't have the possibility to send a switching-event to the RECEIVE-module (for changing to another send module). You have to you use the ICSend to switch it. So some creator uses the meter as ICSend (if they have build internal connections in its properties). Using the meter is only a helpfull construct in R4. Now R5 decides between a meter (only to show values) and an internal connection. I think it clears up the structure.
ciao herw

 

thats what I knew, the point is, that the auto-replacement for these structures isnt reliebale

so people who had used this construct need to check back if it's still working

 

Hi,

I am a Reaktor developer here at NI. I thought that I fixed this LFO-bug some months before the R4 (!!!) Release and as far I test it right now it is fixed.
It would be very helpful if you would add some more description or give a full Ensemble where this bug occurs.

Please feel free to mail me directly:
georg.haupt@native-instruments.de

Best

Georg

 

Georg, did you see my post about the 64 bit bug ?
http://www.nativeinstruments.de/forum_de/showthread.php?t=26513

it would be nice if someone could confirm this bug