What three (new) features would you like to see in Reaktor?

1)like luca better logic statements ,do while,for,loops.very important.

2)a 3d graphics module not to copy jitter but to enhance gui to a new level.

3)audio resynthesis language ,for time frequency manipulation
making dsp more easyily accessable.

 

Some sort of scripting or C++ module SDK would be nice.

 

1. Dynamic arrays; Possibility to change the Event Table/Various other data modules size at runtime.

2. Better GUI elements. A large part of Instrument building goes off on GUI building. Should be easier.

3. VST/AU export feature.

 

1. better snapshot switching! my number one problem with reaktor. i am using reaktor live and i can't switch patches without clicks and skips.

2. better sounding filters. maybe i just don't know enough yet, but i can't seem to get a good sound out of the filters, especially with high resonance and audio rate modulation.

3. multi-processor support. maybe this is unrealistic, i don't know anything about it. but i sure would like twice the cpu!

 

A few things i've found that could be improved:

1. No limit for OSC receive objects! aaarrrgh!

2. The ability to load sample maps from a folder (e.g. into a beatloop object) by using an event input. for example, if there are 100 map files in the folder of the currently loaded map, an event value from 1-100 will load the 1st-100th map, in alphabetical order. i know this sounds a bit insane but it might make things easier for people using lots of large sample maps in a live situation.

2b. Also, stop the GUI being locked up while a large sample map is being loaded.

3. Increase the BPM range of the BeatLoop object so it includes faster tempos (i.e. >174bpm or whatever the top limit is at the moment).

 

I guess I do have three.

3. better memory management for Tapedeck and Audio Table. i.e. do away with setting maximum memory size in Tapedeck. In Audio Table, implement a use-as-you-go scheme for memory when recording audio and provide an option for infinite samples.

 

Paraphrased:
1. Cleanup and Complete the CORE system and OBC connections(whose usage in my opinion is very limited to a few points), preferably by introducing new built-in features.
2. Implement Class/Object system.
3. Step Debugging
4. Scripting Engine(preferred)/SDK(not preferred) used to develop additional modules(Both Core and Primary).


Reaktor is better used as a Father-Of-All-Plugins plugin, not a DAW/Sequencer(since we have professional ones already)! Though Reaktor is pretty capable to build decent sequencers...

 

I would just write that one 3 times.

 

The tapedeck from Guitar Rig
The ease of setting modulation that Guitar Rig has
Fix the synch.

 

Unfortunately, I don't see how that can be done. GR's components have hard-assigned parameter IDs. Reaktor assigns the parameter IDs in the order that the module/what have you's inserted into the structure. Hard-assigned IDs wouldn't work in Reaktor's case for the most part.

ew

 

1. Toolbars and easy navigation through windows

2. A LOT MORE thorough and extended, yet accessible documentation

3. Full OSC implementation

 

i think the ability to make sound installations and pieces for multiple performers is all most are getting at with that. for the most part is it not already a community of certain individuals building and others enjoying the fruits of their labor? also i know we have all noticed the appearance of NI moving its focus to hardware and "players", is this the only way we can hope to keep reaktor alive is through the process of creating a feature restricted version, to supplement the current line? i dont know, but the idea of reaktor becoming less exclusive is an idea i on one hand dont like on the other, it will boost the familarity of the product. in addition reaktor at its heart is something to be uniquely used by each individual.anyway
1multicore support
2runtime
3better help
i know they were all mentioned but i needed to chime in

 

- better reaktor standalone multicore support on mac
- openCL support for all plattforms -> look here for more info... this is a killer performance booster
- a cheap player version of reaktor
---
oh... and not to forget. fast native c/c++ coded core and primary FFT's/iFFT's modules... its nice to have those from the userlib, but they cost way to much cpu.

 

What was Reaktor Session? Sorry, I'm new user and haven't heard anything of it before.

 

owners of session could use reaktor ensembles and also had access to the UL but you could not build or edit ensembles, if i remember rightly.

i nearly bought it, but i'm glad i didn't.

 

You could only work at Instrument level, but not inside Instruments. You could then build your custom Ensembles using ready made Instruments.

Nice idea but I guess too clever for it's own good...

 

This is easy.

1) Quit gimping around and make a music DSP IDE plugin for Eclipse. For the noobs you can still provide drag & drop design (ala Flex Builder), for the advanced people let them integrate in source code directly. Steal Actionscript or Python syntax for the programming language, compile it into optimized bytecode -- programming 'core' is like programming assembly with visio as an IDE -- worse than programming assembly using a text editor. The drag-and-drop component idea is great, but don't punish people who can think beyond it.

The day of all-in-one is over and unnecessary, build discrete components that allow you to document, test, package and distribute coherently.

If you do this and create an 'Apple Store' for Kore sounds (NI gets a cut of everything sold), NI could be rolling in cash. This is a no-brainer.

I've been saying variations on this for ages tho.

-n

 

1: a vst/i loader
2: can changing color and police for a gui directly in reaktor for knobs.
3: new language for interface and note (french :-D)
4: possibilities of "macroisation" like synthedit. you select your modules with your mouse, right click>macroisation, and you have a new macro, all connected!