Approaching: norns

[glia]

can you please post a gist of the code? this looks great!

[perhaps here Norns: dust ]

[Inkwell]

so rad. excited to mess with it.

[Tyler]

I will certainly have it posted sometime this weekend.

[enneff]

I already have a version of this done that uses samples instead. I should get it out there. I’ll tidy it up this afternoon.

[greaterthanzero]

I made a polyrhythmic sampler that uses the grid.

very cool.

Interface question: can you change the number of steps / divisions once established? How would one go about that?

I imagine that adding columns is as simple as pressing a button outside of the recognized steps. But, how would you remove columns?

(press-and-hold might be the answer. maybe.)

[Tyler]

Two grid key press extends the row the the highest pressed key. Right most column resets row. Single presses toggle divisions on/off.

It’s 4-track, 2 channel. In the video you see the first channel only, which sets tuplets relative to a ‘quarter note’ the second track sets the quarter note on or off. So it’s sort similar to a Euclidean rhythm at the same time.

[simondemeule]

@tehn will crow be usable as a standard audio interface? I do not own Norns (yet?), but I’d absolutely love being able to both input and output sound, CV, and i2c through a single, ridiculously good looking and chainable tiny device.

[greaterthanzero]

Right most column resets row.

Is that variable? (How much effort would it take to support 8x8 grids?)

[tehn]

crow is not standard audio soundcard, but it will certainly be usable from a non-norns computer. details forthcoming.

[Tyler]

I could make an 8x8 version of the script pretty easily. Though, if the values wrap around 8 on your grid, it should still work. I posted the gist in the code review thread if you want to try it out yourself.

[dmon]

the code is a bit lower level, but I’ve already done it for the push2 , and its available in my repo/ push2 branch.
this code could be quite easily adapted for a push 1. its mainly just removing the display code.
(note: i cannot do this, as i don’t have a push 1 anymore)

emulating the monome grid was pretty simple, as it has quite a restricted api (things like set, refresh) ,
if there was a will this could be done quite easily, not only for push, but also other grids like launchpads, using the same/similar approach.

Oh yeah - the cuckoo mode is pretty much the thing I’d want… I’m not experienced enough with C programming (I may have once programmed “hello world”, though ;)) to modify your Push 2 branch… but this seems like a cool project for the time after my thesis!

[TheTechnobear]

cool, @dmon, Im refactoring the code at the moment, so that it works nicer alongside monome grids, but some of this might help your efforts…

Ive also started implementing scripts using the ‘push2 native api’, so that will help solidify that api.

first project is a rewrite of MLR (called un-imaginatively PLR ) , basic idea is to make use of the full display, and colours of the push (lcd and pads), and also to start using all the ‘musical’ buttons, in place of the unlabelled grid (so things like quantise… and also to build on the metaphors of ableton, so its familiar for push users.

took me a few hours to get the basics running…

• so all parameters, including per track
• tracks running, start/stop, record, cut/loop , and track state handling
  (this layout is 4 tracks per page, so 16 steps take 2 rows, so use slightly different colour for each ‘track’’)
• pattern selection.
• quantize
• tempo

to do:

• move tempo/volume to their normal push locations, and quantise on to a hold quantise button (like ableton) , this will free up some parameter space on the lcd
• I’m going to use the mod strip for ‘speed’ (fwd/reverse), with spring back … or perhaps position?!
• file selection (browse button) , this will give me ‘proper’ track names too, where relevant.
  (will have a file selector like the ableton view, this will then be reusable for other scripts)
• mixer view (mix button), so all levels on one view
  (i need to look into getting crone to send back levels so I can view them)
• alternative pad layouts, current thoughts
  • a detail view, so one track, will other parts of the pads doing things like speed, and other parameters
  • 1 page view (so , a track per line)
• extend to 8 tracks from 6
• enable mute/solo/stop per track

id also love to have a ‘clip’ view, where it shows a tracks waveform, and then enables you to accurately select start/end points with the encoders (like you can in ableton on a sample)… so need to see if crone supports that, and then work out how to quantise the start of it (thats not that difficult i don’t think!?)

(theres still other expected functions, like duplicate, double loop, fixed length (for record) ) … but they all come later , I think the above are the minimum set )

anyways its been a fun couple of hours, i was surprised how quickly it came together - so hopefully I can get through my to do list pretty quickly

[jlmitch5]

had some fun with the kayan app (by @burn – thank you for the great app!!) this evening. heavily inspired by mary lattimore’s recent harp through delay work (specifically Baltic Birch from her album Hundreds of Days and her piece she composed for a player piano exhibit called Glamorous Mom).

It’s a really simple piece, I am just slowly bring up the reveal knob, ran through delays. I started modulated the delay time at the end.

I learned that bringing up the volume of norns with a lot of gain from mutable instruments veils, and then back down with mannequins rip works well for gain staging in my particular setup.

[franwilder]

I updated Dust to get the new version, I see the notes and new scale options which is rad. Are there instructions anywhere to set up the midi out?

Also, I think this might be a bug or something. The music keeps playing even if I remove all orbs, this wasn’t happening before. Has anyone else reported this?

[Prnts]

Wasn’t able to get midi out myself. Figured maybe there was another piece required somewhere inside Norns that I was missing maybe? Looking forward to hearing more about this.

[enneff]

The midi out for rebound is supposed to send midi notes on channel 1 of every attached midi device. It’s entirely possible that it is broken, though. I was able to get it to work on one of my midi devices but not all of them.

As for the music playing after removing the orbs, that is indeed mysterious. Are you able to reproduce it reliably? If so, what are the steps?

I won’t have much time this weekend to investigate this, but I’ll see if I can take a look on Sunday evening.

[davidjez]

I’m likely in the wrong place for this, but I’m quite intrigued by Norns and thinking of picking one up from the next batch coming out in October 2018. I’m not really a programmer, but I do have a technical background (engineering physics);

(1) I assume there is lots of available SW already for Norns/Grids that I can use right out of the box?
(2) How easy is the programming language if I wanted to learn. It’s been awhile. I used to know things like Matlab without too much trouble. Are we talking a week or two, or months to do something reasonably interesting.

Thanks for entertaining this post.

[trickyflemming]

How easy is the programming language if I wanted to learn. It’s been awhile. I used to know things like Matlab without too much trouble. Are we talking a week or two, or months to do something reasonably interesting.

Lua (the scripting end) is quite easy. You already are at an advantage over many of us since Lua and MATLAB are both 1-indexed (the first element of myArray is myArray[1] not myArray[0]).

SuperCollider (the audio engine end) is significantly harder to learn. norns comes with a pretty solid collection of audio engines to start with.

I recommend taking a look at the first study and seeing what it takes to add interaction to a sine generator (the “TestSine” engine): https://monome.org/docs/norns/study-1/

[madeinspace]

Hi guys when can we expect having Norns talk modular with that crow module?

[alphacactus]

i believe so

Approaching: norns

crow will control jf (!)