[06:52] <studio-user431> Good day all, I just want to know if this is normal. I have Intel Intel core2 quad CPU Q8200 @ 2.33Ghz with 6Gig RAM, running Ubuntu 18.10 64bit. Without any applications open besides Task Manager and Web IRC I am using 10% of my memory. This seems to be much, I have noticed drag when moving my mouse and started to investigate...is this normal?
 I using US 18.04 and yesterday I in
 Installed the backports. I feel like I have lost control. Is there any way to remove the backports and go back to vanilla 18.04 where I had control? In the past I have tended not use Jack because I have always used low latency hardware instead. Currently using Fucusrite 6i6. That is what I want to use as my main audio hardware.
 US audio controls seems to impose Jack on everything else. How can I de-link Jack completely from everything else! Driving me nuts. The volume controls on my (typing) keyboard no longer control the volume in the US mixer.
[12:43] <Limuxic> @studiobot: If you install pulseaudio-module-jack you can control the behaviour of qjack through the pulse audio app (pavucontrol).
 @Chris [Installed the backports. I feel like I have lost control. Is there any way to re …], What is the command to do that? Thanks.
[12:53] <Limuxic> I really don't know what you mean by 'backports'
 It is a ppa I installed that enables software from later versions of US to be installed.
[13:01] <Limuxic> software-properties-gtk
[13:01] <Limuxic> go to the second tab "other software" and untick all sources that you don't want to use
[13:05] <mrz80> Has there been any discussion of folding VCV Rack into the distribution when it hits 1.0? It's just about the coolest thing I've run across in years. :D
 @Limuxic [<Limuxic> go to the second tab "other software" and untick all sources that you …], Thanks. Done. Anyway I can remove US Controls and revert to the default 18.04 audio controls?
[13:28] <Limuxic> I don't that, haven't done it
 I have removed US Controls via the GUI software manager. Back to normal. Phew! I am sure the US controls are greAt but I need to study them before I dive in. What was disconcerting was that my USB audio interface Focusrite 6i6 had disappeared from the menus.
 @Chris [I have removed US Controls via the GUI software manager. Back to normal. Phew! I …], All you had to do was click "stop Jack" and it would've been back to normal.
 Tried that but didn't allow me to regain control. And on rebooting, Hack was activated again.
 Jack was activated again.
 @Chris [Jack was activated again.], Did you make sure that the checkbox for "start jack at system start" was deselected after clicking "Stop Jack"?
 We need to troubleshoot this since 1) we develop Ubuntu Studio Controls, and 2) we can't support systems without it for reasons I can't get into right now.
[14:55] <Eickmeyer> OvenWerks: Might need your help here.
 Yes. I deselected Start Jack at System Start but it was enabled after rebooting.
 @Chris [Yes. I deselected Start Jack at System Start but it was enabled after rebooting.], How do you know?
 It was checked in the settings
 Reason I ask is because that checkbox is always selected by default. Ubuntu Studio Controls does not show the state Jack is in.
 Chris That's normal and exepected, but does not mean Jack was running.
[15:09] <OvenWerks> cat ~/.config/autojack
[15:10] <OvenWerks> The first line if you have autostart turned off should be JACK=false
[15:11] <OvenWerks> If you Start jack that will turn it on. Stop jack should turn it off
 Chris ^
[15:12] <OvenWerks> The system should start in the state it was shutdown.
 Chris I urge you to work with us here. If this is a bug, we need to get it fixed ASAP since Beta Freeze is coming up in just over a week.
[15:14] <OvenWerks> The keyboard volume up and volume down should still work as well, but there was someone else who found the default keyboard shortcuts for volume up and down were not correct being set to device 1 rather than the default device.
[15:14] <OvenWerks> That is fixable.
[15:14] <OvenWerks> Eickmeyer: That is something we should fix in the xfce default config (system wide)
[15:15] <Eickmeyer> OvenWerks: Is that something we can put in -default-settings?
[15:15]  * OvenWerks keeps forgetting... having a KB so old it has an XT/AT switch
[15:15] <OvenWerks> I think so we can.
[15:16] <Eickmeyer> If you can commit the config, I'll get it uploaded.
[15:17] <OvenWerks> Eickmeyer: I don't have a keyboard with volume controls.
[15:18] <Eickmeyer> Eek... daang. Okay, if you commit the config, I'll test it and, if it works, get it uploaded. :)
[15:19] <OvenWerks> Eickmeyer: what are the key codes?
[15:20] <Eickmeyer> OvenWerks: I'd have to check. Right now I'm working on getting my son out the door.
[15:21] <OvenWerks> Me too.
[15:21] <Eickmeyer> Let's take this to -devel so we can keep @Chris troubleshooting his problem with us a separate conversation.
[16:12] <Eickmeyer> mrz80: VCVRack isn't in our current plans.
[16:13] <Eickmeyer> Also, I'm worried about the licenses since some of the components used aren't compatible with the GPL.
[16:13] <Eickmeyer> Or, may not be compatible.
[16:40] <mrz80> Eickmeyer:  Ah, ok. Just curious.
[17:30] <carbonzero> I'm here to help answer any questions (granted it's within my horizon of knowledge) for anyone.
 Thank you all for your help. … I suppose I must be the classic refugee from Windows who likes the idea of floss but who is dependent on GUI and limited when it comes to a terminal, apart from copying and pasting commands.  … I am happy to help refine the user experience of US controls. … A,l complication might be that I am using a new P
[20:54] <studiobot> C system. I am still testing it.
 @Chris [Thank you all for your help. … I suppose I must be the classic refugee from Windo …], You're welcome. We just made plans to make an indicator for whether or not Jack is running, but it won't be for the 19.04 release. Thing is, Ubuntu Studio Controls doesn't run in the background, it simply tells Jack whether or not to ru
[21:00] <studiobot> n in the background and when (on-demand vs at boot).
 It also figures out whether or not the pre-configuration is done for lowlatency audio and fixes it for you. It basically eliminates the need for a lot of tools and terminal configuration that was required before, which simplifies not only the process for the user, but for those of us supporting it.