that’s the one! if you just delete the previous version, you can use the ;install method to pull in the pre-release version :slight_smile:

3 Likes

Fixing my TwoHost as we speak, in preparation for eventual fun to be had!

TwoHost fixed! Time to make that dang Peak SIIIIIING, y’all

1 Like

the meta sequencer is indeed so dope! love it. don’t want to be greedy, but it makes me think if it would be possible to make individual presets midi mappable? for instance mapping the preset slots to note on midi messages to allow live switching between them. i assume that’s how it works looking at the new grid support, but unfortunately don’t have a grid yet : )

3 Likes

Could you send me a DM and tell me some more about your workflow and a typical workflow using prgm changes? I haven’t used that myself but would be interested in looking into it for sure. Could I replicate with Ableton? Don’t have a midi controller other than Keystep 37.

2 Likes

@vicimity this is awesome! Builds so nicely on @dan_derks original script. Finding some very cool patterns, greatly enjoying w/syn output.

2 Likes

i just updated the repo with a test of midi program change. the default midi device in is 2 but you can change this in params. i did a quick test with ableton and it works. but i am not used to this workflow so any input and/or help on this is appreciated. basically it will listen to program change and select the preset matching the program change value.

3 Likes

wow, that was quick! i’ll give it a spin tonight and let you know how it works – thanks!

update @vicimity
been trying out the program change update – it’s neat and works great! my workflow would involve creating any numbers or presets (for instance, p1-p16) with different variations/riffs and then simply changing between them on the fly. kind of like triggering different clips in ableton live’s session view, to then jam on top of then playing live on top of.

however, i feel that midi program change may not the most optimal way of doing it, since many controllers, keyboard or midi sequencers are not able to send program change messages. (i had to dig out an old yamaha cbx-k1 to try it, hehe). the way i imagined it, p1-p16 would appear in the parameter map menu, where one could midi learn and assign a note to a preset. so i could play c1 and it would instantly jump to p1, c#1 and jump to p2 etc. that way i could also use a launchpad or a keystep for instance, or more easily sync up preset changes with another sequencer just by sending a out note on the right midi channel to norns. slow arpeggios to meta sequence the presets might also be cool.

2 Likes

I’ve been running this thing in the background most of the day, occasionally getting up from work and meddling with parameters, and I must say I’ve ended up in some pretty strange sonic places. Currently at some sort of liquid mercury seashore on a moon.

Thanks for picking up this script and spreading the strangeness!

3 Likes

Ok, just so I get this right. I could hook up my Keystep (or any other normal midi keyboard) and play notes to trigger the various snapshots? (This actually makes way for using the internal sequencers instead of the basic cycling stuff in the script, I like that!)

If my understanding is correct it should be fairly straight forward to implement before release which is due late this / early next week.

EDIT…

Getting closer to 3.0

Updated the repo with:

  • wsyn velocity control in params (go low to prevent distortion, 5 is preset is it too high?)
  • midi note in → snapshots (could not find a way to map keys, you choose root note (C3 is standard) and 16 notes up represent the 16 snapshots. Is this ok? Suggestions welcome!
  • fix for grid interaction of destructive cycling modes (bug)

There is also a “manual” in the GitHub readme if your interested in the additions and how they work.

Let me know if you run in to any bugs or general wierd behaviour.

3 Likes

yes, exactly!

brilliant! definitely works for me. excited to try it out. thanks for all your work!

1 Like

beautiful script, going to try it now