#2039

normal shutdown…yes the counter is not advancing properly sometimes…

#2040

are you seeing this mid-session or on fresh startup? i’ll do some further testing here, but just now on mine it seems to be properly working. i’ll add deliberate file naming thing which should avoid this altogether.

#2041

I regularly boot Norns with hot input. Have experienced the monitor-route distortion only once in thousands of power cycles. It seems like this is not particularly correlated and is hard for me to imagine a causal mechanism that would make it so. (but, I will double check things like the averaging history for VU meters. [update: haha, there is no history between audio blocks. should fix that.])

I strongly suspect that the problem is happening somehow at the jack layer for the system capture -> crone connection. (Suspicion based on observing the various reports: no distortion on synthesis paths, no distortion when capturing to other client, etc)

1 Like
#2042

I appreciate the reply/input. I figured I’d at least report that I may have found a possible correlation to an incoming input with norns as its been the only time I’ve seen it happen on multiple occasions but as you said it still could be something else!

#2043

It was mid session, I noticed though the mixer outs were frozen, possibly because of a very loud signal that went through the inputs. I was using mangl that had loaded track 18. the tape rec overwrote track 18 with the new recording…

#2044

by outputs frozen do you mean entire menu system? or just the VU’s?

#2045

just VU…

1 Like
#2046

doubtful in the extreme. there could be actual DC garbage going through if you are playing back a corrupted sound file.

#2047

just had a crash, I mean norns froze, while I was playing with cranes, had to use the white btn. It seems to happen sporadically when input is involved…

#2048

how are you powering your norns? i also don’t think the input signal is a problem, but i’m interested just as a data point

#2049

Usb multi-plug, why?

#2050

191028 seems to have brought (back) wifi stability issues for me.

I was having issues with this back when norns was first released, then it become rock solid a few releases ago. Seems to be back to spottiness. WIFI page on norns shows connected. Signal around -60dBm

I am currently experience the issue (maiden will not load), and I have ssh’d in and done ping google.com. It seems to be resulting in wildly different values.

64 bytes from iad23s61-in-f14.1e100.net (172.217.13.238): icmp_seq=338 ttl=54 time=1579 ms
64 bytes from iad23s61-in-f14.1e100.net (172.217.13.238): icmp_seq=339 ttl=54 time=503 ms
64 bytes from iad23s61-in-f14.1e100.net (172.217.13.238): icmp_seq=340 ttl=54 time=752 ms
64 bytes from iad23s61-in-f14.1e100.net (172.217.13.238): icmp_seq=341 ttl=54 time=956 ms
64 bytes from iad23s61-in-f14.1e100.net (172.217.13.238): icmp_seq=342 ttl=54 time=2047 ms
64 bytes from iad23s61-in-f14.1e100.net (172.217.13.238): icmp_seq=344 ttl=54 time=4939 ms
64 bytes from iad23s61-in-f14.1e100.net (172.217.13.238): icmp_seq=345 ttl=54 time=3939 ms
64 bytes from iad23s61-in-f14.1e100.net (172.217.13.238): icmp_seq=346 ttl=54 time=5048 ms
64 bytes from iad23s61-in-f14.1e100.net (172.217.13.238): icmp_seq=347 ttl=54 time=4009 ms
64 bytes from iad23s61-in-f14.1e100.net (172.217.13.238): icmp_seq=348 ttl=54 time=2970 ms
64 bytes from iad23s61-in-f14.1e100.net (172.217.13.238): icmp_seq=349 ttl=54 time=1971 ms
64 bytes from iad23s61-in-f14.1e100.net (172.217.13.238): icmp_seq=350 ttl=54 time=1929 ms
64 bytes from iad23s61-in-f14.1e100.net (172.217.13.238): icmp_seq=351 ttl=54 time=2361 ms
64 bytes from iad23s61-in-f14.1e100.net (172.217.13.238): icmp_seq=352 ttl=54 time=1380 ms
64 bytes from iad23s61-in-f14.1e100.net (172.217.13.238): icmp_seq=353 ttl=54 time=339 ms
64 bytes from iad23s61-in-f14.1e100.net (172.217.13.238): icmp_seq=355 ttl=54 time=36.8 ms
64 bytes from iad23s61-in-f14.1e100.net (172.217.13.238): icmp_seq=356 ttl=54 time=101 ms
64 bytes from iad23s61-in-f14.1e100.net (172.217.13.238): icmp_seq=357 ttl=54 time=28.2 ms
64 bytes from iad23s61-in-f14.1e100.net (172.217.13.238): icmp_seq=358 ttl=54 time=42.0 ms
64 bytes from iad23s61-in-f14.1e100.net (172.217.13.238): icmp_seq=359 ttl=54 time=562 ms
64 bytes from iad23s61-in-f14.1e100.net (172.217.13.238): icmp_seq=360 ttl=54 time=709 ms
64 bytes from iad23s61-in-f14.1e100.net (172.217.13.238): icmp_seq=363 ttl=54 time=25.4 ms
64 bytes from iad23s61-in-f14.1e100.net (172.217.13.238): icmp_seq=365 ttl=54 time=24.9 ms
64 bytes from iad23s61-in-f14.1e100.net (172.217.13.238): icmp_seq=367 ttl=54 time=23.7 ms
64 bytes from iad23s61-in-f14.1e100.net (172.217.13.238): icmp_seq=368 ttl=54 time=564 ms
64 bytes from iad23s61-in-f14.1e100.net (172.217.13.238): icmp_seq=369 ttl=54 time=46.7 ms
64 bytes from iad23s61-in-f14.1e100.net (172.217.13.238): icmp_seq=370 ttl=54 time=41.9 ms
64 bytes from iad23s61-in-f14.1e100.net (172.217.13.238): icmp_seq=371 ttl=54 time=33.8 ms
64 bytes from iad23s61-in-f14.1e100.net (172.217.13.238): icmp_seq=373 ttl=54 time=21.4 ms
64 bytes from iad23s61-in-f14.1e100.net (172.217.13.238): icmp_seq=374 ttl=54 time=28.7 ms
64 bytes from iad23s61-in-f14.1e100.net (172.217.13.238): icmp_seq=375 ttl=54 time=25.7 ms

--- google.com ping statistics ---
615 packets transmitted, 560 received, +3 errors, 8% packet loss, time 631126ms
rtt min/avg/max/mdev = 19.438/713.480/16022.404/2027.266 ms, pipe 14

It seems like processes are stable in their mem/cpu values (and don’t seem crazy high):

192.168.1.16 ~ $ ps aux --sort=-%mem | awk 'NR<=10{print $0}'
USER       PID %CPU %MEM    VSZ   RSS TTY      STAT START   TIME COMMAND
we         350 11.1 23.5 263680 236312 ?       SLsl 08:25   1:14 /home/we/norns/build/crone/crone
we         418  8.0 10.2 168344 102448 ?       SLl  08:25   0:53 scsynth -u 57110 -a 1024 -i 2 -o 2 -b 1026 -R 0 -C 0 -l 1
we         317  3.5  9.1  98664 91364 ?        SLsl 08:25   0:24 /usr/bin/jackd -R -P 95 -d alsa -d hw:0 -r 48000 -n 3 -p 128 -S -s
we         351  1.1  3.5 105640 35412 ?        Sl   08:25   0:07 /usr/bin/sclang -i maiden
we         335  1.7  3.0 180100 31084 ?        Sl   08:25   0:11 /home/we/norns/build/matron/matron
root       327  0.2  1.4 101696 14376 ?        Ssl  08:25   0:01 /usr/sbin/NetworkManager --no-daemon
we         314  0.0  1.1 809588 11328 ?        Ssl  08:25   0:00 /home/we/maiden/maiden server --fd 3 --app ./app/build --data /home/we/dust --doc /home/we/norns/doc
root       403  0.0  0.5   9672  5972 ?        Ss   08:25   0:00 /sbin/wpa_supplicant -u -s -O /run/wpa_supplicant
root         1  0.1  0.5  27920  5856 ?        Ss   08:25   0:01 /sbin/init

Anything else y’all can think of to try to figure out what is causing the issues?

#2051

fwiw, i think -60dbm is pretty weak, no?

are you able to compare with a usb-ethernet connection, different network, different adapter, hotspot, &c?

(haven’t experienced anything like this with the 2 units i have. even with relatively weak connection - by which i mean minus-fifty-ish.)

#2052

I am away from my device at the moment so I can’t really investigate right now. I personally haven’t seen any difference with the recent update but I generally use wifi less than 25% of the time (usually I have a wired connection). I don’t believe there have been any changes to the networking setup or the kernel since the 2.0 overhaul.

Out of curiosity is this norns running a more or less stock norns image or have additional packages been installed? Any use of apt-get update or apt-get upgrade?

1 Like
#2053

Appreciate y’all giving me some other ideas.

The only one of these I can try based on what I have access to at the current moment is hotspot…maiden does seem to load in a normal amount of time when I am connected.

Completely stock. Only thing it has on it are packages that were installed through maiden.

The other issue I’ve had is the wifi screen on norns feels buggy. For example, after trying to switch from hotspot back to my network just now, norns now is hung “activating” the network (doesn’t respond to any sort of button pressed or encoder turns. I’ve had other weird things happen on this screen. like clicking off doesn’t do anything.

#2054

Hmmm maybe it is a signal issue…moved right next to the router, getting signal in the -30’s.

--- google.com ping statistics ---
120 packets transmitted, 119 received, 0% packet loss, time 119201ms
rtt min/avg/max/mdev = 18.897/32.205/218.668/26.100 ms

Let’s see if this thing helps, will report back in a couple days… https://thewirecutter.com/reviews/best-wi-fi-extender/

maiden seems to work good. Weird though, as I was not having spottiness before the last update when it was in the same spot.

#2055

i’ve found my wifi extender to somehow have varying effectiveness on different days. sometimes norns has a strong signal, others not quite enough.

i’ll try to get together a list of stronger wifi dongles. the tiny nub is really the lowest strength.

1 Like
#2056

This one has worked for me. Far better signal strength and range, and it “just works” with norns :slight_smile:

4 Likes
#2057

Thanks! Switched my order from the extender to the antenna, thanks @Justmat

1 Like
#2058

plus, it just looks frickin cool :sunglasses:

1 Like