It’s based around a patcher which plays a sound randomly from a bank of 10 or any one of those specifically. You can loop them or play them as one shots. You can trigger them randomly, with a repeater device, basic step sequencer, keystrokes or midi from renoise. It’s then got some speed adjustments and deformation, doppler, loop end point controls, finally its all run through renoise effects controlled by midi. Then there is also a granular synth configured to make drones, and some basic soundfile players. Oh and its got a basic sine wave generator for making some sub bass. Heres a screenshot:
it’s mainly just getting the midi and rewire routings into a usable state. the key thing with this patch was using the max/msp bpatcher object which allows you to make the patches as modules which you then hook up as you want (and recall in other patches). it means i can reuse stuff like the midi-in and midi-out objects and the control surfaces quite easily if i design more instruments and whatnot, or just want a basic midi routing interface for renoise which labels what all the controls do on-screen. you’ll definitely be able to take a similar approach in bidule i would think.
one of the useful things about having it designed in this way is that its pretty easy to reassign an individual midi slider to multiple midi parameters in renoise, which you couldn’t (yet) do otherwise. you’ll want to keep a midi-out module seperate from your instrument for that, otherwise it’ll all be totally integrated and you’ll be starting from scratch at a later date. you can also do things like mute tracks in renoise via midi (where it just 0’s the amplitude but remembers what it was last was when you unmute it), its not in this patch but i made it and it works.
if we get pattern moving commands assignable to midi it’ll be possible to get an even nicer live interface going. as it stands i think you might be able to do this with the host transport rewire controls, but it’d probably be pretty tricky. i do also have a java based direct input keystrokes-out object someone made for max so you would be able to do anything you can with keyboard shortcuts via the patch (and thus via midi). this will work, unlike other macro mappings because its direct input, it works with games and stuff (i made a quake patch which you can control with max, quake would not respond to stuff like autohotkey or bome’s midi translator but it works with this). i don’t think you can control the new live-style pattern navigation with shortcuts yet, but when you can it’ll be sweet.
another idea which i just had is that you could read the renoise logfile in max and use it to trigger things that happen in the patch. for example, the logfile says:
so you get max to read the logfile and recognise what song you loaded. then it automatically loads settings in your max/msp patch for that song. could be pretty handy for a live scenario where you want to quickly load new settings. again i got the logfile reading thing to work in quake; its not too difficult. just an idea that one…
i think i can get close to a basic version of this,if i use the audio matrix(because the step sequencer isent that good,need a overhaul IMHO Very Happy )
and build some loopers that uses audio buffers,and i need to look into building some sort of keystroke input device,where i can trigger different samples either using the keys on my laptops keyboard or a midi keyboard.
yeah i got some tips on the plogue bidule forum,so now i have the keystroke thing nearly done,have some of the other stuff done to,so it is atleast possible to make a simple version of your max/msp patch in bidule
This one has a significantly improved and clearer layout, and full instructions of how it all works. You can also use it more easily ‘stand-alone’ without Renoise as it outputs to 2 channels instead of 10 by default. If you click on the ‘patch info’ and scroll to the bottom i’ve got a description of how you should set it up to work with Renoise and MIDI Yoke step by step.
You also have buttons now that you can click which will then tell you what all the MIDI routings and actual cc# numbers are.
I think possibly the reason you got a MIDI feedback loop is because you need to assign letter abbreviations in the MIDI settings of Max, otherwise i think it’ll be sending and receiving from the same devices.
The only thing that I had to figure out was to make the (Renoise) instrument “00” transmit it’s midi to MAX. Similarly, the patch mentions the abbreviated input “f”, but it’s not explained anywhere in the info?
Anyway, this is a lot of fun to play with. I’m especially impressed with the “atomizer” and “drone machine”, really good sounding! Shame that you (AFAIK) can’t save the setup with the free MAX 5 runtime - but then, it kinda lures you to doing something different each time
Yeah thanks, will try and make that abit clearer in the info.
No you can’t. I did try adding presets for the individual devices but they were doing weird things they weren’t supposed to, like adjusting controls they weren’t meant to on other devices… I might be able to add one general preset box for the whole thing.
What would be really useful is to be able to save the sound buffer settings and recall them, because it does have a habit of throwing up interesting results depending what sounds you load in, it’d be nice if you could store them. I’ll try and add that if I get time…
in max you have a few different objects which playback samples. on the atomizer, i used the groove~ object which accesses buffer~ objects which you load the sounds into. groove~ allows looping and adjustments to the playback speed. when its in looping mode some routes and gates change which buffer~ the groove~ object accesses.
when its in one shot mode it actually switches to a different system where there are individual groove~ objects for the 10 buffers (hence you can have polyphony in one-shot mode).
the patch is the same, but i’ve made some changes to the instructions so its hopefully a little clearer how you set it up ReWired to Renoise. There’s also a pdf of the instructions and some added tables with the midi routings.