I’m not sure why your computer won’t give you permissions to install this. Let’s see if someone else has that issue as I cannot reproduce it.

I have a hunch that it may be an issue with the virtual modular program rack being installed. I’m going to try something.

**edit that wasn’t it. Tried on another machine which actually had a problem due to what I had mentioned above but it is still an issue on my main computer. So strange.

SOLVED
Apparently when I had installed linn I had made a mistake and installed to my home directory instead of the documents folder. So when I had just tried to to the rack install in the home folder it worked. Geez

1 Like

Happy to hear!
I’ve created a new thread dedicated to Rack.

Hey, I have finally had a chance to try out the linnstrument on a non-vari brightness monome. Thing’s look great. I only see the C notes, but that’s absolutely fine. That basically gives enough of a footprint to be able to use it.

Sorry it took me so damn long to try it out. Lots of work and travel, followed by brief stints fooling with the norns.

2 Likes

Would this work on a 256? Would it only be the top or bottom half that would have the Linnstrument layout?

it is hardcoded foer 128x64 elements, and will probably work with the upper half of your 256.

at a quick glance, seems that it would only require these mapping tables to be updated:

or for lua version:

i didn’t spot anywhere else where row count was assummed but could have missed something.

the concept itself is pretty simple, just a list of notes that correspond to (x,y) locations, so might be simpler to apply it more directly in whatever environemnt (norns script, m4l patch etc)

1 Like

Thanks for this. I’ll give it a shot.

@neauoire Would love to try this out! I’m getting lots of npm WARN old lockfile and npm ERR! when I do the npm install. I can post the specifics if you like. Any suggestions for the novice coder - Thanks!

It has been a long time since I’ve used NPM, but what happens if you simply delete the package-lock.json file?

1 Like

has anyone gotten this to work on windows? i get this error, i wish i knew what to do to fix it:

MidiOutWinMM::openVirtualPort: cannot be implemented in Windows MM MIDI API!

1 Like

Newbie here

Can tou explain to me how I can use this with norns ?

Does it work with neotreillis 128 grid ?

1 Like

for anyone getting errors on the
npm install, removing the package-lock.json file worked for me, thanks for the tip! :point_up:

1 Like

Installed, setup and everything works great!

[Turned everything off, came back and using the directions:]
[## Whenever you want to use it]

  • type cd Documents/linn
  • type node index

[terminal threw an error:]
[ code: ‘MODULE_NOT_FOUND’]

EDIT: its all fine I was forgetting the “/linn” after cd documents

Is anyone using Linnstrument in this way routinely? Is it worth it?

so, apparently it is working correctly after several attempts with different versions of serialosc in windows, but is not showing up in ableton :frowning: any ideas?

sdsd

1 Like

i could use some help getting this running on my m1 mac. i keep getting ‘ERR_DLOPEN_FAILED’. it has something to do with the ‘easymidi’ module, and maybe something to do with the version of Node i’m running – i’m very out of practice with development… not sure how to find which version of Node i need to use, or if Node is actually the problem. i also do not understand ‘incompatible architecture’, (seemingly the actual problem) which started popping up as an issue for me when i transferred everything from my old mac to the m1. any help would be appreciated!

/Users/tymaraist/Documents/Monome/linn/node_modules/bindings/bindings.js:121
        throw e;
        ^

Error: dlopen(/Users/tymaraist/Documents/Monome/linn/node_modules/easymidi/node_modules/midi/build/Release/midi.node, 0x0001): tried: '/Users/tymaraist/Documents/Monome/linn/node_modules/easymidi/node_modules/midi/build/Release/midi.node' (mach-o file, but is an incompatible architecture (have 'arm64', need 'x86_64')), '/System/Volumes/Preboot/Cryptexes/OS/Users/tymaraist/Documents/Monome/linn/node_modules/easymidi/node_modules/midi/build/Release/midi.node' (no such file), '/Users/tymaraist/Documents/Monome/linn/node_modules/easymidi/node_modules/midi/build/Release/midi.node' (mach-o file, but is an incompatible architecture (have 'arm64', need 'x86_64'))
    at Module._extensions..node (node:internal/modules/cjs/loader:1577:18)
    at Module.load (node:internal/modules/cjs/loader:1282:32)
    at Module._load (node:internal/modules/cjs/loader:1098:12)
    at TracingChannel.traceSync (node:diagnostics_channel:315:14)
    at wrapModuleLoad (node:internal/modules/cjs/loader:215:24)
    at Module.require (node:internal/modules/cjs/loader:1304:12)
    at require (node:internal/modules/helpers:123:16)
    at bindings (/Users/tymaraist/Documents/Monome/linn/node_modules/bindings/bindings.js:112:48)
    at Object.<anonymous> (/Users/tymaraist/Documents/Monome/linn/node_modules/easymidi/node_modules/midi/midi.js:1:31)
    at Module._compile (node:internal/modules/cjs/loader:1467:14) {
  code: 'ERR_DLOPEN_FAILED'
}

Node.js v22.4.0

It sounds like you copied this from your old mac to a new m1? If that’s the case I would imagine some stuff needs to be recompiled and that’s why it can’t open the dynamic library (DL). This might explain it better Apple Silicon and legacy command-line software — AstroWorldCreations

1 Like

this feels like a step in the right direction, but i get the same ‘ERR_DLOPEN_FAILED’ when running the intel emulation command. but yes, i ( stupidly, but i didn’t know it was going to cause problems at the time ) used Migration Assistant when i upgraded and it has caused a lot of problems

edit: i wish i know what i did that fixed it, but it is working for me now

edit 2: the bottom row of grid isn’t illuminated. it’s shooting midi and i’m happy, just not sure why