[12:06] <musicfan999> Hello!
[12:10] <musicfan999> Hi! I have recently started getting ambiguous messages about an OS upgrade
[12:10] <musicfan999> "A new version of Ubuntu is available, do you want to upgrade?"
[12:11] <musicfan999> I can't know from this is an offer about upgrading to Vanilla Ubuntu 20.10?
[12:11] <musicfan999> Or is it talking about Ubuntu Studio?
[12:11] <musicfan999> 19.10 is working ok and I do NOT want to compromise the integrity of my music production
[12:15] <sirriffsalothp> musicfan999: Hey, to be honest there is little need to jump the gun and upgrade to 20.10, at least that's how it is for me
[12:15] <sirriffsalothp> musicfan999: you still have support for 19.10 for a while yet, and once some of the unavoidable bugs that will surface from 20.10 have been fixed, your support for 19.10 will have ended and you can upgrade without the need to worry :) That's my plan anyways
[12:16] <sirriffsalothp> musicfan999: also I'm waiting for the sick Ardour 6-release :D
[12:16] <musicfan999> Thanks @sirriffsalothp  question is not really about the decision to upgrade. I'm just trying to decipher this message prompt.
[12:16] <sirriffsalothp> musicfan999: well, what's cryptic about it? :P
[12:17] <musicfan999> This pop up message, can I be sure it isn't a vanilla Ubuntu upgrade they are offering? The text is ambigious
[12:17] <musicfan999> it says "A new version of Ubuntu is available"
[12:17] <sirriffsalothp> I believe you can turn off those notifications if they're annoying. If you go further in the message-prompt chain, you should be able to see exactly what it is that will be installed, before installing it
[12:18] <musicfan999> No, there is just a yes and no from that message box. I'm not annoyed about an offer to upgrade either, i'm annoyed at not knowing who is making the offer
[12:21] <sirriffsalothp> musicfan999: try to run sudo do-release-upgrade, you should get an option to confirm the upgrade, with a list of everything that will be upgraded, before you actually upgrade
[12:23] <musicfan999> @sirriffsalothp  that might be useful;  I will make a note
[12:24] <sirriffsalothp> musicfan999: or just run update-manager, the version you're asked to run will be shown there
[12:29] <musicfan999> I just tried clicking on System/Software Updater
[12:29] <musicfan999> It says "Ubuntu Studio base" (203kb) is avilable to download. That's not ambiguous. :)
[12:30] <musicfan999> Or anyway, less so.
[12:31] <musicfan999> If i apply that update, hopefully it will quiet that other ambiguous message that intermittently appears
[14:39] <Eickmeyer> musicfan999: The upgrade will take you to 20.04 LTS. 19.10 will end *all* support (including security updates) in July, so upgrade ASAP.
[14:50] <musicfan999> @el
[14:50] <musicfan999> Eickmeyer: thanks
[14:50] <musicfan999> Yikes
[15:02] <musicfan999> Yay. I applied the small update, and have a new message that is not ambigious
[15:03] <musicfan999> thanks for the help you guys
[19:17] <sirriffsalothp> How are we looking for an Ardour 6 on Ubuntu Studio? :D
[19:17] <OvenWerks> it will show first in backports
[19:19] <OvenWerks> sirriffsalothp: so for 20.04, it will come from backports. 20.10 should have the latest 6.* version
[19:19] <sirriffsalothp> OvenWerks: aww, too bad. Any idea when this might be? :)
[19:20] <OvenWerks> sirriffsalothp: be aware that finishing a project on Ardour 6.0 that was started on 5.12 may (slightly) change the sound or even timing (latency comp has changed)
[19:21] <OvenWerks> That depends on A:debian... or if that is too slow due to some kind of freeze, we will likely package it locally
[19:22] <OvenWerks> sirriffsalothp: in that case it would depend on how long it take Eickmeyer to get tired of waiting... and having time in his busy schedual.
[19:38] <Eickmeyer> To clarify, it will be a special backport repository. I don't want to mess people up who still rely on backports *and* Ardour 5. OvenWerks , sirriffsalothp
[19:38] <sirriffsalothp> Fair enough :)
[19:40] <Eickmeyer> I'm also waiting to see what upstream Debian does because I don't want to reinvent the wheel when it comes to packaging. I'd rather just use what's there.
[19:41] <linuxgecko> heya guys, comming back about an issue i had with jack/carla not seeing the second output on my usb "soundcard".  carla is in Multiple Client mode, and Ubuntu Studio controls sees the second output in the USB master dropdown, but i have no master selected.
[19:41] <linuxgecko> no usb master, that is. jack master is my onboard audio controller.
[19:42] <OvenWerks> ok, what are you expecting to see?
[19:43] <Eickmeyer> linuxgecko: ^
[19:43] <linuxgecko> I'm expecting to see Controller0.0 input, controller 0,0 output (i see these), but also Controller1,0 output.
[19:44] <OvenWerks> Ah, you actually have a USB device that has a ,1?
[19:44] <linuxgecko> yes.
[19:45] <OvenWerks> wow, ok. I would sugest in this case... untill we fix this in controls, you will need to start a new zita-ajbridge on a terminal.
[19:46] <OvenWerks> I was working under the assumtion that USB devices did not do that because I have never seen, read about one.
[19:47] <linuxgecko> for your reference, this is the device in question.
[19:47] <linuxgecko> Bus 001 Device 005: ID 1532:0520 Razer USA, Ltd Razer USB Audio Controller
[19:48] <OvenWerks> If you can see the second device in the the USB master drop down, maybe set that as jack master and 0,0 will be picked up and then use extra devices to include onboard sound
[19:48] <OvenWerks> linuxgecko: I do not doubt you at all.
[19:49] <OvenWerks> and the fix is certainly possible... I will be adding that for the next version of controls for sure.
[19:49] <linuxgecko> OvenWerks i didn't paste that because i thought you did.  i thought knowing the exact device might help your solution to the inconveniece.
[19:50] <linuxgecko> i have a workaround, but i thougth it might just be that you've not seen it,  or i'm doing something wrong.
[19:50] <OvenWerks> The use of sub devices was originally for internal devices where the original audio archetectur only thought in terms of stereo.
[19:51] <OvenWerks> so it surprises me that a Newer USB device would go back to that when they can just add more ports.
[19:51] <linuxgecko> the audio controller registers 2 playback devices, and has a fader between them on the hardware.    i use 1,0 as my promary on windows, (which i dual-boot with this.  i "just" have to fade over to 0,0 when i boot studio.
[19:51] <OvenWerks> The problem is therefore a thinko on my part.
[19:52] <linuxgecko> but not hanving to,  would be better :)
[19:54] <linuxgecko> the usecase for them having 2 is it's for a gaming headset.  they want you to have the option of sending voice-chat audio to one, and game audio to the other,  and fade between them for the mix that's most effective for you.
[19:55] <linuxgecko> all with one 4-connector 1/8" jack for the headphones :)
[19:55] <sirriffsalothp> OvenWerks: what do you mean "change the sound" though?
[19:56] <Eickmeyer> sirriffsalothp: Ardour 6 uses a different DSP.
[19:56] <OvenWerks> sirriffsalothp: subtle changes mostly due to new latency comp in buses etc.
[19:57] <sirriffsalothp> Eickmeyer: but.. changes the sound of the music being made?
[19:57] <OvenWerks> but there may be other slight math differences as well. (as in more correct)
[19:58] <Eickmeyer> sirriffsalothp: Sure. Different way of processing sound.
[19:58] <sirriffsalothp> Yikes...
[19:58] <OvenWerks> The same could be said for a new version of any plugin.
[19:58] <Eickmeyer> Yep. Any time a change is made to a DSP is a change to the sound, even if minute.
[19:59] <OvenWerks> so in some cases, even keeping 5.12 but having plugins built on new libs could have the same effect
[20:00] <OvenWerks> Any audio project should be finished on the same version of everything that it starts with unless it has not yet reached mixdown
[20:00] <OvenWerks> Maybe even then
[20:00] <sirriffsalothp> Good to know, I suspected as much, but not for those reasons..
[20:00] <OvenWerks> So same OS version, same DAW version, same jack version, same plugin versions.
[20:01] <Eickmeyer> Basically, finish what you started before you upgrade anything.
[20:01] <OvenWerks> or keep two partitions :)
[20:01] <linuxgecko> only 2?! :)
[20:01] <Eickmeyer> ^ This guy partitions.
[20:02] <linuxgecko> OvenWerks how do you mean 2 partitions?
[20:02] <linuxgecko> i may be an example of taking that to rather an extreme :)
[20:06] <Eickmeyer> linuxgecko: One with an older version of Ubuntu, one with a newer version of Ubuntu.
[20:08] <linuxgecko> ahh..  ok,. i have a drive with that.  in a weird cofig.  19.10on MBR, and 16.04 on EFI, in a hybridMBR confiig :)
[20:51] <sirriffsalothp> Could this change in DSP have repercussions that are unforeseen? like breaking a session
[20:55] <Eickmeyer> sirriffsalothp: Anything is possible, especially with major new releases of software. Testing is done, but testing only goes so far.
[20:55] <sirriffsalothp> This has me worried, and so excited at the same time
[20:55] <sirriffsalothp> Imagine... an even more stable ardour
[20:55] <sirriffsalothp> With actual 100% functional MIDI
[20:55] <sirriffsalothp> ZOMG
[20:55] <Eickmeyer> Nobody can account for everything. It's not humanly possible, and it's impossible to predict the future.
[20:56] <sirriffsalothp> Sure, but are there known issues to a DSP-switch that will doubtlessly have to be fixed as the problems appear?
[20:56] <Eickmeyer> You're asking questions to which there is no answer.
[20:56] <Eickmeyer> Speculation is speculation.
[21:20] <OvenWerks> sirriffsalothp: there is a difference between a DSP problem and a dsp fix. A dsp fix can change the sound too.
[21:28] <sirriffsalothp> Mkay, here's hopin' *fingers crossed*
[21:29] <OvenWerks> for example, if any of the Calf plugins were fixed it would change their sound