#437

As @tehn mentioned we made some changes to the wifi: we switched drivers for the wifi nub included with norns. For all of the dev team this was an improvement.
If you can, please use the wifi and let us know how it’s working for you.

Thanks!

[edit] Almost forgot: Wifi should now stay in the same state when shutting down and starting norns again. In other words if it’s on when shutting down it’ll be on when you start norns again.

3 Likes
#438

Occam’s razor says you didn’t download the .tgz in the update directory. I could be wrong though. I’d say redownload and everything should be ok.

#439

still very confused as I have tried directly dragging and dropping the .tgz file into the terminal prompt to ensure the directory would be correct and it still is giving me the same error.

11%20AM
Screen Shot 2019-03-21 at 4.57.11 AM.jpg1558×1014 409 KB

#440

Move it with cyberduck using the SFTP protocol.

1 Like
#441

into the update folder? Also thank you for the help

44%20AM
Screen Shot 2019-03-21 at 5.04.44 AM.png1392×1038 247 KB

2 Likes
#442

Wow, wifi looks very stable, in fact it’s been connected for some three hours with no hiccups. Chapeau!

2 Likes
#443

Awesome, that’s great to hear!

1 Like
#444

hmm - finally got around to updating so have just gone from 1.x to 2.0 latest beta

MLR works - but awake just sticks on the ‘loading…’ screen.

Tried loading in Maiden as well - can’t see anything obvious, likewise we/demo/ui works - we/demo/scales does not

output from maiden while loading awake

norns.script.load("code/awake/awake.lua")
# script load: /home/we/dust/code/awake/awake.lua
# cleanup
# script clear
pset >> write: /home/we/dust/data/system.pset
# script run
loading engine: PolyPerc
<ok>
#445

it seems like supercollider isn’t running or is hung.

try SYSTEM > RESET

if this doesn’t work, get a terminal.

cd ~/norns
./stop.sh
sclang

this will show you is supercollider is working. it may be crashing if there are duplicate classes (which wouldn’t make a whole lot of since given the updater copies new versions over everything)

#446

yes - that sorted it!

cheers

1 Like
#447

Did you have class collisions? If so, which classes/files caused this?

#448

just needed the reset - I’d rebooted after install but for some reason it needed the reset too

1 Like
#449

this could just be placebo effect, but messing around with playfair and the 909 kit again last night and it sounded so massive. I obviously can’t compare at this point but it’s hard not to think the sound quality has gotten even better. thanks for all the hard work!

3 Likes
#450

./update.sh with 190320 led to a couple lines at the end that I just wanted to share. I doubt it’s anything broken:

rm: cannot remove '/home/we/*.wifi': No such file or directory
rm: cannot remove '/home/we/*.conf': No such file or directory
1 Like
#451

Not to ditto, but I also noticed a nice quality improvement in the overall sound. Well done!

1 Like
#452

You can safely ignore those errors. They come from the setup.sh script which is trying to clean up any files left over from the norns 1.0 wifi setup.

2 Likes
#453

that’s what I figured :+1: thanks the one thing that seem kind of strange is that they were looking in the we dir (making me think their might have been a typo) which is why I wanted to pop it in here

#454 
instance methods use colon instead of dot, ie g.led(...) -> g:led(...)
grid callback function renamed g.event -> g.key

bloody hell - BRB writing scripts to rewrite Kria!!!

2 Likes
#455

MIDI commands also, if kris uses it.

#456

it’s more that basically in the ~2000 lines of code that make up Kria - an awful lot of it writes to the grid

2 Likes