Yeeee that’s fresh!

So: getting back to the topic of integrating with monome. For me I’m trying to approach things in terms of what the strengths of Reaktor/Monome are. Things like the shift register and other cv jugglers like comparators can be scripted in teletype, so those might not be the best use of my 8 ins and outs.

What things does reaktor do well that an isms system lacks? CV controlled sample playback is the first thing I can think of off the top of my head. As soon as I wrap my head around cold mac, i have a feeling it could integrate with a granular sampler in pretty rad ways. Same goes for meadowphysics and just friends. Reaktor can also provide a lot of oscillator options that the isms lacks, as well as CV controlled effects. All filed under “tones that isms doesn’t natively make”.

But Reaktor also excels at snapshots. I was bummed to see that earthsea doesn’t have built in scale functionality (as in modes), but that could be easily handled by Blocks. Similarly White Whale has scales, but they’re a few clicks presses from the other pattern manipulation functions, making it tricky to jazz it up on the fly.

What Reaktor isn’t so hot at is multitouch integration. I would much rather sequence with white whale or earthsea than chase the on-screen sequencers around. That’s just me.

I’mama keep brainstorming. Tell me what you come up with.

1 Like

Yeah, there are many excellent, free sampler Blocks. In the video I demonstrate the “Sample Scanner” Block, which treats any sample like a wavetable. Using a slow, rising sawtooth LFO plays your sample back forwards while a falling ramp wave will play it backwards. All other shapes, well… There’s also the Sample Looper, which is more traditional. Both of them have 2 CV inputs that can target any parameter. There are other incredible samplers by Colugo, Matthew Friedrichs, Joey Valizan, etc. Sampling, in my personal opinion, is a field that hasn’t quite been nailed yet in Euro.

Other than that, the one surprising module that’s missing in isms is delay! We have a new plug-in coming out on Monday, but after we get some sales in I’m planning on releasing a “Smooth Delay” Block that doesn’t click when delay times are modulated. I’d love to see a delay by @Galapagoose, as I think 3 Sisters is the best, most versatile filter design in Euro. There are other effects missing in isms, but delay is the only one that I would describe as “essential”. Maybe reverb if you don’t have the actual isms case, but it sounds like you do.

Multitouch integration… if you have Lemur or TouchOSC, you can create your own multitouch controller for Reaktor. It has OSC + MIDI learn when you right click on any knob.

3 Likes

Unsure of what other systems you have but for me once I get an ES-8 Reaktor will become my percussion section, and then just an endless bank of utility and fx processing modules. Basically Reaktor will be everything that I don’t want to waste case space on/have direct tactile control over. Also any ensembles/Blocks that I want to make in the future can become integrated with my euro system.

looking specifically at the isms case and what Reaktor could add to it though I would agree with @trickyflemming, isms doesn’t have much for processing, also just more utility modules, like mults, attenuators, inverters, VCAs ect, can always use more of those.

this is super helpful and interesting, thank you!

ps: Love your reaktor work :slight_smile:

1 Like

I use Reaktor for the Chaotic blocks Mike Hetrick included in his EuroReakt Blocks suite and i drop them in Ableton and use Expert Sleepers to integrate them. Arc/Grids control into ableton --> Reaktor seems to be enough for me. and i Use and ES-7 to get CV into the system. I also have started integrating Numerology Pro4 as well because it has some very nice 128 step resolution that i can see playing nice with a grids

2 Likes

Michael: have you been able to control Reaktor with pitch cv sent from your modular? I assumed I could, but now that I think about it, everything I see online is how to control hardware with Reaktor, not vice versa.

I can get Reaktor to make sense of gate/trigger signals from my modular. And going in the other direction, I can totally control my modular’s oscillator pitch using the blocks 1.2 cv pitch out/calibration block (the use case most people initially struggle with), but I can’t get Reaktor to understand note CV sent from the modular into Reaktor.

I’ve tried sending cv signals straight into an in port on Reaktor routed to an oscillator block, I’ve tried it routed through a cv offset block (to try and see if it was an offset issue), and also tried to send a modular cv signal to the pitch input on Reaktor’s native cv pitch block.

The outcome i’ve gotten is that the pitch cv i send from, say, earthsea’s position output comes through as a a high volt attack followed by what sounds like a sloped release down to low voltage. It makes the pitch pop up high, then the pitch rapidly bends down to whatever it was before I sent the new cv signal, in other words. I expect that (and see that) with gate signals, but not cv. What am I doing wrong?

I’m using a motu 828 mk3 (DC coupled) with those expert sleepers floating ring cables.

CV into the motu is not supported (it gets filtered out IIRC)

you would need some silent way magic and hardware (es-2 or disting mk3 with the recently released firmware)

1 Like

Ohhhhh okay yeah that’s what I worried.

Thanks for clarifying.

I wish Silent Way fit in the Isms case. Maybe someday I’ll make dedicated case for control signal stuff like that.

can anybody provide me with an working example how to setup grid with Reaktor? What are the in and out ports i need to set in Reaktor prefs, and a simple receive and set led example would be cool.

https://llllllll.co/t/reaktor-and-monome/3492?u=jasonw22

I saw that, no working example in that thread.

That’s because it doesn’t work.

that’s a bummer, so i have to go back to old monome serial app to make it work i guess. It was working with that.

That’s interesting because Reaktor’s OSC implementation doesn’t support the full OSC spec. I’d be curious to know how you made it work.

monomeserial and serialosc use the same protocol, so there’s no reason why Reaktor would see different OSC messages from one or the other.

yup, i worked just fine. Maybe just the prefix stuff changed, i will dig into it. What is the OSC receiving port to set in Reaktor? The docs just mention the listening port.

If you are using monomeserial, the ports are whatever you want them to be.

yes, but with serialosc? I thought I might give it a try, maybe it can work if it is the same protocol.

serialosc allocates ports automatically. This allows for things multiple grids or grid+arc to be setup with automatic configuration (assuming you’re working with things that are serialosc-aware).

Some more info about serialosc in this thread:

I thought so, is there a terminal command to find out the port assigned? Even better would be to have the option to set a fixed port.

You communicate with serialosc with osc. There is no option to set a fixed port.