[00:22] <Tooncenator> holstein - this is UncleJed - someone nabbed my nick. lol.
[00:23] <Tooncenator> Have been following your directions - lsusb sees it. aplay and arecord both see it just fine. Jack server starts without any errors. I have disabled internal audio.
[00:24] <Tooncenator> i opened audacity, dropped in a tune, played it and can hear perfectly. I check the sound settings and the signal is definitely being sent to the m-audio box.
[00:26] <Tooncenator> Here's the part I don't get. The m-audio box only shows up on jack on the ALSA tab with a midi channel. Nothing on audio.
[00:27] <Tooncenator> So if I understand correctly, the sound I'm hearing is not actually being routed through jack - it's going straight to the box from the computer.
[00:28] <Tooncenator> Ok - i think saying that helped me think through it a bit. Doing more experimenting - will get back.
[00:32] <Tooncenator> No luck....no matter which interface i choose in the jack settings (i tried all multiple times), the only place the m-audio box shows up is for ALSA midi. No audio.
=== wook is now known as Guest67850
[04:07] <Tooncenator> Anyone know what this might mean? It was a message in qjackctl:
[04:07] <Tooncenator> (qjackctl:9526): Gtk-CRITICAL **: IA__gtk_widget_get_direction: assertion 'GTK_IS_WIDGET (widget)' failed
[04:33] <Tooncenator> holstein - does this patch information help? I'm pretty sure the Fast Track Pro is quite different than most external boxes and doesn't work as-is with qjackctl. I'm just getting nowhere with your suggestions.
[04:33] <Tooncenator> http://alsa.opensrc.org/M-Audio_FastTrack_Pro
[05:02] <OvenWerks> Tooncenator: The gtk messages are not audio related. They seem to not affect qjackctl's operation. I think it is the window manager using gtk while the application uses QT as a gui toolkit
[14:05] <Tooncenator> OvenWerks: Thank you. I suspected that, but as part of troubleshooting, I thought I'd open every possible door. Appreciate the response.
[15:08] <holstein> Tooncenator: it may not say 'maudio box' in jack or alsa
[15:09] <holstein> Tooncenator: what i do is, i'll literally eliminate the variable. i'll disable, or remove other audio interfaces.. i'll take the usb device to a *different* machine with *no* other audio devive
[15:09] <holstein> device*
[15:09] <holstein> i'll run a live iso, to remove my installed OS and config from the equation
[15:10] <holstein> i'll run on other hardware to remove my chipset drivers, and USB hardware, and motherboard, and othher hardware from the equation
[15:10] <holstein> i'll do whatever it takes to make sure i see *only* that maudio usb device
[15:10] <holstein> i'll then route *all* of the ins and outs to something i have, as i suggested, already learned about exectly how to use
[15:11] <holstein> for example, ardour, with the internal audio device. i will have already sucessfully learned to create a channel, and route my internal audio device's inputs to a channel in ardour, and record it
[15:11] <holstein> be sure you have done that, and know the proceedure, and what that should look like
[15:11] <holstein> i wouldnt expect to use audacity and jack together
[15:15] <holstein> Tooncenator: if its me, i donwload the AVlinux live iso, as well as the latest ubuntustudio, and the last LTS.. i'll just run those live, testing with *only* the one audio device
[15:16] <holstein> anything you learn from those live environments will be applicable to your installation now
=== wook is now known as Guest74117