thom
41
Well, to take it a little further I must say that I only use one Native Instrument product (Reaktor), and I’ve never been annoyed by Native Access.
(edit) …Or maybe two products to be honest, as I use both Reaktor 5 and Reaktor 6 !
1 Like
Szuumm
42
Love the sound of this (albeit on my phone speaker).
Definitely going to have a play once the sun has gone down sufficiently to justify me sitting inside on my laptop 
)
1 Like
Is there something that 5 does that 6 can’t? I also have both, but never thought to keep using 5 after I got 6…
Szuumm
44
I think I’ve you’ve already got DAW projects that use 5, there’s no easy way to replace instances with 6 ( I could well be wrong though).
1 Like
thom
45
This is part of the answer.
Also, almost every single day I use two computers (for various reasons) to work on the same Ableton Live 9 Projects that include many Reaktor instances.
The Projects are shared between the two computers using DropBox.
When loading a Project that was last opened on the other computer, I have to locate the Reaktor Ensembles that were previously saved with the Project, as proposed by the following window.
With Reaktor 5, I have to show the path only once for all Ensembles, thanks to this second window.
Unfortunately, the second window does not appear when using Reaktor 6.
This means that I would have to locate between 20 and 40 Ensembles separately (depending on the Project) each time I open a Project that was last opened on the other computer (several times a day).
One day, I read the user manual and searched the forums for a solution to this problem, without success.
Until today I didn’t ask Native Instruments about it, as I’m fine with Reaktor 5 most of the time (I only use Reaktor 6 to see how builders have implemented such and such function, to find inspiration or a solution to a specific problem).
And, honestly, I’d prefer to continue using Reaktor 5 as long as possible.
I’m comfortable with the interface and do not need the extra features offered by Reaktor 6.
Anyway, if anyone has a trick for showing the path only once when using multiple instances of Reaktor 6 in Live 9, I’d be happy to know, as it would be useful to me from time to time when I reverse engineer a Reaktor 6 Ensemble.
It’s quite possible that there is an extremely simple solution that I completely overlooked !
1 Like
LLK
46
I agree it’s a major annoyance with R6, I have sort of the same process and it’s just very problematic to have to deal with this each and everytime. I think we can fairly say that in general, NI’s softwares file management systems (metadata, folder structure coherence from one program to the next, importation, etc.) is close to catastrophic. It feels like they’re just crumbling under the weight of their own scattered gigantic mess of softwares coded with no coherent idea in mind.
Part of why NI access is such a breath of fresh air regarding their ecosystem. (it’s also kind of misleading since it can lead you believe the softwares share a common set of tools that transpose from one to another and they absolutely definitely don’t)
1 Like
Wow, that’s a massive failure in R6! I had no idea, only using it on one machine…
Good to know about that. I do share the occasional Live projects with my two collaborators, so we’ll have to watch out for such weirdness…
Thanks!
1 Like
This is great! I like the way the Spread controls work. Very nice job.
1 Like
6.4 is out now, it adds front-patching capabilities to User Blocks and allows you to add them to Racks. Apparently you can also browse / search the blocks easier now, too. (I haven’t tried it yet.) Some new drum modules from NI as well.
I like that Blocks are still getting more support. VCV Rack is fun but I always end up coming back to Reaktor.
11 Likes
Quru
51
Inspired by the wonderful Serge Resonant EQ and filter banks in general and test equipment passive bypass filters I set on to make something that would help highlighting interesting content in noise and drones, and creating depth and movement in stereo field and our came catchily named Sequenced Triple Bandpass Stereo Audio Processor. As the name would suggest it’s an effect processor based on three independent resonant stereo bandpass filters, one of which has it’s own 5-step sequencers for both left and right channel. I really like the sound how it works, but I light tweak scalings and such in the future when I have more experience with it. Feedback would be nice if any od you end up trying it out.
Reaktor User Library: https://www.native-instruments.com/en/reaktor-community/reaktor-user-library/entry/show/13821/
Youtube demo: https://youtu.be/2pp7_8RscWQ
7 Likes
STBSAP? Trips off the tongue beautifully! 
This looks superb - I shall investigate and explore as soon as I get a chance!
3 Likes
Ithacus
53
Can anyone recommend a delay line macro (or ensemble) in Reaktor similar to SoftCut (used to great effect in so many Norns scripts)?
I’ve got an idea for a new processor (will share here when complete). It’s taking inspiration from the wonderful Norns Buoys script.
I just need a simple delay line/looper that has separate record and playback heads (for variable speed playback) as a basic building block.
Any help would be greatly appreciated 
Hi everybody,
I wanted to share here this ensemble I just uploaded in the user library here .
It is a 4 OP FM synth with two simple twists, an envelope per FM amount in the matrix (so 4 per OP including feedback) and a delay in the modulator out path of each OP.
I worked à bit on the envelopes to take advantage of the « per FM matrix connection » idea, so they are long, scalable by velocity for amplitude and by key for times. I also aded a simple lowpass filter and two LFOs and envelopes for pitch and cutoff modulation, and modwheel dependency amount for each OP’s FM amount and modulation.
In the end it is quite simple but I like the idea of the envelopes per FM point, it make for a lot of possibilities with only 4 Op.
I wish everybody a really good day !
7 Likes
This sounds great! I always think I don’t really have a use for FM sounds because they’re too glassily digital (if that makes sense) but when I try them I often really like them
FM sounds do have a bad rep, but they are so much more than those DX7 patches that might have been overused a bit at some point.
To me when I go for digital sounds it is FM first, for the flexibility and possibility of morphing (in FM8), and that uncanney valley between natural and synthetic feeling…
4 Likes
hermbot
58
I had the itch again… after diving into the Lyra 8 to fix a bug and add a feature, I decided to make a Benjolin. I added an intentionally crude and dirty reverb that can be modulated by the Rungler.
This is the first in a series that I’ve been thinking about that’s designed with the MIDI Fighter Twister in mind. The goal is to ship it with a MFT config file that has everything mapped, including MIDI feedback to the controller. Obviously any MIDI controller would work, but I’m enamored with an instrument whose main interface is just 16 knobs.
At this point I’m just doing UI stuff, below is a WIP.
It does need a name, though. I’m terrible at naming things.
14 Likes
LLK
59
Oh this might be incredible with my launchcontrol as well, although obviously the lack of endless encoders might be a bit penalizing but it should still be cool. Is MFT capable of doing bidirectionnal midi with Reaktor? (like, if you load the patch, will the MFT automatically recall the current state of the knobs on the encoders lights?)
2 Likes
I would love to have a play with this!
1 Like
hermbot
61
Yes, Reaktor can send feedback to the MFT so that preset changes and any changes made onscreen are sent back to the controller and shown on the LED rings. It’s one of the reasons I’ve always liked the endless encoder-style controllers.
One thing I’ve never been able to figure out is a MIDI message to toggle switches, it would be really neat to be able to toggle with an encoder push.
3 Likes
