[06:29] <kashem> how do i get source code of ubuntu studio-18?
[06:30] <SlidingHorn> kashem: https://launchpad.net/~ubuntustudio
[06:30] <SlidingHorn> is there something in particular you're looking for?
[06:30] <cfhowlett> https://askubuntu.com/questions/167468/where-can-i-find-the-source-code-of-ubuntu
[06:32] <kashem> thnx :SlidingHorn
[06:45] <SlidingHorn> kashem: please ask questions in one of the channels instead of PMs - that way it can be seen, the answers can be found if others have the same questions, and also, people can keep an eye on the responses (in case someone gives bad information)
[06:45] <SlidingHorn> kashem: in terms of the "blueprint" section of launchpad, see here https://help.launchpad.net/Blueprint
[08:42] <kashem> which firewall i can use?
[08:47] <kashem> SlidingHorn,theres no source-code  there
[08:47] <SlidingHorn> !firewall
[08:56] <kashem> i can not access the sourcecode(Ubuntu studio) from launchpad.net,SlidingHorn
[08:57] <kashem> firewall is ok
[08:57] <SlidingHorn> kashem: the source code for any package within it is available through there...you may have to follow a few links, but it's all there
[08:57] <SlidingHorn> you can also refer to the link that cfhowlett posted earlier
[09:00] <SlidingHorn> I'm heading off to bed (it's 5am here and I haven't slept), but I'll be back on later (and others will be here by then as well, I'm sure)
[09:04] <kashem> thnx,SlidingHorn.
[09:10] <kashem> any VPN in Ubuntu studio?
[11:07] <kashem> is it possible to know if anyone pinging me?plz...Help
[15:45] <OvenWerks> should kashem show up again.... here are two links:
[15:45] <OvenWerks> https://serverfault.com/questions/448541/how-to-know-who-ping-my-computer?utm_medium=organic&utm_source=google_rich_qa&utm_campaign=google_rich_qa
[15:45] <OvenWerks> https://askubuntu.com/questions/430069/how-to-monitor-who-is-pinging-me
[15:46] <OvenWerks> And perhaps point them to server for server question and #ubuntu for desktop questions...
[15:46] <OvenWerks> doing some research might help too.
[18:35]  * SlidingHorn slams head against desk
[18:35] <SlidingHorn> So now that I've restarted, I can't get *any* audio whatsoever
[18:41] <SlidingHorn> jack is somehow now set to autostart (I never set that in any jack controller) and pulse audio now (I'm assuming as a result) won't start, even after I've killed any jack processes
[18:49] <SlidingHorn> I think it's -controls, because any time I open it, the "auto start jack at session start" is checked, no matter how many times I uncheck & apply
[19:35] <SlidingHorn> okay was able to keep jack from auto-loading by deleting ~/.config/autojackrc  however, still can't get pulseaudio to start on session now
[19:56] <studio-user412> why doesn't pressing (window) button bring up the start menu?
[20:02] <SlidingHorn> It's not a default behavior in XFCE
[20:26] <SlidingHorn> For posterity, as I know it's empty here:  Simply starting and enabling pulseaudio using systemctl was the required fix after removing the autojackrc file
[20:26] <OvenWerks> SlidingHorn: that doesn't make sense.
[20:27] <SlidingHorn> OvenWerks: which part?  (if not all of it, lol)
[20:27] <OvenWerks> I will take that as a bug report
[20:28] <OvenWerks> removing autojackrc
[20:28] <OvenWerks> That is not the file that starts jack at session start
[20:28] <SlidingHorn> ...weird.
[20:29] <OvenWerks> actually it does make sense. I have not set defaults.
[20:30] <OvenWerks> so if jack would return false.
[20:31] <OvenWerks> What doesn't make sense also is if you have autostart jack turned off and apply pulse should get reset.
[20:35] <OvenWerks> Ya it works here, uncheck auto start jack and click Apply, jack stops, (jackdbus will still appear with ps) and pulse is restarted and can see all the audio cards... it chooses the wrong one as default of course... so I get no sound unless I change the default back...
[20:36] <OvenWerks> then clicking Auto start jack and apply, jack restarts and pulse sends all its audio to jack
[20:36] <SlidingHorn> hmm...
[20:36] <OvenWerks> SlidingHorn: do you have more than one audio device?
[20:37] <OvenWerks> (internal and usb for example)
[20:37] <SlidingHorn> I *have* more than one, but I never *used* more than one, if that makes sense (at least output)
[20:37] <SlidingHorn> like...my headset has a mic, but I use my snowball instead
[20:38] <OvenWerks> I understand. However, pulse will choose whatever hw:0,0,0 is when it sees audio devices after restarting I think.
[20:39] <OvenWerks> with controls you should be able to use both devices.
[20:39] <OvenWerks> Anything that shows up in "Add"
[20:41] <SlidingHorn> I don't know...maybe I'm not meant to use this system, lol - now my snowball mic doesn't show up under inputs in cadence
[20:42] <OvenWerks> you can not use cadence and -controls at the same time.
[20:43] <SlidingHorn> I'm not trying to use -controls (only opened it again on previous boot to try to find out why jack was auto-loading)
[20:43] <OvenWerks> If you have cadence installed -controls will probably not work and if you use any of the Audio setup controls it may break Cadence's operration.
[20:44] <OvenWerks> You would need to remove one or the other.
[20:45] <OvenWerks> Cadence removes the respawn in pulse, but -controls relies on it being active
[20:46] <OvenWerks> That is a bug. I need to detect Cadence has changed the system and put up a dialog saying I can't run :)
[20:48] <OvenWerks> cadence and -controls both auto load jack. I am not sure if Cadence uses jackd or jackdbus, but if it is not the same as -controls, bad things will happen.
[20:49] <OvenWerks> (your issues will have offspring ;)
[20:53] <OvenWerks> SlidingHorn: I will have to figure out Cadence. I will try building as if it is still qt4 and see if that works.
[20:53] <SlidingHorn> I just feel dumber every time I try to touch anything JACK related
[20:56] <SlidingHorn> jackdbus is running, as I started cadence, however "System Status: CPU Scaling Governor" is greyed out, and Server Status is "Stopped"
[20:56] <SlidingHorn> My mic isn't listed in "Configure > Input"
[20:56] <OvenWerks> SlidingHorn: I am the oposite... if jack is not there I am at a loss with audio...
[20:57] <OvenWerks> if you have zapped autojackrc and logged out and in, everything should normalize to Cadence config.
[20:58] <OvenWerks> Oh... no it won't
[20:59] <OvenWerks> SlidingHorn: if you are going to use cadence, sudo chmod -x /usr/bin/autojack
[20:59] <OvenWerks> then logout and in.
[21:00] <OvenWerks> Cadence will then work correctly
[21:01] <SlidingHorn> I actually removed -controls
[21:01] <OvenWerks> -controls audio setup will not.
[21:01] <OvenWerks> that should work too
[21:02] <SlidingHorn> the issues I mentioned were after doing that and rebooting (the CPU Scaling Gov & Mic not being shown in "Input Devices")
[21:03] <OvenWerks> Input Devices in which place? Cadence of pavucontrol?
[21:03] <SlidingHorn> Cadence
[21:03] <OvenWerks> Have you rebooted?
[21:03] <SlidingHorn> yep
[21:03] <OvenWerks> Hmm, I am stumped then
[21:04] <OvenWerks> is the mic still plugged in? does it need to be unplugged replugged?
[21:04] <OvenWerks> (rebooting does not remove USB power)
[21:04] <SlidingHorn> It's plugged in - pavucontrol shows it and is getting input still
[21:05] <OvenWerks> Oh, that is probably the problem
[21:05] <OvenWerks> Cadence can not bridge something that is being used by pulse
[21:06] <OvenWerks> (I think assuming it is using zita-a2j or alsa-in)
[21:06] <OvenWerks> Jack knows how to tell pulse to drop a device, the other two do not
[21:07] <SlidingHorn> no clue what either of those are, lol - Should I turn off its profile in pavucontrol, close cadence, kill jackdbus & try again?
[21:07] <OvenWerks> Was the mic plugged in at reboot?
[21:07] <SlidingHorn> yes
[21:08]  * OvenWerks wishes he knew what cadence was doing
[21:08] <SlidingHorn> that makes 2 of us :P
[21:09] <OvenWerks> you shouldn't have to kill jackdbus, but setting the mic's profile to off may help.
[21:09] <OvenWerks> telling cadence to force restart after that.
[21:09]  * OvenWerks is just guessing at this point
[21:12] <SlidingHorn> nothin
[21:12] <SlidingHorn> Also, I find it strange that it says "JACK has restarted successfully" but the "server status" is still "stopped"
[21:14] <OvenWerks> what does this give you: cd /tmp && wget http://jackaudio.org/downloads/adevices.sh && bash ./adevices.sh
[21:15] <SlidingHorn> http://paste.ubuntu.com/p/5HRbqSCF9c
[21:18] <OvenWerks> Wowo you have a lot of audio devices.
[21:19] <OvenWerks> you are right jackdbus is not running
[21:19] <OvenWerks> pulse is connected to everything
[21:20] <SlidingHorn> honestly, all I need are the devices listed as cards 3 & 4
[21:20] <OvenWerks> your headset is USB?
[21:20] <SlidingHorn> yes
[21:21] <OvenWerks> (ah so hea does not stand for "happily every after"?
[21:21] <SlidingHorn> if only
[21:22] <OvenWerks> hea comes from a kids movie...
[21:23] <OvenWerks> I don't know why cadence can't deal with that, at least it should be able to start jack with card 4 connected.
[21:23] <OvenWerks> jack_control start says what?
[21:26] <SlidingHorn> "---start"  (took over my terminal
[21:28] <OvenWerks> so it never came back to the prompt.
[21:28] <SlidingHorn> oh there it is
[21:28] <OvenWerks> was there an error? or just a long time?
[21:29] <SlidingHorn> DBus exception: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did no t send a reply, the message bus security policy blocked the reply, the reply timeout epired, or the network connection was broken
[21:29] <OvenWerks> killall -9 jackdbus
[21:30] <SlidingHorn> then try again?
[21:30] <OvenWerks> so cadence :"Server started" indication just means we sent the start message so we assume it is running
[21:30] <OvenWerks> jack_control start
[21:31] <OvenWerks>  -1 for cadence ;)
[21:32] <SlidingHorn> same thing - (should cadence not be running when I do this?)
[21:32] <OvenWerks> If it errors out again... it probably means that you have tried some setting that the audio device is not able to deal with.
[21:33] <SlidingHorn> what could have changed though?  It worked just fine before I restarted :(
[21:33] <OvenWerks> may be look at ~/.log/jack/jackdbus.log
[21:34] <SlidingHorn> Connection timed out, Driver is not running, cannot lopen client name =dbusapi, failed tocreate dbusapi jack client
[21:35] <OvenWerks> maybe pull out both USB cards and plug them back in. it sounds like they (or one of them is confused
[21:36] <OvenWerks> I am almost to the powerdown, unplug wait 2 min and start over stage :P
[21:37] <OvenWerks> (the unplug is the AC)
[21:37] <OvenWerks> I am assuming you are trying to use the hea as the jack master and the snowball as jack client.
[21:38] <SlidingHorn> ...if by master/client, you mean output/input, then yes?
[21:40] <SlidingHorn> okay so unplugged/plugged both devices (again, though, should cadence be closed & jackdbus killed before all this?)
[21:40] <OvenWerks> no I mean which do you start jack with
[21:40] <SlidingHorn> I don't know what you mean by that, I'm sorry
[21:41] <OvenWerks> I don't know cadence well enough to put it in cadence terms
[21:42] <OvenWerks> but I think the headset is used to start jack and then the snowball is bridged to jack after
[21:43] <SlidingHorn> Previously, under the "Driver" tab of "Configure" the Device/Interface was hea - Input Device was the snowball
[21:43] <OvenWerks> ok
[21:44] <OvenWerks> does jack_control start do any better?
[21:44] <SlidingHorn> need to know if I should make sure cadence is closed & jackdbus killed first?
[21:45]  * OvenWerks doesn't know any more :P
[21:46] <SlidingHorn> did it just in case...
[21:46] <SlidingHorn> same error
[21:48] <OvenWerks> does your headset have to be 44k1?
[21:48] <SlidingHorn> Not that I know of?
[21:49] <OvenWerks> just noting that pulse sets it to 44k1
[21:49] <OvenWerks> (but then that is pulse default)
[21:49] <OvenWerks> What buffer size do you use?
[21:50] <SlidingHorn> IIRC I set it to 128
[21:50] <OvenWerks> That should be ok. lets try something completely different...
[21:51] <OvenWerks> commandline stuff so it will give lot s of output.
[21:51] <SlidingHorn> ok
[21:53] <OvenWerks> jackd -d alsa -d hw:hea -n 2 -p 1024
[21:54] <OvenWerks> You will not get your terminal prompt back unless it fails
[21:55] <SlidingHorn> OvenWerks: http://paste.ubuntu.com/p/qbVQvzPkHW
[21:56] <OvenWerks> Oh sorry it would be Hea... cap H
[21:56] <SlidingHorn> k just a sec
[21:57] <SlidingHorn> it's running
[21:57] <OvenWerks> does ^c stop it ok?
[21:57] <SlidingHorn> yep
[21:57] <OvenWerks> so try the same line but change the 1024 to 128
[21:58] <SlidingHorn> works...
[21:58] <OvenWerks>  control c to stop...
[21:58] <SlidingHorn> taking much longer to stop this time
[21:58] <OvenWerks> killall -9 jackdbus
[21:59] <SlidingHorn> ...still not stopped :/
[21:59] <OvenWerks> maybe 128 is too low.
[22:00] <OvenWerks> jackd is so busy dealing with the device
[22:00] <SlidingHorn> I'd set my AH!
[22:00] <SlidingHorn> HOLD
[22:00] <OvenWerks>  :)
[22:00] <SlidingHorn> Set periods/buffer to 3 instead of 2
[22:01] <SlidingHorn> force restart caused the server status to actually respond and show "Started"
[22:01] <OvenWerks> 3 is ok.
[22:01] <ErichEickmeyer> 3 is good if it's a USB interface, or so I've read.
[22:01] <SlidingHorn> it is
[22:01] <ErichEickmeyer> Yeah, that should keep your xruns to a minimum.
[22:02] <SlidingHorn> so next step is determining why the snowball isn't showing up in "Input Devices"
[22:02]  * ErichEickmeyer uses a mixer at work that acts as a USB interface
[22:02] <OvenWerks> yes, usb works at 1ms intervals... which is 16x3
[22:03] <OvenWerks> no the next step is to get rid of any default jackdbus setup.
[22:03] <SlidingHorn> that too :P
[22:03] <OvenWerks> jack_control ds alsa dps capture none dps playback none
[22:04] <OvenWerks> This will not start jack, jus clear some stuff
[22:04] <OvenWerks> jack_control dps device hw:Hea dps rate 48000
[22:04] <OvenWerks> that will not start it either :)
[22:05] <SlidingHorn> done
[22:05] <OvenWerks> jack_control  dps period 128 dps nperiods 3 start
[22:06] <OvenWerks> this should start with no error
[22:06] <SlidingHorn> ended with --start and no errors...back to prompt
[22:06] <OvenWerks> \o/
[22:08] <OvenWerks> zita-a2j -j Mic -d hw:Snowball -r 48000 -n 3
[22:09] <OvenWerks> Opps I have to run and pick the lovely Laura up from work...
[22:11] <SlidingHorn> ok...when you're back I got - "Warning: only 1 channels are available. (next line) Starting synchronisation." (no new prompt
[22:37] <OvenWerks> So that means you should see your mic available to connect in jack
[22:37] <OvenWerks> Everything should be working as it should...
[22:38] <SlidingHorn> doesn't show in Cadense
[22:38] <SlidingHorn> Cadence*
[22:40] <OvenWerks> In the patch bay?
[22:40] <OvenWerks> Or patchage or the qjackctl connections window?
[22:40] <OvenWerks> or in ardour?
[22:41] <OvenWerks> The main question is what setting in cadence did we get wrong?
[22:42] <SlidingHorn> Looking at Catia, there's a "Capture_1" & "Capture_2"  Right-click > info shows that it's the headset mic
[22:42] <OvenWerks> There should also be a Mic, capture_1
[22:43] <SlidingHorn> (that was after killing the zita-a2j - re-ran it and Mic Capture_1 shows
[22:43] <SlidingHorn> in catia*
[22:44] <OvenWerks> I am going to have to spend time with family for at least a while. It may be tomorrow afternoon before I am back
[22:59] <SlidingHorn> I'll be here :)  Thanks for the help OvenWerks