#661

@jonsimon AFAIK, the old image doesn’t have kernel support for CM3+. use 2.0 image

i think you may also want to expand disk size (after successful installation) as suggested rather far above

1 Like
#662

i am unable to even see my CM3+ anymore under

diskutil list

which is why i wonder if i effed it up.

#663

you are running rpiboot again, yes?

i’ve always found this step to be a little flaky, sometimes requiring repeats and different orderings power / rpiboot / connect / DISK/RUN- not specific to norns.

#664

I am using that, under OSX terminal, but i am unable to even see the volume after flashing it with the wrong image. when i would plug norns in originally with the new CM3+, it would ask my if i wanted to initialize the disk. now it doesn’t recognize, aka norns under disk mode doesn’t let me access it or see it anywhere.

EDIT:
i’m back in! thanks @zebra!!!

1 Like
#665

@zebra, so if I want to upgrade to @tehn’s latest early beta 190404, would it be best to flash CM3+ first with 190303 (since it’s an img file), then go thru SFTP and update that way once the CM3+ is bootable?

1 Like
#666

i have not personally done this and so cannot make specific assurances. it seems reasonable, as does trying the latest update from whatever bootable state you can get in. or just wait for final non-beta image incoming tomorrow. (goodnight for me :crescent_moon:)

2 Likes
#667

thanks sir!
i had every intention of waiting, until i saw all these freakin arc 2.0 apps!!!
yes. thanks so much.

ps sweet dreamz :heart:

1 Like
#668

I believe the 190314 image should work, though I could be wrong. One of the images didn’t have the correct files to make it work on a CM3+.

#669

ok thanks!
190303 did NOT work, so trying that…

EDIT:
i haven’t gotten past the “error: audio engine” part, and even when i updated to 190404, it didnt work still on the cm3+ and still says i’m on 190303 even after doing the process twice. just gave up and waiting for 2.0 today… learned a lot though!

1 Like
#670

Good to hear :slight_smile:
Have fun!

1 Like
#671

Update went well, hotspot works great.
Just a heads-up, it looks that @dan_derks’s Less Concepts and @trickyflemming’s gemini and easygrain don’t work. Can anyone check? (I was in a hurry so I have no maiden output at the moment)

#672

@AlessandroBonino re: less concepts, there were some necessary changes to the requirement syntax. I made those changes in the library-posted version, which is working on my machine: Less concepts

confirm success?

1 Like
#673

Any news regarding cranes? @dan_derks :slight_smile:

6 Likes
#674

D’oh. I’ll take a look at it tonight. @dan_derks What changes were needed? Was it the engine location syntax?

@tehn if I include Gemini inside of its own lib folder, can I do
engine.name = 'Gemini'
or does it need to be more explicit like lib\Gemini or gemini\lib\Gemini

Also, “Gemini” now doesn’t seem like a real word after typing that.

1 Like
#675

yep yep!

passersby = include "passersby/lib/passersby_engine"

working on it today! goal is to update with new softcut syntax, but would love to fold in some ideas that i’ve had brewing. we’ll see where we end up, but i’ve been missing it :slight_smile:

4 Likes
#676

you can do lib/Gemini if the lib is in the current folder.

other scripts can get your lib with gemini/lib/Gemini

3 Likes
#677

heads up to people writing scripts that use @jah’s engines ack, r, gong

we’re moving things out of the we repo into individual repos.

we is just going to be studies, demos, and tests. there are some libs/engines in there currently that haven’t been claimed/moved. we’d prefer these live with their respective authors in the future, but we’re not going to push it.

these repos will be included in the 2.0 release, so all engines will be availalbe.

but if you use ack for example, you’ll need to change your includes if you use lib/ack.lua

engine = 'ack'

will still continue to work just fine if you add the ack repo. (again, which will be included in 2.0)

#678

What is correct syntax for using engines with support libraries, such as Passersby and MollyThePolly?

#679

Assuming ack is installed in ~/dust/code/ack, this will be correct:

#680

you’ll have to check the file path, per engine.

for example, in passerby.lua

local Passersby = require "passersby/lib/passersby_engine"
engine.name = "Passersby"
1 Like