norns: help

Prnts · 2019-07-14T19:53:04.306Z

Dust v1 has now become irrelevant since your upgrade to 2.0. If you have any recordings from tape or any samples you want to keep then you should back those up or move them into the 2.0 audio folder.

The code folder is the right place for scripts in Norns 2.0

If you go to the library section of lines you can find all of the available scripts to add to Norns.

There should be a “we” folder inside the “code” folder

okyeron · 2019-07-14T19:54:53.952Z

dust is the folder you want to use. inside there, go to code and then we and then lib - so the path is /home/we/dust/code/we/lib (or dust/code/we/lib from your home directory.)

remove/delete the fm7 files from that directory.

Then go to the norns menu and do SYSTEM>RESET

ecfike · 2019-07-14T19:59:16.521Z

Screen Shot 2019-07-14 at 2.57.07 PM.png1582×1310 345 KB

So this is what the folders inside “Dust” look like. I’m not seeing a “We” folder. I guess it’s possible I’ve misplaced it but I have no memory of doing that.

okyeron · 2019-07-14T20:39:49.804Z

well that’s a horse of a different color…

I’m guessing you obtained this norns used and this is how it was when you received it?

Hard to say exactly where the problem is. I’d suggest deleting older script folders (from 10/31/18) and re-installing those from the current source for each.

Also maybe go ahead and re-fetch we as that are considered “stock” and may have some dependencies

from ssh

cd ~
git clone https://github.com/monome/we.git

ecfike · 2019-07-14T21:00:12.934Z

I’m sorry, I’m like really new to this whole thing. Just got started in it today. The odd thing is, take the script “Otis” for example. That didn’t exist on the norns prior to me getting it, I installed that this morning. Why it shows October of last year as the modified date I’m not sure.

Also, where do I enter that code?

Once again, apologies. I’m very new.

EDIT: You are correct, I bought it used.

Justmat · 2019-07-14T21:09:59.439Z

ecfike:

it shows October of last year

This bit is because norns only updates the time/date on connecting to the internet. It has no way of keeping time while powered off.

edit:

norns: ideas

norns doesn’t have an internal RTC, so it doesn’t keep its own time without being connected to a network. hotspot does not sync time. so if you need/want legit timestamps, you’ll need to connect to a router that is internet-connected. we’re currently working on the wifi UI and workability as the router connections has presented problems in some configurations.

kasselvania · 2019-07-14T21:13:36.943Z

I had just got a Norns working just before I left for 2 weeks for a trip. I’m back in 1 week and going to begin exploring it a bit more again. I can tell it’s a pretty deep hole and there isn’t so much of a ‘shallow end’ besides the studies and such. These should help a ton. But, as a fellow newby on this tool, when I’m home it would be fun to compare notes. It’s nice to have fellow learning buddies.

okyeron · 2019-07-14T21:23:45.280Z

ecfike:

Also, where do I enter that code?

This suggests to me you do not know how to SSH into norns. So you could do some research on that if you want to learn more. (search for “how to ssh to linux or raspberry pi” perhaps).

If you want a “start from scratch” solution, I’d suggest the following:

from cyberduck delete everything in the dust/code folder
then manually add Awake and We by downloading
https://github.com/tehn/awake/archive/master.zip and https://github.com/monome/we/archive/master.zip, unzipping those folders, remove “-master” from the folder names, then upload to the dust/code folder.
next to be sure you don’t have another duplicate engine hiding somewhere - in cyberduck, go to norns/sc/engines and delete anything here that is not in the following screengrab:
then once again go to the norns menu and do SYSTEM>RESET or fully reboot norns.
at which point you could start adding scripts once more

zebra · 2019-07-14T22:44:31.547Z

ecfike:

I haven’t seemed to be able to update to the latest version. I select update but nothing happens. Rather confusing.

ecfike:

I seem to be having difficulty connecting to Internet

@tehn perhaps can confirm, but AFAIK: using SYSTEM > UPDATE requires an internet connection. that would be good to fix first if possible. wired USB->ethernet adapter is an option.

ecfike:

I updated from the older version

whatever process you used there (i assume it was via thumb drive and the serial shell? please confirm this), you should be able to repeat the same steps with the 190422 update, even if you can’t get the norns online.

[edit]: woops; for the benefit of future readers, i was wrong about this. i forgot that pre-2.0, the SYSTEM > UPDATE command would attempt to search the filesystem for downloaded update files.

it is important to perform a clean update one way or another, as there are changes to the executables and not just the lua files. from shell, you should be able to see if update.sh completes.

once you have a current system, i would recommend simply deleting / moving everything in ~/dust/code and starting over with just the newest version of the scripts you want (from the Library section and the norns tag) note each script’s requirements, if any. you do not necessarily need to install we, but it should not hurt to do so as long as you get the latest version of everything.

ecfike · 2019-07-15T17:12:07.160Z

I have done this and everything seems to be working ok, I have the “we” scripts all in place. I’m going to start adding scripts I’m interested in and then I’ll look into trying to get it updated/connected to the internet.

tehn · 2019-07-15T17:12:21.435Z

we perhaps need to further clarify the update instructions here, please let me know what is unclear: https://monome.org/docs/norns/#update

this goes for help here in general. the docs attempt to be thorough and are the work of many people helping here. please help further by letting us know what needs elaboration. lots of help and debugging happens here that doesn’t make it back into the docs, so we need to identify repeat issues.

@ecfike if your network is giving you trouble (ie please let me know how it is not working) there are ways to attempt a manual connect by connecting via serial and running nmtui. also, wifi is not built-in, you have to use the included wifi dongle (i know this sounds like a patronizing suggestion, but it’s happened several times)

ecfike · 2019-07-15T17:15:38.512Z

zebra:

i assume it was via thumb drive and the serial shell? please confirm this

I put the file onto a hard drive and connected it to the norns. I have had a bit of difficulty understanding what serial shell is. Perhaps that is where the problem lies.

okyeron · 2019-07-15T17:23:06.742Z

The docs page seems a bit lacking for someone who has never used SSH or a serial connection. Perhaps linking to a guide there would be helpful?

I thought there was an SSH how-to somewhere here on lines, but my search-fu is failing me.

ecfike:

I have had a bit of difficulty understanding what serial shell is. Perhaps that is where the problem lies.

@ecfike Take a look at the top post in the Norns Tutorial post and look for the link for terminal window where it says “To install new projects(SSH)” that video can help explain how to start using the Terminal. Then you can use the commands the tutorial post mentions to connect to your norns via SSH.

The “serial shell” is using the terminal but connecting to norns via the USB-UART. This is a bit much to explain, but it gives you the same terminal command line access as using SSH, but using a hard-wire connection instead of wifi.

Here’s some youtube videos which might help?

ecfike · 2019-07-15T17:34:11.870Z

I followed the instructions here. It told me to install the previous update, which I did. However, I had already updated to that version successfully. I went through with it, however, and all seems to be well. Is it recommended that I repeat the same process, only replacing the .tgz with the most recent update?

tehn · 2019-07-15T17:48:31.955Z

if you’re on 190405 (as told in the fail thread) you can then simply use SYSTEM > UPDATE to automatically update (it is painless).

but, you need to get your network working. can you describe what is not working for your network?

ecfike · 2019-07-15T17:58:19.710Z

Alright. So I have my USB nub connected to the norns. I go to “Add”, select my network, enter the password, and select “Ok”. After a second or two, the display will go back to the previous screen. It says:

STATUS: unavailable
NETWORK:
IP:

Nothing happens after that.

tehn · 2019-07-15T19:03:23.484Z

try going to CONNECT and see if there are previous networks in there, try that.

is your network WPA or WEP? what’s the router itself? have you tried moving closer to it?

try using putty to serial login, then type nmtui for a graphical interface which may have better luck.

ecfike · 2019-07-15T19:13:52.934Z

Ok so, the issue has been identified.

Case-sensitivity.

When inputting the password into the norns, I failed to realize that there was an entire different alphabet off-screen for lowercase. It’s all good, I put in the password with the correct characters and the update ran all fine and dandy.

If I could make a recommendation, however, perhaps there could be a notice in the manual alerting people to make sure they take note of the case-sensitivity of their password and the alternate keyboard? Or maybe make a character at the beginning of the alphabet to toggle between uppercase and lowercase, to make things more intuitive? Idk, it was probably dumb of me to not think of this sooner, but I feel like it could be helpful to at least point that out somewhere. Thank you!

bereenondo · 2019-07-16T12:44:05.463Z

I got my Norns last week, and had the same problem with FM7. Norns works fine after removing the script, but does this mean that FM7 doesn’t work anymore?

Justmat · 2019-07-16T13:38:41.317Z

FM7 still works. Just make sure that you have the current version, and that dust/code/we/lib doesn’t contain an Engine_FM7 file. The problem is that the FM7 lib used to live in we, now it lives in the project folder. It can’t be in both places, or norns will complain.