#41

Finally got around to try out wrms yesterday. I’m a big fan of Cranes already and this is another looper right up my alley. Thank you @andrew , you’re a star

Here’s a little jam

16 Likes
#42

Dang. You make this look easy! What a great demonstration of the beauty that odd wrms ~

Thanks for sharing!

2 Likes
#43

it is nice !!!

more wrms coming soon

any ideas or feature requests out there now that things have sunk in ?

#44

Would it be possible to to adjust the loop points for the 2nd worm after it’s recorded (sorry if that’s already a possibility and I’ve missed it somehow :sweat_smile:)

#45

I haven’t played with wrms in a couple weeks but the last time I did I got super surprising (and loud) feedback with it! I think I was doing something with them filter maybe? (Probably, I forget).
I turned on the compressor in Norns after that. I don’t have an idea of the signal path but not sure if it’s possible to have it on by default within wrms?

#46

definitely - planning this for the nxt update / variation. the default version is intentionally minimal but
i’ve been craving something more maximal

very resonant filter values get feedback-y (the filter is in the feedback loop for wrm #1), I’m guessing that was it ? I don’t think they are that resonant by default in the filter version tho

2 Likes
#47

hi, first post, so let me know if I need to post this elsewere. I started using norns shield this week and really enjoy it. I installed cranes successfully and installed wrms via maiden. However when I want to open wrms i get an error: load fail.
/home/we/norns/lua/core/softcut.lua:201: ‘for’ limit must be a number …

Some other programs, like compass also give errors: init /home/we/norns/lua/core/paramset.lua:237: invalid paramset index: clock_tempo

looking forward to get wrms to work! thanks

2 Likes
#48

The “clock_tempo” one implies your norns isn’t up to date. Go to the main menu, go to System, go to Update, and install any updates it finds (you’ll need to have the WiFi nub in and be connected to the internet)

2 Likes
#49

thanks for the quick reply! I downloaded the latest norns.shield image but it needed an update indeed! All working now, cool!

1 Like
#50

finally made somethin w/ wrms that i’m proud of…

12 Likes
#51

for those whose hands live in the soil

here’s wrms on an aux send (having an extra fates/shield/norns) on an aux send has been nothing less than remarkable…

here’s a little snippy with all the raw bits attached - what you initially hear is the not so “dry” dry signal, then wrms fades in while the dry signal fades out

9 Likes
#52

ooooo fantastic tip and wonderful artifact! excited to dig into this config :wink:

1 Like
#53

whats the signal path? @claasp

#54

@glia ahh i see, it’s a morphagene going into clouds (spectral madness) no rvrb. i then grabbed a few seconds of that into wrms and manually scrubbed through one of the buffers. the aux send is completely turned down, i fade it in on the return so the initial voice isn’t being affected, as i fade that in i fade the sample out if that makes any sense

#55

ah ok sorry i’m trying to figure out the way you made it

is this a no-input patch with just norns or fates? are you using mixer feedback?

you mention aux but i have no real clue where the original audio is coming from

#56

did something similar this month @glia @claasp

this was otis in a send, recorded from the master, then into wrms as a send, or something like that. wavatable & kalimba as sound sources / unedited messiness

5 Likes
#57

@claasp As somehow who doesn’t REALLY understand sends and all, but appreciated the effect gained here, would you mind describing your signal chain in slightly more laymen terms?

3 Likes
#58

Hi, every time i upload wrms to my norns shield, I get an “error: load fail” message. tried scanning through this thread to find a solution but didn’t see any. sorry if this has been answered before. Thanks!

1 Like
#59

Is your norns up to date?

1 Like
#60

Thanks, forgot to do this. just got it up and running after a few months off.

1 Like