search

flipcoder / textbeat

🎹 plaintext music sequencer and midi shell, with vim playback and the powers of music theory 🥁
MIT License
406 stars 13 forks source link

document setup steps for mac #11

Open mwesterhof opened 2 years ago

mwesterhof commented 2 years ago

I was trying to get this running on a macbook. I've made some progress, roughly based on the linux instructions. I've managed to get it working, but there's currently no sound. I'd troubleshoot this further so I could provide a PR with the instructions, but i'm not really sure how to interpret what i'm seeing. Unfortunately, i'm also not much of an export on Macs. Of course, feel free to close this if you don't intend on supporting mac.

Initially, textbeat wouldn't launch at all, because it couldn't find any midi devices. After adding one manually, it did launch, but now there's no sound. The output looks like this:

Copyright (c) 2018 Grady O'Connell
https://github.com/flipcoder/textbeat
Active Modules: midi, carla, auto
Inactive Modules: soundfonts, espeak, csound, fluidsynth, sonicpi, supercollider
Other Devices: test Bus 1

txbt> (120bpm x4)> maj&
maj&
.
.
txbt> (120bpm x4)>

i'm assuming that something useful can be gleaned from the modules output, but i'm not really sure what to make of it at the moment

flipcoder commented 2 years ago

Thanks for trying it out. I haven't personally tested on Mac but I can probably get it working for you soon. I just need to know the device names that Mac users use for playing midi. The way it selects the midi device to use is based on common names of default midi devices in textbeat/def/dev.yaml. It's a partial string match. Otherwise you have to specify the device using --dev= but I think that flag might be broken. You could try adding "test Bus 1" or the name of your midi device to the default devices list in textbeat/def/dev.yaml. Also, you can ignore the module names since they're mostly just stub plugins and I removed those from being displayed in the latest develop branch.