<html> <head> <style></style></head> <body class='hmmessage'><div dir='ltr'><br><div>From: bart.deruyter@gmail.com<br>Date: Thu, 13 Aug 2015 16:31:48 +0200<br>To: ubuntu-studio-users@lists.ubuntu.com<br>Subject: Re: [ubuntu-studio-users] ubuntu-studio-users Digest, Vol 100, Issue 4<br><br><div dir="ltr">thanks for the tip. <div><br><div>I'll try using the pid to kill jackdbus, though I thought it was killed by right clicking in systemmonitor and clicking on destroy process. </div><div>That did not help to get jackd running again by the way.<br></div><div><br></div><div>I find it weird that it used to work in previous versions of ubuntu and not now. </div><div><br></div><div>I run an external device as soundcard (audiofire12) and don't keep it on every day (I do mind to keep power consumption low, so I don't activate things when I don't need them) . Starting up with jackd running is not an option I'm afraid since my soundcard won't be on, and jack would definately crash.</div><div><br></div>--<br><br>Have two lots of Jack settings saves in qjackctl. Have it your computer start-up with the settings for the onboard audio. If you connect your external interface all you have to do is Stop Jack, chose the settings for your external device, reStart Jack. It's what I always used to do when running Ubuntu Studio.<br></div></div></div> </div></body> </html>