No that's fair, I haven't articulated myself very well.
I'd like two things out of this:
1) to be able to play my keyboard as a midi keyboard, record directly into Reaper and be able to edit notes after the fact in Reaper.
2) Use the keyboard as a midi controller for controlling virtual instruments (VSTi?) in Carla. To be fair I am only trying to intergrate Carla at this point as it has such good reviews for being able to support lots of different types of plugins. I'm guessing you can also just do this directly through reapers fx tab without going via Carla.
So far I haven't worked out how to do either of the above with my set-up. A lot of the time Reaper refuses to acknowledge the midi input even when it is connected via Jack Ctl.
Linuxmusician01 wrote:I'm having trouble to exactly understand what you want to do (= my bad). You have a Yamaha Midi keyboard that you want to use in Reaper? Is it the Windows version of Reaper, or the Linux one. Why do you use Carla? To connect your hardware keyboard to a virtual VST synthesizer?
I am using the Linux version of Reaper.
I have played around using Jack or Alsa midi support and Alsa seems to work best. Intuitively the "seq" instead of "raw" or "none" option in Jack seems to work best as well? Does this mean I should be using the MIDI or ALSA tab in Jack Connections? I also have Cadence (which came with the Carla package) that has "Jack Bridges" as options. Not sure if these are useful though... They create a separate connection option called a2j...
I understand what you want now.
I never play a Midi keyboard to record the midi notes in my DAW (that's what you want), and I don't use Reaper. But a lot of other people do. So I'm convinced that they'll help you out w/ that. If not, I hope that there's a Reaper forum around...
Your problems are the "standard" problems people have w/ DAW's and Midi in any OS and w/ Linux in particular. Let me explain something 'bout that in general. After that you might be able to solve your probs by yourself or I might give it a try. The way I see it is as follows and it is by NO means the proper or right formal way to see it. NOR is it complete.
There are "plugins" for DAW's. They can be effects (e.g. delay) or instruments (e.g. a Minimoog synthesizer "emulator"). The most used plugin format in the world is VST from Steinberg (or VSTi for an i
nstrument). However, one can compile the source code in which a VST is written to Linux or Windows. For Windows the VST code then results in a dynamic link library: a .dll
file. For Linux that results in a shared object library: an .so
Some DAW's support VST's, some don't. Reaper supports VST's. Native Linux Reaper supports Linux VST's, the Windows version of Reaper supports Windows VST's. Sounds logical doesn't it? Not a lot of companies and free programmers compile their VST's to the Linux format. If you've got a VST, 99% chance that it's a Windows one. So bummer for us Linuxers, right?
Well, not so. To make Windows VST's usable to Linuxers there is "bridging" software. We can use Carla (has a graphical user interface) or LinVST (is best when compiled from source code). Now how does that work in the practical sense: Carla to bridge your favorite (Win) VST to Linux? Carla will "present" itself to your DAW as a plugin that your DAW actually does recognize! Like:
- a Linux VST
- an LADSPA plugin
- a LV2 plugin (dunno for sure if Carla does this...)
In Linux Reaper you must look for the "Linux VST version of Carla". This plugin is located on my Linux PC in: /usr/lib/vst/carla.vst/
. You must tell Linux Reaper to search for plugins (read: Linux VST's!) in that path. Do that in Linux Reaper via: "Options > Preferences > (left-hand list) Plugins > VST > (right-hand panel) VST plugin path > Edit > Add". Now you can use Carla as if it was a Windows VST. When the Carla window opens you can add/use your favorite Windows VST in Carla.
How to use Carla is a separate story all together. This might be why some Linuxers use the Windows version of Reaper instead of the native Linux version...
Now what about all that Jack and Alsa Midi: seq, raw, none. There are two ways of using Midi in Linux: via Jack or via ALSA. Confusingly (or better: conveniently) Jack can also use ALSA's midi implementation. Alsa has a secret code word for Midi: it's "sequencer" or seq
for short. What "raw" is: I down't know. Probably Jack's Midi. If you use the command line method to start Jack that I gave you in my post above then Jack is started w/ it's default options. That is: with Alsa seq Midi.
Now what about all those cryptic tabs in the "Connect" windows of Qjackctl
. "Audio" means exactly what it says: you can connect audio in- and output signals there. Like the output of your DAW to the audio input of your computer system (i.e. your speakers). The "Midi" tab means Jack Midi. The "Alsa" tab means Alsa Midi. That's the one you want.
I think that's enough lessons for the day, Grasshopper
P.S. More caveats to be explained when there is a need for it:
- 32 bit VST's versus 64 bit VST's and how to use them
- Connect Midi and Audio outputs to inputs via Qjackctl
- Use LinVST instead of Carla
- Use LinVST w/ 32 bit VST's
- Use Qtractor instead of commercial (Windows) DAW's
- Use Audacity w/ effect plugins for quick 'n' dirty multi track recording