#1966

Have you seen the Library? There is a norns tag :slight_smile:

#1967

Click on the norns tag next to the title of this thread and you’ll see all norns related stuff. I believe most scripts are in there.

#1968

ahaaaa… perfect. Thanks to both of you!

#1969

apologies for the delay, didn’t see this till now.

you may either purchase a new WiFi nub here or just email help@monome.org for a $10 (shipping incl.) replacement

1 Like
#1970

Hi! simple question here that I bet I could find myself but…
Okay so I want to update to the newest version of norns (this is the easy part). After I do so, if I want/need to update my scripts (it seems like some needed some tweaks after the new norns update), what is the best way to do so?
Thanks!

#1971

if you mean scripts written by others: hopefully addressed in the norns FAQ, but let us know if you run into something not covered :rainbow:

if you mean your own scripts, I believe softcut and crow were the only things that might require changes in your code. softcut changes documented here

1 Like
#1972

Ah, so as I thought I’d need to overwrite the current code with the new code :slight_smile:

I wish it was my own scripts, hopefully soon!

Thanks so much Dan :v:

1 Like
#1973

If you’re comfortable with the command line, I find it can also be faster to ssh into norns and run “git pull” in the script directory. for example:

ssh we@norns.local
cd dust/code/otis
git pull
7 Likes
#1974

didnt realize the whole git thing was that simple (in terms of updating scripts)…I’ll have to try this out tonight!

2 Likes
#1975

well yea, not as easy as just typing “git pull” in the command line :slight_smile:

but also not that hard (coming from this dum-dum). apologies if this is basic git stuff most people know, just putting it out there for other git-clueless folks like myself. The thing to note is that I had been previously downloading zip files and sftp the files onto norns using cyberduck. The thing I had to do to get it to work was to “clone the git repository” onto my norns via terminal first, which creates the same folder in dust. (on a side note, if you already have the script with the same folder name in your dust/code folder from earlier, you will need to delete that before cloning the git repository if it has the same folder name) THEN, once thats done you can change directory into the script folder and “git pull” to update. BRILLIANT! Some screenshots of what I mean, and the link which kinda explained wtf to do for me…

04%20PM
Screen Shot 2019-10-23 at 8.36.04 PM.png1120×350 59.8 KB

edit: also important, to get the https address you go to the github page, hit the green button for “clone or download” and then copy the text of the https and past it into terminal after punching in: git clone (copy paste https address)

57%20PM
Screen Shot 2019-10-23 at 8.44.57 PM.png2066×1146 218 KB

3 Likes
#1976

That’s a good point… I forgot when you download the zip from gihub it doesn’t contain the .git folder which indicates it’s a git repository and allows you to run commands like git pull.

Somehow I am still able to run git pull for most scripts although I thought I also installed them via cyberduck. weird… Anyway, glad you figured it out!

1 Like
#1977

Hi All,

There used to be a way to download the update for Norns and then either sftp or thumbdrive it onto norns and do the update. Is that still possible? How do I do it? I don’t have internet at home (I know I know), and my work wifi won’t let me connect the norns to it. Thanks for any advice!

#1978

You can find the newest release here:

copy the folder to your norns (via cyberduck, scp etc)
Connect via ssh, navigate to the the folder e.g.:
cd 190405 and run:
./update.sh

1 Like
#1979

20+ characters worth of thanks!!!

#1980

and if you’re unable to Cyberduck, here’s manual install instructions with serial: https://monome.org/docs/norns/help/#manual-update, just replace the 190409 of tar xzvf norns190409.tgz and cd 190409 with the number version you’ve downloaded.

#1981

Thanks, that was helpful. I moved the file no problem, but was missing the step of unpacking the .tgz and the shutdown. For others reference what I did after moving the file to the update folder on the norns was this:

cd ~/update
tar xzvf norns191016.tgz
cd 191016
./update.sh
sudo shutdown now

With the shutdown happening only after the update completed (which was pretty fast).

Working great. Now to try out my new crow!

3 Likes
#1982

I like my Norns so much I’m considering a 2nd.

Is it possible to have 2 Norns on the same wifi network? Would they each be accessible from Maiden, or would this cause issues?

My apologies if this question has been asked before.

#1983

yes you can put as many norns on the same network as you’d like.

the norns.local will only connect to one, so instead you’ll need to conenct via the IP address instead.

2 Likes
#1984

stuck during download process …downloading…
used white button, now when on, nothing on screen…
what next?
edit: solved after switching disk run positions…

#1985

I’m wondering where user Engines should be stored so that they don’t get wiped after an update to norns? For example, I put the glut engine in norns/sc/engines, but this directory gets overwritten after an update. I’m guessing there is some kind of user folder where this stuff should go…?