Reaktor Session Update 1.0.1.004 - Bug List (PC)

Reaktor Session Update 1.0.1.004 - Bug List (PC)

Alectro started the list for the first version of Reaktor Session. Now we have the update and some of the bugs will have disappeared others won't ... I think, it's a good idea to have a new list for the updated version ...

Alectro, for the following I use your words:

Please check through list and see if your bug is already listed. If not then add to end of the list (i.e. give next number is sequence).

This will prevent multiple postigs of the same bug and help to get an idea of the number and severity of problems.

Keep your bug report short and to the point and include the operating system and host, plus any other identifying fators (e.g. soundcard incompatibilities):

 

Known Bugs

Found on PC, AMD Athlon 2100+, Windows XP, running Cubase SL:

1 - Add a new Reaktor Session VSTi, load any ensemble, move any control, then leave Cubase without saving. CPU load increases to 100% and Cubase will hang. Doing the same with LinPlug FreeAlpha VSTi works correct.

2 - Now loading ensembles from the user library works in most cases using Session in standalone mode. Loading such ensembles as VSTi in Cubase SL reports "Error while reading file ...: Not A Valid File!", then an Exception is thrown by Cubase "Unknown Exception". Thereafter you cannot load any other ensemble, not even the ones from Session's library. You will get "Unknown Exception".

Found on PC, AMD Athlon 2100+, Windows XP, running Reaktor Session in standalone mode:

3 - Sustain (Controller 64) does not work. In VSTi mode sustain works fine.

 

More known bugs

Found on PC, AMD Athlon 2100+, Windows XP, running Cubase SL:

1 - Add a new Reaktor Session VSTi, load any ensemble, move any control, then leave Cubase without saving. CPU load increases to 100% and Cubase will hang. Doing the same with LinPlug FreeAlpha VSTi works correct.

2 - Now loading ensembles from the user library works in most cases using Session in standalone mode. Loading such ensembles as VSTi in Cubase SL reports "Error while reading file ...: Not A Valid File!", then an Exception is thrown by Cubase "Unknown Exception". Thereafter you cannot load any other ensemble, not even the ones from Session's
library. You will get "Unknown Exception".

3 - When opening a song with an instrument saved and the solo button 'on', the solo button needs to be turned off and on again before sound can be heard even though the GUI indicates that solo is already on.

Found on PC, AMD Athlon 2100+, Windows XP, running Reaktor Session in standalone mode:

4 - Sustain (Controller 64) does not work. In VSTi mode sustain works fine.

5 - When sizing the Reaktor Session window to full size there are small regions (0,5 -1 cm) at the right side and the bottom of the window, which will not be refreshed.

 

Re: More known bugs

Found on PC, AMD Athlon 2100+, Windows XP, running Cubase SL:

1 - Add a new Reaktor Session VSTi, load any ensemble, move any control, then leave Cubase without saving. CPU load increases to 100% and Cubase will hang. Doing the same with LinPlug FreeAlpha VSTi works correct.

2 - Now loading ensembles from the user library works in most cases using Session in standalone mode. Loading such ensembles as VSTi in Cubase SL reports "Error while reading file ...: Not A Valid File!", then an Exception is thrown by Cubase "Unknown Exception". Thereafter you cannot load any other ensemble, not even the ones from Session's
library. You will get "Unknown Exception".

3 - When opening a song with an instrument saved and the solo button 'on', the solo button needs to be turned off and on again before sound can be heard even though the GUI indicates that solo is already on.

Found on PC, AMD Athlon 2100+, Windows XP, running Reaktor Session in standalone mode:

4 - Sustain (Controller 64) does not work. In VSTi mode sustain works fine.

5 - When sizing the Reaktor Session window to full size there are small regions (0,5 -1 cm) at the right side and the bottom of the window, which will not be refreshed.


Found with Windows XP running FL Studio 4 and Cubase SX

6 - Windows XP suffers total system failure after installing update and restarting PC.

1 - Install v1.0.1 update
2 - Open Reaktor Session as a VSTi in host (FL Studio 4.1 and Cubase SX)
3 - Open any ensemble (e.g. Junatik)
4 - Close Reaktor Session VSTi and host.
5 - Restart PC
6 - On restarting PC nothing works at all in Windows XP.

No programs work (e.g. internet explorer, Reaktor Sessions, FL Studio 4, Cubase SX). No system tools work (e.g. control panel, system restore). Cannot restart computer again except in safe mode.

I have found that I can install the update and as long as I don't open Reaktor Sessions at all then I can restart my PC without any system failure. I only get the system failure if I open RS after installing update and then restarting PC.

 

just some more

Found on PC, AMD Athlon 2100+, Windows XP, running Cubase SL:

1 - Add a new Reaktor Session VSTi, load any ensemble, move any control, then leave Cubase without saving. CPU load increases to 100% and Cubase will hang. Doing the same with LinPlug FreeAlpha VSTi works correct.

2 - Now loading ensembles from the user library works in most cases using Session in standalone mode. Loading such ensembles as VSTi in Cubase SL reports "Error while reading file ...: Not A Valid File!", then an Exception is thrown by Cubase "Unknown Exception". Thereafter you cannot load any other ensemble, not even the ones from Session's
library. You will get "Unknown Exception".

3 - When opening a song with an instrument saved and the solo button 'on', the solo button needs to be turned off and on again before sound can be heard even though the GUI indicates that solo is already on.

Found on PC, AMD Athlon 2100+, Windows XP, running Reaktor Session in standalone mode:

4 - Sustain (Controller 64) does not work. In VSTi mode sustain works fine.

5 - When sizing the Reaktor Session window to full size there are small regions (0,5 -1 cm) at the right side and the bottom of the window, which will not be refreshed.


Found with Windows XP running FL Studio 4 and Cubase SX

6 - Windows XP suffers total system failure after installing update and restarting PC.

1 - Install v1.0.1 update
2 - Open Reaktor Session as a VSTi in host (FL Studio 4.1 and Cubase SX)
3 - Open any ensemble (e.g. Junatik)
4 - Close Reaktor Session VSTi and host.
5 - Restart PC
6 - On restarting PC nothing works at all in Windows XP.

No programs work (e.g. internet explorer, Reaktor Sessions, FL Studio 4, Cubase SX). No system tools work (e.g. control panel, system restore). Cannot restart computer again except in safe mode.

I have found that I can install the update and as long as I don't open Reaktor Sessions at all then I can restart my PC without any system failure. I only get the system failure if I open RS after installing update and then restarting PC.

Found on PC, AMD Athlon 2100+, Windows XP, running Cubase SL:

7 - Cubase crashes when moving the morph slider after using a snapshot previously saved

- Load Reaktor Session as VSTi
- Load Carbon.ens(I tried with Nanowave and Junatik too, it's the same)
- Select the instrument's snapshot view
- Use the Reaktor Session VSTi as output device in a midi track
- Save the ensemble or close the Reaktor Session Window then save the Cubase project
- Restart Cubase
- Open the Reaktor Session Window with the "e"-Button in Cubase
- Move the morph slider - Cubase crashes

What I noticed:
After restart of Cubase the initially loaded bank within Reaktor Session is not the bank used before - it's a bank with empty snapshots, like a bank in init state. But in the "Banks" Listbox (in snapshot view) the name Bank 1 is displayed. Choosing Bank 1 again will make Cubase throw an Unknown Exception.

Workaround:
Changing the snapshot (or choosing the selected snapshot again) within the listbox in the instrument window header will show
the real Bank 1 snapshot names in the snapshot view. Other possibility: change from snapshot view to browser view and back again.

8 - Create a snapshot in Reaktor Session standalone mode (Nanowave.ens) then open Cubase and try to load the previously modified ensemble, "Error while reading file ...: Not A Valid File!" is shown, next a Cubase Unknown Exception will be thrown.
When trying to open a Cubase project where that ensemble is already used, it's even worse: the project cannot be opened again.

 

more pc bugs

Running it on a Pent 4, 1.4 gig, 512ram, Windows xp, Sonar 2xl, Aardvark lx6.

Sharing a few woes, in hopes that they will be addressed in future updates. I know some of these have been listed elsewhere.

1. With BeatSlicer, I can't play my own loops. I load one up, it appears in the table, but all I get is a few dull pops when I play the loop sequencer. Detecting or slicing does not help.

2. None of RS's sequencers sync up well when I'm using it as a DXi in Sonar. The rhythm has an irregular shuffling sound. I tried several MIDI out settings in Sonar, but it doesn't improve it. Maybe a compatibility problem because RS syncs up fine to FLStudio. I can open up FL as a DXi and open RS there and it will be in sync in Sonar though.

3. Neither the Recorderbox nor Playerbox will loop the recording. I press the button and it's lit up, but the playing stops after one cycle. Makes it hard to check my loops. Also, the quality of the recording is generally noisy - it sounds like it's clipping. Adjusting the main level in the instrument or ensemble before recording seems to help, but the quality of the audio is different than the sound coming from the instrument.

4. The envelope in the Analogic Filter doesn't work.

5. Green Matrix, Panel B: Where is it? It's kinda ironic that "matrix" is part of the name of the instrument. I've heard that a modification in Reaktor proper will fix it. Perhaps a kind soul with "Big Daddy" will post it in the library.

 

bug list updated - three bugs disappeared

Bugs 1,2,8 - listed in the thread formerly - do not exist in RS Update 1.0.1.004. Because of a mistake I made when installing the update, I got another vstplugins folder within the existing vstplugins folder. For some reason, I did not realize the new ReaktorSession VSTi within that new folder and continued working with the original ReaktorSessionVST VSTi, which was the old RS VSTi. Sorry for that. Following the new list:

-- Found on PC, AMD Athlon 2100+, Windows XP, running Cubase SL:

1 - When opening a song with an instrument saved and the solo button 'on', the solo button needs to be turned off and on again before sound can be heard even though the GUI indicates that solo is already on.

Found on PC, AMD Athlon 2100+, Windows XP, running Reaktor Session in standalone mode:

2 - Sustain (Controller 64) does not work. In VSTi mode sustain works fine.

3 - When sizing the Reaktor Session window to full size there are small regions (0,5 -1 cm) at the right side and the bottom of the window, which will not be refreshed.

-- Found with Windows XP running FL Studio 4 and Cubase SX

4 - Windows XP suffers total system failure after installing update and restarting PC.

1 - Install v1.0.1 update
2 - Open Reaktor Session as a VSTi in host (FL Studio 4.1 and Cubase SX)
3 - Open any ensemble (e.g. Junatik)
4 - Close Reaktor Session VSTi and host.
5 - Restart PC
6 - On restarting PC nothing works at all in Windows XP.

No programs work (e.g. internet explorer, Reaktor Sessions, FL Studio 4, Cubase SX). No system tools work (e.g. control panel, system restore). Cannot restart computer again except in safe mode.

I have found that I can install the update and as long as I don't open Reaktor Sessions at all then I can restart my PC without any system failure. I only get the system failure if I open RS after installing update and then restarting PC.

-- Found on PC, AMD Athlon 2100+, Windows XP, running Cubase SL:

5 - Cubase crashes when moving the morph slider after using a snapshot previously saved

- Load Reaktor Session as VSTi
- Load Carbon.ens(I tried with Nanowave and Junatik too, it's the same)
- Select the instrument's snapshot view
- Use the Reaktor Session VSTi as output device in a midi track
- Save the ensemble or close the Reaktor Session Window then save the Cubase project
- Restart Cubase
- Open the Reaktor Session Window with the "e"-Button in Cubase
- Move the morph slider - Cubase crashes

What I noticed:
After restart of Cubase the initially loaded bank within Reaktor Session is not the bank used before - it's a bank with empty snapshots, like a bank in init state. But in the "Banks" Listbox (in snapshot view) the name Bank 1 is displayed. Choosing Bank 1 again will make Cubase throw an Unknown Exception.

Workaround:
Changing the snapshot (or choosing the selected snapshot again) within the listbox in the instrument window header will show
the real Bank 1 snapshot names in the snapshot view. Other possibility: change from snapshot view to browser view and back again.

-- Running it on a Pent 4, 1.4 gig, 512ram, Windows xp, Sonar 2xl, Aardvark lx6.

6 - With BeatSlicer, I can't play my own loops. I load one up, it appears in the table, but all I get is a few dull pops when I play the loop sequencer. Detecting or slicing does not help.

7 - None of RS's sequencers sync up well when I'm using it as a DXi in Sonar. The rhythm has an irregular shuffling sound. I tried several MIDI out settings in Sonar, but it doesn't improve it. Maybe a compatibility problem because RS syncs up fine to FLStudio. I can open up FL as a DXi and open RS there and it will be in sync in Sonar though.

8 - Neither the Recorderbox nor Playerbox will loop the recording. I press the button and it's lit up, but the playing stops after one cycle. Makes it hard to check my loops. Also, the quality of the recording is generally noisy - it sounds like it's clipping. Adjusting the main level in the instrument or ensemble before recording seems to help, but the quality of the audio is different than the sound coming from the instrument.

9 - The envelope in the Analogic Filter doesn't work.

10 - Green Matrix, Panel B: Where is it? It's kinda ironic that "matrix" is part of the name of the instrument. I've heard that a modification in Reaktor proper will fix it. Perhaps a kind soul with "Big Daddy" will post it in the library.