#146

Wanted to have some gridless control with the 16n, is MIDI mapping gone?
I guess the params have preset CC numbers now, is there a list?

#147

In the meantime I recorded this little piece. RND adds a ton of movement for gridless operations.

Dan’s signature piano loop, voice loop and live recorded electromagnetic field sounds produced by Norns shield and the laptop. Free running.
You can’t call it dawless as the daw was open and probably affecting the load on the CPU thus affecting the EM field… I guess?

Enjoy :slight_smile:

13 Likes
#148

holy hell, carlos. this is fuckin’ gorgeous. that EM noise is bonkers cool, the vocal sample is out of control cool – and you did all of this gridless??? i need you to do a Twitch stream on the other side of this beta to showcase these techniques, omg. thank you for sharing!!

general MIDI mapping through PARAMS will still be possible, it’s just broken in the current beta :slight_smile:
I fixed it up this morning, just waiting to see if any additional bugs surface before I push it.

to clarify things, I changed the “MIDI setup” PARAMS group to “MIDI keyboard setup” – those have fixed CC’s + channels, which will be outlined in docs but have no affect on the standard mapping you’d want to do with a 16n.

1 Like
#149

Thanks for the kind words!
For gridless ops I guess it takes longer to do a nice preset, I tend to go deep. During performance there’s only one thing you can do at at time without going nuts so you better have a good starting point.
I played with RND activation and delay feedback to 0 and back to 100 as fast as I could for both channels. I REALLY need an external control for delay feedback.

Glad to see MIDI map is still there :slight_smile:

By the way, when overwriting a collection I can’t press/twist anything to take me out of the screen “saved!” without being k2 or k3 thus cancelling the process of overwriting. You may want to take a look onto that.

3 Likes
#150

for sure!

yeah, i’m trying to add as much on-norns control as possible to things (eg. the [loops] page nav overhaul feels like an improvement). rnd really opened gridless play up, and i hope that euclid helps folks get to rhythmic things a lot more quickly.

thanks for reminding me – there’s some definite optimization to be done on the pattern generators when flying gridless :slight_smile:

this is weird. if you can repro this, please send over the maiden output? sounds like one of the saving functions isn’t completing and so it’s not returning you to the main menu after successful completion.

#151

I’d need some guidance here :sweat_smile:
How can I do it?

#152

oh! of course:

  • when you run the script next, get norns connected to wifi
  • navigate to norns.local on another computer on the same network
  • perform the overwrite function in collections
  • when it goes wrong, the bottom screen (the matron REPL) should flood with errors
  • just copy and paste them here, which will help me understand what variables or functions are being problematic :slight_smile:
1 Like
#153

Ah, it’s automatically showing in matron, I had the setup ready. Here you go:

pset >> write: /home/we/dust/data/cheat_codes2/collection-Piano/params/all.pset lua: /home/we/norns/lua/core/clock.lua:82: /home/we/dust/code/cheat_codes2-beta-beta3/cheat_codes.lua:5210: attempt to concatenate a nil value (field 'target') stack traceback: [C]: in function 'error' /home/we/norns/lua/core/clock.lua:82: in function 'core/clock.resume'

1 Like
#154

ah excellent!

dang, you were on that beta3 quick – there’s a hotfix up which should change the line printed in the error. can you please try this version and repost errors?

2 Likes
#155

Seems ok now :slight_smile:

pset >> write: /home/we/dust/data/cheat_codes2/collection-Piano/params/all.pset saved midi pattern 1 saved midi pattern 2 saved midi pattern 3

I should do a cleanup of all this betas and extra data stored once the master version is out. I guess collections will be compatible :black_heart:

1 Like
#156

between the betas and the public release? I’m hoping so – unless there are some critical gotchas, collections are in their final form :slight_smile:

1 Like
#157

I second @dan_derks’ petition of a video/live stream of you doing your thing gridless! This is amazing

3 Likes
#158

Thank you so much @PaulFe!

I wouldn’t mind to do a video, but 90% of what you hear is done before recording anything and it’s heavily influenced by what samples/live sampling I am using. I take the modular synth approach of spending time setting up a nice complex patch and study what options I have for performance and do a little practice before hitting rec.

A couple of key things for me:

  • Delay is too well implemented to ignore, playing with feedback is really rewarding. It takes longer without a Grid, but fortunately Dan made the selected params to stay the same when navigating back and forth through CC. So once you hace feedback highlighted, three quick presses on K2 takes you back to main screen, three quick presses on K3 on top of delays and you are back again in feedback, no need to think about navigating with encoders (1) (unless you want to change another parameter of course, but we are streamlining the actions by embracing limitations here).

  • There’s no possible pattern recording gridless so well tuned random adds a lot of movement. Selecting bank and random number is really painless with only two encoders involved, K1+K3 activates/deactivates them(2). So random is definitely performable gridless. Random to rate is always a win with melodic samples, even random semitone offset octave + fifth. For unison samples best to use a scale.

  • Looped envelopes adds a toooon of movement as well, even for live sampled loops. Loloopop.

I haven’t played much with more rhythmic stuff on euclid or arp yet (cooking an OSC keyboard on the current layout since I don’t have one where I live now) but I’ll update about them.

(1) Petition to have K1+ E3/E2 on delay parameters to change both L and R simultaneously and sync. So feedback L on 50% and feedback R on 75% would jump to 80% in both if K1 is pressed while turning the respective encoder.
Edit: Specifically on feedback I’d rather have a quick on/off function (not synced): turn left to jump to 0%, turn right to jump to the current value. For the rest sync is better.

(2) Petition to have a shorter starting window of pressing K1+* commands. It takes too long for K1 to be on to detect a second key. I guess you can’t go too short or you mess with going to PARAMETERS?

Edit: sorry for the unexpected length :sweat_smile:

5 Likes
#159

Bug/feature report:

rnd > param: semitone offset has an invisible parameter below scale.

2 Likes
#160

Any plans or other requests to have the delay timing available on the grid? Would be ace to be able to hit a key or combo to change the timing on the fly.

Edit I’m kind of a nincompoop. found the mult lane buttons outside of the rate keys.

3 Likes
#161

And just a pipe dream. Add a reverse delay buffer button… and you almost have some 4ms looping delay Action going on.

1 Like
#162

@dan_derks, good morning!
Report:

  1. Surf trip = huge success. Many waves and lots of sun!

  2. test-mft = huge success. CC’s 1-4 working as expected and displaying random encoder values.

I just tested the MFT with the beta 3 hotfix and still the same result of no LED’s being updated. All the controls work fine though. Let me know what you’d like me to do next.

P

#163

This is great! I’ll be sure to try out these techniques later! Thanks for writing it all out.

1 Like
#164

:bug: report (or maybe something has changed?): not able to save patterns on the meta page

#165

will update with some more news later, but @DuellingAnts, can you please post matron output + some repro steps here? working on my side, but maybe there’s a param i’m not using?

1 Like