5.5 Bugs

Eventloop occured in Module. Show Moodule in Structure.
The Show in Structure part don´t work here.

In 5.1 the view switched from Panelview to Macroview after i confirmed this message.
Nothing happen in 5.5

 

I'll have sound one minute in standalone, then gone the next, sometimes if I change audio drivers it works, but most of the time it doesn't. I have to ethier close reload ensamble, reaktor and reopen, or even restart my pc which doesn't work all the time.

I have a WASAPI driver and ASIO4ALL

Between the above problem and the crashes things get quite discouraging

 

Can't drag 'n' drop samples any more in the Tape Machine, Audio Table, or Sample Look Up

 

please post 5.5 bugs here.

sowari

 

this sounds like a problem with your system and the WASAPI driver. maybe you should contact tech support.

sowari

 

see attached screenshots

 

also, similar to first post, "show in structure in 2nd pane" sometimes shows a blank pane in 2nd pane - the content is redrawn after some mouse action
---
oh and I have crackles at times using wasapi driver which disappear when I choose WASAPI a 2nd time from the list
but I also have issues with WASAPI in other software

 

is not possible anymore to set up a custom grid value on event/audio tables
it looks like it takes the value but when you go back to the propierties it has switched back to its default value.
---
pro-tools hd osx performance issue as described at the beginning of this thread:

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

 

reaktor 5.5.1 crashes cubase 5.5.1 on my i7 multicore-system.
deactivating hyperthreading and/or unchecking some cpu-cores in task manager for cubase5.exe did help but not fix it.

 

in reaktor 5.5.1:

graphical bug of waveform loopstart/end

it doesn't update itself as turning faders by mouse / or midi controller.

it updates after x seconds, never the same...or by clicking on another reaktor panel.

I tried with sampler resynth and some of my instruments as well.

 

Yep, same ting here. Really annoying because at first you think all modules in there (for example a macro) are deleted...

 

Hello @all in Cubase 5.5.1 & 5.5.2 (both 64bit) crashes Reaktor 5.5.1 the vstbridge

So und in Deutsch verständlicher(schließlich ist NI aus Deutschland) und mein Englisch katastrophal :-/
- es äussert sich so, dass ich nach kurzer Zeit keine Regler mehr bedienen kann
oder es meldet sich noch Cubase, dass die Vst Bridge abgestürzt ist.

ich hoffe, dass nach allen Updates langsam mal eine 64 Bit version rauskommen sollte

please Ni give us a 64Bit Version of Reaktor and no sticky updates

greetings

 

Yes, this is an annoying one. It's a problem for me in the grain cloud sampler module. I hope it gets fixed soon. In the meantime I'm having to muck around building with display objects just so I can see what I'm doing. =(

 

This sample map crash bug is confirmed by another user and makes me sad. :-(

 

When selecting multiple macros/modules and choosing the property "mono", all macros and modules in the current structure will become mono, not only the selected ones.

 

I'm still experiencing this crash and getting similar reports from some of the users buying my sampling pack, which uses the grain cloud sampler module. :-(

I know it's not just things I've built because I can produce the same crash in Grainstates.

It doesn't seem to affect everyone - I've only had a few reports - but the people who experience it get it consistently. Mac crash log is attached - I generated the crash by dragging samples in the Grainstates sample map. I can also produce the crash in Windows so it's not Mac-specific.

 

Drag any affect onto the window
NOw drag the 'grobian' ensemble' electronic musical instruments )into the instruments window ( so that it doesn't replace/create a new ensemble )
CRASH
STrange as this only happens with e the grobian ensemble
---
ahh ...disabling grobian ' legacy 4 'mode and resaving the ensemble solves the problem

 

In cubase 5.5, ( happens now and then )osx, The window displaying reaktor is sometimes cut off, only displaying the top 2/3rds, of the vst, and the browser.

 

Start/Stop module is randomly delayed in 7-16ms range (at least Start). Confirmed in Cubase in Ableton, don't know about other hosts. The bug is succeeded from older Reaktor 5 versions and still isn't fixed.

 

i get an odd bug

open new ensemble (by default it opens in split-screen for me).
go to the bottom half, right click and create new macro.
reaktor crashes

anybody else get this?