[07:36] Eickmeyer[kde]: just decided... no more features this release. I need to work on other things. I think I will add jackdbus.log rotate because I noticed mine is rather large again and I already have the code for our logfile. [07:37] Eickmeyer[kde]: I would also like to add to convert for future proofing. [07:43] I have added a version to things so that it is possible to tell what version the config file was written by and then if the version is newer, run it through convert and any updates should happen. That way all fixes are kept in pne place not both in control and autojack. It shold be possible to run convert at any time and it will check what is hanging around and decide if it needs fixing and [07:43] do that. The nice thing is the new config method deals much better with aditions and changes than the old version. [07:46] Eickmeyer[kde]: all this to say that I hope to have a final of what I expect 2.1.0 to be by the begining of next year... should be what I think is done by the end of the week, then bug fixes for a few weeks. [16:16] OvenWerks: That sounds great. :) You've already done a TON! [16:17] OvenWerks: I'm also interested in the work with OBS you were doing before. :) [16:35] Eickmeyer[m]: All I have on v4l loopback is notes: https://paste.ubuntu.com/p/zx45RzQjNJ/ [16:46] OvenWerks: Does the latest version in focal-updates (was an SRU) fix the issue you were having in Focal? [16:46] I haven't tested [16:46] Ok. [16:46] 2000 lines + of code for controls has kept me busy :) [16:46] Thing is, even Kubuntu Focus would be interested in this, and we use backports by default there. [16:47] I feel ya. :) [16:49] Hmm, I do have the update installed though. [16:49] I must have removed the 20.10 package at least. [16:49] If it doesn't work, I might just take the version in hirsute and throw it into backports. [16:50] Even though there is an open backporting bug (#1905613). I know teward wanted to get the official backports working again, so this might be up his alley. [16:51] LP: #1905613 [16:51] Launchpad bug 1905613 in v4l2loopback (Ubuntu Groovy) "Please backport v4l2loopback 0.12.5-1 (universe) from hirsute" [Undecided,New] https://launchpad.net/bugs/1905613 [16:51] bug 1905613 [16:51] ubottu: do your job!!!! [16:51] Eickmeyer[m]: I am only a bot, please don't think I'm intelligent :) [16:51] I never do. [16:52] there are some non-bott I wonder about... [16:52] *sends Eickmeyer[m] into the abyss for not caring to test the rdeps too* [16:52] backports require the rdeps to work too :P [16:53] teward: I had nothing to do with that other than linking the right team. :P [16:54] well [16:54] it ain't moving [16:54] ever :P [16:54] until they test the rdeps [16:54] :P [16:55] teward: I just now commented as such: https://bugs.launchpad.net/ubuntu/+source/v4l2loopback/+bug/1905613/comments/3 [16:55] Launchpad bug 1905613 in v4l2loopback (Ubuntu Groovy) "Please backport v4l2loopback 0.12.5-1 (universe) from hirsute" [Undecided,New] [16:57] so basically, repeating my comment (#2 ) [16:57] :P [17:02] Yeah, because I had the bug up before you and Launchpad isn't intelligent enough to auto-refresh. [17:06] teward: So, basically it's ready for backport. Those are rsuggs. [17:06] i saw [17:06] but still [17:06] i need to see successful build logs [17:06] so i have to test some stuff [17:06] BUT [17:06] i also have other things to worry about atm [17:06] ERR:LowPriority [17:07] No worries. Didn't know if you had anything in the backports anyhow. Regardless, the bug didn't sub anyone to it and wasn't against the official package until I saw it. [17:08] In other words, reporter failed to follow procedure completely. [17:13] TIL backportpackage is a thing. My life just got WAY easier. [17:14] Eickmeyer[m]: confirm that v4l2loopback-dkms version 0.12.3-1ubuntu0.3 fixes the problem listed in my notes. [17:15] That is I can take my DLSR and make it work as a v4l2 device that will then show up in OBS. [17:16] I have not tried using it as a loopback for OBS output to allow it to work with zoom, etc. as a v4l2 device [17:17] But it seems most of the people who commented on the bug report were more interested in that and at least some of them reported success as well [17:19] OvenWerks: I agree. Thing is, this would be a killer feature for Studio to have a GUI that configures this. [17:20] Yup, but you want a separate app from controls [17:22] I don't really see its use as separate personally. It would seem that pipewire agrees [17:22] Yeah, because, for the sake of people who might only want to install the ubuntustudio-video meta, they might not want controls which pulls-in jack and a couple other things. [17:23] I guess you can put it in -controls. I'm OK with that. [17:23] I just thought it should be separate, but if you feel differently then, it's really your project. [17:23] That would be controls 2.2 or later [17:24] Ok. I guess I should've been less stubborn earlier because I would love to see this ASAP. 2.2 would be out roughly in time for 21.10. [17:25] But, I'm not going to push you. That would be bad. [17:26] There should be a way of running a separate app(let?) inside a tab I think. And then just add a main window to run that as it's own app [17:28] * OvenWerks is finding two screens is not enough :P [17:36] I'm thinking about getting a third screen as well. [17:38] Eickmeyer[m]: obs-v4l2sink (the osb plugin) does not seem to be packaged for ubuntu. [17:38] teward: No rush, but I did a successful PPA build myself. Commented in the bug. [17:39] Therefore I am guessing testing that would not be useful at this time [17:39] OvenWerks: I saw something about that in the Debian Multimedia Team email list about packaging it. [17:39] it seems there is a debian package [17:40] I might JFDI. [17:42] https://www.bountysource.com/issues/81364921-deb-plugin-is-not-installed-in-the-correct-directory [17:42] I don't know if this has been solved or not [17:43] Wow, that's an easy one to fix. [17:44] Like, low-hanging fruit easy. [17:45] OvenWerks: It was fixed. https://github.com/CatxFish/obs-v4l2sink/pull/35 [17:45] ok, but no ubuntu package? [17:48] Apparently not, but I'm looking into Debian at the moment to see if anyone has done anything in Salsa. [17:48] Anyway, the loopback itself seems to work [17:52] OvenWerks: Cool. Checking the ML, it appears as though it's to be part of the main obs-studio package. [17:53] That would make sense. It could be added to the other stream setups [18:28] OvenWerks: https://lists.debian.org/debian-multimedia/2020/11/msg00191.html [18:29] So, probably when Version 27 hits. [23:17] Eickmeyer[m]: I had not had an interest in a loopback backend for obs until I started trying to fix loopback for my dslr and saw that most complaints were from people trying to use the OBS backend. I then realized that for a Studio user that might be the more important use. So I am glad OBS is adding that. [23:18] OvenWerks: Same.