Yeah, I guess in general, having some reliable method of syncing the clock is really all I would truly want, and the Crow method seemed like one of the more easily conceptualized due to my lack of understanding behind the true structural nature of both crow and vcv architecture.

The Midi note to clock method would be awesome, but that’s still a bit over my head. Someone linked to the lose structure that someone has used to house Lua in VCV which seems like it could be fruitful.

I guess I’m asking this all selfishly for 2 reasons; these types of questions are the best way for me to learn a subject and that I really just want to modulate the clock of certain norns scripts from VCV haha.

Sorry these instructions aren’t more detailed, but at a high level, it would go like this:

  • Get an iConnectMIDI2 or 4 or some other host-host USB MIDI adapter, and connect your computer and norns to it
  • On the norns, assign the midi device to slot 1 in devices > midi
  • In VCV Rack, add a CV-MIDI module from the Core collection and patch your clock into the Gate input
  • In the norns script you want to use, add a m = midi.connect() to the top of the script, and then take the code that’s inside the script’s clock callback and paste it in a new m:event(id, data) handler.
  • Put in a check for note on messages so you don’t double-trigger on note offs.
3 Likes

If you don’t want to have to bother with another piece of hardware, you could also try the same strategy with OSC messages over the network. Use trowaSoft’s cvOSCcv module, and put your norns clock action into a osc.event(path, args, from) handler. (I have not personally tried this.)

1 Like

So, I’ve had midi in to VCV Rack using the 2host by @okyeron

It’s worked well for getting midi triggers in through the Midi to CV I guess I could just do this similar method of the m = midi.connect trick. I’ll take a look at some of the scripts I’d like to have this work for (for now I’ll scope out awake) and see about setting up the callback script. You mind if I PM you about my eventual novice question or two?

The OSC event script seems awesome, cause it could cut out a ton of problems in relation to a second norns (via the FATES board). This all allows for a huge amount of flexibility though, which is always my main reason for reaching for Rack

1 Like

Hey everybody, I’ve just released my first VCV module called Seasons.
Seasons combines a sequencer and a shift register to create 4 simultaneous outputs that can be used to modulate multiple parameters at once.

It’s quite a fun way to add clocked movement to your patches.

It’s open source and it’s available at https://github.com/SpektroAudio/Seasons/

Update: It’s now available on the VCV Library!

25 Likes

I’ve been thinking about this for a while, and below you can see the rack that I came up with. It only requires three free module sets: Befaco, Vult, and Nysthi. It’s a pretty good start for a “VCV Shared System.”

Priority went to ease of readability and use. I left out modules that may have done a more in depth job but I felt were too complex. This rack allows the user to jump right in and start making sounds, with the heart of experimentation likely coming from the Simpliciter. This allows for real time sampling and loading of wav files

Otherwise, the inspirations should be clear.

Imgur

Playing around with this and a MIDI Fighter Twister has been very entertaining.

11 Likes

That’s a fantastic setup! I will definitely be using it as a jumping-off point. (Those nsynthi modules are way prettier and more usable than I remember them being not too long ago, what a relief).

On first glance, I’d personally replace the Befaco spring reverb with Valley Audio’s Plateau, which takes its main inspiration from Make Noise’s Erbe-Verb. Seems more fitting with the “Shared System” approach, I suppose. Likewise, I’d throw in dBiz’s SPan, which is modelled after Make Noise X-Pan. Maybe for some deeper oscillation capabilities, either dBiz’s Verbo (Verbos Harmonic Oscillator) or Trosc (Instruo Troika). And for a straightforward lowpass filter, something from Lindenberg Research - either Valerie (12db MS-20) or Alma (24db Moog).

2 Likes

Curious, what would be your reasoning for using the twister fighter as a CC device like this instead of midi training out to control module knobs?

Sadly, it’s only those two modules which have been re-designed (by a mysterious ‘Pyer Cllrd’). The rest are still… eccentric.

1 Like

'Cause I didn’t realize they had implemented easy mapping like that. :sweat_smile:

Also I added the dual attenuverter to round out the top row. It adds some needed utility. Also evens up the hp!

Imgur

7 Likes

The Midi Learn function is SO HELPFUL! If I can make one suggestion, use the knobs on channel 1 and the knobs presses (to simulate pressing a button, on say, a plaits or another Mutable Instruments module) on channel 2. This will mean you have two midi learn modules for the Twister Fighter, but it gives greater control.

1 Like

Throw in an interesting clock and I’m sold.

There’s a couple of things you can do for clocks:

  • The sequencer can be used as clock divider by taking the individual step gates out from the bottom.
  • Modulating the sequencer clock will get a variable clock output from the gate output of the sequencer.
  • Noise from the noise generator can be sent into the Rampage input, then the Rampage’s “Falling” (end of cycle) output is a fully random clock. The timing can be adjusted with rise and fall.
  • Any modulation into the Rampage will change the Rising or Falling gate outputs.
2 Likes

My saved template (saveable in the File menu, resulting in the patch being recalled when you make a new file) includes the audio module, a mixer with sends, my send effects, and a clock (currently Orca’s Heart, which is also a fantastic quantized sequencer).

I build sound generation, modulation, shaping, and filtering from scratch every time because there’s no space or dollar cost to doing so. Does this patch call for a dozen sample and holds? A dozen sample and holds coming right up…

I get the idea of a shared system for sharing and learning. Perfect concept for a classroom. But for day to day patching I really don’t mind just using the module browser. It seems daunting at first, especially if you’ve installed all the free modules, as I have, but you learn your way around it over time.

re: MIDI learning vs using MIDI-CCs: i prefer the latter for these reasons: easier to see what controls what and quickly switch as needed and you can scale/offset with other modules.

1 Like

As a newcomer to the field of modulars and VCV, I love that it gives the flexibility for both the opportunity of building a more ‘traditional’ rack with a template and having all the free Modules in the back pocket. The idea that there’s a way to ramp up familiarity and get more comfortable is really nice and eases many folks in.

Sharing practices also help, in which folks explain why a certain module is used instead of another, or even adding just one new module to a chain to show how it can truly effect things with a really solid contextual base of what came before.

All in all, this program has given me something I’ve desired since I fell out of electronic music making 10 years ago; a pathway away from Ableton. And I’m thrilled to learn and be inspired by any choices folks care to share!

4 Likes

This makes a lot of sense. With the MIDI twister since there are four bank pages it can get a bit… rough to begin with. Maybe having one page, or in my case a separate device like my UC-33 fader/knob bank you be a MIDI CC device seems logical to me. I’m also sitting with a shopping crate full of the BOM of a 16n Fader Bank and the PCB/faceplate as we speak…

I really like the idea of a ‘shared system’,
useful for education purposes, and sharing techniques.
also nice for those starting out with vcvrack where the sheer choice in the browser can be daunting.
Easier to start from a common place and explore from there.

Perhaps a couple of starters racks with different focuses, eg inspirations from

  • make noise shared
  • doepfer basic system
  • Endorphines shuttle / techno racks
4 Likes

Omri has cloned (sort of) a 0-coast and a DFAM in this playlist and it’s an interesting example of how to think through building up higher order behaviors from lower level modules.

Might be good inspiration for shared system ideas.

8 Likes

One thing I am finding is that if you use midi learning, it locks out mouse control to that parameter. Whereas if you send CC messages, you still retain control over both.

3 Likes