[06:38] <kdenliver> Hey! This may be question asked in a kdenlive forum or something, but do I have to install some ffmpeg on Ubuntu to make the proxy clips?
[06:46] <kdenliver> Never mind, I think it's already installed. Thanks, I just got the path.
[17:04] <cupantae> Hey :)  I'm trying out Ubuntu Studio for the first time and it looks really slick, but.....
[17:04] <cupantae> Jack does not work. Which is unfortunate because avoiding understanding Jack was the main reason I installed
[17:05] <cupantae> Didn't check it from the live system. Any ideas?
[17:06] <OvenWerks> Jack should just work
[17:06] <OvenWerks> how does jack fail for you? cupantae
[17:07] <OvenWerks> cupantae: how are you running jack?
[17:07] <cupantae> Will I show you some Qjackctl output?
[17:07] <OvenWerks> Why are you using qjackctl instead of ubuntustudi0o-controls?
[17:07] <OvenWerks> but sure
[17:07] <cupantae> I've also tried Start/Restart Jack in Ubuntu Studio Controls but that does nothing and gives no output
[17:07] <cupantae> that I can see
[17:08] <cupantae> I can try running that from a terminal?
[17:08] <OvenWerks> sure
[17:08] <StevenJayCohen> An output log would be a welcome addition to Studio Controls
[17:08] <OvenWerks> there is one
[17:08] <StevenJayCohen> ?
[17:08] <StevenJayCohen> checking...
[17:09] <cupantae> Cannot connect to server socket err = No such file or directory...is the first thing that comes out. It spams the same few lines over and over while USC is running
[17:09] <OvenWerks> generally ~/.log/autojack,log
[17:09] <cupantae> JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock
[17:09] <cupantae> is also possibly significant
[17:09] <StevenJayCohen> OvenWerks, ahh, with newbies in mind I was hoping for a button in Studio Controls to open the log
[17:10] <cupantae> OvenWerks: I don't have that file but I have .log/jack/jackdbus.log
[17:10] <OvenWerks> StevenJayCohen: with the new (20.04) version there is also a debug level
[17:10] <StevenJayCohen> OvenWerks, nice!
[17:11] <cupantae> ERROR: failed to stat "/home/ubustudio/.config/jack/conf.xml", error is 2 (No such file or directory)
[17:11] <cupantae> is the first error there
[17:11] <OvenWerks> cupantae: perhaps a screen shot of the audio tab of -controls might help
[17:11] <cupantae> ok
[17:11] <OvenWerks> That error should not be a problem.
[17:12] <cupantae> OK
[17:12] <cupantae> https://imgur.com/qNCE80R.png
[17:13] <cupantae> That "host on imgur" option in the PrntScr window is a very nice feature.
[17:13] <cupantae> (I guess that's an Xfce feature)
[17:15] <cupantae> Here's another bit from the .log/jack/jackdbus.log
[17:15] <cupantae> ERROR: ALSA: Cannot open PCM device alsa_pcm for playback. Falling back to capture-only mode
[17:15] <cupantae> So it could be a sound card / alsa issue?
[17:16] <OvenWerks> give me a sec, on the phone
[17:16] <cupantae> Yeah, no rush at all lol
[17:17] <OvenWerks> cupantae: it sounds like your default device is HDMI from your video?
[17:18] <OvenWerks> cupantae: in a terminal type this all as one line: cd /tmp && wget https://community.ardour.org/files/adevices.sh && bash ./adevices.sh |pastebinit
[17:19] <OvenWerks> then give us the url that should result
[17:19] <OvenWerks> (BTW there is a newer version of -controls)
[17:24] <Eickmeyer> Newer version of -controls is in Backports for Eoan and Bionic.
[17:24] <Eickmeyer> !ubuntustudio-backports
[17:27] <cupantae> OvenWerks: will try and report back hopefully soon
[17:28] <cupantae> Eickmeyer: I'll take a look at that too
[17:28] <Eickmeyer> cupantae: Also, just to note: your screenshot showed you hadn't set an audio device. "default" doesn't always work, it's best to just specify when stuff isn't working.
[17:29] <cupantae> Eickmeyer: OK let's start with that
[17:30] <cupantae> Yeah I think this might be the issue. There are 4 HDMI devices showing and another.. I am not using HDMI
[17:32] <cupantae> Oh! Pavucontrol shows no devices at all
[17:32] <OvenWerks> That is correct
[17:33] <cupantae> OK
[17:33] <cupantae> It seems like it's running now :)
[17:33] <OvenWerks> pavucontrol should just show jacksink/source
[17:33] <cupantae> I just selected the non-
[17:33] <cupantae> whoops
[17:33] <cupantae> pavucontrol shows just dummy output
[17:34] <cupantae> Oh no, now that jack is working, you're right
[17:34] <Eickmeyer> That means pulseaudio isn't running/there are no jack bridges.
[17:34] <cupantae> I see
[17:34] <OvenWerks> I think it was just jack was not there yet
[17:34] <cupantae> I just selected the non-HDMI card before hitting Start/Restart in USC.
[17:34] <OvenWerks> cupantae: right
[17:35] <cupantae> It's called "PCH,0,0 playback and capture (ALC255 Analog)"
[17:35] <OvenWerks> PCH maybe
[17:35] <cupantae> Well done :) I suppose that's my laptop speakers?
[17:35] <OvenWerks> PCH is generally what on board audio is called
[17:36] <cupantae> Cool beans
[17:36] <cupantae> This is great anyway! Thank you both OvenWerks and Eickmeyer. No need to edit config files or anything =D
[17:37] <Eickmeyer> Yep. It just works. (tm)
[17:37] <OvenWerks> It used to be almost always what showed as default, but many newer systems put hdmi first
[17:51] <cupantae> It's certainly working. Now I just have to teach myself how to use these programs XD
[18:00] <OvenWerks> cupantae: the main thing to remember with jack is that not all programs auto connect to the audio device. Use patchage or Carla to check or make new connections
[18:04] <Turdlar> regarding carla and patchage - i keep seeing them recommended for hooking things up with eachother. what are the differences from them to qjackctl and aconnectgui?
[18:08] <Turdlar> im asking because qjackctl has gotten me through most everything i wanted to achieve
[18:08] <OvenWerks> Turdlar: those are both fine too.
[18:09] <Turdlar> and the interface is way less scary in comparison to carla and patchage
[18:09] <OvenWerks> We try to avoid recommending qjackctl because using it to start jack gives problems for people using USB mics
[18:09] <OvenWerks> that is two devices at the same time
[18:10] <Turdlar> haha, ouch! that explains the first 10 hours of troubleshooting i did in ubuntu studio
[18:11] <OvenWerks> With qjackctl there are some many paramters the chance of making it so nothing works is easy
[18:11] <Turdlar> i got around it by disabling all other sound inpit or output sources on a bios level
[18:12] <Eickmeyer> !ubuntustudio-controls
[18:12] <Eickmeyer> And think of Carla's patchbay as exaclty that: connecting wires between devices. It's that simple.
[18:13] <Turdlar> but why is qjackctl included then? if it creates known issues  with common hardware, then i figure it would be easier to leave it out?
[18:13] <Eickmeyer> Turdlar: Because it's part of the Jack package and we can't exclude it.
[18:13] <Turdlar> ah. ok
[18:14] <OvenWerks> And some people just don't want to change :)
[18:14] <Eickmeyer> ^
[18:14] <Turdlar> it seems like Patchage is showing more options for me to connect, compared to Carla
[18:14] <Turdlar> looking forward to play around with it
[18:14] <Eickmeyer> If that works for you, then go for it.
[18:15] <Eickmeyer> New carla version will be dropping soon for 20.04, but for reasons can't be backported.