[00:47] <guiverc> Eickmeyer, fyi:  BDLL have publically stated Ubuntu Studio will be covered next week
[02:04] <Eickmeyer> guiverc: Thanks!
[02:17] <SoundShaman> is there a way to set a host mask on freenode
[02:17] <Eickmeyer> SoundShaman: You'd have to ask #freenode.
[02:17] <Eickmeyer> Ubuntu members are given masks.
[02:18] <SoundShaman> oh ok
[02:18] <SoundShaman> thnx
[02:18] <SoundShaman> hi again Eickmeyer btw
[02:18] <Eickmeyer> Hi!
[02:18] <SoundShaman> how ru
[02:18] <Eickmeyer> Doing ok. Trying to spend some time with my family, just jumped-in to check on things. :)
[02:18] <SoundShaman> cool right on
[02:19] <SoundShaman> i been trying to figure out how to mix tracks together from seprate instruments to make one song on Audcaity
[02:19] <SoundShaman> audacity
[02:19] <SoundShaman> lots of reading
[02:20] <Eickmeyer> Yep. Should probably take it to #ubuntustudio-offtopic for chit-chat since this is the support channel, but I'm about to hop off.
[02:20] <SoundShaman> oh yeah my bad
[02:20] <SoundShaman> laterz
[02:20] <Eickmeyer> o/
[05:59] <OvenWerks> Eickmeyer: fyi, audacity is not made for tracking instrument. qtractor or Ardour are. (even the video editors like blender or kdenlive would do a better job.... and most people who use blender for video still use ardour or such for sound staging.
[05:59] <OvenWerks> Audacity is great for audio editing though.
[14:49] <t0rg> On my upgrade to focal fossa the hydrogen package seems to have gone missing. Any ideas on the easiest way to bring it back?
[15:08] <OvenWerks> sudo apt install hydrogen?
[15:08] <t0rg> Ah, for some reason i had an older version of hydrogen-data from another repo lying around. Removing it apt install hydrogen sucessfully installed the new one.
[15:08] <OvenWerks> that would do it...
[15:12] <t0rg> ..from kxstudio, probably added that as a source ages ago
[15:13] <sirriffsalot> OvenWerks: I'm liking the overall feel of Ubuntu Studio without kxstudio repos, but one thing that really is a ridiculous pain in the ass is the fact that I can't watch and listen to web-browser audio while US-c is the one running the audio-show...
[15:14] <sirriffsalot> Like now for instance, I have three different ardour sessions running, as I'm sorting through a lot of files, and I'd like to just take a break and listen to an interview. I'll have to close everything down, shut off US-c and let pavucontrol take over again just to watch a video online in order to hear the audio.. surely there must be a solution to this which is more practical?
[15:15] <OvenWerks> use pulse bridging...
[15:15] <OvenWerks> you don't have to close anything
[15:16] <OvenWerks> That is the way controls does things by default
[15:18] <OvenWerks> if you can hear your daw, then with pulse bridging you can hear your browser
[15:19] <sirriffsalot> OvenWerks: well the pulse bridge is happening, the chromium-section in the playback tab of pavucontrol is showing audio happening, but I can't route it/see it going anywhere
[15:19] <sirriffsalot> Even in carla
[15:20] <OvenWerks> in pavucontrol it should show a jacksink. Do you see that?
[15:20] <sirriffsalot> Uh, wait, wtf... now it works. What on earth happened
[15:21] <sirriffsalot> Seriously I didn't change anything, lol. Hang on
[15:21] <sirriffsalot> OvenWerks: huh, odd... seems to be working now. I'll keep an eye on this and get back to you if it happens again :)
[15:22] <OvenWerks> ok
[15:22] <OvenWerks> as a note, allowing pulse to be able to see any device while bridged to jack can cause jack to crash on ardour export
[15:23] <OvenWerks> it also cause the odd xruns all the time.
[15:23] <OvenWerks> That is why controls removes pulse's ability to see alsa devices while jack is running.
[15:24] <sirriffsalot> Depends on your buffer size and periods I imagine, my beast of a machine has had no trouble with that in the past :)
[15:24] <sirriffsalot> But usually I shut down everything else when doing an export
[15:24] <OvenWerks> nope does not depend on buffer size.
[15:24] <OvenWerks> pulse will try to use the sync of even an unused device it can see.
[15:25] <sirriffsalot> If you have a lower buffer size, that makes for more likelyhood of xruns in general, in my experience? At a certain point a machine just isn't good enough to cope with the processing speeds you're demanding
[15:25] <OvenWerks> because the two devices are not in sync it will (_will_) cause xruns every time that device does not irq in time
[15:25] <sirriffsalot> Ah, well yeah sure
[15:26] <OvenWerks> this is really a bug in the pulse-jack bridge.
[15:26] <OvenWerks> I would think a crash whle exporting would be the bigger problem though
[15:27] <OvenWerks> because pulse is syncing itself to some unused device, it causes trouble when jack is put in freerun mode.
[15:28] <OvenWerks> No one is going to work on pulse at this point though, because it looks like pulse will be replaced by pipewire.
[15:28] <OvenWerks> possibly jack will be as well if things go well.
[15:30] <sirriffsalot> OvenWerks: jack will be replaced? What on earth for?
[15:32] <OvenWerks> I think the idea is that jack will be a part of pipewire. That is with pipewire running, a jack client will see jack running
[16:10] <sirriffsalot> OvenWerks: why fix or change jack, is it not working optimally enough?
[16:35] <OvenWerks> sirriffsalot: pipewire should not be either better or worse than curent jack. but system integration should be better.
[16:35] <Treskjeg> I've got a Focusrite pro 40 set up with firewire, but I only see 2 system audio inputs in Jack. Ubuntu Studio 20.04... any ideas?
[16:36] <OvenWerks> Treskjeg: not enough information for me to give any suggestions
[16:36] <OvenWerks> I am not familiar with the device at all.
[16:36] <sirriffsalot> Treskjeg: you need to configure jack to see your device's respective ins/out?
[16:37] <OvenWerks> first question would be if you are using the device as jack master.
[16:37] <Treskjeg> Yes, using as jack master. Or attempting to. When I select the firewire driver in jack, it doesn't let me select anything other than "default" for device.
[16:38] <sirriffsalot> Treskjeg: close controls for now, open up qjackctl instead and see there what you can do, you have a lot more options
[16:38] <sirriffsalot> But that option should be in US-c
[16:38] <sirriffsalot> Under "Channel Count"
[16:39] <OvenWerks> controls does not show firewire at all in 20.04.
[16:39] <OvenWerks>  it expects firewire devices to show as alsa devices
[16:39] <sirriffsalot> OvenWerks: Treskjeg oh, lol. I misunderstood then
[16:40] <OvenWerks> So i expect using qjackctl
[16:41] <Treskjeg> Yup, using qjackctl. Selecting firewire as the driver there empties the interface options to just "default".
[16:42] <Treskjeg> Selecting "Alsa" as the driver shows three options for the Focusrite Pro-40, but running jack with any one of these still has only two inputs in jack.
[16:43] <OvenWerks> I do not know how qjackctl deals with FW. I know that the alsa fw modules have to be unloaded before the ffado drives can be loaded
[16:44] <OvenWerks> I don't know if qjackctl somehow does this or if the user needs to blacklist the snd-* firewire modules first.
[16:45] <Treskjeg> I had read we no longer have to blacklist snd-dice, but if we still need that in 20.04, that would help... I'll try that next.
[16:46] <Treskjeg> As far as I know, the FireWire driver in Jack is really just Alsa's FireWire utils.
[16:46] <OvenWerks> Treskjeg: my problem is that I know pretty much nothing about fw devices. I got one last year to play with but so far it does not even show up as anything :P
[16:47] <OvenWerks> I do not think that is true though qjackctl may deal with it that way.
[16:47] <OvenWerks> jack itself deals with fw in a different way
[16:48] <OvenWerks> qjackctl may detect a fw as alsa device and silently use the alsa backend
[16:48] <OvenWerks> but I don't really know.
[16:49] <OvenWerks> This is a big part of why support in ubuntustudio for firewire devices is not here. There is no one who knows enough to help people.
[16:50] <sirriffsalot> Treskjeg: if you use qjackctl you'll get an error message that's pretty detailed, that might give some hints. Link a pastebin to the error output :)
[16:50] <sirriffsalot> Treskjeg: as the device should pop up there at least :-S
[16:51] <sirriffsalot> Treskjeg: did you google to check if some drivers are required for this particular device in GNU/Lin?
[16:52] <Treskjeg> I've attempted that. Didn't find much that was useful. Everything I did find said it should work through Alsa, but this device has 8 inputs and I'm only ever seeing 2 in Jack no matter which of the 3 instances of it I pick from the dropdown.
[16:52] <Treskjeg> I'll get to work on deeper googling and keep an eye out for the error messages, and I'll be back then to run through this here if I need to.
[16:53] <OvenWerks> sorry to not be much help...
[16:53] <Treskjeg> No worries; helped some anyway, especially with regards to maybe having to blacklist snd-dice.
[16:54] <OvenWerks> Some of the arch docs on that may be helpful
[16:54] <OvenWerks> They at least have a list of modules to BL
[19:06] <augugusto> hey. the ubuntu studio web pag does not use https for the downloads or the checksums. does anyone have an iso and can send me the checksum?
[19:26] <Eickmeyer> augugusto: Known problem, but even the source of the images or the checksums doesn't use https (cdimage.ubuntu.com). This is beyond our capacity to fix. You *can* trust the checksums on cdimage.ubuntu.com as those are accurate, and nobody (not even myself) has access to that server.
[19:27] <Eickmeyer> augugusto: Every flavor of Ubuntu has gets the checksums from the same source, so if you can't trust ours, you can't trust anybody.
[19:27] <augugusto> no but if you have an image that you've used, you can send me the checksum so at least i can be sure i have the same image as you
[19:27] <Eickmeyer> augugusto: https doesn't work that way. The site hasn't been compromised. You can trust it. I'm not going to go out of my way to provide you information that's already published.
[19:28]  * Eickmeyer is the Ubuntu Studio leader
[19:30] <Eickmeyer> teward: If you're around, can you explain to augugusto why they shouldn't be paranoid about the lack of http on cdimage.ubuntu.com?
[19:31] <teward> umm?
[19:31] <teward> you mean https?
[19:31] <Eickmeyer> Yes.
[19:31] <teward> it's Canonical's faul
[19:31] <teward> t
[19:31] <teward> also
[19:31] <teward> there's a set of official cdimage mirrors as well
[19:31] <teward> and distributiong a cdimage.ubuntu.com SSL cert to every mirror host will be problematic
[19:32] <teward> becasue they also need to share a privkey for that which in turn *compromises* the key
[19:32] <teward> it's a logistics challenge to support that across the mirrors
[19:32] <teward> it's not compromised though
[19:32] <Eickmeyer> augugusto: So, that basically means adding https to the site would *compromise* security of the images, not enhance it.
[19:34] <teward> it also introduces its own logistics headache to manage it securely.
[19:35] <teward> augugusto: you may want to ask this question to the ubuntu mirrors team instead - this isn't an Ubuntu Studio issue it's a higher level issue that is far more wide-spread than just Studio (and not within Studio's purview to control)
[19:35] <augugusto> sorry i wasted your time. i'll go ask somewhere else. my network could be compromised. thats why i asked
[19:41] <oerheks> so https is safe. not.