I’m also stuck on infinite ‘loading…’ after using the librarian script to get new scripts on Norns. Deleting Haven didn’t solve it for me. Not getting any errors afaics.

I’m sorry I caused that confusion. we used to have an independent version of the haven engine. It is fixed in the current state of the we repository and should work now as expected.

Please try this https://monome.org/docs/norns/#error-audio-engine

1 Like

Thanks! Unfortunately it doesn’t do anything and I can’t see any log outputs (or errors) displayed after following the ‘help’ guide.

@Joakim can you attach a screenshot?


also i wanted to point out: if you need to re-download the newest we folder, it’s here: https://github.com/monome/we

here’s a direct link: https://github.com/monome/we/archive/master.zip

No problem, was able to figure it out. Haven is really awesome, thank you for sharing it!

2 Likes

working through the studies (#4) - getting an error with this ’ instance methods use colon instead of dot, ie g.led(…) to g:led(…). Ok if set it to dot?

Does Awake spit out MIDI?
I could not quite make it work…

Yes it does ! Used it yesterday with a Prophet Rev2 connected in USB directly, worked perfectly.

1 Like

yes, that was supposed to be changed for 2.0. where are you seeing it in the study? i am not seeing that particular problem in 4 but i see some metro.alloc()s that need to be changed to metro.init()s.

FYI here are all the things that are potential wrong with older syntax:

it should not be like that in the study though, so good to point out anything like that you see.

I can also confirm this works. I sequenced some iOS apps with it yesterday without issues.

Study 4 - para beginning ‘expanding’ - in the code that follows the line after the g = grig:connect()
get error as is - but change the g:key to g.key no error.

that said not getting any lights on either?

final word on this. I’ve been using Vivaldi browser for norns interaction with good results. 2 days ago there was an update - and I have to say odd things were happening with scripts - then late in the day yesterday another update - and suddenly my odd scripts burst into action. :upside_down_face::upside_down_face:

Hmmm, good to know.
I was just testing this with CV-Pal, and not a peep…

(Dumb Question) Did you select your midi controller in SYSTEM>DEVICES>MIDI?

awake will default to the first one in the list.

So, and pardon my lack of knowledge here, I just need to install haven again and all will be well or is there something I need to do with “we”? Still learning how all of this fits together! Thanks!

just in case…

cd ~/dust/code/we
git pull

and you’ll get the most recent version

1 Like

You’ll need to update we. Use the same process as for other scripts as documented here (and under the “gathering” section slightly below that), just remove the we directory first and then replace it with the unzipped version of this https://github.com/monome/we/archive/master.zip
Make sure to (re)name the directory we, not we-master.

[edit] As @okyeron mentioned you can also use git, but if you’re not familiar with it better just use the SFTP method to replace the directory.

4 Likes

Thanks, I actually figured out how to git it, and I got it good. :triumph:

4 Likes

I have a function within a script that calls the init function to effectively ‘start again’ - fine in norns prior to 2.0. Now appears to be ignored - any thoughts ?

No - I’ve noticed that my m.stop() to halt the metro is at fault. What is the syntax now to halt the metro - I’ve tried counter:stop() and metro:stop() both give a script error / load fail. I’m using the code from study 4

function init()
  position = 0
  counter = metro.init()
  counter.time = 1
  counter.count = -1
  counter.event = count
  counter:start()
end

function count(c)
  position = position + 1
  print(c .. "> " .. position)
end

what does the error say in maiden?