An implementation of the Ableton Drum Rack layout for the Monome 128. This tiny console script will create a new virtual instrument called Rack Monome to use with your DAW.
This script does not require MaxForLive. Download sources here.
type git clone https://github.com/neauoire/rack.git
type cd rack
type sudo npm install
type node index
Whenever you want to use it
type cd Documents/rack
type node index
Channel
By default, the rack monome will send to Channel 0, you can change channel by holding down the last key(bottom right), and pressing one of the 16 keys of the top row.
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?
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.
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?
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?
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
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?
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…
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.
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!
thanks for this!