[03:42] <Eickmeyer[m]> OvenWerks: Dolphin has native sftp support too, I use it all the time.
[03:42] <OvenWerks> yes but...
[03:43] <OvenWerks> I open a directory with dolphin I can start my editor on one of the files in that remote directory not problem.
[03:44] <OvenWerks> then I want to create a new file with the editor in the same directory but I can't (unless I am missing something)
[03:45] <OvenWerks> I use the bluefish IDE mostly for my web pages. And unless it can see the directory I can't even get it to see whtever other files are in the same directory
[03:53] <OvenWerks> Eickmeyer[m]: normally there is column on the left that shows the directory I am in with the file I opened. It shows the remote directory and I can move up and down the directory tree. Open other files etc. With the file I opened in Dolphin It shows the location as ~/.cache/kioexec/krun/11785_0/index.html
[03:55] <OvenWerks> the column where the directory should be just shows the file I opened in an empty directory
[03:58] <OvenWerks> If I use the same application to open file two... it shows up in a new empty directory in another editor instead of the same one... this is a pain to work with and can be confusing when doing html pages where there may be any number of index.html files... and the editor does not show the real path.
[04:03] <OvenWerks> Eickmeyer[m]: so tghe conclusion is that a quick touchup of one file is no problem but creating a new web page set from scratch means crating it locally and copying to remote is the only sane way.
[04:21] <OvenWerks> Just simple things like adding a link or image where I would normally beable to open a browser of the remote directory from within the application and choose <that file>, I have to do by hand.
[05:01] <MauroGaspari[m]> OvenWerks  Network shares management wirh KIO in plasma is a pain point for me too. GTK DEs have m uh better network share support,  where plasma KIO is a pain to deal with. Can't work with network shares in real time, each file has to be first downloaded locally,  then when save, it will try to push it back. On top of that apps that are not KIO aware will ask you every time 2 extra confirmation dialogs,
[05:01] <MauroGaspari[m]> do you want ti upload? Do you want to overwrite? 
[05:01] <MauroGaspari[m]> You can mitigate with smb4k but that only works for SMB shares. 
[05:01] <MauroGaspari[m]> * OvenWerks  Network shares management wirh KIO in plasma is a pain point for me too. GTK DEs have much better network share support,  where plasma KIO is a pain to deal with. Can't work with network shares in real time, each file has to be first downloaded locally,  then when save, it will try to push it back. On top of that apps that are not KIO aware will ask you every time 2 extra confirmation dialogs,
[05:01] <MauroGaspari[m]> do you want ti upload? Do you want to overwrite? 
[05:01] <MauroGaspari[m]> You can mitigate with smb4k but that only works for SMB shares. 
[05:02] <OvenWerks> MauroGaspari[m]: yes that is what I find. I am using sftp though not shares
[05:09] <MauroGaspari[m]> Yeah same for all the network protocols you can use with dolphin, sadly. The main reason that prevents me from using plasma full time. In my job I need to constantly access and work with webdav, sftp, smb, nfs shares and plasma makes it do much clunky so I give up and go back to GTK based DEs. Mostly ubuntu budgie because the team there cares a lot of great defaults and a DE that gets out of my way and
[05:09] <MauroGaspari[m]> let's me focus on work.
[05:09] <MauroGaspari[m]> Thanks to you guys i can still use studio installer on any ubuntu flavor 😍
[05:50] <OvenWerks> Eickmeyer[m]: I see you have already started a studio-controls wiki, good :) I am thinking that while I have all my sw pages on my own site, having them in the github repo would be better in the long run.
[05:51] <OvenWerks> There are two ways to do this, A) include a docs directory and put the website there. B) create a branch in the same repo and put it there.
[05:52] <OvenWerks> The advantage of using a docs directory is that the user will end up with the website locally on their box and can refer to it without being on line.
[05:54] <OvenWerks> If it was installed in the right place, the application could even have a button that opened a browser with it. This could replace the outdated and pretty useless help button there now.
[06:01] <Eickmeyer[m]> OvenWerks: Yes, I've actually been meaning to move the screenshots into the wiki, right now they're hosted by the Ubuntu wiki. Just so much documentation to do. BTW, Mauro Gaspari has volunteered to help with documentation, so perhaps he could be of assistance?
[06:05] <OvenWerks> The sreen shots are old :)
[06:06] <MauroGaspari[m]> OvenWerks: Eickmeyer sure, you guys know where to find me. Let me know how I can be of help. Just not a master audio wizard so gotta keep that in mind. 😅 
[06:07] <OvenWerks> MauroGaspari[m]: I am going to set up a "website" in a docs directory
[06:07] <OvenWerks> So a standard pr will work.
[06:07] <Eickmeyer[m]> Mauro Gaspari: It's just a matter of describing what each piece of the interface does.
[06:07] <Eickmeyer[m]> You can use the items I've already written.
[06:07] <OvenWerks> (actually I think it would for the wiki too)
[06:08] <MauroGaspari[m]> ah so I think it is similar to what we do for openconnect server yes? basically markdown documents get uploaded to gitlab, and then there is some automagic process that organizes the documents in a web page. something like that?
[06:08] <Eickmeyer[m]> Pretty much, except it can all be done from the github page. github.com/ovenwerks/studio-controls
[06:09] <Eickmeyer[m]> You can simply fork it and change it on the site, no need to learn a bunch of git stuff.
[06:09] <OvenWerks> MauroGaspari[m]: I am less sure of the wiki but the docs would be a sort of stanard webpage layout.
[06:10] <OvenWerks> Eickmeyer[m]: did the fix I put in fix the start when off problem for you?
[06:10] <Eickmeyer[m]> OvenWerks: The build is installing now. It's amazing how fast Launchpad is this time of night. hehe
[06:12] <OvenWerks> MauroGaspari[m]: I wanted to do more of a paged manual than the one page wiki is.
[06:12] <Eickmeyer[m]> OvenWerks: So far so good. I'll let you know if that changes.
[06:12] <OvenWerks> I think each tab or even section of tab should have its own page
[06:26] <OvenWerks> Eickmeyer[m]: this is not as good as yours but it works MauroGaspari[m] you can see to and give direction: https://ovenwerks.github.io/studio-controls/
[06:27] <Eickmeyer[m]> OvenWerks: Yeah, I saw that. It's definitely a good start.
[06:27] <OvenWerks> MauroGaspari[m]: Eickmeyer[m] we can put the web page here and then it ends up in the package too I would guess
[06:27] <OvenWerks> Eickmeyer[m]: the difference is that it is now hosted on github
[06:28] <Eickmeyer[m]> OvenWerks: Yeah, but since it's not packaged it's not a big deal.
[06:28] <Eickmeyer[m]> It could become docs, but yeah, I don't see the point.
[06:28] <OvenWerks> Eickmeyer[m]: why would it not be packaged?
[06:29] <Eickmeyer[m]> OvenWerks: The website? Well, like I said, it could be made into a doc installation.
[06:29] <OvenWerks> I would guess once someone had it set up they would likely never look at the docs again :)
[06:29] <Eickmeyer[m]> OvenWerks: Realistically, how often do you reference local docs?
[06:30] <OvenWerks> or any docs
[06:30] <Eickmeyer[m]> Yeah, kinda my point. Most people look at websites for docs, or manpages for command line utilities.
[06:31] <MauroGaspari[m]> actually I have already a ton of new screenshots for both 20.04 and 20.10 that I used for FPL articles. very easy for me to simply re-upload. 
[06:32] <OvenWerks> The image on that page is from ubuntustudio 18.04 (32bit)
[06:33] <OvenWerks> I was working on my laptop
[06:33] <Eickmeyer[m]> OvenWerks: Yeah, I figured. I can easily grab screenshots of each page if you want. Just can't this very moment.
[06:33] <OvenWerks> if MauroGaspari[m] has already got them that would be fine.
[06:34] <OvenWerks> Eickmeyer[m]: so you would prefer if the docs directory did not install when make is run?
[06:35] <OvenWerks> (not sure where I would install it anyway)
[06:35] <Eickmeyer[m]> OvenWerks: We don't even run make for the Ubuntu package.
[06:35] <Eickmeyer[m]> Make kinda.... fails with the Ubuntu package.
[06:35] <OvenWerks> :)
[06:36] <Eickmeyer[m]> OvenWerks: But, it'd be /usr/share/doc
[06:36] <OvenWerks> because make with no parameters does nothing
[06:36] <Eickmeyer[m]> Specifically /usr/share/doc/studio-controls
[06:36] <Eickmeyer[m]> Well, with Debian packaging, the makefile is kinda pointless anyhow.
[06:36] <Eickmeyer[m]> It's able to pick stuff up regardless.
[06:36] <Eickmeyer[m]> Besides, there's no code compilation.
[06:37] <OvenWerks> yupe
[06:38] <Eickmeyer[m]> I did, however, have to override dh_auto_build and dh_auto_install because debhelper wants to use the makefile since it merely exists.
[06:40] <OvenWerks> I guess I was hoping it would matter because make and make install works
[06:40] <OvenWerks> make doesn't _do_ anything, but it doesn't fail either
[06:45] <MauroGaspari[m]> OvenWerks: let me know when and where you need the screenshots. I got local copies of all those on my computers. If you prefer to upload to the right place I can share my nextcloud folder with you. anything that works best for you is ok.
[06:48] <OvenWerks> ok
[07:02] <OvenWerks> Eickmeyer[m]: if we want to make the web page not go into the downloaded tarball, we can make a branch which includes docs and leave it out of master. The wiki is fine but has the github header on top. A webpage looks better if not.
[07:05] <OvenWerks> Eickmeyer[m]: your wording and setup is better than mine (first paramgraph for sure in mine is not good.
[07:05] <Eickmeyer[m]> OvenWerks: Yeah. A branch is probably a good idea for the webpage.
[07:06] <OvenWerks> OK, might be a few days till I get to it
[16:39] <Eickmeyer[m]> OvenWerks: Looks like latest tag fixes the jack autostart on USB connect.
[17:12] <OvenWerks> Eickmeyer[m]: good
[17:14] <OvenWerks> Eickmeyer[m]: I have taken your wiki page and stolen most of your text for the home page: http://www.ovenwerks.net/software/controls/index.html
[17:14] <Eickmeyer[m]> Steal away.
[17:16] <OvenWerks> I learned html 20 years ago, so CSS is not something I have learned. If there is a way to make things look less "dull" I am all for it.
[17:19] <Eickmeyer> Yeah, I'm not good with CSS either.
[17:19] <Eickmeyer> !studio-controls
[17:20] <Eickmeyer> !studio controls is <reply> Studio Controls is the application through which audio is configured in Ubuntu Studio. It configures Jack, sets the CPU governor, and ensures the user has realtime audio permissions. For more info, see !jack and http://www.ovenwerks.net/software/controls/index.html
[17:20] <Eickmeyer> !studio-controls is <reply> Studio Controls is the application through which audio is configured in Ubuntu Studio. It configures Jack, sets the CPU governor, and ensures the user has realtime audio permissions. For more info, see !jack and http://www.ovenwerks.net/software/controls/index.html
[17:21] <Eickmeyer> Can't do it from here, standby...
[17:26] <OvenWerks> Eickmeyer[m]: the final home page will be on github, the one on ovenwerks is just my quick so I can look at it without commit/push
[17:27] <OvenWerks> https://ovenwerks.github.io/studio-controls/
[17:27] <Eickmeyer> OvenWerks: Oh, ok.
[17:27] <Eickmeyer> Still, ubottu is being a jerk and isn't recognizing my edit perms.
[17:27] <OvenWerks> :P
[17:29] <Eickmeyer> ubottu: no, studio-controls is <reply> Studio Controls is the application through which audio is configured in Ubuntu Studio. It configures Jack, sets the CPU governor, and ensures the user has realtime audio permissions. For more info, see !jack and https://ovenwerks.github.io/studio-controls/
[17:30] <Eickmeyer> Somehow my edit perms are gone. smh
[17:32] <Eickmeyer> There we go.
[17:32] <Eickmeyer> !studio-controls
[17:33] <Eickmeyer> Helps to have the ops team helping.
[20:53] <OvenWerks> Eickmeyer: I think the QASMixer button shold be a dropdown with a list of devices... maybe after next release.
[20:53] <Eickmeyer> OvenWerks: Yeah, probably.
[21:00] <RikMills> Eickmeyer: seems to be some breakage due to only partial migration of Frameworks 5.77.0. e.g. systemtray things awol, krunner not working. it will fix itself when it all migrates, but slow slow tests make that hard to do an ETA
[21:00] <RikMills> FYI in case anyone reports
[21:06] <Eickmeyer[m]> RikMills: Awesome, thanks for the heads-up, and Rick Timmis says hi.
[21:27] <RikMills> np
[21:27] <RikMills> sorry for the breakage
[23:00] <OvenWerks> MauroGaspari[m]: looking at https://frontpagelinux.com/tutorials/ubuntu-studio-20-10-audio-setup-tutorial/
[23:00] <OvenWerks>  MauroGaspari[m]: the images are all out of date
[23:04] <OvenWerks> MauroGaspari[m]: where I am at so far: http://www.ovenwerks.net/software/controls/index.html
[23:39] <MauroGaspari[m]> <OvenWerks " Mauro Gaspari: the images are a"> I took all of those screenshots using 20.10 fresh install. 
[23:40] <MauroGaspari[m]> <OvenWerks "Mauro Gaspari: where I am at so "> Checking