Is there a general rule that script folders shouldn’t have ‘- master’ after the name? And if this is the case, why have 75% of those I’ve downloaded been named like that? Just wondering…

It’s likely a default with the way github creates the zip file when there’s more than one branch in the repo.

Aha. So I should re-name them all?

I just got a norns! Very excited. Brand new, running 190405. However, I immediately run into an issue when trying to follow the instructions for Study 1.

After connecting to maiden and entering the initial program (file is named studies1.lua in the top-level folder containing audio/, code/ and data/), I get an error:

lua:
/home/we/norns/lua/core/script.lua:96: attempt to concatenate a nil value (field '?')
stack traceback:
/home/we/norns/lua/core/script.lua:96: in function 'core/script.load'
(...tail calls...)

I’ve checked the code I’ve entered and it seems character-for-character the exact same as in the Study 1 guide. I’ve also checked this by deleting everything I typed and literally copying-and-pasting from the Study.

I feel like I must be doing something obvious wrong. Can anyone help me see the mistake? Happy to do whatever needs to be done to help debug (I am comfortable with git and poking around via ssh).

If after grabbing a script from github as a zip file and you end up with a directory that is thing-master you should rename it to thing

4 Likes

20 characters of thanks.

1 Like

It probably just needs to go in the code folder?

1 Like

Ahhh. That worked. I understand now. Thanks for the help!

Still though, I might suggest adding that detail (“your scripts must go in the code/ folder”) for those of us new to Norns.

1 Like

this is on the top of the docs: third link here: https://monome.org/docs/norns/
and first paragraph here: https://monome.org/docs/norns/script-reference/

maybe better links are needed for people to find the docs?

a docs.url file in the root of the repo perhaps?

it should be reiterated in study 1, though.

2 Likes

I plead guilty to not being observant enough to find those existing tips! But I also agree that reiterating in study 1 is wise, because I feel that it was written as a way to dive right in and learn by doing. Thanks all for the help.

it is done, thanks @simonvanderveldt!

2 Likes

Is it so that you can only do git pulls on scripts «included» in norns? Trying to do a git pull in Timber returns this error message:

192.168.86.33 ~/dust/code/timber $ git pull
fatal: Not a git repository (or any of the parent directories): .git

did you install timber via git? Pretty sure that git pull will only work if you used git clone to install.

1 Like

This is true. However I think the default install includes the .git directories so a pull could be done in this case.

Rule of thumb - be consistent in your install method

2 Likes

This all makes sense. And also a good rule of thumb. Thanks guys.

Trying to get my head around an external clocking issue that i’m finding with several scripts but not all.

I can’t get the following to clock as sequences just don’t play:
Awake, Playfair, Foulplay, Less Concepts, Meadowphysics, Traffic, Takt.

These do work as I’d hope:
Isoseq, Loom, Strum

Using an iConnectivity mio.

Does anyone else have the same problem? i haven’t tested with all of the non-working scripts but midi out does work on Awake for example.

i know i’ve seen issue resembling this elsewhere on here, check out this suggestion:

i did traffic and based it off of loom, so if one is working but not the other, it’s because i messed something up when i was tweaking it, i don’t have any devices to send clock to so i wouldn’t have noticed, sorry about that! i will figure out what i botched. thanks for pointing it out.

If I power on the device with a grid plugged in it does the sparkle motion animation and then has a blank screen till I remove the grid. Is that normal operation?

Thanks - although i think that post refers to problems sending midi/clock out from Awake. I’m trying to use an external clock on these scripts!