What are the major differences in the way that grainstorm functions in comparison to say Mangl? Mangl

With midi cc mapped to an external controller you have access to play speed/direction, grain size, position randomization, etc. You may have have seen this already, but thought I’d point you there if not.

@coreyr; Tak! I’ll have a look.

any progress on this? I’m trying to build the same, wondering maybe if I can contribute to yours rather than try to do the same separately

check out the softcut studies— it shows how simple it is to do this! every looper is idiosyncratic, make yours weird!

1 Like

I am embarking wish me favorable winds

3 Likes

wrms is what i was talking about - at load it’s basically a delay going into a loop, but can shape shift.

I’m also working on wrms mods, which is basically an API for personalizing wrms controls and pages w/o writing any new UI code if that’s yr kind of jam. but yes building a looper from scratch is approachable and fun : )

4 Likes

I don’t know the technical differences but they sound different…

1 Like

I guess it’s really the UX which appeals so much. grainstorm is just such a pleasure to interact with… Obviously norns’ display is somewhat limited, but I would think that a clever designer could approximate what grainstorm has.
Also, it seems like the control assignments are different. AFAICT, mangl doesn’t have the controls which grainstorm has - sliding the window over the sample, smoothly changing the window size; they’re similar, but it seems like they have different philosophies about which things to control.
Grainstorm focuses on quickly finding sweet spots in entire samples, and using the usual grain controls + filter to shape the sound.

3 Likes

I’d also like to see a Norns grainstorm

1 Like

You don’t have to use the speed param in mangl. :grin:

Set speed to zero. If you hold alt, arc ring 1 will let you quickly scrub through a file in a search for sweet spots. mangl will continue making grains acording to the other params when you stop searching. Each voice also has a filter for further shaping.

5 Likes

Is there a limit on the samples size?

After watching this talk on this development of a headerless Pi build of Yoshimi, I had the idea of a terminal based polysynth. The concept is something like Teletype but with a focus on waveforms rather than cv/modulation. I think you can do similar things with the teletype expander telexo.

I think it would be cool to be able to issue terminal-esque commands, and scripts rather than twiddling knobs.

3 Likes

I’ve been thinking lately about an OP-Z file management script. Here are the things I think would be useful and doable, organized in order of how much work I’d estimate they’d take:

  1. harvest the bounce wav files (and rename them on the way to their destination, as they are all named bounce.wav)
  2. manage sample sets and synth presets
  3. easy backups of projects
  4. create new ‘OP-1’ format sample sets

The only thing that’s kept me from diving in is my general lack of comfort with the proper way to wrangle the mount/unmount of the OP-Z in disk mode without requiring users to SSH in.

Happy to help test and do whatever work I can if someone with more experience wants to give me some guidance!

4 Likes

For my first proper norns script I’m thinking of implementing a MIDI arpeggiator based on the Waldorf note-list arpeggiator concept.

You can set each Step to either play the note it would do so anyway, to pause, to play the previous note again, play the first or the last note, play those together, play a chord consisting of all held notes or a randomly selected note.

Then you can adjust the Accent of each step (including silence), activate or deactivate Glide for each step, set the timing to play a step ahead or behind its nominal time, and finely adjust the note length between short staccato and full legato.

This is somewhat similar to spacetime and Dunes, with the difference that the note list is built from the MIDI input.

Additional arpeggiator details from the Q manual

Arp Step [ * / - / < / > / <> / ♫ / ?] basically determines which note of the note list is played at a particular step.

  • If * is selected (asterisk symbol), the Arpeggiator plays the step unaltered. The note list is advanced beforehand, except when you press a new chord.
  • If off is selected (empty space), the Arpeggiator plays nothing at this step position. When Length or Steplen is set to legato, the previous step that isn’t set to Off is still held to create the legato effect. The note list is not advanced.
  • If - is selected, the Arpeggiator plays the same note as it had to play in the previous step that was set to * or ?. With this setting, you can repeat a particular note of the note list several times. The note list is not advanced.
  • If < is selected, the Arpeggiator plays the very first note of the note list. This might be interesting if you want to only play the “root note” of a chord in a bass sound. The note list is not advanced.
  • If > is selected, the Arpeggiator plays the very last note of the note list. The note list is not advanced.
  • If <> is selected, the Arpeggiator plays a chord with two notes, the first and the last one of the note list. The note list is not advanced.
  • If ♫ is selected (notes symbol), the Arpeggiator plays a chord with all notes from the note list. The note list is not advanced.
  • If ? is selected, the Arpeggiator plays a random note from the note list. The note list is not advanced.
9 Likes

any news on this? anyone willing to collaborate on setting this up?
what is needed:

  • add libmanta to norns
  • add udev (?) rule to start mantaOSC if manta plugged in
  • provide basic manta osc callbacks in supercollider layer (since the manta generates a lot of OSC traffic, IMHO it’s easiest there)

Only just discovered this thread so thought I’d throw this into the mix and see how possible it would be.

This idea is based on Keith Fullerton Whitman’s “Generator” eurorack patch. The core of the patch is as follows:

An LFO (Usually ramp shaped) into the sample in of a clocked S&H, with a quantized output being fed into an ASR into 3 vcos.

Tweaking the Ramp LFO speed and the Clock speed causes shifting yet eventually looping melodies to emerge. The ASR element adds a density to the melodies, which is further expanded by the ability to tune the VCOs to 5ths, 7ths etc.

In my head, there could be pages for the following:

Page 1: LFO speed , shape, depth, clock speed
Page 2: LFO Shape, LFO Depth, VCO shapes, root notes, volume, fine tune
Page 3: quantizer scale etc

The main page for playing the patch would be Pg1 as it’s the correlation between the LFO and Clock speeds that cause the patch come alive, so being able to control those parameters from encoders 2 & 3 would be ideal.

Details on the basics of the patch can be found written by the man himself here:

https://www.muffwiggler.com/forum/viewtopic.php?f=52&t=133029&p=1943758#top

Anyway, I’m completely new to all this so this may be an absolute impossibility to create but I think it would be a fun and useful patch for the community.

5 Likes

Actually, when I mentioned making this patch for Norns in the Shift Registers thread, @Oootini kindly mentioned there’s a Crow script in the Bowery pack that may be repurposed for it.

R might be suited for this. It’s basically a scriptable modular synth…
Here are demo scripts: this one shows how to script a complex patch.

2 Likes

Thanks for that! Hadn’t looked into R before. On an initial read, it seems to click with me a little better, bearing in mind I have no coding experience whatsoever.

The only issues I can forsee based on the modules available is the generation of a quantized output from the S&H and then shift registering the same output across multiple vcos.

Maybe some sort of delay sync’d across a S&H module for each vca might do the trick? Hmm

I know this was written a while back, so maybe someone is already on this, but I’m banging my head against Supercollider currently, with a view to eventually attempting a port of my LPC synthesis Axoloti objects.

1 Like