[01:39] <bashfulrobot> OvenWerks: I just wanted to be able to run a command against a particular device and knowmifnit was muted or not.
[04:16] <OvenWerks> amixer can do that... with the correct parse of the output ;)
[09:49] <Luca> Hello everybody! I am here again after I re-installed the 20.04 version which is working super well. I have solved the no-sound problem, but now I have a problem with Jack
[09:50] <Luca> Here the log from Jack: Sat Apr 18 11:49:08 2020: Starting jack server...Sat Apr 18 11:49:08 2020: JACK server starting in realtime mode with priority 10Sat Apr 18 11:49:08 2020: self-connect-mode is "Don't restrict self connect requests"Sat Apr 18 11:49:08 2020: Acquired audio card Audio0Sat Apr 18 11:49:08 2020: creating alsa driver ...
[09:50] <Luca> hw:0|hw:0|1024|2|44100|0|0|nomon|swmeter|-|32bitSat Apr 18 11:49:08 2020: configuring for 44100Hz, period = 1024 frames (23.2 ms), buffer = 2 periodsSat Apr 18 11:49:08 2020: ALSA: final selected sample format for capture: 32bit integer little-endianSat Apr 18 11:49:08 2020: ERROR: ALSA: cannot set period size to 1024 frames for captureSat Apr 18
[09:50] <Luca> 11:49:08 2020: ERROR: ALSA: cannot configure capture channelSat Apr 18 11:49:08 2020: Released audio card Audio0Sat Apr 18 11:49:08 2020: ERROR: Cannot initialize driverSat Apr 18 11:49:08 2020: ERROR: JackServer::Open failed with -1Sat Apr 18 11:49:08 2020: ERROR: Failed to open serverSat Apr 18 11:49:10 2020: Saving settings to
[09:50] <Luca> "/home/luca/.config/jack/conf.xml" ...qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 1903, resource id: 12700633, major code: 40 (TranslateCoords), minor code: 0
[10:08] <StevenJayCohen> What device do you have set as default in Ubuntu Studio Control
[10:11] <Luca> one sec that it asks me to update my system
[10:45] <Luca> StevenJayCohen: I cannot open the Ubuntu Studio Control
[10:48] <Luca> And I got a crash: https://imgur.com/ucmqqiV.png
[11:03] <StevenJayCohen> Can you launch it after an update and a reboot? I had issues with it that were solved by an update
[11:03] <StevenJayCohen> Sorry for the slow reply, making coffee
[11:08] <Luca> StevenJayCohen: Updated and Rebooted, but still the same
[11:08] <StevenJayCohen> How about qJackCtl?
[11:10] <Luca> For reference about the crash: https://imgur.com/Eyo4Jtm.png
[11:11] <Luca> Ok, I am having multiple problems with QJackCtl, and I absolutely need to find a way to have it working. Definitely problems with this laptop of mine, but this is what I have got right now
[11:12] <Luca> When I try to start QJackCtl I get the following error: Sat Apr 18 13:11:15 2020: Starting jack server...Sat Apr 18 13:11:15 2020: JACK server starting in realtime mode with priority 10Sat Apr 18 13:11:15 2020: self-connect-mode is "Don't restrict self connect requests"Sat Apr 18 13:11:15 2020: Acquired audio card Audio0Sat Apr 18 13:11:15 2020:
[11:12] <Luca> creating alsa driver ... hw:0|hw:0|1024|2|44100|0|0|nomon|swmeter|-|32bitSat Apr 18 13:11:15 2020: configuring for 44100Hz, period = 1024 frames (23.2 ms), buffer = 2 periodsSat Apr 18 13:11:15 2020: ALSA: final selected sample format for capture: 32bit integer little-endianSat Apr 18 13:11:15 2020: ERROR: ALSA: cannot set period size to 1024
[11:12] <Luca> frames for captureSat Apr 18 13:11:15 2020: ERROR: ALSA: cannot configure capture channelSat Apr 18 13:11:15 2020: Released audio card Audio0Sat Apr 18 13:11:15 2020: ERROR: Cannot initialize driverSat Apr 18 13:11:15 2020: ERROR: JackServer::Open failed with -1Sat Apr 18 13:11:15 2020: ERROR: Failed to open serverSat Apr 18 13:11:16 2020: Saving
[11:12] <Luca> settings to "/home/luca/.config/jack/conf.xml" ...
[11:13] <Luca> Basically, I noticed that I have this problem with more or less all kernels after 5.3.0-18 (QJackCtl started with Ubuntu Studio 19.10)
[11:16] <StevenJayCohen> What's your audio hardware?
[11:20] <Luca> StevenJayCohen: the lspci command says "Multimedia audio controller: Intel Corporation Device 02c8"
[11:26] <StevenJayCohen> Does this happen in a new user as well (without your settings, a brand new account)?
[11:31] <Luca> Well, this is a out-of-the-box installation
[11:32] <StevenJayCohen> <Luca "Well, this is a out-of-the-box i"> It takes 3 minutes for you to confirm
[11:33] <Luca> I bought a computer exactly like this one (Lenovo C640) in December, installed Ubuntu 19.10 and had Jack working. After, the computer broken, I bought another one of the same type, and now I have problems with more or less all OS
[11:33] <Luca> StevenJayCohen: how can I try to make a brand new account?
[11:34] <StevenJayCohen> Add a user and log into that user
[11:37] <Luca> StevenJayCohen: Ok, just tried to switch account to a brand-new one and I have the same problem with jack
[11:38] <StevenJayCohen> Your audio hardware? What is it?
[11:50] <Luca> StevenJayCohen: I cannot retrieve the model as the command "aplay -l" doesn't show any sound device: https://imgur.com/oPeFimw.png
[11:51] <Luca> It's a Realtek Alc+something
[11:53] <Luca> Maybe an Alc882, but I am not sure
[11:58] <Luca> Wait, I go to windows and check
[11:59] <StevenJayCohen> Have you filed a bug on this?
[12:08] <Luca> StevenJayCohen: sorry, I am unable to retrieve the specific Realtek sound card type
[12:10] <Luca> However, this is the model: https://www.lenovo.com/gb/en/laptops/yoga/yoga-c-series/Yoga-C640/p/88YGC601300
[12:26] <oerheks> lspci should tell.
[12:27] <oerheks> adding: set-card-profile 0 HiFi to /etc/pulse/default.pa seems to solve it.
[12:27] <oerheks> https://forum.manjaro.org/t/lenovo-yoga-c640-sound/126933/2
[12:28] <oerheks> interesting that you shared the specs only now.
[12:28] <Luca> oerheks: lspci says "Multimedia audio controller: Intel Corporation Device 02c8"
[12:28] <oerheks> no, it should say xxxx:yyyy as number
[12:30] <Luca> I don't know. Here is the log of the command: https://imgur.com/v6zdsxR.png
[12:31] <oerheks> odd...
[12:32] <Luca> There are very many odd things with this machine of mine. I just don't understand if there is some serious hardware problem specifically on this machine
[12:32] <oerheks> see if that manjaro fix works for you
[12:33] <Luca> Yep, I reboot now and see
[12:33] <Luca> thanks for now
[12:35] <Luca> The fix didn't resolve the problem
[12:36] <Luca> Should I try to downgrade my kernel to the one that was working (UbuntuStudio 19.10 - 5.3.0-18), so to see if it still works with that kernel?
[12:42] <oerheks> there is no downgrade possible.
[12:42] <oerheks> you are on 20.04?
[12:43] <Luca> yes 20.04
[12:44] <StevenJayCohen> And 19.10 works?
[12:45] <Luca> And 19.10 worked in this respect (although there was another kind of problem)
[12:45] <Luca> oerheks: can I not just download the kernel and install it?
[12:45] <StevenJayCohen> Then you could refer to 19.10 report the issue and wait for the  .1 update
[12:46] <Luca> StevenJayCohen: sorry, I did not understand what you mean
[12:46] <StevenJayCohen> What's more important a working machine or making the newest version work today?
[12:47] <Luca> in 19.10, it worked everything perfectly, apart that there was no sound coming our of my computer at all. OvenWerks and I tried to go through this problem, but it was like a magical problem: everything seemed to work just fine, but still no sound
[12:48] <StevenJayCohen> And if you change out the interface for another one?
[12:48] <Luca> A working machine. But it is not working properly in Ubuntu 18.04, 19.10, Ubuntu Studio 19.10 nor 20.04 :)
[12:48] <Luca> StevenJayCohen What do you mean by changing interface?
[12:49] <StevenJayCohen> The device that Jack is using to talk to your mic and instruments
[12:49] <Luca> Either Ubuntu 18.04 and 19.10, if I remember correctly, had both sound and Jack working, although I kept having a choppy sound ot of Jack
[12:50] <Luca> StevenJayCohen: well, I have none right now.
[12:50] <StevenJayCohen> And before you installed you tested by running it from the USB live and had no issues?
[12:51] <Luca> StevenJayCohen: I can't answer that, as I didn't try actually. But I can now if you want
[12:53] <StevenJayCohen> No just wondering how the system broke and what the original working state was
[12:54] <Luca> Well, I have problems with jack with more or less all kernels after 5.3.0-something. It's really a recurrent problems among different OS.
[12:55] <oerheks> long bugreport, no fix.. that 02c8 device is not supported.. https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1850439
[12:55] <Luca> And before 5.3.0-something, I have a Choppy Jack sound
[12:56] <oerheks> i wonder why you have choppy sound, nobody got it working
[12:56] <Luca> weird enough, 5 months ago, when I bought this machine for the first time, everything just worked fine. That's very incredible
[12:57] <StevenJayCohen> So some piece of hardware you own has issues with all newer software. I don't think we're going to be able to fix it here if it's always broken
[12:57] <StevenJayCohen> I would say revert back to that original os
[12:57] <Luca> oerheks , I was able to have it working multiple times hacking here and there (of course, randomly hacking as I don't really understand what I write), Just kept being choppy
[12:57] <StevenJayCohen> Go back to the last stable state
[12:58] <Luca> StevenJayCohen: "that original os", I really wished I knew which one was
[12:59] <Luca> I asked online how to retrieve information on old versions. That time I installed Ubuntu 19.10 from the official website. Now, the release from that same website doesn't work
[12:59] <Luca> It looks more that that time I was just lucky
[13:00] <Luca> @oer
[13:00] <Luca> oerheks: thank you for having searched for the bug!
[13:08] <StevenJayCohen> On any Ubuntu mirror, you can grab an old is with an older kernel. Test it via USB key before install. Find a good state. Install that. Use Clonezilla to make a backup. Then upgrade. If it breaks restore from Clonezilla.
[13:08] <StevenJayCohen> Old OS*
[13:10] <Luca> StevenJayCohen, oerheks: Guys, I know that this makes no sense, but I just booted with kernel 5.3.0-18-lowlatency and now it works
[13:10] <Luca> Event the Ubuntu Studio Controls
[13:11] <Luca> https://imgur.com/PgWswHL.png
[13:12] <StevenJayCohen> Make a fresh backup now
[13:12] <Luca> I have now other problems :D
[13:13] <Luca> "Establishing connection to PulseAudio. Pease wait..."
[13:20] <StevenJayCohen> Ubuntu Studio Controls should do that for you
[13:23] <Luca> Guys! We are proceeding very well!! I have sound a Jack working
[13:24] <Luca> StevenJayCohen: how can I make a backup now?
[13:25] <StevenJayCohen> Install deja dupe from the app store
[13:25] <StevenJayCohen> Once installed, it will be needed backup
[13:25] <StevenJayCohen> Named*
[13:26] <Luca> Super good thanks. I do that now
[13:29] <Luca> Now I have a choppy sound. Somebody wanna try to solve that with me? This is the last step from having a completely working machine and being happy
[13:38] <StevenJayCohen> My guess, somehow you have started multiple Jack sessions so the same time
[13:39] <StevenJayCohen> Drop all Jack sessions in qJackCtl
[13:39] <StevenJayCohen> Check in Ubuntu Studio Control to be sure it is stopped there too
[13:39] <StevenJayCohen> Then reboot
[13:40] <StevenJayCohen> Then ONLY start Jack from Ubuntu Studio Control
[14:22] <Luca> StevenJayCohen: to drop all Jack sessions I just press the "Stop" button, or should I also do something else?
[14:23] <OvenWerks> Luca: not getting sound and jack complaining about 1024 being to low sounds like audio is going to hdmi or that your system sound is hard tied to hdmi
[14:24] <OvenWerks> try setting jack to 4096 buffer size and see if jack runs
[14:25] <Luca> OvenWerks: hi! Now Jack runs fine and I can hear sound from both pulsaudio and jack. My last problem is that Jack makes sound choppy
[14:27] <OvenWerks> good
[14:28] <StevenJayCohen> Luca: follow OvenWerks request, set Jack to 4096
[14:28] <Luca> At this point, however, I would consider the option that my system is hard tied to hdmi (whatever this means). Is there a way to understand it?
[14:31] <OvenWerks> opps hes gone.
[14:32] <OvenWerks> Luca: looking at the way your devices are layed out, all of your internal devices including hdmi are listed as card 0
[14:32] <Luca> OvenWerks, StevenJayCohen: Much progress I suppose. I followed both suggestions, rebooted and set 4096
[14:33] <Luca> I pressed "Start or Restart Jack" from the Controls
[14:33] <StevenJayCohen> Still choppy?
[14:33] <Luca> I opened youtube, and played a video. It works fine
[14:33] <Luca> Dows it mean it is working?
[14:33] <OvenWerks> it means it is working at a large buffer
[14:34] <OvenWerks> That may be ok for most thing
[14:34] <Luca> How can we prove it? Meaning -> what is a Jack-dependent audio software here that I can see if it works?
[14:34] <StevenJayCohen> You can set Jack lower one step at a time and restart the jack server until you hear choppiness. When you hear choppiness, go back up one setting.
[14:35] <StevenJayCohen> Wait, what audio software do you use that requires JACK?
[14:36] <OvenWerks> but (from reading the back scroll) if this hardware is known for similar problems. It sounds to me like they have tied the hdmi sync together with the onboard sync
[14:36] <Luca> Usually SuperCollider. That will be my final proof :D
[14:36] <OvenWerks> and hdmi generally askes for 4096
[14:36] <OvenWerks> there are some very cheap audio devices that will work better.
[14:36] <Luca> OvenWerks, I don't understand what that means, but anyway you're guess worked
[14:38] <StevenJayCohen> Luca: You may want some SuperCollider specific support at this point. You can find them at this link: https://join.slack.com/t/scsynth/shared_invite/enQtMzk3OTY3MzE0MTAyLTFmMTliMmU0NjIwYzgyZGY1MjgxNGI2MGUxMTNlMWVhZWQzZjFmOTJhNzg2NDdmNzZmM2JiYTkyMjRiNDBiOTk
[14:39] <StevenJayCohen> That's a supercollider Slack channel
[14:39] <Luca> Ok, I tried that with Blender and it worked! Technically Blender is Jack-depending. So super thank you everybody!!
[14:39] <Luca> StevenJayCohen: that's very useful, thank you
[14:39] <Luca> Thank you everybody for your time and patience
[14:39] <StevenJayCohen> Be well Luca, stay safe!
[14:40] <Luca> I'll have to write all this down somewhere for people in the future looking why their Lenovo c640 isn't working
[14:40] <OvenWerks> https://www.amazon.ca/Adapter-CableCreation-External-Microphone-Compatible/dp/B0776QNHKD/ref=sr_1_17?crid=MFDFYK32ZBKS&keywords=usb+audio+adaptor&qid=1587220762&sprefix=usb+audio%2Caps%2C293&sr=8-17
[14:40] <Luca> StevenJayCohen: Yes, you too!
[14:40] <StevenJayCohen> OvenWerks: I missed that all of the devices were at 0 on that one
[14:40] <OvenWerks> is an example of something thatwill work at least down to 64 sample buffer
[14:41] <OvenWerks> I have found them for as low as 10 cents
[14:41] <OvenWerks> (and cost $5 to ship :P)
[14:41] <StevenJayCohen> I've gotten spoiled with my Audient Interface, can do 32 without xruns
[14:44] <OvenWerks> but they all look to be around $10 any more
[14:45] <OvenWerks> StevenJayCohen: even though they are all on card 0, they should be able to operate incependantly
[14:46] <OvenWerks> I would say on this hardware they have chosen to use one clock for all
[14:47] <OvenWerks> I have seen stuff like this before or the oposite way. I had a laptop where the bult in mic was 48k only. but the audio i/o jack could be 44k1 as well and the hardware allowed for setting the SR there.
[14:48] <OvenWerks> If the SR was set to 44k1 everything worked but the mic had a static-y sound. Set the SR to 48k and it was fine.
[15:11] <Luca> OvenWerks, StevenJayCohen: Just wanted to report that now everything is working even a 1024. Can't understand why, but it works great. Thanks
[15:19] <StevenJayCohen> great
[20:20] <shaban238> OvenWerks hi! if i setup 256 buffer size in ubuntustudiocontrol and than hit apply auio settings, when i open qjackctl preferences i notice that the buffersize there its still 1024. within the DAW anyway its 256. i mean, it looks normal but should it visually change it also in qjackctl?
[20:26] <OvenWerks> it depends on where you look in qjackctl
[20:27] <shaban238> qjackctl/srtup/parameters
[20:27] <shaban238> setup*
[20:27] <OvenWerks> in the messages status window in the status tab you should see the real numbers
[20:27] <OvenWerks> setup is just what qjackctl will use the next time it starts
[20:28] <OvenWerks> *starts jack
[20:28] <shaban238> ah ok thank you :)