[00:47] Eickmeyer, fyi: BDLL have publically stated Ubuntu Studio will be covered next week [02:04] guiverc: Thanks! [02:17] is there a way to set a host mask on freenode [02:17] SoundShaman: You'd have to ask #freenode. [02:17] Ubuntu members are given masks. [02:18] oh ok [02:18] thnx [02:18] hi again Eickmeyer btw [02:18] Hi! [02:18] how ru [02:18] Doing ok. Trying to spend some time with my family, just jumped-in to check on things. :) [02:18] cool right on [02:19] i been trying to figure out how to mix tracks together from seprate instruments to make one song on Audcaity [02:19] audacity [02:19] lots of reading [02:20] 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] oh yeah my bad [02:20] laterz [02:20] o/ [05:59] 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] Audacity is great for audio editing though. [14:49] 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] sudo apt install hydrogen? [15:08] 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] that would do it... [15:12] ..from kxstudio, probably added that as a source ages ago [15:13] 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] 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] use pulse bridging... [15:15] you don't have to close anything [15:16] That is the way controls does things by default [15:18] if you can hear your daw, then with pulse bridging you can hear your browser [15:19] 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] Even in carla [15:20] in pavucontrol it should show a jacksink. Do you see that? [15:20] Uh, wait, wtf... now it works. What on earth happened [15:21] Seriously I didn't change anything, lol. Hang on [15:21] 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] ok [15:22] 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] it also cause the odd xruns all the time. [15:23] That is why controls removes pulse's ability to see alsa devices while jack is running. [15:24] 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] But usually I shut down everything else when doing an export [15:24] nope does not depend on buffer size. [15:24] pulse will try to use the sync of even an unused device it can see. [15:25] 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] because the two devices are not in sync it will (_will_) cause xruns every time that device does not irq in time [15:25] Ah, well yeah sure [15:26] this is really a bug in the pulse-jack bridge. [15:26] I would think a crash whle exporting would be the bigger problem though [15:27] because pulse is syncing itself to some unused device, it causes trouble when jack is put in freerun mode. [15:28] No one is going to work on pulse at this point though, because it looks like pulse will be replaced by pipewire. [15:28] possibly jack will be as well if things go well. [15:30] OvenWerks: jack will be replaced? What on earth for? [15:32] 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] OvenWerks: why fix or change jack, is it not working optimally enough? [16:35] sirriffsalot: pipewire should not be either better or worse than curent jack. but system integration should be better. [16:35] 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] Treskjeg: not enough information for me to give any suggestions [16:36] I am not familiar with the device at all. [16:36] Treskjeg: you need to configure jack to see your device's respective ins/out? [16:37] first question would be if you are using the device as jack master. [16:37] 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] Treskjeg: close controls for now, open up qjackctl instead and see there what you can do, you have a lot more options [16:38] But that option should be in US-c [16:38] Under "Channel Count" [16:39] controls does not show firewire at all in 20.04. [16:39] it expects firewire devices to show as alsa devices [16:39] OvenWerks: Treskjeg oh, lol. I misunderstood then [16:40] So i expect using qjackctl [16:41] Yup, using qjackctl. Selecting firewire as the driver there empties the interface options to just "default". [16:42] 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] 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] I don't know if qjackctl somehow does this or if the user needs to blacklist the snd-* firewire modules first. [16:45] 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] As far as I know, the FireWire driver in Jack is really just Alsa's FireWire utils. [16:46] 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] I do not think that is true though qjackctl may deal with it that way. [16:47] jack itself deals with fw in a different way [16:48] qjackctl may detect a fw as alsa device and silently use the alsa backend [16:48] but I don't really know. [16:49] 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] 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] Treskjeg: as the device should pop up there at least :-S [16:51] Treskjeg: did you google to check if some drivers are required for this particular device in GNU/Lin? [16:52] 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] 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] sorry to not be much help... [16:53] No worries; helped some anyway, especially with regards to maybe having to blacklist snd-dice. [16:54] Some of the arch docs on that may be helpful [16:54] They at least have a list of modules to BL [19:06] 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] 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] 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] 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] 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] 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] umm? [19:31] you mean https? [19:31] Yes. [19:31] it's Canonical's faul [19:31] t [19:31] also [19:31] there's a set of official cdimage mirrors as well [19:31] and distributiong a cdimage.ubuntu.com SSL cert to every mirror host will be problematic [19:32] becasue they also need to share a privkey for that which in turn *compromises* the key [19:32] it's a logistics challenge to support that across the mirrors [19:32] it's not compromised though [19:32] augugusto: So, that basically means adding https to the site would *compromise* security of the images, not enhance it. [19:34] it also introduces its own logistics headache to manage it securely. [19:35] 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] sorry i wasted your time. i'll go ask somewhere else. my network could be compromised. thats why i asked [19:41] so https is safe. not. === adam__ is now known as Guest35343