[00:11] <MaynardWaters> hello
[00:11] <MaynardWaters> anyone have any suggestions on a monitor/screen for kdenlive video editing?
[00:11] <MaynardWaters> I'm considering this beast...
[00:12] <MaynardWaters> https://www.newegg.com/Product/Product.aspx?Item=9SIAC4Z5241544&nm_mc=AFC-C8Junction-MKPL&cm_mmc=AFC-C8Junction-MKPL-_-Monitors%20-%20LCD%20Flat%20Panel-_-LG%20Electronics-_-9SIAC4Z5241544&cm_sp=&AID=11517614&PID=6361382&SID=trd-435560208
[03:07] <studio-user765> hi
[03:07] <studio-user765> help
[03:08] <studio-user765> anyone theere
[18:48] <studio-user332> ciao è l mia prima volta qui, si parla in italiano?
[18:54] <slidinghorn> !it
[21:42] <slidinghorn> When trying to start JACK from qjackctl, I get the following error in the message window (this does not change if I add "pasuspend -- " before the server prefix) http://paste.ubuntu.com/p/3Zmw56yhFq/
[21:43] <slidinghorn> this is Ubuntu Studio 18.04
[22:32] <OvenWerks> odd, I had no trouble starting and stopping jack via dbus
[22:32] <OvenWerks> However I was using jack_control not qjackctl.
[22:37] <slidinghorn> Also possibly of interest, after I "Quit" qjackctl, jackdbus is still running, according to ps aux
[22:41] <slidinghorn> If I attempt to open qjackctl again and start the server (without killing the previously opened jackdbus process) I get the following: http://paste.ubuntu.com/p/Sq9wfJ3h9J/
[22:42] <OvenWerks> jackdbus should still be running, but if you do jack_control status it should return stopped.
[22:43] <OvenWerks> pasuspend should not be needed.
[22:43] <OvenWerks> (for over 4 years now i think)
[22:45] <slidinghorn> jack_control status returns ERROR:dbus.proxies:Introspect error on :1.268:/org/jackaudio/Controller: dbus.exceptionsDBusException: org.freedesktop.DBus.Error.NoReply: Did not receive a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
[22:45] <OvenWerks> It sounds like jackdbus is not running correctly then... so killall -9 jackd jackdbus
[22:47] <slidinghorn> status now returns "stopped"
[22:47] <OvenWerks> qjackctl should work better too.
[22:47] <OvenWerks> what is sound card 3? is it a USB audio box?
[22:52] <slidinghorn> I have my interface set to my USB headset.  This is what JACK says in Messages now when I click "Start" (currently the status seems stuck on "stopping")  http://paste.ubuntu.com/p/HDKKQ2nXQH/
[22:55] <OvenWerks> Ok, lets try pasting the output of: cd /tmp && wget http://jackaudio.org/downloads/adevices.sh && bash ./adevices.sh
[22:55] <OvenWerks> All one line
[22:56] <slidinghorn> should I click "Stop" first?
[22:56] <OvenWerks> no
[22:57] <slidinghorn> Here you go: http://paste.ubuntu.com/p/QYgG3mH7Pv/
[22:59] <OvenWerks> How did jackd get started? was that with qjackdbus or some other way?
[22:59] <slidinghorn> I have no idea - I've only attempted to start using qjackctl, and even though it says it failed, jackdbus still is running
[23:00] <OvenWerks> Thats just the dbus server part, jackdbus it self is not.
[23:01] <slidinghorn> what's this?  /usr/bin/jackd -dalsa -dhw:Hea -r48000 -p64 -n2
[23:02] <slidinghorn> (qjackctl still shows "stopping" btw...been like that for 14 minutes now
[23:02] <OvenWerks> -p64 -n2 may be a bit small for a USB 1.1 audio interface though, might try -p64 -n2 or -p128 -n2
[23:03] <OvenWerks> jack_lsp should show at least 4 ports
[23:03] <OvenWerks> (unless it errors)
[23:05] <slidinghorn> https://paste.ubuntu.com/p/h8SNjr6gCG/
[23:05] <OvenWerks> jack can be started in two ways, with dbus and with out. jackd is without dbus control though it still uses dbus to ask pulse to give up the interface
[23:06] <OvenWerks> jack is frozen, killall -9 jackd jackdbus qjackctl
[23:06] <slidinghorn> ok...
[23:07] <OvenWerks> then open qjackctl again and go to settings
[23:07] <OvenWerks>  in setting change frames/period from 64 to 128
[23:07] <slidinghorn> done
[23:07] <OvenWerks>  try to restart
[23:07] <slidinghorn> ayyyyyy
[23:08] <slidinghorn> so in lay-terms...why was that a problem?
[23:09] <OvenWerks> the usb driver/card combination was not able to handle the small size of buffer
[23:10] <OvenWerks> the fact that it is limited to 16bit audio kind of hints at it being a USB 1.1 design rather than USB 2.0 audio.
[23:10] <slidinghorn> okay...now when selecting an input device, I have an option for hw:Snowball and hw:Snowball,0  -- what's the difference?
[23:11] <OvenWerks> there shold be no difference between the two.
[23:11] <OvenWerks> snowball is a USB mic?
[23:11] <slidinghorn> yes
[23:11] <OvenWerks> use zita-a2j to connect it
[23:12] <OvenWerks> other wise you will have input to jack only
[23:13] <OvenWerks> In other words set up jack with your output device and then add the snowball with zita-a2j
[23:13] <slidinghorn> okay
[23:15] <OvenWerks> zita-a2j -j mic -d hw:snowball  -r 48000  -p 128 -n 2 &
[23:15] <slidinghorn> hmm...typing zita into my search only pulls up zita-mu1, zita-Rev1 and AT1
[23:15] <OvenWerks> or something like that
[23:16] <slidinghorn> oh I have to call it via CLI - got ya
[23:16] <OvenWerks> sigh, I thought it was included
[23:17] <slidinghorn> apt-cache policy shows zita-ajbridge is installed...apparently it's not in the menu though
[23:17] <OvenWerks> ya, in qjackctl connections window and "mic" port should just show up
[23:17] <OvenWerks> no it is not in the menu
[23:17] <OvenWerks>  it has no gui
[23:18] <OvenWerks> it can be added to qjackctl though
[23:20] <OvenWerks> in the qjackctl setup window in the Options tab there is a line with checkbox called: Execute script avter Startup.
[23:20] <OvenWerks> the zita-a2j line can go there
[23:20] <OvenWerks> Then it will start at the same time as jack does
[23:20] <slidinghorn> without the ampersnad, I take it?
[23:20] <OvenWerks> the & is needed
[23:21] <slidinghorn> ah, ok
[23:21] <OvenWerks> it lets control return to qjackctl
[23:22] <slidinghorn> (sorry for all the dumb questions - completely new at this)
[23:24] <OvenWerks> we all start somewhere