#1687

This looks like a typo or leftover from an earlier beta perhaps.

As you found, the correct usage is a.delta(n, delta)

(Pull request submitted to fix the script reference page.)

1 Like
#1688

Thank you. Sorry yeah I should have tried to update the document for the function. I was mostly unsure if I was looking in the wrong places. And I wasn’t sure if Delta was replacing Enc and the docs were out of dated or if enc was replacing Delta and the code change had not happened.

1 Like
#1689

Hi!
Im getting an error when trying to load ASH/ORBIT

error output 
error: init

the maiden output:

1

matron

sc

# script load: /home/we/dust/code/ash/orbit.lua

# cleanup

# script clear

pset >> write: /home/we/dust/data/system.pset

# script run

Engine.register_commands; count: 0

___ engine commands ___

___ polls ___

amp_in_l

amp_in_r

amp_out_l

amp_out_r

cpu_avg

cpu_peak

pitch_in_l

pitch_in_r

# script init

### SCRIPT ERROR: init

/home/we/dust/code/ash/orbit.lua:15: attempt to call a nil value (field 'level_ext_cut')

stack traceback:

/home/we/norns/lua/core/norns.lua:190: in field 'level_ext_cut'

/home/we/dust/code/ash/orbit.lua:15: in global 'init'

/home/we/norns/lua/core/script.lua:74: in function 'core/script.init'

[C]: in function 'xpcall'

/home/we/norns/lua/core/norns.lua:191: in field 'try'

/home/we/norns/lua/core/engine.lua:89: in function </home/we/norns/lua/core/engine.lua:88>

>> reading PMAP /home/we/dust/data/ash/orbit/orbit.pmap

I have tried re uploading the latest glut engine, from

but to no avail, any ideas?

Many thanks!

1 Like
#1690

the same error was mentioned a few months ago, and it was quickly fixed. make sure you’re running the latest version of the orbit script, which you can get by pulling in a copy of the whole ash folder, as seen in the solution:

1 Like
#1691

@tehn - do you happen to have a model/part number for the WiFi nub that ships with Norns? The one I ordered online was DOA.

#1692

Thanks that fixed it!

#1693

Is something like this strictly for midi clock sync? Or is this to also send midi notes and CC values to something like Ableton?

#1694

not strictly for clock, it’s a full midi connection. not only that it also has 4 separate bi-directional ports.

1 Like
#1695

Cool. I’m going to be scoring a 2host from the creator of them, to allow for communication, but figured I’d ask around about what other measures there are, since I didn’t want to maybe miss anything. There are a few apps (such as Kris, Awake and more) that I wanted to send midi info from to ableton.

#1696

anything with an rtl8192 chipset will certainly work. but various others should also be fine.

a nicer wifi dongle is this one: https://www.thinkpenguin.com/gnu-linux/penguin-wireless-n-usb-adapter-gnu-linux-tpe-n150usb

1 Like
#1697

Awesome - many thanks :bowing_man:

#1698

First, a suggestion for Euro Norns types who don’t like adapters. I’ve bought a powered USB hub with dedicated high powered charging slots. So you just power that up, plug the wifi nub and your array of controllers into it and then a single usb from the hub to Norns. It’s tidy and I can confirm that Grid/Nub/Arc works and I’ll be trying out adding a Kenton Killamix (worst name for a controller?) and a PC4 if it’s needed.

The one I got is here: https://www.amazon.co.uk/Anker-PowerIQ-Charging-Macbook-Surface-7-Ports-3/dp/B00VE4UJD4/ref=sr_1_3?crid=2C5L6ZBJ9A6AO&keywords=anker+powered+usb+hub&qid=1565172976&s=gateway&sprefix=anker+powered+usb%2Caps%2C273&sr=8-3

The power brick is bigger than the unit, which is odd but hopefully means that it won’t crap out.

Now, a question. I’m thinking about taking Norns away with me on holiday and so far I’ve just used the midi out and recorded patterns that are interesting. I know that you can record the audio but that’s not super useful to me as I want to use the patterns on my synths when I get home. The dirty option that I was looking at was to record some audio internally, tag it and then take pictures on my phone of the state, it’s long winded and kind of ropey. A look up this thread shows:

‘some scripts save, others don’t. try going to PARAMETERS and hold KEY1. you’ll see the state save/load screen (use KEY2/KEY3 respectively). this should save/load everything in the PARAMETERs screen’

This was over a year ago and I know things have moved fast, is this still the best way? Would I need to grab the state file if I run out of save slots? I could SFTP in from my phone I think?

Given that it’s so small and battery powered and nice to mess with I bet loads of you lot are using it the same way, anyone got any advice on how to save travel noodles?

#1699

I use this one, and can say it’s a big improvement in range and stability over the smaller nubs.

2 Likes
#1700

Oooh, I ended up ordering something very similar. Thanks for the confirmation!

#1701

Hey! I finally managed to buy norns. I installed the latest update and would like to update the dust scripts. I assumed that https://github.com/monome/dust.git is the right repo and cloned it on norns. I then get a “Suppercollider fail” after rebooting norns. Going back to the pre-installed dust folder things work again.
What is the canonical process for keeping up to date with those community scripts?

#1702

Hi there! Check out the Library, there’s a tag for Norns scripts. This is where scripts are shared, and updates posted.

#1703

This was the right repo for Norns 1.x. This is changed in 2.x and everything is moved to individual github repos. So there’s no “master” repo anymore.

This might be helpful to understand the structure in 2.0
https://github.com/monome/norns/wiki/dust-2.0

1 Like
#1704

Thank you both, this helps…

#1705

Im working on a script that calls another script in the same directory.
local list = require("ericmoderbacher/zellen/linkedlist")

i call that library later
print(list.getNodeCount(the_past.next))

I was having there was an issue in getNodeCount so I edited the code in maiden and hit save.

Then I reran the parent script, and the issue persisted. Took me ages to find that a change in the included file did not take effect untill I reset or restarted norns.

Is this a bug? If no: where can I learn these types of things about norns development? I was totally gaslighted by this.

#1707

use include instead of require and it won’t shouldn’t have this problem.

I believe require caches the file in question or something

NOTE - include i believe wants a path local to the current script, or will reference from /home/we/dust/code/