As an add on to this - is it possible that norns keeps a cache of softcut scripts so that changes to them don’t immediately take effect, but require a reset?

trying to move the update file to norns via serial tty since my wifi broke

will report back back if it works

Never ma’aged to get wifi working so curious how that works out

I have updated to 2.0 beta (190320) on Raspberry Pi 3B+.

The update broke my installation, I suspect it was something to do with the Kernel update. I rebuilt from scratch (and commenting out the kernel when updating) using the BlokasLabs Patchbox image.

Everything seems to be performing really well. On 1.0 I had a lot of clicks and pops whilst recording to tape but I just put it through it’s paces with EarthSea and it didn’t show any signs of slowing.

Thanks for all your hard work @tehn

1 Like

i’m using the cp command to copy from my mac to norns…

source makes sense

currently trying to find the correct folder extension for the destination

then it should be easy to follow steps provided above

I’ve just tried to use an external usb drive. Might be useful for your situation without ssh/wifi.

  1. copy norns190320.tgz to usb thumb drive on computer (drag & drop)
  2. insert usb drive into norns and ‘screen’ into norns.
  3. cp /media/usb/norns190320.tgz ~/update
    (the usb dir in media might be different)
  4. run the update instructions in OP (step 9 Norns 2.0 beta)
3 Likes

yeah that would be easiest method

but i dont have a thumb drive handy & am willing to try teaching myself this since it hasnt been posted yet


gave up for now
will tackle again tonight at some point but i thought this should work:
cp ~/downloads/norns190320.tgz /home/we/update

i thought it should work but the path is wrong

1 Like

cp can only copy files between locations on the same computer. Your ~/downloads/ path is on a mac and your /home/we/ path is on a norns. cp in this case only knows about ~/downloads/ and has no way of seeing /home/we.

You’ll need to use a thumb drive or a network connection+SFTP.

But if you are super determined, you could try this (I do not recommend it, just sharing for completeness):

lrzsz, kermit, etc are other ideas for file transfer over serial. you’re back in ‘modem’ land now…

2 Likes

I just wanted to say that, as a simple user, I have found no faults yet in the latest beta, and I really want to thank all the developers for this awesome work. :raised_hands:

5 Likes

shouldn’t something like scp work?

2 Likes

Scp works over ssh. The serial port is a whole new area of fun and @jasonw22 is right. Once you are on the serial port you are in modem territory. Life is too short for that ;-). Order a usb stick from Amazon & do it tomorrow would be my advice…

(Random idea. ‘Binhex’ it into ascii and paste it into the terminal ‘cat’ing it into a file. Might work if it’s not too big. Trying to remember all the tricks from back in the day but like I say: i’ve Forgotten them for a reason)

4 Likes

That’s more or less what the stackexchange answer suggests. It’s not a good idea, but it’s amusing to ponder!

Which requires an ethernet network. (Won’t work over serial)

1 Like

in lua, require caches its argument, dofile doesn’t.

IOW, require 'foo' always does nothing if foo was already loaded using require. this is ususally desired behavior except during development when you’re changing module code.

a workaround during development is to clear the entry for foo in the cache:

package.loaded.foo = nil

if you want to always run foo.lua then use dofile('/path/to/foo.lua') (notice the full filename). rule of thumb: this is fine for “local” libraries (in your script’s directory) and require is probably better for core modules (from ~/norns/lua or equivalent - you shouldn’t be explicitly specifying paths for those since they may move around, and you shouldn’t be needing to edit them as a matter of course.)

in the specific case of softcut “child scripts” like halfsecond, i personally would advocate making “local” copies of those, customizing them for your needs, and running them with dofile from your “main script.”

2 Likes

I made a little script to nuke my cached requires for my own libraries while I’m in active development. It might be useful for people running into this: https://github.com/nathankoch/NornsMachines/blob/new_os/lib/reload_libraries.lua

well you aren’t going to like my idea of plugging a microphone into the Norns and transmitting it over the speakers by Morse Code (this is kind of how an acoustic coupler works - which is another way people moved data around across crappy low bandwidth connections back in the day)

:wink:

Yeah - wasn’t suggested it seriously - file will be too big. It does work on smaller files. I’ve also ended up typing data in again back in the day

The answer definitely is one of: spend the time fixing the wifi or getting a usb stick

2 Likes

Just updated to the latest beta and upon reboot I can’t get wifi to connect or a hotspot to start up. Any info I can supply that would be helpful?

Yeah, that would be helpful :slight_smile:
Can you post the output (to some paste service like https://bpaste.net or whichever one you prefer) of the following commands after (re)starting norns (A clean boot is important, otherwise there’s too much noise):

lsmod
rfkill list
nmcli radio
nmcli device
journalctl | grep 8192
journalctl | grep kill

Are you using system > wifi to connect or something else?

Yes, system > wifi

Thanks @zebra for the explanation. Oh and, trial and error, I think it’s

package.loaded.foo = nil

not packages

1 Like

my bad, edited above