[00:00] <len-dt> You should get a dialog window open up
[00:00] <ariel__> do you want a pastebin of the error messages?
[00:00] <len-dt> on the right side there is a buttom that says Interface
[00:01] <len-dt> is it still set to (default)?
[00:01] <ariel__> yes
[00:02] <ariel__> it's default
[00:02] <len-dt> To the right of that there is a > if you click that you will get a list of what jack sees for devices.
[00:02] <ariel__> yes
[00:03] <ariel__> hw:1 is the fast track pro
[00:03] <len-dt> That would be where yu select the USB device
[00:03] <len-dt> default is HW:0
[00:03] <ariel__> so i should pick hw:1 right?
[00:04] <len-dt> Yes.
[00:04] <ariel__> anything else?
[00:04] <len-dt> Then ok the dialog and start or restart jack
[00:04] <ariel__> ok
[00:04] <ariel__> now is working
[00:05] <len-dt> Does it have all the inputs and outputs?
[00:05] <len-dt> Open connections
[00:05] <ariel__> it has capture 1 and 2
[00:05] <len-dt> select the audio tab
[00:06] <len-dt> does it have playback as well?
[00:06] <ariel__> yes
[00:06] <ariel__> 1 and 2
[00:06] <len-dt> should it be 1-4?
[00:06] <len-dt> I don't know that unit at all
[00:06] <ariel__> it has 4 inputs
[00:07] <ariel__> but two of them are spdif
[00:07] <ariel__> i don't use them
[00:07] <len-dt> SO do you have all you need then?
[00:07] <ariel__> i think so
[00:08] <ariel__> one more question
[00:08] <len-dt> Good. You may need to remember that hw nunbers change from boot to boot sometimes.
[00:08] <ariel__> ah ok, it is normal that?
[00:08] <len-dt> So after a boot you may need to set the device in jack again.
[00:08] <ariel__> ok
[00:09] <len-dt> some video displays have sound outputs and most web cams do too.
[00:09] <len-dt> those can mess the setup up
[00:09] <ariel__> ok
[00:09] <ariel__> i will check then
[00:10] <len-dt> there is a way of setting the device up to have a name and select the name, but I don't remember how
[00:10] <ariel__> i also have a usb midi controller, a keyrig 49 that i use to play virtual instruments
[00:10] <len-dt> That should just work, mine does.
[00:10] <ariel__> how do i set it up?
[00:10] <ariel__> i have to make some moves with jack?
[00:11] <len-dt> plug it in and it should just show up in the ALSA window of connections.
[00:11] <ariel__> yes it is
[00:11] <ariel__> so its ready?
[00:11] <len-dt> If you have some stuff that uses jack midi, then run a2j to bridge them.
[00:12] <ariel__> a2j?
[00:12] <len-dt> If you can see the connector in qjackctl it is ready to use
[00:12] <ariel__> ok
[00:12] <len-dt> the connections window has two tabs called alsa and midi. a2j bridges them.
[00:13] <len-dt> So that all the midi connections in alsa show up in MIDI as well
[00:13] <ariel__> but i have to make a conection or there is no need?
[00:13] <len-dt> Some synths only show in the midi panel.
[00:14] <len-dt> Click on the source (you usb midi) and the program you want to connect it to.
[00:14] <len-dt> then hit the connect button.
[00:14] <ariel__> i just opened the foo yc20
[00:14] <ariel__> it only apears at the midi tab
[00:14] <ariel__> but my keyrig its in alsa
[00:15] <len-dt> in a terminal type a2j -e
[00:15] <ariel__> yes, now appears in midi also
[00:15] <ariel__> a2j
[00:16] <len-dt> click on the triangle
[00:16] <ariel__> yes
[00:16] <len-dt> You should see you midi IF
[00:16] <ariel__> midi through
[00:17] <len-dt> di you start a2j with the -e switch?
[00:17] <ariel__> yes
[00:17] <ariel__> i typed what you told me
[00:17] <len-dt> odd.. normally that works.
[00:18] <ariel__> what is supposed to happen?
[00:18] <len-dt> a2j should have both through and your IF in the MIDI tab
[00:19] <ariel__> oh
[00:19] <ariel__> can it be fixed?
[00:19] <len-dt> I am sure it can
[00:20] <len-dt> It is just that it just works for me :)
[00:20] <ariel__> so what should i do?
[00:21] <len-dt> I would try restarting a2j first
[00:21] <ariel__> ok
[00:21] <len-dt> you may have to stop it first
[00:21] <ariel__> yes
[00:22] <ariel__> how?
[00:22] <len-dt> a2j_control exit
[00:22] <ariel__> ready
[00:23] <len-dt> try a2jmidid -e
[00:24] <ariel__> error!
[00:24] <len-dt> opps.
[00:25] <ariel__> it says a2j_alsa_connect_from: can't subscribe to 16:0
[00:25] <ariel__> resource temporary unavailable
[00:25] <ariel__> port skipped: keyrig 49
[00:25] <len-dt> Instead of a2j lets try the jack midi driver.
[00:25] <ariel__> ok
[00:26] <len-dt> maybe do a killall -9 a2j just to be sure.
[00:26] <len-dt> then open the qjackctl setup again
[00:27] <len-dt> at the bottom, there is a midi driver box that right now says none
[00:27] <ariel__> i'm there
[00:27] <len-dt> it used to be on the left bottom but I see mine is on the right
[00:27] <ariel__> yes, in my case it is in raw
[00:28] <ariel__> maybe that is why a2j didnt work
[00:28] <len-dt> Ya.
[00:28] <ariel__> i will try again
[00:28] <ariel__> nop
[00:29] <ariel__> still doesnt who if
[00:29] <ariel__> midi if
[00:29] <len-dt> RAw should have already put your midi port in the MIDI tab with out a2j
[00:30] <ariel__> lets see
[00:30] <ariel__> midi capture
[00:30] <ariel__> 1 and 2
[00:31] <len-dt> One may be the through. Jack doesn't give nice labels like a2j
[00:33] <len-dt> They are numbered in the order they apear in the alsa tab
[00:34] <ariel__> in the output tab or input tab?
[00:36] <ariel__> on my left i have the output ports
[00:36] <ariel__> it says 14:Midi through
[00:36] <ariel__> 16:KeyRig 49
[00:37] <ariel__> 20:Fast track pro
[00:37] <ariel__> on my right just 14:midi through and then 20: fast track pro
[00:44] <len-dt> I'm sorry, I will have to go (family outing) do try #opensourcemusicians
[00:44] <len-dt> And maybe if ailo or holstein are around they can talk to you
[00:45] <ariel__> ok
[00:45] <ariel__> thank you!