#37

Hmmm… seems like it’s a couple wednesdays away from grids. midi. sync. OSC, HID.

I’d like to figure out how to get OSC messages doing something.

I’ve got a TouchOSC template I’m working on to emulate a grid. Maiden shows me OSC messages recieved, but beyond that I’m not sure what I need to do to tell the script to do something with the OSC message. Ideally I’d like the script to believe it’s just getting messages from a grid.

Any quick pointers?

#38

we’re working on a set of musical helper functions— so yes you won’t need to do it by hand.

by in the meantime, here’s a midi to hz function:

function midi_to_hz(note)
  return (440 / 32) * (2 ^ ((note - 9) / 12))
end

throw this in your script, then use:

engine.hz(midi_to_hz(60))

to play middle c

ps. functions are covered next week

8 Likes
#39

Here is some code I worked out the other day. Change the IP address and port as needed.

-- turning a knob moves a 
-- number randomly around 
-- the screen
-- and sends OSC

require 'osc'

engine.name = 'TestSine'

local value="turn a knob"
local speed=0

function init()
  engine.amp(0.2)
end

-- screen redraw function
function redraw()
  -- clear screen
  screen.clear()
  screen.move(math.random(0,120),math.random(0,50))
  screen.text(value)
  screen.update()
end

function enc(n,delta)
  value = n
  osc.send({'192.168.1.10',6000},'/goto/prev/',{n})
  engine.amp(0.2)
  engine.hz(n*delta*400)
  redraw()
end

function key(n,z)
  value = n 
  osc.send({'192.168.1.10',6000},'/goto/next/',{n})
  engine.hz(n*20)
  engine.amp(0.5)
  redraw()
end
1 Like
#40

And whoops I see now you were more interested in doing something with received OSC messages. Check out the OSC docs for osc.event(from, path, args) See: http://norns.local/doc/modules/osc.html

#41

Yup - i’ve been banging my head against those docs for awhile and trying to make sense of it.

Still trying to wrap my head around lua

1 Like
#42

I’ve got a draft musicutil.lua on the go here that has functions for converting notes to freqs and back, converting notes to friendly names, generating scales and snapping notes to a table (scale). Pull request coming soon!

5 Likes
Norns: scripting
#43

Oooh… this turned out to be very helpful in getting my virtual grid buttons to light up in touchosc.

:+1: Thanks!

2 Likes
#44

It’s Wednesday :clap:

2 Likes
#45

somewhere in the world - like here! :slight_smile: my Wednesday nornsday is actually a Thursday nornsday for me

2 Likes
#46

wednesday!

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

27 Likes
#47

“pause. really consider the possibilities, and i hope your mind explodes a tiny bit. this is why programming in a musical context is so incredibly powerful and interesting.”

Yep, my mind exploded just watching that demo video. First I was like “oh great a sequencer [yawn]. Then I was like “wait what is happening?!? [head explodes]

7 Likes
#48

You know these series of studies really give me the same feeling as the Micro Adventure books of the 80s where you’d type BASIC programs into a computer as part of the story. These are great ways to learn about programming. Norns is really turning into an excellent platform for learning about creative coding and music. Thank You!

11 Likes
#49

@tehn I love the creative possibilities in adding additional functions to the sequencer. Here is the edited list that is working for me right now.

function on() engine.amp(0.2) end
function inc() on() note = util.clamp(note + 5, 40, 120) end
function dec() on() note = util.clamp(note - 5, 40, 120) end
function bottom() on() note = 40 end
function top() on() note = 120 end
function rand() on() note = math.random(80) + 40 end
function metrofast() counter.time = 0.125 end
function metroslow() counter.time = 0.25 end
function positionrand() position = math.random(STEPS) end
function rest() engine.amp(0) end
function filt() res() engine.cutoff(math.random(5000)+50) end
function res() engine.gain(math.random(4.0)) end
function randsynth() width() release() end
function width() engine.pw(math.random(1.0)) end
function release() engine.release(math.random(3.0)) end

act = {inc, dec, bottom, top, rand, metrofast, metroslow, positionrand, rest, filt, randsynth}
COMMANDS = 11
label = {"+", "-", "<", ">", "*", "M", "m", "#", "r", "f", "s"}
8 Likes
#51

This is a really nice study.

Reading it, the things that leap out at me are a slight glossing over scope, which you use as a term a few times without fully clarifying. My gutfeel is to not slow down the study with endless explanation, though; I almost want footnotes, or something. (My notes on scope would be about “local scope” inside a function, and basically where variable names are relevant and not - eg how argument names are chosen, how local variables in a function are freed, etc. Also “class function” isn’t quite fully explained).

Sorry for nitpicking - just know that these tutorials are largely aimed at users whose exposure to programming, or at least programming Lua, might be limited. Mainly, it makes me appreciate how effective the narrative of the studies is - I’m only ever thinking about polish/reference/clarity.

3 Likes
#52

are the studies planning to dive into the SC side at all (e.g. adding engines etc) ? (perhaps after matron/lua?)
(I know, lots to cover so all takes time, so might be ‘a while yet’, just wondering what is ‘in scope’)

btw… I like your examples @tehn, they are a great balance of ‘simple enough’ to understand, and extend, yet interesting enough to want to dive into - its tricky balance to achieve.

1 Like
Norns: crone/supercollider
#53

metro class is in (norns/docs)[norns.local/docs] (must be connected to norns)

I suppose this should be norns.local/doc ?

#54

just checked. It is /doc… but honestly, it seems like it should be /docs lol

1 Like
#55
1 Like
#56

Wondering if this has happened to anyone else here or if someone can point out what I may have done wrong here but last night my first day with Norns I wanted to start the first study “many tomorrows”.

I was able to get into maiden and create a new script, name it, then add the first block of code from the study. However once I ran it in Matron I got no sound and my Norns pretty much became unresponsive except for encoder 2. When I turned encoder 2 it allowed me to scroll though the page I was on but that was about it.

Now what I’m wondering is could this have happened because I went into maiden while a script was locally loaded on Norns? Forgive my lack of knowledge here as Norns will be my first foray into programming.

For about two hours I thought I had bricked or ruined Norns. After rebooting my computer I was able to have control over it again.

#59

@prnts this sounds like a wifi bug that we’re working on. if it happens again and still isn’t responsive after a minute, shut down the norns via the emergency switch on the bottom and reboot. (use this bottom switch only if there’s a crash-- use SLEEP from the menu normally, which does a clean shutdown.

EDIT: also see @Olivier’s post below

2 Likes