Using a Grid as Drum Rack

Prnts · 2019-07-12T04:35:41.085Z

Thanks again @neauoire that was very nice of you to compile this

neauoire · 2019-07-12T07:47:52.250Z

beforeitwascool · 2019-07-12T16:51:55.340Z

I’m getting some errors when trying to install with sudo npm install

> midi@0.9.5 install /Users/filippomasi/Desktop/Music Software/rack/node_modules/midi
> node-gyp rebuild

gyp ERR! configure error
gyp ERR! stack Error: EACCES: permission denied, mkdir '/Users/filippomasi/Desktop/Music Software/rack/node_modules/midi/build'
gyp ERR! System Darwin 18.6.0
gyp ERR! command "/usr/local/Cellar/node/12.5.0/bin/node" "/usr/local/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
gyp ERR! cwd /Users/filippomasi/Desktop/Music Software/rack/node_modules/midi
gyp ERR! node -v v12.5.0
gyp ERR! node-gyp -v v3.8.0
gyp ERR! not ok
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! midi@0.9.5 install: `node-gyp rebuild`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the midi@0.9.5 install script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

tehn · 2019-07-12T17:22:27.787Z

mod edit: seems like this should go in Library? (also if more are coming, we may want a node tag?)

atomboyd · 2019-07-12T17:34:14.191Z

Was thinking the same, maybe an ableton or midi util tag?

atomboyd · 2019-07-12T17:37:15.207Z

Hey @neauoire any chance you’d consider a rename?

I had a similar issue as @Prnts, which I still have to revisit today, but also realized that if you pull VCV-rack source code, the name of the git repo and related Document folder is Rack/

Not a huge deal, obviously. Just a thought. Naming, amirite?

Prnts · 2019-07-12T17:55:48.174Z

atomboyd:

I had a similar issue as @Prnts, which I still have to revisit today, but also realized that if you pull VCV-rack source code, the name of the git repo and related Document folder is Rack/

What you can do is just install rack in another directory. Rather than inside your Documents folder you can just tell terminal to go somewhere else. This would get around the naming issue.

Prnts · 2019-07-12T17:58:37.207Z

beforeitwascool:

I’m getting some errors when trying to install with sudo npm install

Try installing it in another directory. Looks like you put it on your desktop nested a few folders down. Were you able to get the linn version installed and working?

atomboyd · 2019-07-12T18:00:51.135Z

I actually never installed in ~/Documents since I have bunch of audio repos etc in a directory called ~/Documents/workspace/AUDIO, but was wondering if installing into ~/Documents was a hardcoded requirement, but i just reread your comments and it looks like you got it working outside of that folder.

So now I have Linn and Rack in a folder called neauoire/ and linn works fine, but even with sudo npm install, Rack gives me the following:

WARN tar EISDIR: illegal operation on a directory, open '/Users/zeroship/Documents/workspace/AUDIO/neauoire/rack/node_modules/.staging/easymidi-36aa7c17/examples'
WARN tar EISDIR: illegal operation on a directory, open '/Users/zeroship/Documents/workspace/AUDIO/neauoire/rack/node_modules/.staging/easymidi-36aa7c17/tests'
WARN tar EISDIR: illegal operation on a directory, open '/Users/zeroship/Documents/workspace/AUDIO/neauoire/rack/node_modules/.staging/nan-e86cae03/doc'
WARN tar EISDIR: illegal operation on a directory, open '/Users/zeroship/Documents/workspace/AUDIO/neauoire/rack/node_modules/.staging/nan-e86cae03/tools'
WARN tar EISDIR: illegal operation on a directory, open '/Users/zeroship/Documents/workspace/AUDIO/neauoire/rack/node_modules/.staging/midi-f63ae4bd/test'
WARN tar EISDIR: illegal operation on a directory, open '/Users/zeroship/Documents/workspace/AUDIO/neauoire/rack/node_modules/.staging/midi-f63ae4bd/test/fixture'
WARN tar EISDIR: illegal operation on a directory, open '/Users/zeroship/Documents/workspace/AUDIO/neauoire/rack/node_modules/.staging/midi-f63ae4bd/src/lib/RtMidi/msw'
WARN tar EISDIR: illegal operation on a directory, open '/Users/zeroship/Documents/workspace/AUDIO/neauoire/rack/node_modules/.staging/midi-f63ae4bd/src/lib/RtMidi/autom4te.cache'
WARN tar EISDIR: illegal operation on a directory, open '/Users/zeroship/Documents/workspace/AUDIO/neauoire/rack/node_modules/.staging/midi-f63ae4bd/src/lib/RtMidi/doc'
WARN tar EISDIR: illegal operation on a directory, open '/Users/zeroship/Documents/workspace/AUDIO/neauoire/rack/node_modules/.staging/midi-f63ae4bd/src/lib/RtMidi/doc/doxygen'
WARN tar EISDIR: illegal operation on a directory, open '/Users/zeroship/Documents/workspace/AUDIO/neauoire/rack/node_modules/.staging/midi-f63ae4bd/src/lib/RtMidi/doc/images'
WARN tar EISDIR: illegal operation on a directory, open '/Users/zeroship/Documents/workspace/AUDIO/neauoire/rack/node_modules/.staging/midi-f63ae4bd/src/lib/RtMidi/tests'
WARN tar EISDIR: illegal operation on a directory, open '/Users/zeroship/Documents/workspace/AUDIO/neauoire/rack/node_modules/.staging/midi-f63ae4bd/src/lib/RtMidi/tests/Debug'
WARN tar EISDIR: illegal operation on a directory, open '/Users/zeroship/Documents/workspace/AUDIO/neauoire/rack/node_modules/.staging/midi-f63ae4bd/src/lib/RtMidi/tests/Release'

> midi@0.9.5 install /Users/zeroship/Documents/workspace/AUDIO/neauoire/rack/node_modules/midi
> node-gyp rebuild

gyp ERR! configure error
gyp ERR! stack Error: EACCES: permission denied, mkdir '/Users/zeroship/Documents/workspace/AUDIO/neauoire/rack/node_modules/midi/build'
gyp ERR! stack     at Error (native)
gyp ERR! System Darwin 16.7.0
gyp ERR! command "/usr/local/bin/node" "/usr/local/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
gyp ERR! cwd /Users/zeroship/Documents/workspace/AUDIO/neauoire/rack/node_modules/midi
gyp ERR! node -v v6.13.1
gyp ERR! node-gyp -v v3.8.0
gyp ERR! not ok
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! midi@0.9.5 install: `node-gyp rebuild`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the midi@0.9.5 install script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     /Users/zeroship/.npm/_logs/2019-07-12T17_56_39_122Z-debug.log

rack git/master  9s
❯```

UPDATE: killing the package-lock.json cut my errors in half to only permissions issues, but still strange. Maybe a versioning issue?

Prnts · 2019-07-12T18:03:05.496Z

Ok so if you read mine you’d see that my issue was that I had installed linn the first time in my Home directory. When I installed rack in that same directory everything ended up being fine. Im not sure but I think they would need to be installed in the same location

atomboyd · 2019-07-12T18:05:47.724Z

Yeah both Linn and Rack are in a neauoire/ directory, gonna try to kill and reinstall.

atomboyd · 2019-07-12T18:12:18.972Z

@Prnts & @neauoire got it sorted, but I think there was an issue using Sudo when installing node modules (sudo npm install).

We ran into this issue at work too. Here’s an article that explains why better than I ever could:

Medium – 15 Aug 18

Don’t Use `sudo` with `npm` …still - Andrew Crites - Medium

This is a rehash of an article I wrote in 2015 about how you shouldn’t use the sudo command with npm. That is to say, you should never do…

Reading time: 5 min read

Edit: @Prnts thank you for the help!

neauoire · 2019-07-12T21:50:12.463Z

I will update the README and not use sudo, and possibly not put it in Documents, I didn’t realize that it would interfere with VCV.

@tehn I didn’t put it as library because it didn’t feel like a library but more like an application, I didn’t want to tag it norns or max4live. Maybe something like #standalone might work, or just #grid?

atomboyd · 2019-07-13T02:52:50.061Z

Hmmm, still getting no lights when running this or Linn.

After starting either of the apps in a terminal, Rack Monome and/or Linn Monome show up in Ableton as a midi source, but no lights, no midi being sent. No dice on Midi Monitor either. Thoughts?

I was running node 6.13.1 (migrating work apps to 8 currently), so I switched to 10.16.0 and still no dice…

atomboyd · 2019-07-13T03:02:26.692Z

Ugh, I think it’s my mac not recognizing my grid out of nowhere. It’s the latest grid with the latest serial osc installed. I used to have to trouble shoot my old grid, but this one has always just worked. Blergh

UPDATE/SOLVED:
had to delete that pesky FTDI kext

In case it’s any help for anyone else using a 2018 grid that doesn’t get recognized with the latest serialOSC installed, I deleted /Library/Extensions/FTDIUSBSerialDriver.kext and everything works.

I’ll stop posting now

neauoire · 2019-07-13T03:15:35.257Z

Seems to be working here, I wonder if someone else has that issue. I’m afraid the only thing I can say is, maybe try to reboot…

The node script isn’t spitting out any errors right?
When you press keys in the Linn script, does it display things in the console?

atomboyd · 2019-07-13T03:18:33.779Z

All sorted, sorry to bother. Something something FTDI kext. Deleted /Library/Extensions/FTDIUSBSerialDriver.kext and I’m good to go.

Unclear what generates that. I tend to get my hands into a ton of music tech at once so I love causing recursive chaos throughout my machine. It’s my “learning” style!

neauoire · 2019-07-13T03:19:21.615Z

Sounds like my setup as well.

electret · 2019-07-13T08:47:07.203Z

I would prefer standalone as well, unless we could have a tag for each language that might be used?

tytytytyty · 2019-08-11T23:33:04.583Z

This is really cool. Thanks for sharing!