It’s got a brilliant skin courtesy of Jonathan Style, a new sound set based on samples from a very popular hardware synth (can you name it?), and at the moment only four new snaps. I could delay release and make more presets, but I want to get this out as soon as possible considering what a wait it’s been since the last update. It sounds like this:
This is a free update for people who’ve already purchased – the same password will unlock this skinned version. Be aware that I’ve migrated to the fantastic and problem free Reaktor 5.5 beta, and the new skinned version will no longer open in earlier versions. Get the beta here.
The 5.5 beta is rock solid stable and if anything uses less CPU than previous versions. I have had no hiccups or crashes using it. Nevertheless, back up your custom ens before saving them in the new version, just in case you want to revert to 5.15. Like this version of ParamDrum, the Reaktor 5.5 update will be free for current license holders.
Haven’t purchased yet? $15.00 gets you the password to all versions.
I’ve been working with someone on creating custom MIDI controllers for use in Ableton and thought I’d share ideas. The most flexible way to send MIDI in Reaktor 5 is to use the Channel Message module.
The input ports, from bottom to top, work like so:
Val: self explanatory. This is where you send the value of the message you want to transmit. By default the range is zero to one, but you can change this in the module properties.
Nr: In this case, the number of the MIDI CC to transmit.
Ch: The MIDI channel to transmit on. This overrides the settings of the instrument containing the module, but you can go into the module properties and tell it “always use instrument’s send channel”.
St: Status – this determines what kind of message will be sent. We’re sending type 3 which is a MIDI controller message. You can also send note on/off information, pitch bend, and so forth.
The tricky bit: this module only sends data when it receives events at the St input. When it receives an event there, it transmits whatever values are at its other inputs. That’s why I’m using the order and value modules, to ensure that every control change is followed by an event with the value “3” at St. Hover over St and the other ports for hints on what values they accept and what the values mean. I’ve deliberately kept the structure as simple as possible for clarity… some enhancements you might make are to add panel controls to set the MIDI channel and CC#, and to rig up a more interesting event source than a knob. How about the LFO module? Try it but keep in mind the default range of the LFO is -1 to +1, not 0 to 1. You can either compensate with a few math modules or (not recommended) change the default range in the Channel Message module’s properties. Here’s the test ensemble – build something fun with it!