I am receiving an “error:init” whenever I try and load a script. Is that also a duplicate engine? I am checking in cyberduck but can’t see any duplicates

if you can, use maiden in a browser and go to the “sc” tab in the bottom portion of the window (the REPL section)

Then type ;restart (and hit enter) at the very bottom and look at that output. It should tell you if there’s a duplicate engine.

06%20PM

1 Like

Hrm, unless it specifically says something about “audio engine” I would assume it is a lua bug or missing .pset or something of that nature.

But yeah checking both REPLs and posting output is a helpful first step

I can see its unable to find “abstractions” and I don’t have that folder when I look through cyberduck, should I add one or remove it from compiling?

not sure why that’s there, but i think that’s harmless.

For completeness - i’d suggest going to the matron tab in REPL and doing ;restart as well.

FWIW - have you tried turning it off and on again? :grin:

Yes I have unfortunately this starting happening a few weeks ago but I just haven’t had the time to getting around to figuring it out. After the maiden restart its giving me an audio engine error

switch your REPL to the sc tab (instead of matron) and ;restart

got @Minimum fixed up. Note the cause of the problem was not having awake installed (specifically PolyPerc) - see https://github.com/monome/we/issues/21

1 Like

Are older grids not supported based upon the variable brightness? I’m a little bummed that much of the Norns would not work with my gs128.

Any thoughts if the potential upgrade for variable brightness would allow older grids to work with these scripts?

the norns platform can be used with all grids going back to 40h.

some scripts assume variable brightness for grid UI design.

it is easy to modify them. (change value of grid:led(...) calls…)

3 Likes

Are there keyboard limitations for norns?
I tried using my ajazz ak33 keyboard and it regularly displays in the HID menu (actually two keyboards “keyboard” and “keyboard 2” pop up when i plug it in) but then inputs are not recognized by Orca

This 2 Hid devices thing seems common for usb keyboards.

Try connecting to the second one using the vport number (the number listed in the devices menu)

myhid = hid.connect(2)

Or… I can’t remember if the keyboard select thing got added to orca - check the params menu.

1 Like

Thanks, it worked!
should I add that line to Orca code?

You would want to just change line 16 in your version of the orca code to the vport number of your device. i.e. local keyboard = hid.connect(2)

For the moment I don’t think Orca allows for selecting the keyboard via the params. I’ll maybe send a request to add that when I have some time.

Oh I could have a look at that.

Does anyone know how to get the norns to send midi over wifi?

1 Like

not currently supported, but OSC is!

does ALSA have a network midi device?

Quick search…,
https://blog.tarn-vedra.de/pimidi-box/

this uses RaveloxMIDI

Or someone mentioned Aseqnet http://ccrma.stanford.edu/planetccrma/man/man1/aseqnet.1.html

UPDATE - Using the directions in that first link, I did a quick install of RaveloxMIDI and got it to show up on the network (visible from the Mac), but there’s some ALSA shenanigans I’ll need to figure out later as I think norns is commandeering the midi ports

more later.

This should work I believe https://github.com/rncbc/qmidinet, haven’t tested/tried it myself though

But… qmidinet appears to be something different than the MacOS RTP-MIDI?

FWIW - I’ve been hacking on RaveloxMIDI a bit just now and I can get it to be recognized over the network, but can’t yet send midi. Another potential problem is that RaveloxMIDI requires virMIDI and Timidity… and I’m unclear how to pipe things to the right ports.

There’s also a rtmidi-python library