[08:27] <BrianHechinger[m> OvenWerk1: On FFADO Studio Controls claims it's creating the pulse bridges but actually doesn't. :(
[08:28] <BrianHechinger[m> Ok, Pulse may need a kick in the butt: `AutoJack - DEBUG - Pulseaudio: Connection failure: Connection refused`
[08:49] <BrianHechinger[m> OvenWerk1: Ok, here's the status. 64/2 start and runs fine. Well, it failed once, had to switch back to 128 then back to 64 but it did eventually start up and work as expected. 32/2, however, is weird. It tries to start but can't connect to Pulse. After this start attempt studio-controls is hung and I need to `kill -9` it. Pulse is also left is a funky state and I need to restart it as well.
[08:49] <BrianHechinger[m> https://gist.github.com/bhechinger/8f4b5b2a4a0fc91b6ca17c47844310e5
[08:49] <BrianHechinger[m> at that point everything is hung
[08:51] <BrianHechinger[m> I can't `pulseaudio -k`. I need to `kill -9` both studio-controls and pulseaudio.
[09:00] <BrianHechinger[m> Ok, 64/2 works and is stable so that'll be fine. :-D
[10:07] <neff> Hello guys!I have a lame question,but...i can't upgrade my 21.10 to 22.04. Any help?
[10:08] <twbuncho[m]1> That's what I get,So I use iso clean install method
[10:09] <neff> No way man.This system a 8 years old(upgraded many times).So clean install it's not a way.
[10:10] <twbuncho[m]1> are you using sudo do-release-upgrade
[10:10] <neff> Tried it
[10:11] <neff> Say no new distro found or something like this
[10:11] <neff> do-release-upgrade -m desktop
[10:11] <twbuncho[m]1> no new release found
[10:11] <neff> not work
[10:11] <neff> Yes
[10:12] <neff> I can upgrade to dev version...but i want real LTS :D
[10:12] <twbuncho[m]1> I did not type -m deskto[
[10:12] <neff> did it
[10:14] <neff> not work
[10:16] <twbuncho[m]1> s/deskto[/desktop/
[10:16] <neff> ???
[10:53] <neff> Any advice guys?Somebody?
[10:54] <twbuncho[m]1> Normally, Short Term release version will not have new version upgrade delay
[11:04] <neff> sad
[12:08] <BrianHechinger[m> I'm so glad I started making my desktop easier to rebuild. I just did a fresh install of 22.04 (which has the benefit of not dragging all my filth with it)
[12:10] <tomreyn> neff: https://ubuntustudio.org/ubuntu-studio-22-04-lts-release-notes/ has notes on upgrading
 It's cool,but it's not work
[13:04] <neff> I follow every step from their instructions and it's keep saing no new version found
 "I follow every step from their..." <- Use USB Media Clean Install
 man it's not an option.I need upgrade.
[13:29] <neff> I don't wanna spend hours to configure everything from zero
[13:32] <BrianHechinger[m> Bah, still getting the firewire crash with FFADO. :(
[15:05] <OvenWerk1> neff, I think the upgrade may not work untill 22.04.1
[15:24] <OvenWerk1> Eickmeyer: ^^^ would that be true? is there a way to bypass that?
[15:25] <OvenWerk1> neff: you will get the dev version 22.04.0 untill 22.04.1 releases if I understand right
[15:27] <Eickmeyer> LTS -> LTS is delayed until after the release of 22.04.1, and upgrading *at all* is delayed due to a few showstopper bugs in the upgrade mechanism.
[15:27] <Eickmeyer> Also, we don't support LTS -> LTS upgrades due to the DE change.
[15:28] <OvenWerk1> Eickmeyer: in this case 21.10 to 22.04
[15:29] <Eickmeyer> OvenWerk1: Yeah, there's still some upgrade items that need to be worked out yet, that's in the Ubuntu release notes. This is why ALL release notes need to be read.
[15:29] <OvenWerk1> neff: so the real answer is upgrade is not working yet
[21:08] <jazzslag> hi, how do I restart Ubuntu Studio Controls from the command line? 
[21:09] <jazzslag> I've used the autojack command but I'm wondering if there might be another 
[21:25] <OvenWerk1> jazzslag: studio-controls for any recent version will start the gui.
[21:26] <OvenWerk1> studio-controls will start autojack if it is not already running
[21:26] <OvenWerk1> if you actually have ubuntu-studio-controls... you should probably upgade. That is a number of years old by now
[21:43] <jazzslag> thanks but I meant restarting jack while it is already running 
[21:46]  * twbuncho[m]1 uploaded an image: (382KiB) < https://libera.ems.host/_matrix/media/r0/download/matrix.org/hBJLYOQMQtEvngQAgXtiWECB/image.png >
[21:47] <twbuncho[m]1> Start or Restart JACK,no need command
[21:48] <jazzslag> I know but I want an automated solution - I'm trying to do it via a Python script as part of a larger system 
[22:11]  * twbuncho[m]1 uploaded an image: (729KiB) < https://libera.ems.host/_matrix/media/r0/download/matrix.org/xBqkwAXQpvIijOyCZdmBRqDR/image.png >
[22:12] <twbuncho[m]1> Small bug of Light/Dark Change
[22:14] <jazzslag> that's lovely 
[22:14] <jazzslag> if anyone knows this command it'd be great lol 
[23:11] <Eickmeyer> jazzslag: There's no command line for studio-controls as it's only a gui to control autojack.
[23:12] <Eickmeyer> twbuncho[m]1: That is a known bug with gtk/qt. Simply go to System Settings -> Appearance -> Colors, go to a different color scheme, apply, go to your desired color scheme, click apply again. That's a workaround, but it's a bug with Plasma, not ours.
[23:13] <jazzslag> so the autojack command might be my best bet? 
[23:13] <Eickmeyer> jazzslag: autojack simply parses a config in ~/.config/autojack and also has no command line.
[23:14] <Eickmeyer> The entire point of studio-controls and autojack is to make it easier for users to use Jack and not have to use the terminal.
[23:15] <jazzslag> i get that, and it definitely solves audio problems I was experiencing with 'vanilla' ubuntu
[23:16] <Eickmeyer> In the future I hope to make a Plasma widget that can start/stop Jack from the systray.
[23:17] <Eickmeyer> But OvenWerk1 is the primary dev.
[23:17] <Eickmeyer> On studio-controls.
[23:19] <jazzslag> the main reason is that the program i'm running (a threaded python program with overlapping playback of samples) seems to be causing xruns 
[23:20] <Eickmeyer> jazzslag: You don't have to run studio-controls at the same time Jack is running. Once it's running, you can safely close it.
[23:21] <jazzslag> i get that also, all i want to do is restart the jack server from the command line 
[23:21] <Eickmeyer> Then what I'd do if I were you is learn how to use Jack directly from the command line.
[23:22] <Eickmeyer> https://jackaudio.org is a good place to start.
[23:23] <Eickmeyer> Because, to be honest, I don't know how myself.
[23:25] <jazzslag> lol I was really hoping to avoid getting into the guts of Jack. appreciate the help though 
[23:26] <Eickmeyer> No prob. BTW, I don't know of a single jack controller that provides a command-line control beyond dbus interfaces, which is its own ball of wax.
[23:31] <jazzslag> I had a feeling this would be tricksy, I'll have a think, there must be a workaround  
[23:33] <Eickmeyer> Most people, when they need a custom solution, build custom scripts, which gets very tricky and builds a lot of trial/error. If you're getting xruns, my guess is studio-controls is probably not the culpret since it's literally the process running Jack.
[23:34] <Eickmeyer> If you have a USB interface, you might try making sure you're using these settings: https://wiki.linuxaudio.org/wiki/list_of_jack_frame_period_settings_ideal_for_usb_interface
[23:34] <Eickmeyer> Rather, it's not the process running Jack.
[23:35] <Eickmeyer> It provides literally zero overhead.
[23:37] <Eickmeyer> !morehelp
[23:43] <jazzslag> Ah great thanks for the link, (samplerate/buffersize)*period might be the culprit, I'll try it tomorrow. My orig hunch was that it was a problem with playing multiple audio streams via python threading
[23:44] <Eickmeyer> jazzslag: Yeah, likely not. While studio-controls is written in Python, it isn't running if the gui isn't running. It was written in such a way that it has no overhead.