#1

200712

norns 2.4.2

image

  • NEW ā€˜maidenā€™ alias

details:

  • crow 2.0 support! (crow firmware coming later today!)
  • FILE SELECT now has an up-folder (..) selection for navigation, K2 is now only for cancel (makes so much sense!), and folder location is resumed! FILE PARAMs can be adjusted with E3.
  • controlspec now has quantum: previously delta was 1/100 of the range. number and control param types now have wrap attribute. see #1149
  • @ngwese has a rad project in the worksā€” these libs are part of it, but also more generally useful
  • maiden is now in the path which simplifies command-line operation ie:
ssh we@norns.local
maiden repl

(you have to enter password after ssh)

run SYSTEM > UPDATE when connected to the internet

68 Likes
Fates - a DIY norns DAC board for Raspberry Pi
^^ crow 2.0.0
#2

20 Characters of THANK YOU!

1 Like
#3

All the interface changes make so much sense (both user and dev facing). Many thanks!

Also, donā€™t need my bash alias anymore!

Also,

DSC_0015-3
DSC_0015-31029Ɨ579 368 KB

6 Likes
#4

this is awesome! :partying_face:

should this be K2?

1 Like
#5

yes, fixed! thanks mat!!

1 Like
#6

Nice! Now Iā€™m wondering, what are the different use cases for step vs. quantum when it comes to controlspec? I canā€™t think of one where I would want the former over the latter.

1 Like
#7

step is the output quantization, itā€™s guaranteed that the control output is always a multiple of this, whether you adjust the control via the PARAMS menu or from calling params:delta / params:set in your script. So one use for this might be controlling something that is ultimately discrete ā€“ for instance if your script outputs midi CCs you could use a controlspec with an output range of 0-127 and a step of 1.

quantum instead controls the input quantization, which affects the step size when adjusting via the menu or mapped params, but has no effect on calls to params:delta / params:set ā€“ you can pass any value to these and the controlā€™s output value will be adjusted accordingly, and quantized to a multiple of step.

3 Likes
#8

@tehn @ngwese are there docs or more information on these libs? Might be useful for a script Iā€™ve been thinking of making lately.

1 Like
#9

Great, thank you!!! :blush: :heart:

Edit:

NEW fileselect resume folder location

This is something I wanted so much! Makes things way easier :partying_face:

#10

There are luadocs to serve as an API reference but nothing like tutorials or studies for these container libraries. I havenā€™t looked yet to see it the HTML reference docs are included in the release or not. Iā€™ll look later today.

In the meantime you could look at the source directly: https://github.com/monome/norns/tree/main/lua/lib/container

Using one of the libraries in a script would look like:
local Deque = require ā€œcontainer/dequeā€

3 Likes
#11

I am most happy about the ā€œFileselect Resume Folder Locationā€. This makes the sample-based scripts much easier to use. Thanks for the update.

5 Likes
#12

Im trying to update and its throwing up 200604? after ā€œchecking for updateā€ - any ideas?

#13

Thank you!
Does it works also with Fates? By now it says ā€œup to dateā€ but Iā€™m sure is the 200604ā€¦

1 Like
#14

iā€™m getting the same thing. just gives me the ā€œup to dateā€ message

1 Like
#15

@dogma @Alessio @encephalitislethargi are you all using fates? thatā€™s on a different update system, so youā€™ll have to waitā€” check the fates thread.

2 Likes
#16

Yep,mine is a Fates :slight_smile: thank you for the clarification!

#17

currently the fates update needs to be managed separately because of kernel divergence. this will likely change in the future with version 3.0, but until then these will not be in sync.

4 Likes
#18

The ever present and thrilling shadow of 3.0ā€¦!

3 Likes
#19

Trying to grab this using System > Update but my norns is stuck on ā€œchecking for updateā€¦ā€ for over an hour. Able to SSH to it so wifi is working. Should I update manually?

#20

I think I had this issue as well. I think it worked after reconnecting the wifi and/or a restart.