#578

I’d love a quick status update today if possible - I’ve got a jam with friends on Sunday and I’m tempted to give 2.0 a spin if it’s not going to be too painful to install.

1 Like
#579

i’d generally suggest staying with 1.x until release, especially if you want to play right away. there is not yet a way to easily locate scripts, but it’s coming very soon (next week!)

9 Likes
#580

i upgraded because i had gotten the new CM3+ to increase storage…looking for the legit release so i can play with the old scripts :smiley:

1 Like
#582

@zebra any clue where I might look to find where this path is being included?

I’m seeing this (crone error) on one install but not on the other one - both are up to date with current dev branch.

WARNING: Could not open directory: '/home/we/norns/sc/abstractions'
	To resolve this, either create the directory or remove it from your compilation paths.

also the we repo looks like it got cleaned up today and angl and earthsea got moved out of there to… nowhere yet?

1 Like
#583
1 Like
#584

may need to nuke yaml or cycle sclang after change to norns_config.sc

new plan is to for authors to manage own scripts / engines

more soon on how to aggregate these

1 Like
#585

to confirm - deleting /home/we/.config/SuperCollider/sclang_conf.yaml and re-running sclang fixed the warning/error.

1 Like
#586

Haven’t been able to open updated foulplay since the beta. Getting this:

SCRIPT ERROR: init

/home/we/dust/code/foulplay.lua:851: attempt to concatenate a nil value (global ‘data_dir’)
stack traceback:
/home/we/norns/lua/core/norns.lua:185: in metamethod ‘__concat’
/home/we/dust/code/foulplay.lua:851: in global ‘loadstate’
/home/we/dust/code/foulplay.lua:333: in function ‘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>

#587

the version of foulplay on github right now is not updated for the most recent beta changes. If you want to live dangerously you could edit the version you have to replace data_dir with _path.data and it should work.

or… wait for @Justmat to update the script when he has time.

5 Likes
#588

data_dir with _path.data
worked, thanks a ton!

#589

Oops! I could have swore that I had fixed that already. I’ll make sure everything is up to date this morning. :sweat_smile:

Edit: looks like I had only fixed it locally! everything is pushed and all is good now. Thanks for the heads up, @okyeron and @altoaiello!

3 Likes
#591

It looks like the engine has moved since the last update.
updating line 22 to
"local Passersby = require “passersby/lib/passersby_engine”
seemed to fix it. :slight_smile:

thx for the links!

#592

I’m on update 190320, which is I believe the most recent.

#593

I can confirm it works on the latest beta, and it’s an excellent piece of work! :raised_hands:

2 Likes
#594

Will we have a 2.0 «GM» this week?

#595

2.0 approaching late this week.

just created the Library category. feel free to start creating threads with your projects!

keep in mind there may be a few final changes to the system prior to release. run git pull inside the norns folder for newest version.

14 Likes
#596

I must have missed an update with some of the changes to the lib directory. Thanks for confirming.

1 Like
#597

@carvingcode - I tried to load up Isoseq on a fresh norns 2.0 build

and got this…

### SCRIPT ERROR: load fail
/home/we/dust/code/isoseq/isoseq.lua:22: module 'we/lib/passersby' not found:

Looks like passersby engine lib is no longer in we (but is available here on @markeats github )

So… what’s the best approach to posting a script with dependencies on another user’s engine like this?

2 Likes
#599

In the short term #1 seems preferable.

#600

Any idea on how to correctly remount read-only partition on norns? Currently when connecting op-1 in disk mode it mounts read-only