the other thing i should say about setting high rates is that i just wouldn’t do it if you don’t have to, particularly while writing, because it’s just expensive. if rate is, say, 63.9, then each sample of processing will require 63 or 64 interpolated writes to the buffer, and these are the costliest operation.

since you only have 2 voices you should be ok pushing the envelope of performance, but in general i’d limit rate modulation to 3 or 4 octaves to avoid dropouts. (not crashes.)

the crashes are almost certainly from exceeding the hard limit on rate, which will smash memory since we have traded some safeguards for speed in the inner read/write loops.

during initial dev I was thinking about either of these being great to have ! rate is being modulated in my case, otherwise util.time() is super easy. no rush at all, bc I think if I clean up my redraws the current method will be plenty fine for this app. (redraw in poll was total laziness on my end to poop this app out quickly)

& yes definitely next update I’ll head in and limit rate so nobody is crashing things. I haven’t even noticed the performance drops at high rates outside of the full crash though which is honestly a testament to how robust everything is

for the record, when i work on softcut my target is usually to have good CPU headroom (>50%) with all voices reading and writing simultaneously at +/- 8x speed. chose to make the rate limit bigger because why not (just don’t use that for all voices at once) but it does need a caveat.

i’ll push a change on the backend, maybe such that setting loop point to -1 indicates “set to current position,” and also limit the rate there of course. (but clamping the rate on backend will happen silently from perspective of script.)

2 Likes

thank you for the worms , they are really sweet :slight_smile:

3 Likes

thank you !! wld love hear what everyone is making :eyes:

many more wrms coming soon ~~

2 Likes

here is some no input wrms! Wanted to try this script but was at the gym with no inputs avail.

enjoy (careful it’s loud!)

9 Likes

This is one of the few times someone would be excited to hear that there’s wrms at a gym! :laughing:

2 Likes

this is bonkers @vcvcvc_val ! !

just pushed a quick update. probably didn’t break anything

1.0.1

  • auto-generated params from controls
  • session persistence
  • screen lag fixes

fixed the super annoying loss of settings btw sessions and added a bit of midi control options via params - rec should work with footswitches ! also cleaned up my redraws to address the weird screen lag stuff - if anyone gets that again be sure to let me know + maybe share yr cpu % ?

been putting lots of energy into revamping the guts for * wrms mods * via a new softcut lib, stay tuned !

10 Likes

version 1.1 is here !!

  • fixes
    • visual lag (?)
    • softcut crashes
  • reverse rate (k2+k3)
  • persistence
  • params
    • input mixer
    • param per control for midi mapping
    • file read
    • voice panning
  • wrms mods / internal architecture restructure *

*

with this version I invite you to check out -> * the guts *

(a script is an interface, after all)

i’ve put a lot of thought into the internal structure of wrms and it is now ripe for redefinition via modification or the integration into other norns projects as a softcut controller

to help illustrate this I’m going to be posting some wrms mods of my own but my hope is that others may choose to do the same ! a looper is very personal and I’m hoping you and wrms might be able to change && grow together


filt ~~

wrms_filt.lua (4.0 KB)

1st wrms mod is a very simple addition that I decided to leave out of the main release. It adds a filter to the feedback path of wrm 1 - very great for dark analog-delay tails in lowpass mode but also for other things when wrm 1 is looping

just pop the file into dust/code and run the file ! it’ll need main wrms installed to operate

! read the guts for more info !

20 Likes

this is so dope and such a cool gift to folks wanting to extend the capabilities of their synth-based scripts. super stoked on (and grateful for) this release and your work, @andrew!!

2 Likes

thank you for footswitch support! that’s awesome! :grin:

1 Like

lemme know if it works :call_me_hand:

1 Like

thank you for sharing these wrms @andrew! Been having some fun wonky jams with em.

1.1 is giving me error:load fail though sadly… Maybe user error somehow? anyone else load it ok?

Thank you for this! Love the idea of the mods, and yeah, people (myself incuded) should read more code :slight_smile:

1 Like

u on latest norns version ? I just tested w/ my partner’s norns - had the same load fail and an update got it working (expected this bc I’m using a new function on the softcut side)

but glad it’s jelling w/ you !

if anyone has ideas / confusions / feature requests hmu

oh durp ya that did it. thx!

some wrm bloops from just now~

3 Likes

wrmsmsh ~~

another mod - first of the combo type

adds a grid keyboard hitting molly the poly into the input of wrms. very easy script (18 lines) since both scripts are extensible and don’t have any interface conflicts

11 Likes

Wonderful work Andrew! Spent the last couple hours with wrmsmsh and it’s bliss in a script. Can’t wait to get some mods of my own going

1 Like

yay !! excited to see what you do

I should spend some time with wrmsmsh too

Of all the norns scripts this is the one I currently get the most joy with.
Thank you for this wonderful instrument

4 Likes