Getting driver descriptor from /usr/lib/jack/jack_dummy.so Getting driver descriptor from /usr/lib/jack/jack_freebob.so Under certain conditions see the file COPYING for details This is free software, and you are welcome to redistribute it I have yet to test this, as two people near me are having the same problem.Ĭode: Select all 23:14:35.411 Patchbay deactivated.Ģ3:14:35.430 ALSA connection graph change.Ģ3:14:36.600 /usr/bin/jackd -v -dalsa -r48000 -p128 -n3 -m -H -M -D -C"ALSA::FastTrack Pro: USB Audio (hw:1,0)" -Phw:0,0 -i2 -o2Ĭopyright 2001-2009 Paul Davis, Stephane Letz, Jack O'Quinn, Torben Hohn and others. The ehci driver is supposed to be fixed in 3.1.6, I think, thanks to a patch by Thomas Poussevin.
#CAN I USE M AUDIO FAST TRACK PRO FOR LIVE AUDIO HOW TO#
If this works, I will tell you how to do it from qjackctl.Īs for the problem with the duplex mode, I think you should tell GMaq. Don't bother with the setup now (jack has already been set up via the first command) but open the connection window and check / make connections from system capture to rakarrack inputs and from rakarrack outputs to onboards' outputs. If there are no errors, launch qjackctl and rakarrack. Jackd -t2000 -dalsa -dhw:Pro -C -p512 -n3 (m-audio, capture only) In this case, you will be able to listen to rakarrack outputs. In this case, you will hear your input, not the rakarrack output (but you can always record the output of rakarrack to a jack-aware recorder, e.g., ardour).
Through hardware with some speakers or headphones connected to the m-audio. Depending on the position of the mix knob and the A/B switch, you can choose to monitor either: You can run jack on the m-audio as only capture and use the onboard as the playback device. Well, there is a workaround that I think it is not so bad.