[03:50] <abhi_> ok
[03:50] <abhi_> i joined just now
[05:03] <Jessedavid4> So Ovenwerks. Unless I am wrong... I think I found a driver for the Wacom tablet. For me (and this was preinstalled, I am sure): /usr/share/X11/xorg.conf.d/70-wacom.conf .
[06:40] <Eickmeyer> Jessedavid4: That's just a configuration. Drivers are in the kernel.
[06:41] <Eickmeyer> The idea is to have something that exposes command line commands in a GUI.
[06:41] <Eickmeyer> That's what OvenWerks was referring to.
[10:28] <Jessedavid4> Oh, yeah, no you're right. I knew that. Just thought that meant a driver was there. But totally understandable. Would be a lot of work to create a GUI for that, no?
[22:48] <studio-user417> Hi, I updated and ubuntu cant find my audio interface any more. How can I find the hardware and instal the propper driver again?
[22:51] <OvenWerks> no such thing as drivers in linux. How do you know Ubuntu can't find your audio device?
[22:51] <OvenWerks> What kind of audio device do you mean?
[22:52] <OvenWerks> Is it internal? USB?
[22:55] <studio-user417> Its a presonus firepod recording audio interface pluged via firewire
[22:56] <studio-user417> in sound settings, it use to be an option as a playback device and input
[22:56] <studio-user417> now it does not apear anywhere
[22:57] <OvenWerks> Ah FW, stuff. Anything I can say is second hand info.
[22:57] <OvenWerks> How big of an update? (in years)
[22:58] <studio-user417> months not years, maby 6
[22:58] <OvenWerks> a few years ago firewire code was added into ALSA directly
[22:58] <studio-user417> maybe
[22:59] <OvenWerks> A lot of people found the alsa FW modules did not work that well and so took them out and unblacklisted the old fw drivers
[22:59] <OvenWerks>  Does your device show up with aplay - or arecord -l
[23:00] <OvenWerks> updating may very well reinstall the alsa drivers
[23:01] <studio-user417> In QjackCtl/Alsa it only finds "14:Midi Trough" no presonus
[23:04] <OvenWerks> studio-user417: run: cd /tmp && wget http://jackaudio.org/downloads/adevices.sh && bash ./adevices.sh
[23:04] <OvenWerks> in a terminal and use a past site like pastebin to show us what it outputs
[23:05] <studio-user417> no it does not find the preconus interface with aplay - or arecord -l. It just lists the Ardour project files....
[23:10] <OvenWerks> I wonder if the upgrade replaced the kernel module blacklist.
[23:11] <studio-user417> benjamin@benjamin-MacPro:~$ cd /tmp && wget http://jackaudio.org/downloads/adevices.sh && bash ./adevices.sh --2019-01-12 23:08:11--  http://jackaudio.org/downloads/adevices.sh Resolving jackaudio.org (jackaudio.org)... 69.163.217.234 Connecting to jackaudio.org (jackaudio.org)|69.163.217.234|:80... connected. HTTP request sent, awaiting response... 200 OK Length: 2249 (2,2K) [application/x-sh] Saving to: ‘adevices.sh
[23:11] <OvenWerks> I wish there was still someone around who uses FW interfaces. I still use PCI devices
[23:11] <studio-user417> ah sorry w8
[23:11] <OvenWerks> use a paste site or you will find yourself kicked
[23:12] <studio-user417> sorry woking on it
[23:15] <studio-user417> https:https://pastebin.com/i/night_mode_cube.png
[23:15] <studio-user417> omg... never used this before
[23:16] <OvenWerks> Are you trying to send a screenshot? just paste the text.
[23:17] <studio-user417> benjamin@benjamin-MacPro:~$ cd /tmp && wget http://jackaudio.org/downloads/adevices.sh && bash ./adevices.sh --2019-01-12 23:08:11--  http://jackaudio.org/downloads/adevices.sh Resolving jackaudio.org (jackaudio.org)... 69.163.217.234 Connecting to jackaudio.org (jackaudio.org)|69.163.217.234|:80... connected. HTTP request sent, awaiting response... 200 OK Length: 2249 (2,2K) [application/x-sh] Saving to: ‘adevices.sh
[23:17] <OvenWerks> There should be a lot more than that
[23:18] <OvenWerks> bash ./adevices.sh might show it
[23:18] <studio-user417>   benjamin@benjamin-MacPro:~$ cd /tmp && wget http://jackaudio.org/downloads/adevices.sh && bash ./adevices.sh --2019-01-12 23:08:11--  http://jackaudio.org/downloads/adevices.sh Resolving jackaudio.org (jackaudio.org)... 69.163.217.234 Connecting to jackaudio.org (jackaudio.org)|69.163.217.234|:80... connected. HTTP request sent, awaiting response... 200 OK Length: 2249 (2,2K) [application/x-sh] Saving to: ‘adevices.
[23:18] <studio-user417> wtf...
[23:18] <studio-user417> yes there is
[23:21] <OvenWerks> https://pastebin.com/sHVMxH2u
[23:21] <OvenWerks> that is what my system looks like
[23:22] <studio-user417> ah! I see
[23:22] <OvenWerks> So you can see there are Card 0, 1 and 2
[23:22] <studio-user417> https://pastebin.com/vg9qgYEh
[23:22] <studio-user417> there we go
[23:23] <OvenWerks> so the USB is the missing device?
[23:24] <OvenWerks> It is not being used by anything right now
[23:24] <OvenWerks> Jackd bus is stopped
[23:26] <OvenWerks> if you use qjackctl it should show as hw:Audio
[23:27] <OvenWerks> If you use ubuntustudio-controls it should show up as the same
[23:27] <OvenWerks> in ubuntustudio-controls if you leave "default" as the master jack device then your USB device should just show up in the jackd graph
[23:28] <studio-user417> so QjackCtl - Setup?
[23:28] <OvenWerks> sure
[23:28] <OvenWerks> do not use the "Advvanced" tab
[23:29] <OvenWerks> *Advanced
[23:29] <studio-user417> then what do I do?
[23:29] <OvenWerks> (That only leads to pain)
[23:30] <studio-user417> in the pachbay I got nothing
[23:30] <studio-user417> patchbay
[23:30] <OvenWerks> in the Parameters tab click the down pointing triangle and select hw:Audio
[23:30] <OvenWerks> Have you tried to use the USB for input and internal for output?
[23:31] <OvenWerks> from your main menu under System, do you have Ubuntu STudio Controls?
[23:34] <studio-user417> hw:Audio Display Audio (hw2,0) or hw:Audio USB Audio ?
[23:35] <OvenWerks> yup
[23:35] <OvenWerks> use patchage to see the graph
[23:36] <studio-user417> which one? Display or USB?
[23:37] <OvenWerks> Either one should be the same
[23:37] <studio-user417> ok
[23:37] <OvenWerks> I would prefer hw:Audio though
[23:37] <studio-user417> and yes I have "Ubuntu Studio Controles"
[23:38] <OvenWerks> you can use that (as of 18.10) to start jackd
[23:40] <studio-user417> how?
[23:41] <studio-user417> I can pick user, realtime Audio and CPU Governor..
[23:42] <OvenWerks> That is a very old version of controls then
[23:42] <OvenWerks> So back to qjackctl then
[23:43] <studio-user417> ok
[23:43] <OvenWerks>  You have set the device to hw:Audio the Sample rate to 48000 or 44100? Frames to 1024
[23:44] <studio-user417> 44100
[23:44] <OvenWerks> That should be ok
[23:45] <OvenWerks> so there is a green start triangle does that work?
[23:46] <studio-user417> yes
[23:46] <OvenWerks> and "Connections shows the device?
[23:47] <studio-user417> no
[23:47] <OvenWerks> (system)
[23:48] <OvenWerks> what does the log say?
[23:48] <studio-user417> what log?
[23:49] <OvenWerks> in the qjackctl main window. there is a button right under the start button
[23:50] <OvenWerks> It probably says message/status
[23:51] <studio-user417> 23:46:08.906 Statistics reset. 23:46:08.920 ALSA connection change. 23:46:08.927 D-BUS: Service is available (org.jackaudio.service aka jackdbus). Cannot connect to server socket err = No such file or directory Cannot connect to server request channel jack server is not running or cannot be started JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock JackShmReadWritePtr::~JackShmReadWritePtr
[23:52] <OvenWerks> go down a bit to Starting jack server...
[23:53] <OvenWerks> The next line should be something like: JACK server starting in realtime mode with priority 10
[23:53] <studio-user417> Sat Jan 12 23:53:22 2019: Jack: JackSocketServerChannel::Execute : fPollTable i = 4 fd = 26
[23:55] <OvenWerks> you should see: Acquired audio card Audio2