#1477

Hey all, having the same problem as @kcikdrumk updating to 2.1 from a previous 1.xx release.

My Norns updated successfully (kinda), but now it’s only loading with an error message that reads, “NONE (error: AUDIO ENGINE)” on the main menu. When I attempt to select any script, it freezes on the “loading…” screen and I have to back out. Wifi and network connections are unavailable. I tried several resets and lit some candles and recited some incantations that I found on another forum. No dice.

As you can probably see, I’m not so good with this troubleshooting stuff. Anyone have any ideas? Please let me know if I should be posting this in the help thread instead.

I’m still not able to connect to Maiden because Norns has connection issues. On the wifi page it says, STATUS: unavailable
NETWORK:
IP:

Both Network and IP are empty, and the Hotspot and Connect buttons below do nothing when I choose them.

Hotspot causes the Norns to freeze and wifi mode is not showing any networks. I’ve tried updating from a flash drive, but using the update method also doesn’t seem to work. The one thing I haven’t tried is a USB A-A cable, but I’d prefer to avoid that if possible. Does anyone have any insights (other than The Candle Method mentioned in the other thread)?

I’ve tried hard reset (5-6 times) and sleep. I’ve used the hotspot with my computer to test the dongle and it seems to be working on that.

#1478

@kcikdrumk
@Jonathan_Riley

(frstly, caveat: both the update scripts and the wifi config are a bit outside my wheelhouse. so i’m sorry i don’t have any actual specific ideas, having never actually performed 1.x - 2.x update except by manual means.)

it’s worth using screen 115200 to connect via serial port, checking network with nmtui, ifconfig &c, and checking for duplicate SC engines (in dust) with following bash command:

find ~/dust/code -type f -printf '%p/ %f\n' | sort -k2 | uniq -f1 --all-repeated=separate | grep *.sc

or, simpler, just try killing and launching sclang from command prompt, which will show you if there are duplicate classes at any location. (maybe update did not clear out old norns .sc files in ~.local/share/SuperCollider/...)

also:

don’t use the hard reset unless you are actually experiencing a crash and cannot shut down by any other method - including serial login and the shutdown linux command.

every hard reset has a chance of corrupting the filesystem and it will not fix anything. in fact probably worth using fsck to check the health of the filesystem if you’ve used the Rude Button.

(@tehn it seems like a good idea to have some prominent link to full disk image to be reflashed in case of just such a corruption [and only then - bandwidth isn’t free.])

#1479

I can confirm this. Personally I found date stamp naming fine :neutral_face:

#1480

Thanks @zebra , I’ll try this out later today and see what I can come up with. Appreciate the support.

I was using the hard reset because the system was locking up when enabling hotspot mode. Sorry, I should have clarified. I let it sit for 30 minutes or so the first time before I resorted to that. Thanks for the correction, though! Will be more mindful in the future.

Ahh, disregard. I had my ports mixed up :sweat_smile:

#1481

Thank you!
I actually tried a reboot inbetween trying all of the different ports - none worked…
Not sure which port I should change to in the script, or what to type either.

If anyone could figure our how to get MIDI clock in to Orca (Norns version), please let me know!

#1482

Ok so here’s what you would need to do…

Step 1 - look at the norns system menu and find which device your midi dongle is using. This is at SYSTEM>DEVICES>MIDI and this lists your devices by number. That number is what you need to use in scripts for that device

Step 2 - edit the script. with Awake for example you would look for midi.connect and make that change:

local clk_midi = midi.connect(1) changes to local clk_midi = midi.connect(3)

Now… midi clock to Orca for norns might not work at all. I’m not sure if that midi-in is enabled at all. You might bring that up in the Orca thread. Or you could try changing the line with orca.midi_out_device = midi.connect(1) to whatever your device number is.

#1483

I have to do a hard reset at least once per session. I’m not a sys admin, therefore I poke it in the eye when it won’t behave. Can someone provide some details for serial login and Linux shutdown commands? Or point me to it? Appreciated!

1 Like
#1484

Oh no! Called out be the ZEEB. :scream:
Luckily I don’t need to hard reset much anymore.

#1485

if you ssh into the Norns from a terminal on your computer

$ ssh we@[device IP]

with the default password “sleep”

you should be able to shut it down with

$ sudo shutdown now
1 Like
#1486

in the context of this discussion, networking might not be functional, ssh isn’t an option; use the serial port:

(from the docs)

Without WIFI, you can connect to norns via USB-UART by connecting the power cable to your computer. On Mac/linux do:

screen /dev/tty.usb(tab) 115200

where (tab) means: use the shell’s autocompletion to give you the right device path to norns; it will be the only one starting with /dev/tty.usb (or maybe /dev/ttyUSB) unless you have other usb-serial things attached.

on windows, use PuTty and a COM port; same baud setting

that’s definitely not good and indicates some root issue that should be addressed instead of subjecting the flash storage to constant abuse.

2 Likes
#1487

ah this is good to know!

#1488

posting this here as well as the meadowphysics thread incase people here know of a solution. Meadowphysics used to run fine, but now I get the following error:

pset >> read: /home/we/dust/data/meadowphysics/mp_midi/mp_midi.pset

### SCRIPT ERROR: init

/home/we/dust/code/meadowphysics/mp_midi.lua:52: bad argument #1 to 'pairs' (table expected, got nil)

stack traceback:

/home/we/norns/lua/core/norns.lua:185: in function </home/we/norns/lua/core/norns.lua:185>

[C]: in function 'pairs'

/home/we/dust/code/meadowphysics/mp_midi.lua:52: in field 'action'

/home/we/norns/lua/core/params/option.lua:48: in function 'core/params/option.bang'

/home/we/norns/lua/core/params/option.lua:35: in function 'core/params/option.set'

/home/we/norns/lua/core/paramset.lua:246: in function 'core/paramset.read'

/home/we/norns/lua/core/paramset.lua:264: in function 'core/paramset.default'

/home/we/dust/code/meadowphysics/mp_midi.lua:211: in global 'init'

/home/we/norns/lua/core/script.lua:71: in function 'core/script.init'

[C]: in function 'xpcall'

/home/we/norns/lua/core/norns.lua:186: in field 'try'

/home/we/norns/lua/core/engine.lua:83: in function </home/we/norns/lua/core/engine.lua:82>

>> reading PMAP /home/we/dust/data/meadowphysics/mp_midi/mp_midi.pmap
#1489

This is weird error because I can clearly see that table defined in the script, and it would be broken for everybody if it wasn’t… I would just try removing and re-adding meadowphyics if you haven’t already.

#1490

Interested to hear how others have been getting on with the compressor, I was playing with it today but not really getting expected results.
Specifically, I couldn’t hear any change when attack is adjusted, am I missing something?
Also curious as to why there are both pre-gain and threshold params?

1 Like
#1491

Tried that already unfortunately…also removed any of the new scripts I installed since it stopped working…I have ZERO programming skills/knowledge, so I am at the mercy of all you savvy people on the forum :grimacing:

#1492

Do you host the image? Is it not on GitHub?

I’m happy to stick it on a seedbox and let people use a torrent to get at it if that helps?

#1493

I have also been curious about ppl using it. I haven’t found a case where I preferred it on. I also wish for clarity on some of the controls in the audio menu. If there is a reason it makes sense to have both of the controls you’re asking about, for example, I’d like to hear about the intended use cases :slight_smile:

#1494

What would you like to know more vs what’s already in the docs at the moment?

#1495

hey, there’s a bug! lua/crone time units don’t agree. fortunately a trivial fix. seems to work for me.
[ https://github.com/monome/norns/pull/837 ]

Also curious as to why there are both pre-gain and threshold params?

just different options / workflows. for example, set threshold / ratio / postgain to produce the desired nominal output level / amount of compression given 0dbFS input. then, adjust pregain to make it work for the actual material present. there’s no other control that changes the level of the insert fx bus before compression is applied.

i think the comp sounds pretty dang good on drums. it’s a simple approximation of an optical gain curve, (knee smoothing is implemented by an additional lowpass step after gain, in log domain, with smoothing time tied to attack time; poor man’s 1176 but sounds decent to me. thanks, faust stdlib.)

i would have expected more controversy over putting comp after reverb :slight_smile:

3 Likes
#1496

Cool thanks for the quick fix and tips, going to spend some more time playing with it tomorrow! :smiley: