Norns: studies

norns

#84

i’ve just shipped the last order. like just now.

the study is up next. (actually, a series of studies). thanks for your patience. tomorrow’s only task is getting the next study done.


#85

just got it hooked up! loving the studies, super easy to follow.

i did have one note, and sorry if this is the wrong place to mention this or if i’m just wrong for some reason:

in study 1, the section “the robots are mad” which is designed to throw an error doesn’t throw the error for me. reading the addendum, i think this is because position is defined (correctly and globally) in the copy of the study 1 script that comes preloaded on norns. so in my own untitled lua script for the study it doesn’t actually matter if i define it first or not. this does still illustrate the danger of global/local variables, though…

thanks to all for their work on this thing! so exited to figure it out


#86

@ypxkap thanks for the tip, i’ll investigate!


#87

in case anyone would like to proof this while i shoot a quick demo vid: https://github.com/monome/docs/blob/master/docs/norns/study-4.md

will have it on the main site in a couple hours.


#88

MIDI is still around and it's still fun. plug in and get to the command line:

Should “plug in” be replaced with “plug a USB MIDI controller into norns”? The study starts off with a grid example, so this part is ambiguous.

push a key and you'll see something like:

“push a key” should be “push a key on the MIDI controller” since norns has keys.


#89

it is live:

https://monome.org/docs/norns/study-4/

thanks to @ppqq and @trickyflemming for last-second edits


#90

(@tehn, old vid embedded in post above!)


#91

Just in time for my latest project!


#92

Yay, I have been eagerly awaiting the midi study! Thanks, @tehn!


#93

thanks @Dan_Derks!! fixed.


#94

Not sure if this should be asked here or in Norns Scripting:

The norns study part 4 “physical” says that this is the method to access grid keys:
g = grid.connect()
g.event = function(x,y,z)

Whereas the original AWAKE script (the only one that I’ve been modifying over and over so far) just uses:
function gridkey(x, y, z)

What’s the recommded way of accessing grid keys?


#95

the new syntax is necessary. the original awake used an old method of accessing the grid, which was completely redesigned (hence the month lapse in studies).


#96

Thanks much – that’s the final trigger for me to update (still on 180707 IIRC), as I love to do the studies.


#97

I can’t manage to use (or receive?) incoming MIDI clock with beatclock. I tried the following:

beatclock = require ‘beatclock’
clk = beatclock.new()
clk_midi = midi.connect(1)
clk_midi.event = clk.process_midi

function init()

clk.on_step = function() print(“step”) end
clk.on_select_internal = function() clk:start() end
clk.on_select_external = function() print(“external”) end
clk:add_clock_params()
clk:start()
end

My ROLAND UM-One MKII is receiving MIDI clock from analog RYTM and is associated to the port1 in “devices”.

When using internal MIDI, “step” is printed in Matron, switching to external makes appear external but that is all, the ‘print step’ function is not activated anymore.

BTW i’ve got a big gig on Saturday and i would really like to use my norns but i need to figure that thing out first so… help anyone? :kissing_heart:


#98

Can you confirm your roland device is showing up to norns as a MIDI device (in SYSTEM>DEVICES>MIDI ). Or that you can re-select it?

My Roland drum machines don’t show up at the moment due to the USB system getting pushed back to USB1.1 in the recent update (due to various errors on the USB system)


#99

@okyeron Yes it is present in devices 1, I also tried to reselect it.


#100

i don’t have a roland um-one but i’ll check with another device to ensure sync is working.