[02:44] <Guest_21> Hello
[02:44] <Guest_21> I have a problem with linux ubuntu
[02:44] <Guest_21> Can somebody help me?
[03:24] <r2b2nz> Best to just ask your question and if anyone can help I'm sure they will :)
[15:05] <david__> Hello, I have upgraded to 20.04 however i have noticed that Carla does not show up as a instrument plugin on LMMS. I was expecting this to be the case due to the Carla version upgrade
[15:08] <OvenWerks> david__: does carla show up at all?
[15:08] <OvenWerks> maybe as an effect or something else?
[15:08] <Eickmeyer> david__: LMMS only supports older ladspa plugins. Carla does not have a ladspa plugin.
[15:08] <OvenWerks> how would LMMS know that Carla should be an instrument?
[15:09] <OvenWerks> Oh, LV1 does not do instruments, that would be dssi
[15:09] <OvenWerks> Eickmeyer: I thought LMMS did see LXVST
[15:09] <david__> When I run the appimage from the lmms website carla patchbay and rack show as a plugin in the instrument plugins.
[15:09] <Eickmeyer> Hmmm.... idk then.
[15:10] <Eickmeyer> david__: We don't support the appimage here.
[15:12]  * OvenWerks is on a 32bit box... so will sit at 18.04 untill I find another repo that still supports 32 bit
[15:12] <david__> No, I get that. But my issue is that I was expecting Carla to appear in LMMS when I installed it from the ubunut repo, and the latest Carla version supports this.
[15:13] <Eickmeyer> david__: I can get the vst version of Carla to show in ardour, so I don't know why LMMS isn't.
[15:14] <david__> Maybe it has something to the way LMMS has been compiled.
[15:14] <Eickmeyer> We get lmms directly downstream from Debian.
[15:15] <david__> Ah, I suppose if they have the older version of Carla then that's why.
[15:15] <Eickmeyer> david__: I see that the default plugin directory for lmms doesn't even point to where Carla would be installed.
[15:16] <Eickmeyer> Carla doesn't exist in Debian.
[15:16] <david__> That's why then I think. It's a bit like how Zynaddsubfx shows up in the instrument list.
[15:20] <Eickmeyer> I just tried to get lmms to see Carla and it, indeed, doesn't. Not sure why though.
[15:21] <Eickmeyer> david__: I'm guessing it's the compilation options in the version of lmms we ship from Debian.
[15:23] <Eickmeyer> Debian doesn't like VSTs because it walks the fine line of "non-free".
[15:24] <david__> Yes I think so. It requies the latest version of Carla to be installed before lmms is compiled if memory serves. It doesn't matter anyhow. The appimage of LMMS works just fine from my limited testing. But as you can probably appreciate having Carla as Midi instrument in LMMS really opens it up. Perhaps something to note for a future release or to put on the website / wiki somewhere.
[15:25] <Eickmeyer> Again, that's not something we have direct control over.
[15:32] <david__> No, and that's fine. I'm not critising, just pointing out.
[15:38] <Guest4957> hello
[15:39] <OvenWerks> LMMS should catch up with the world and use LV2
[15:50] <david__> In the works according to git. Hopefully with 1.3 ... whenever that will be released!
[19:28] <Luca> Hello
[19:28] <Luca> I just made a fresh install of Ubuntu Studio and I am having problems with audio
[19:29] <Luca> It's something like 3 days I am keeping trying various solutions and installing different versions of ubuntu and kernels and keep having this problem that I cannot solve
[19:29] <Luca> Is there anybody who is kind enough to spend some time with me to solve this issue?
[19:30] <oerheks> Luca, ask, wait and see
[19:32] <Luca> Right now, with Ubuntu Studio 19.10, out of the box, the sound is not working. Pavu shows that the system is detecting the internal sound card, but I can hear no sound
[19:36] <Luca> More information: I tried to sudo alsa force-reload
[19:37] <Luca> and also modified the /etc/modprobe.d/alsa-base.conf and wrote the line "options snd-hda-intel dmic_detect=0"
[19:59] <Luca> btw, kernel 5.3.0-18
[20:13] <OvenWerks> Luca: in a terminal type this very long line: cd /tmp && wget https://community.ardour.org/files/adevices.sh && bash ./adevices.sh |pastebinit
[20:13] <OvenWerks> it should put out a url
[20:13] <OvenWerks> paste that url for us to look at
[20:14] <Luca> That looks professional. I did it
[20:15] <OvenWerks> it would only be profesional if I got paid for learing it ;)
[20:15] <OvenWerks> *learning
[20:15] <Luca> haha
[20:15] <Luca> thanks for your dedication to open source
[20:16] <areyouloco> forgot to chmod +x
[20:16] <OvenWerks> if you type in the line exactly as written it should noot need it
[20:18] <areyouloco> also does pastebinit comes by default?
[20:18] <OvenWerks> on ubuntu yes
[20:20] <OvenWerks> I have never looke for the upstream of pastebinit so I don't know how common it is outside of ubuntu
[20:24] <ahq> I recently read somewhere that Ubuntu Studio will no longer support firewire devices. Is that true and if so, what do you mean by that ? Will tha ffado stack not be available or will the kernel not work with firewire ??
[20:25] <OvenWerks> ahq: if the fw devcie happens to work with the alsa fw stack it will work
[20:26] <Eickmeyer> Basically, there's a kernel conflict between the ffado stack and the kernel firewire stack.
[20:26] <OvenWerks> ahq: if you have the technical ability to blacklist the alsafw modules and make sure the ffado modules will load great. but we do not have any one who can help you
[20:26] <ahq> OvenWerks Ok, I have a Presonus Mixer, 3 Presonus Firepods, a few Focusrite devices, A RME device.. I
[20:27] <ahq> I don't need help, I just want to know what you are doing with Ubuntu Stuudio to make it not support fw devices...
[20:27] <OvenWerks> I do have an echo device here but have not managed to get any sound out of it.
[20:28] <ahq> Eickmeyer I know that Alsa and FW stack might conflict, That is not a new thing..
[20:28] <OvenWerks> ahq: the only thing we have done technically is to not include the fw backend as a choice in ubuntustudio-controls
[20:28] <Eickmeyer> ahq: We're not doing anything intentionally. You're just on your own.
[20:29] <Eickmeyer> Additionally, firewire devices are becoming more dated and ancient, and the relevance of firewire is going away. We can't support old devices indefinitely.
[20:29] <OvenWerks> ahq: so we have not removed any kernel modules or anything like that
[20:29] <ahq> So what does that mean, Ubuntu Studio Controls will not work for me in any way if I am using one or more FW devices
[20:29] <Eickmeyer> ahq: It will work if the FW device works with ALSA.
[20:29] <Luca> Sorry, my internet connection stopped
[20:30] <OvenWerks> Eickmeyer: shhh, I have a PCI ice1712 device...
[20:30] <Luca> So, if you wrote anything, I couldn't read it
[20:31] <OvenWerks> nope just waiting for you to post the url from that command
[20:31] <OvenWerks> Luca: ^^^
[20:31] <Luca> I did it!
[20:31] <Luca> I redo it, just to be sure
[20:32] <ahq> That means that I will most likely be better of to go back and use old trusty Cadense and KXstudio since there everything is still supported..  I have not used FW devices with alsa stack since I think that the mixer/configuration software for the devices requires FFADO but I might be wrong.
[20:32] <Luca> https://paste.ubuntu.com/p/RDYSYR4twj/
[20:32] <Luca> Ah, I did not understand there was a link to post, sorry
[20:32] <Eickmeyer> ahq: KXStudio is no longer its own OS.
[20:34] <ahq> Eickmeyer I know but cadence will continue to support Firewire unlike Ubuntu Studio Controls (Which was the sole reason for me to use Ubuntu Studio for the last year or so)
[20:34] <Eickmeyer> ahq: For now. The developer has mentioned he may stop developing Cadence.
[20:35] <ahq> KXstudio doesn't care if I use Ubuntu or Debian and will support FFADO
[20:35] <StevenJayCohen> Eickmeyer: How about Carla?
[20:35] <OvenWerks> ahq: the fw part is still there in -controls, if you have selected it in the past and do not reconfig
[20:35] <Eickmeyer> StevenJayCohen: He's actively developing Carla.
[20:35] <OvenWerks> Luca: that looks fine like pulse is using the right device
[20:36] <OvenWerks> Luca:  where are you trying to get sound from and to?
[20:37] <ahq> Eickmeyer Ok, I will have toi go back to qjackctl then. But anyhow, there will not be a good reason to stay with Ubuntu Studio anyway. Thanks for the quick response and keep up the good work.  i might get back the day all my FW devices died or FW cards are no longer physically supported.
[20:37] <Luca> OvenWerks: from both browsers Firefox and Chrome
[20:37] <Luca> the pavu shows both the input and output signals working fine
[20:37] <Luca> also the alsamixer I guess
[20:38] <Luca> yes, also the alsamixer has the right volume in "speaker"
[20:38] <Luca> but still no sound. Should I try to reforce alsa?
[20:39] <OvenWerks> can you take a screen shot of the Output Devices Tab in pavucontrol
[20:39] <Luca> Yes, But how can I post it here?
[20:42] <Luca> Maybe igmur works? https://imgur.com/a/Gsp1Z21
[20:43] <Luca> OvenWerks: here the link: https://imgur.com/bNg7S5s
[20:44] <Luca> (btw, no sound even from the headphones)
[20:45] <Luca> May be an issue with the driver?
[20:49] <OvenWerks> are the speakers built in tothe computer as in a laptop? or are they plugin?
[20:50] <Luca> built in
[20:50] <OvenWerks> I'm confused, it looks like the sound should be working
[20:51] <Luca> But with Ubuntu 18.04 and 19.10 it works. There they have a kernel 5.3.0-46 however. Should I update?
[20:51] <OvenWerks> does the computer have a volume control on it (not buttons but a round control like thing)
[20:51] <OvenWerks> There should be no difference
[20:51] <OvenWerks> I would think
[20:52] <Luca> No volume on/off control
[20:52] <OvenWerks> the pch/hda interface has been pretty stable for a long time
[20:52] <OvenWerks> I just always check :)
[20:53] <Luca> that's just incredible. I read that sometimes to reforce alsa solves the issue, but this time it hasn't worked out
[20:56] <OvenWerks> Luca: have you actually powered off and on?
[20:56] <OvenWerks> I am wondering if it has gotten a pin signal that it should not have
[20:56] <OvenWerks> or plug headphones in and out may reset it too.
[20:57] <Luca> the sound of the computer? You mean after reforcing alsa? I did, but I will try again!
[20:57] <Luca> I just tried to plug my headphones and still the same
[20:58] <OvenWerks> so no sound in the head phones either
[20:58] <Luca> nope
[20:59] <OvenWerks> in pavucontrol where it says Port: Speakers
[20:59] <OvenWerks> what happens if you click on that to drop it down?
[20:59] <OvenWerks> what other options does it give?
[20:59] <OvenWerks> Your earlier paste made it to be correct)
[21:00] <Luca> headphones (unplugged)
[21:00] <Luca> (and when I plug my headphones, it changes to "Headphones (plugged in)
[21:01] <OvenWerks> and alsa mixer probably shows level changes too
[21:01] <Luca> yep
[21:01] <Luca> Should I try to install the 20.04 version?
[21:02] <Luca> I reloaded my alsa
[21:02] <OvenWerks> You can, it is pretty much ready anyway except maybe some artwork
[21:02] <Luca> If you can keep 3 mins, I reboot
[21:02] <OvenWerks>  ok.
[21:02] <Luca> Ok! I will directly reinstall the 20.04 and get back tomorrow
[21:03] <OvenWerks> sure
[21:03] <Luca> Thanks for the time you gave to me! Have a great evening
[21:04] <OvenWerks> your welcome
[21:04] <Luca> Ooops
[21:04] <Luca> https://ubuntustudio.org/download/
[21:05] <Luca> The 20.04 links say "19.10"
[21:05] <OvenWerks> Eickmeyer: ^^^
[21:05] <OvenWerks> but the links are coreect
[21:05] <Luca> ok good
[21:05] <OvenWerks> correct even
[21:05] <Luca> Thanks again
[21:05] <Eickmeyer> That's because 20.04 isn't released yet.
[21:06] <OvenWerks> Eickmeyer: yaeh but the dl link says 20.04 beta the link text reads 19.10 and the underlaying link is 20.04
[21:06] <Eickmeyer> Oh wait... I see what you're talking about. I'm a bot. >.<
[21:08] <Eickmeyer> Fixed.
[21:08] <OvenWerks> :)
[21:46] <wingedrhino> If I install 20.04 now, is it atleast somewhat usable?
[21:46] <StevenJayCohen> I'm using it, bugs are minor -- still report them if you find them
[22:24] <Eickmeyer> OvenWerks: bashfulrobot has a question for you. He's an Ubuntu Budgie developer.
[22:24] <bashfulrobot> hey OvenWerks - I was pointed in your direction as someone who might be able to answer this. Are you aware of a way to get the mute status of a specific input via the terminal? (Eickmeyer pointed me your way).
[22:24] <bashfulrobot> (and thank you in advance)
[23:31] <OvenWerks> bashfulrobot: do you mean one time get or monitor continuously?
[23:31] <OvenWerks> bashfulrobot: amixer will get a current value
[23:32] <OvenWerks> (or set)
[23:32] <OvenWerks> you do need to know which control you are playing with... which may change from device to device.
[23:34] <OvenWerks> BTW mute = off in this context
[23:35] <OvenWerks> amixer scontrols gives a list of controls
[23:36] <OvenWerks> this seems only to show one device
[23:38] <OvenWerks> Ah, -c or -D can change that
[23:44] <Eickmeyer> OvenWerks: It looks like he figured it out in a video he sent me on Telegram.