#107

FWIW I keep all my manuals on Onedrive so I can pull them up offline on my iPad. This one works fine there.

#108

On my MacBook (OSx10.13.6) some images are missing in Preview. When I use Acrobat reader I can see the images.
On my iPhone (os 12.0.1) all images shows up using Dropbox.
Weird.

/k

#109

Anyone have any issues with X or Y not saving note info when powering down? (or conversely: reading knob values on power up and overriding saved note values?)

I’ve run a few tests and it’s spotty, so I’m unable to 100% reproduce it (unfortunately).

I create a sequence on both the X and Y pages. I save everything (take ~9 seconds for Rene to save, all knobs are the color red while it saves.) The sequence starts again and it sounds good. I then power down. I then change a few of the knob positions. I power up. On power up the notes I saved are gone and are now replaced by the new know position notes.

This doesn’t happen 100% of the time, only sometimes. I’ll keep trying to get exact steps to reproduce but was wondering if anyone else has experienced this.

1 Like
#110

Anyone have any tips for generating complex rhythms (within reason) with rene v II?

#111

Make Noise’s YouTube channel is always a good reference point for learning how to get the most out of RenĂ©. This video, for instance, covers the Z Axis and state-switching will definitely be important for patching complex sequences together:

Also, using the various FUN page options with X and Y’s CV and gate mod inputs will assist, as demonstrated in their RenĂ© S+H Flourishes video, and the techniques in the Self-Patching RenĂ© video have changed the way I patch. There are also short videos on their Instagram page that are fun to try.

One of my favorite things to do as of late is clocking RenĂ© with a sawtooth LFO from DPO VCO A and running a channel of RenĂ© quantized CV outputs into its 1v/oct input while changing the octave range of René’s CV out on the QUANT page. Sometimes I’ll even throw Wogglebug’s Stepped Random Voltage output into X’s CV mod and have the ADD or S+H function on to inject more unexpected changes into the patch.

4 Likes
#112

I have a RenĂ© mk2 incoming (so excited!) but I have a question about using it with other gear. Namely my Digitone. How are you finding the RenĂ© plays with other sequencers? I’m not opposed to having the modular do it’s own thing, while letting other gear take the lead, but I’m just curious if anyone else had any input about using an obtuse sequencer alongside a traditional one.

1 Like
#113

Any one patch I am doing has multiple sequencers (Octatrack, MachineDrum, OC, Klee, Rene2, Pressure Points/ Brains) I mostly use the external sequencers to drive specific melodic content, and key/ program changes. The rene and Klee are great because they add a shit ton of semi random stuff that has a strong relationship to the triggers and CV driving it.

They key for all this is making sure that my clock is being driven from a singular source. Which is usually the octatrack (which is also the center of my midi set up) into an FH-2. I then take the clock from that and divide it using a 4ms clock divider with the expander, which gives me a lot of fine tune control over my trigger timing. I also have 4 tracks on the machine drum routed to individual outs that also spit out triggers into the modular. This allows me to quickly step sequence multiple trigger tracks using a very intuitive interface.

#114

I wish there was a simple midi-to-clock cable that existed, as it’s a bit of a drag needing an extra power supply for my cv.ocd. Also I would love for a reverse cv.ocd to sequence the Digitone with RenĂ© :heart_eyes:

#115

It’s not a cable, but Squarp’s Hermod does an excellent job mingling midi in and out.

#116

are you familiar with addac’s 221 and 222
 cv to midi
 I’m considering them myself, they seem very useful and well made!

#117

I like using a Rene sequence added on top of an external sequence. Which most quantizers will do while keeping in key

1 Like
#118

Or adding another sequence (or other cv) on top of the Rene. Very easy to do with fun.cv.add set. Or to control Rene’s snake pattern, direction, Z-axis (state) like the video shows, etc.

Being able to sequence states is especially powerful since you can change pretty much any aspect of its behavior that way.

#121

“Makenoisesplaining” lol

3 Likes
#122

That is some excellent insight. I’m slowly falling in love with Make Noise as I realize that myself. I suppose I’m building a sort of hybrid MN/MI case, with the Make Noise control and performance philosophy complimenting Mutable’s sound design and workflow. Maybe I need to approach the modular as the soloist and the Digitone as the rest of the band. It could make for some really interesting dynamics, trying to ‘play’ the sequencer over a relatively unsynced backing track.

#123

@fourhexagons’ use of the Planar as a playable precision adder for René’s X and Y CV mod inputs is brilliant:

7 Likes
#124

Man, This kind of work is still so far beyond anything I am capable of at this point. Very beautiful, but also kind kicking’ my ass to keep learning


2 Likes
#125

Ohh I couldn’t really disagree more. I think MakeNoise design stuff that fits within their aesthetic ecosystem, but they all work incredibly well as stand alone tools. I can’t think of a single module they have created that is parasitic in the way you are describing, that is, a module that needs other makenoise modules to truly shine. They definitely push the their ‘no coast’ style, and make module that fit that paradigm, but I would hate for people to walk away from your post thinking that the two planets don’t talk to each other.

I think, as posted earlier by @ThurberMingus, the fact that CV can quickly overwhelm machines that use midi to trigger stuff (making CV->midi less common) can be a bit of a draw back. The MachineDrum is nice in this case because is has a couple of input machines that deal with data at audio rates (Gate, Filter Follower Envelope), however the internal sound architecture, being designed primarily for midi input, will still choke on trying to trigger samples at say audio rate.

However this is really just a midi limitation, and is the case with anything moving between the 2 ecosystems (CV, Midi), and is due to the fact that midi is older than most people on this board, and was designed to copy CV using extremely limited data sets.

#127

Not to be pedantic, but you wrote considerably more than that. And the flavor came across in a way that really felt limiting to me, and my approach to modular/ midi integration over the last 5 years. I just want to add a different voice to the discussion.

#128

Quick question: I was always under the impression that the OT doesn’t send Midi over USB. Or is it only sending Midi clock?

#130

Its sending neither over USB, I forgot I had the uno coming out of it and into the FH2 :confused: