@scrag @carvingcode I suspect you may have duplicate engines installed. try launching maiden and looking at the sc command tab. use system reset or type ;restart

check the sc error message and it will show duplicate files

edit: restart not reset

I’m not seeing anything at all in the SC command tab in Maiden when trying to start a script.

If I enter the reset command it returns “Library has not been compiled successfully.”

The log in the Matron tab seems to suggest that things grind to a halt about the time of loading the engine - trying to start Awake for instance, results in the following:

# 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

Engines should be located where? we/lib? I don’t see any duplicate engines in the norns dir.

BTW: when Passersby quits, this:

CroneEngine.free
free engine: an Engine_Passersby
CroneEngine.free
FAILURE IN SERVER /n_free Node 1012 not found
FAILURE IN SERVER /n_free Node 1013 not found
FAILURE IN SERVER /n_free Node 1014 not found
FAILURE IN SERVER /n_free Node 1019 not found
FAILURE IN SERVER /n_free Node 1020 not found

Have also seen similar when Glut ends.

Edit:

norns now won’t load a script, stuck on ‘loading’. I can back out and choose another, but still stuck. Prior to this, maiden/sc reports:

free engine: an Engine_Passersby
CroneEngine.free
stopPoll failed; couldn't find index 15
stopPoll failed; couldn't find index 14
stopPoll failed; couldn't find index 12
stopPoll failed; couldn't find index 9
stopPoll failed; couldn't find index 8
stopPoll failed; couldn't find index 10
stopPoll failed; couldn't find index 11
stopPoll failed; couldn't find index 13

FWIW - if I try SYSTEM>RESET on device, maiden will lose it’s connection and requires me to click the “reload” icon in the REPL (using Chrome). So you have to quickly reload the REPL to see the output.

Also
;reset
gives me
;reset => unrecognized operation

1 Like

i had the duplicate engines issue due to how i had set up markeats’ scripts (missed that they were in we with the others as the paths in the script pointed somewhere else). if you ssh in and run “sclang” it will tell you which engines are duplicated when it doesn’t work

1 Like

You are so right!

we@norns:~$ sclang
compiling class library...
        Found 716 primitives.
        Compiling directory '/usr/share/SuperCollider/SCClassLibrary'
        Compiling directory '/usr/share/SuperCollider/Extensions'
        Compiling directory '/home/we/.local/share/SuperCollider/Extensions'
        Compiling directory '/home/we/norns/sc/core'
        Compiling directory '/home/we/norns/sc/engines'
        Compiling directory '/home/we/norns/sc/ugens'
        Compiling directory '/home/we/dust'
ERROR: duplicate Class found: 'Engine_MollyThePoly' 
/home/we/dust/code/molly_the_poly/lib/Engine_MollyThePoly.sc
/home/we/dust/code/we/lib/Engine_MollyThePoly.sc

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

ERROR: There is a discrepancy.
numClassDeps 1437   gNumClasses 2872
sc3> 

Thanks!

4 Likes

I believe that sound is coming from the Supercollider Crone/Engine abstraction when it finishes starting up - I noticed it the other day when exploring engine development.

It is safe to ignore right now and may just be some debug code we need to remove at
some point if it proves problematic.

2 Likes

That is almost the right syntax - maiden supports using ;restart in either the matron or the sc REPL. Using that command in the REPL will restart just that component of the system whereas the RESET option in the device menu will restart basically everything.

Using the ;restart option in the sc REPL will make it easier to debug startup problems because maiden will try to quickly auto connect again…

2 Likes

Can anyone see what’s wrong here? I’m going back through study 4 and updating the syntax for v2. Everything seems OK, in that the grid lights up and I can change steps, also no errors.

However, I’m not getting any movement on the sequencer. It’s ‘stuck’ on the first step, which makes me think it’s something to do with the metro…

Study 4
engine.name = 'PolyPerc'

steps = {}
position = 1
counter = metro.init{time = 0.1, count = -1, event = count}

function init()
  for i=1,16 do
    table.insert(steps,1)
  end
  grid_redraw()
  counter:start()
end

g = grid.connect()

g.key = function(x,y,z)
  if z == 1 then
    steps[x] = y
    grid_redraw()
  end
end

function grid_redraw()
  g:all(0)
  for i=1,16 do
    g:led(i,steps[i],i==position and 15 or 4)
  end
  g:refresh()
end

function count()
  position = (position % 16) + 1
  engine.hz(steps[position]*100)
  grid_redraw()
end

You need to ‘start’ the metro

counter:start()
2 Likes

Thanks, hmm there is already a counter:start() in the init() function?

edit:
Not sure why that one isn’t working… Managed to get the main Study 4 example going now, so all good.

Ah gotcha - I suppose @tehn had a typo in his comment above then.

1 Like

Dunno. When I was converting my WIP islands I needed to add starts.

1 Like

midi clock out working? i have nothing to test with atm

Yes? I mean… you’ll need to be a bit more specific if you had a previous issue with clock.

But… there is now a clock helper event type so you can use that in various ways. See my midi-demo script here for more

1 Like

sorry, that was extremely general haha.

simply wondering if midi clock out from awake, mlr, playfair is working for people.

1 Like

Yes it does. Used it until some minutes ago.

2 Likes

Is there yet a curated collection of scripts that have been ported to 2.0? https://github.com/monome/we looks pretty empty. Or am I being dumb and missing something.

Once v2 is released, we’ll probably see a bunch of old and new scripts coming thru. Some will go in we and some to the new library category here. Plus, still others will be available thru git and other means I’m sure.

3 Likes

to be settled by release, but the we repo will likely only be demos, studies, tests, how-tos, and helper libs.

the upcoming Library category will be the collection of scripts, in either attachment for or git release links. i apologize that it’s difficult to find them now… they’re scattered through this thread.

5 Likes