#417

That’s a bug. Reported and fixed/changed.
As I understand it, there’s going to be some folder re-re-organization in the next beta release.

1 Like
#418

Yes, you can always flash a full image, including the v1 images. Note that doing so will wipe the whole device so make sure to copy/backup the data you want to keep.

Can you elaborate on the issues you’re having? Any kind of feedback is always useful.

#419

(btw I’ve just discovered that you can hotplug the wifi nub in 2.0, I don’t think I could do it in 1.0, can anyone confirm this?)

#420

try pulling the newest norns repo, this was a quick fix.

new update wednesday night. thanks for your patience everyone, and for the bug reports. they’re very helpful.

3 Likes
#421

Yes. Hot plugging the WIFI nub should be more robust in 2.0. The next beta release will have further improvements thanks to work done by @simonvanderveldt

1 Like
#422

Yes. Tested failure state with a non-included cable and reproduced the results.

@tehn the screen on the left is monitoring the tty on device. The screen on the right is the macos computer connecting via the included USB cable.

IMG_20190319_221512
IMG_20190319_221512.jpg4032×3024 5.13 MB

#423

I was able to reinstall via Serial and am back in business with Maiden running again. :grin:
seems like there was some problem with the wifi during the install as others have experienced. Thanks for the help!

#424

Some random ideas to try:

  • move any ~/.screenrc file out of the way and try again
  • try cu instead of screen (sudo cu -s 115200 -l /dev/tty.usbserial-A...)
  • check LANGUAGE, LANG, and/or LC_* environment variables and confirm that if set they are set to something you’d expect (in my case LANG=en_US.UTF-8)
#425

To clarify, there are still a bunch of pathing/file structure issues right?

i’ve tried to pull in a few different community scripts (marks_eats) which all give me similar errors below when loading playfair. Each is looking for a norns/ folder within we/. Re reading through this thread has a lot of mirky info at different points in the 2.0 lifecycle, so it’s a little tough to see the bigger picture. (not a judgment, just an observation!)

It seems easy enough to look to where the require is pointing and start shuffling things around, but after re-updating with the 14 update, I’m wondering if I shouldn’t hang tight?

# cleanup
# script clear
### SCRIPT ERROR: load fail
/home/we/dust/we/playfair.lua:20: module 'ack' not found:
	no field package.preload['ack']
	no file '/home/we/norns/lua/ack.lua'
	no file '/home/we/norns/lua/core/ack.lua'
	no file '/home/we/norns/lua/core/params/ack.lua'
	no file '/home/we/norns/lua/lib/ack.lua'
	no file '/home/we/norns/lua/softcut/ack.lua'
	no file '/home/we/dust//usr/local/share/lua/5.3/ack.lua'
	no file '/usr/local/share/lua/5.3/ack/init.lua'
	no file '/usr/local/lib/lua/5.3/ack.lua'
	no file '/usr/local/lib/lua/5.3/ack/init.lua'
	no file '/usr/share/lua/5.3/ack.lua'
	no file '/usr/share/lua/5.3/ack/init.lua'
	no file './ack.lua'
	no file './ack/init.lua'
	no file '/usr/local/lib/lua/5.3/ack.so'
	no file '/usr/lib/arm-linux-gnueabihf/lua/5.3/ack.so'
	no file '/usr/lib/lua/5.3/ack.so'
	no file '/usr/local/lib/lua/5.3/loadall.so'
	no file './ack.so'
stack traceback:
	/home/we/norns/lua/core/norns.lua:185: in function </home/we/norns/lua/core/norns.lua:185>
	[C]: in function 'require'
	/home/we/dust/we/playfair.lua:20: in main chunk
	[C]: in function 'dofile'
	/home/we/norns/lua/core/script.lua:135: in function </home/we/norns/lua/core/script.lua:135>
	[C]: in function 'xpcall'
	/home/we/norns/lua/core/norns.lua:186: in field 'try'
	/home/we/norns/lua/core/script.lua:135: in function 'core/script.load'
	/home/we/norns/lua/core/menu.lua:429: in field 'key'
	/home/we/norns/lua/core/menu.lua:169: in function </home/we/norns/lua/core/menu.lua:146>
# script clear```
#426

There’s a new beta coming tomorrow that fixes the directory structure, so you might want to wait a second :slight_smile:

2 Likes
#427

Hahah all these great Instagram posts got me in a tizzy! Thanks!

1 Like
#428

top post updated.

download: https://monome.nyc3.digitaloceanspaces.com/norns190320.tgz

update 190320

  • old dust gets backed up to dust-old3
  • after much discussion (!) we reverted back to the old dust folder layout, but renamed scripts to code
  • wifi driver change, kernel update, system performance @simonvanderveldt @ngwese
  • tape fixes, softcut buffer save @zebra
  • param:read and param:write now accept numbers to read/write psets to user data folder. also accept path to read/write outside the user folder.
  • tons of little fixes
  • things i forgot that will go in the changelog on release

thank you for your patience and feedback! we’re getting close!

14 Likes
#429

Everything working OK here, update-wise :slight_smile:

2 Likes
#430

norns 1 A-OK after update.

The serial install is rather a breeze. Only thing I’ll mention for others doing it for the first time, I got a blank screen in MacOS Terminal when I did the 'screen…" line. I tapped enter and got the password prompt. So I tapped enter again and got the norns login prompt. So don’t be dissuaded by the blank screen, if you get it.

Will load up a few ‘codes’ soon and test. More in the tomorrow.

Thanks, @tehn et al!

1 Like
#431

good so far. tested adding my softcut script to the same folder as my main script and it’s now loading fine with require = 'name' :+1:

5 Likes
#432

all systems go here.

2 Likes
#433

Script updater heads up:

I believe data_dir is now _path.data

@tehn are there other globals that are changed or updated?

EDIT -
home_dir is now _path.home
dust_dir is now _path.dust
audio_dir is now _path.audio
and there’s now _path.code

4 Likes
#434

All I managed to test this morning seems to work! Very good!

Thanks for this! And also, for absolute newbies like me: don’t copy/paste the first line, because where it says (tab) you should press the TAB key. :smiley:

2 Likes
#435

got my arc in today! work has been destroying me lately, very limited spare time and no creative brain power at all. but was able to pull up today’s beta and get angl running to feel how the arc works. wow. can’t believe the script is sub 150 lines of code. looking forward to figuring out what tau means hopefully soon.

2 Likes
#436

I have been encountering this while trying the most recent update, probably something really simple that i’m missing

57%20AM
Screen Shot 2019-03-21 at 4.02.57 AM.png1150×734 135 KB