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

Just updated to the 190320 build. Everything seems to be OK except I’m getting very low levels on audio outs 1 & 2 and nothing on the HP jack. Awake works but I’ve got to crank the audio to 0db and max throw on my mixer to get any sort of decent level which then comes with a decent amount of channel noise. I’m not getting any audio out of Angl with my arc.

Suggestions?

Did you check all your levels on the LEVELS page?

(from script select page, turn ENC 1 left to go to TAPE and LEVELS)

EDIT - the 4 “pages” are
LEVELS - TAPE - HOME - PARAMS

Yup. Levels are maxed out.

After some troubleshooting with @simonvanderveldt I plugged the WiFi nub into a different USB port and the WiFi started working again. It now works in all ports. Strange, but I’m glad it works.

2 Likes

I’m not on device nor behind a laptop, so this is a wild guess/random suggestion, but could you try the following via SSH or serial console and paste the output here?

amixer
1 Like

alternately you can look at all the audio settings from ssh/serial with alsamixer and see if any of the channels are muted, etc.

running amixer by itself will also print a verbose list of your audio settings and levels.

I’m on RasPi so unfortunately I can’t tell you precisely what that will look like on norns.

1 Like

to confirm - is “EXT” turned up? I just noticed this changes the overall volume in awake for me.

1 Like

currently exploring the 2.0 beta and noticed that norns doesn’t seem to recognize my original push-button arc 4. at one point when hot-plugging into another port the system froze requiring a reset, but otherwise there is no response on the arc and no entries in matron or the devices menu.

is it possible to add support for the original arc?

i’ve been browsing around norns’ arc-related files on GitHub but i’m not sure how to approach things…

I figured out the serial terminal problem I had. I was using two Mac minis with high Sierra on them at a hackerspace. The OS was installed from the same image, which somehow had some weird driver issue. This alert came up but I initially ignored it because the device file was present. When I tried on my own laptop, also running high Sierra but from the retail Apple store I did not see this alert. All characters were sent to the tty as expected. Wacky.

2 Likes

I’m curious about this. Can you start with a fresh reboot and get maiden loaded to see it’s output - then plug in your Arc and see if it prints anything?

you should see some output like this:
arc added: 1 monome arc m2289491

Sounds like there might be something weird happening on disconnect, but hard to debug that remotely

If you wanna PM me I can try to walk you through some debugging steps.