Main menu
You are here
I Can't get MIDI into Qtractor
I have successfully compiled and installed Qtractor (I think...), but I can't connect the MIDI keyboard to Qtractor.
I have an M-Audio Oxygen USB keyboard. When I open the Connections window in Qtractor and click the MIDI tab, I see the Oxygen keyboard listed, but I cannot connect it to anything. With 20:Oxygen 49 selected in the "Readable Clients/Output Ports" window, I tried connecting to 128:Qtractor, and I tried connecting to 14:MIDI Through. Nothing happens.
As a test, I clicked the Audio tab, and disconnected one of the audio connections. The Messages window said "Audio connections change" When I attempt to connect Oxygen, no text is added. I also tried connecting MIDI through (out) to Qtractor (in) and that worked. Text in the Messages window, and a line from MIDI through to Qtractor. It's just the Keyboard.
I can use the keyboard in Ardour, (but MIDI editing in Ardour doesn't work for me) I don't know what to do...
Here is some of the output of ./configure before I ran make and make install:
Qtractor 0.8.0 (Dec 07 2016 20:30 -0500)
Build target . . . . . . . . . . . . . . . . . . .: release
JACK Audio Connection Kit support . . . . . . . .: yes
ALSA MIDI Sequencer support . . . . . . . . . . .: yes
General audio file support (libsndfile) . . . . .: yes
Ogg Vorbis audio file support (libvorbis) . . . .: yes
MPEG-1 Audio Layer 3 file support (libmad) . . . .: yes
Sample-rate conversion support (libsamplerate) . .: yes
Pitch-shifting support (librubberband) . . . . . .: yes
OSC service support (liblo) . . . . . . . . . . .: yes
Archive/Zip file support (zlib) . . . . . . . . .: yes
IEEE 32bit float optimizations . . . . . . . . . .: yes
SSE optimization support (x86) . . . . . . . . . .: yes
LADSPA plug-in support . . . . . . . . . . . . . .: yes
DSSI plug-in support . . . . . . . . . . . . . . .: no
VST plug-in support . . . . . . . . . . . . . . .: yes
LV2 plug-in support . . . . . . . . . . . . . . .: yes
LV2 plug-in UI support . . . . . . . . . . . . . .: yes
LV2 plug-in External UI support . . . . . . . . .: yes
LV2 plug-in MIDI/Event support (DEPRECATED) . . .: no
LV2 plug-in MIDI/Atom support . . . . . . . . . .: yes
LV2 plug-in Worker/Schedule support . . . . . . .: yes
LV2 plug-in State support . . . . . . . . . . . .: yes
LV2 plug-in State Files support . . . . . . . . .: yes
LV2 plug-in State Make Path support (DANGEROUS) .: no
LV2 plug-in Programs support . . . . . . . . . . .: yes
LV2 plug-in Presets support . . . . . . . . . . .: yes
LV2 plug-in Patch support . . . . . . . . . . . .: yes
LV2 plug-in Time support . . . . . . . . . . . . .: yes
LV2 plug-in Time/position support . . . . . . . .: yes
LV2 plug-in Options support . . . . . . . . . . .: yes
LV2 plug-in Buf-size support . . . . . . . . . . .: yes
LV2 plug-in UI Touch interface support . . . . . .: yes
LV2 plug-in UI Idle interface support . . . . . .: yes
LV2 plug-in UI Show interface support . . . . . .: yes
LV2 plug-in UI GTK2 native support . . . . . . . .: yes
LV2 plug-in UI X11 native support . . . . . . . .: yes
JACK Session support . . . . . . . . . . . . . . .: yes
JACK Latency support . . . . . . . . . . . . . . .: yes
JACK Metadata support . . . . . . . . . . . . . .: yes
Non Session Management (NSM) support . . . . . . .: yes
X11 Unique/Single instance . . . . . . . . . . . .: no
VeSTige header support . . . . . . . . . . . . . .: yes
Gradient eye-candy . . . . . . . . . . . . . . . .: yes
Debugger stack-trace (gdb) . . . . . . . . . . . .: no
Install prefix . . . . . . . . . . . . . . . . . .: /usr/local
Thanks in advance!
Paul
re. I Can't get MIDI into Qtractor
please check whether anything is grabbing the MIDI in "raw" mode, might be jackd (-Xraw) or some java application or applet.
as many other linux applications, qtractor uses the ALSA Sequencer (aka. ALSA-MIDI) shared infrastructure, and this becomes pretty much inoperative when some other application takes over any of the old "raw" device interfaces directly or exclusively (eg. /dev/snd/midi*, /dev/snd/seq, etc.)
hth.
cheers
OK, so I set the midi driver
OK, so I set the midi driver in Jack (via Qjaclctl) to "none". I closed Jack, via Qjackctl, closed Qtractor, and then re-opend Qtractor. This is what I got in the messages window of Qtractor:
Cannot connect to server socket err = No such file or directory
Cannot connect to server request channel
no message buffer overruns
no message buffer overruns
no message buffer overruns
jackdmp 1.9.11
Copyright 2001-2005 Paul Davis and others.
Copyright 2004-2014 Grame.
jackdmp comes with ABSOLUTELY NO WARRANTY
This is free software, and you are welcome to redistribute it
under certain conditions; see the file COPYING for details
JACK server starting in realtime mode with priority 10
self-connect-mode is "Don't restrict self connect requests"
audio_reservation_init
Acquire audio card Audio0
creating alsa driver ... hw:MID,0|hw:MID,0|1024|2|44100|0|0|nomon|swmeter|-|32bit
configuring for 44100Hz, period = 1024 frames (23.2 ms), buffer = 2 periods
ALSA: final selected sample format for capture: 32bit integer little-endian
ALSA: use 2 periods for capture
ALSA: final selected sample format for playback: 32bit integer little-endian
ALSA: use 2 periods for playback
JackALSARawMidiDriver::Attach - input port registered (name='system:midi_capture_1', alias='system:2-1 Oxygen 49 1 in').
JackALSARawMidiDriver::Attach - output port registered (name='system:midi_playback_1', alias='system:2-1 Oxygen 49 1 out').
JackALSARawMidiDriver::Start - Starting 'alsarawmidi' driver.
JackALSARawMidiDriver::Start - starting ALSA thread ...
JackALSARawMidiDriver::Start - started ALSA thread.
22:10:06.203 Audio connections change.
22:10:06.204 MIDI connections change.
Jack is clearly using using the raw midi driver "JackALSARawMidiDriver" but how do I tell it not to?
Thanks in advance1
Paul
re. OK, so I set the midi driver
please start jackd at least once from qjackctl first and after making changes to any of its settings, in order to set the auto-start configuration file accordingly (
~/.jackdrc).otherwise you're probably left with the same old settings in place, when qtractor or any other jack client application is run but the jackd server isn't up and running at the time.
hth.
cheers
Add new comment