Have you ruled out signal strength by getting close to your wireless router? When I’ve seen this it was in places where my phone and computer connected fine, but I needed to move closer w/norns to get it to connect.

Yes, thank you for pointing that out. I’ve tried right next to the router, no luck.

The network name will appear briefly, then disappear. Status doesn’t change (from activating), and no register IP or Signal strength.

A couple times, Norns has locked up with no ability to control, requiring long wait times until I can put to sleep and wake up.

UPDATE: wifi working now! Perhaps it was @license tip to reboot router, although that didn’t work immediately. 24 hrs later, with my new wifi nub, wifi connected and update ran seamlessly. Old wifi nub couldn’t complete the update. Thanks for all of your help!

1 Like

Rats. I haven’t seen similar behavior. I’m sure someone else will chime in.

1 Like

I’m seeing similar problems with my 190801 “Fates” Norns, checked into logs and didn’t see much that was helpful other than wifi isn’t working, I noticed there is no /etc/wpa_supplicant/wpa_supplicant.conf available but there is a /etc/wpa_supplicant/wpa_supplicant_bak.conf with some useless info in there… I dunno will keep looking into it… I can get a hotspot going every two in five boots maybe…

Have you tried rebooting your router? I saw the exact same thing last weekend and that sorted it for me.

1 Like

I fixed it!

Turns out, I had to:

sudo vi /etc/NetworkManager/system-connections/my wifi network.nmconnection and fix the psk (password) under [wifi-security] … the password was ALL CAPITALS, and my password is lowercase on my router… I rebooted and it’s working now, BUT I had to fire up a hotspot FIRST then it will allow me to connect to the saved connection, otherwise it doesn’t show up in the list of options under “add”…

Update: now upon booting up, wifi connects automatically just fine, i was able to run “update” and upgrade to 190930 just fine with no problems so far :partying_face:

4 Likes

We (obviously :wink: ) don’t change the password anywhere when we pass it to the wifi config tools, see https://github.com/monome/norns/blob/55b52551fd51ac9e714b9de8810e699cf4f20934/lua/core/wifi.lua#L265
I’m assuming this is pebkac, you might’ve had caps-lock on or something like that?

P.S. nmtui for a tui or nmcli for a command-line interface is probably easier/a better approach than editing NetworkManager files, since NetworkManager likes to keep it’s own state and overwrite stuff in the files it uses.

If you’re buying a different wifi USB stick buy a better one with a better/properly supported chipset (see https://llllllll.co/search?q=chipset%20topic%3A14016 for some posts about this in this topic).

1 Like

An ID10-T error huh? :nerd_face:

Is there a method in Norns to change the case? I didn’t realize, it looked like the only option was uppercase, at least that was the default.

Edit: well that’s embarrassing

2 Likes

Keep scrolling for lowercase

2 Likes

20 characters of :hugs:

1 Like

I think I ran into this same problem this afternoon, listening back to a TAPE file, and for me it wasn’t exactly clipping – it sounded like clipping, but somehow extra awful. Lo and behold, when I zoomed in on the waveform:

Apparently samples outside [-1.0, 1.0] were not clamped, but wrapped around.

I don’t think I heard these artifacts while recording, but I can’t say for sure. I was running a modified version of ash/earthsea with audio input feeding two softcut voices.

I won’t rule out my less-than-ideal “headless” setup (Raspberry Pi 3b+ with no special hardware, just a Behringer UMC-404 as audio interface) as the cause of my problem, but it sounded awfully familiar.

Obviously I too need to watch my levels. Someday I’ll have a screen, which will help with that…!

that makes me suspect that signal is out of range hitting tape, and getting wrapped during the conversion to 24b fixed.

i’ll try and reproduce. hard/soft clipper before tape write is probably called for.

[update] yep, this fixes it for me.

(i mean… you still don’t wanna be clipping.)

7 Likes

Sorry if this has been asked but my searches didn’t find an answer. How is norns at taking hot euro signals at the input?

Have a norns in the mail and am planning my rack which at this point would just be a mangrove, sisters, just friends, cold Mac and crow. Would rather not attenuate on the way in if I can just adjust in norns adequately. Thanks!

i would not suggest this— it’s the same as putting up to 10V into any normal soundcard. norns does not have any particular accommodation to temper these big signals, and it could even cause damage.

i use a RIP in between modular and norns, but there are smaller options of course.

4MS Listen IO works really well for this, and even sending norns into your modular.

1 Like

I recently was browsing through the norns library and found the intonation.lua file (https://github.com/monome/norns/blob/master/lua/lib/intonation.lua). If I wanted to add these scales to say Earthsea, how would I go about doing so? I have looked through the studies and tried a couple of things on maiden but couldn’t get anything to work.

earthsea already includes a JI tuning function:

… which is not used by default. to use it, replace getHzET() with getHz().

to use a table from JI module instead, something like

local ji = require 'intonation'
local ratios = ji.zarlino()

… being aware than many of these scales have >12 degrees.

1 Like

Thank you so much @zebra! Trying this out tonight.

1 Like

Oh, hm. My advice was incomplete. The JI and ET functions take different arguments. You would have to decompose the note number into degree and octave for the JI variant. This requires storing and using the number of scale degrees.

Maybe I will PR this, with tuning as an option parameter. I basically always use JI for this kind of thing.

1 Like

That would be really great- having tuning as an option parameter sounds really nice.

Thanks for the clarification!