[09:55] <cub> Hi NickG, I put up my tutorial on installing a local LEMP server yesterday
[10:32] <cub> zequence: are you around?
[10:32] <zequence> cub: Yeah
[10:33] <cub> hi, I was just playing around with recordmydesktop to do tutorials
[10:33] <cub> and installed the gtk-recordmydesktop as well, and it was placed in the menus under "Media Playback"
[10:33] <cub> perhaps it should be moved to Video Production?
[10:34] <zequence> cub: Len does the menu customization mostly
[10:34] <zequence> OvenWerk1: ^
[10:34] <cub> aha. Perhaps that's changed in 13.04 though?
[10:34] <cub> since it's installed by default then I think?
[10:34] <zequence> haven't checked
[10:38] <cub> strange, it will not capture my whole screen. A small bit on the left and right of screen is cut
[10:50] <cub> ok that's just how it works. 1366x768 will be recorded at 1354x768.
[10:50] <zequence> cub: If you want jack support, you need a patched version of the program I think
[10:51] <zequence> I have built one for raring here https://launchpad.net/~zequence/+archive/testing?field.series_filter=raring
[10:55] <cub> To start out I'm not going to do any voice over so I record with no sound
[13:32] <OvenWerk1> zequence: we lost two computers yesterday...
[13:33] <OvenWerk1> 10 hours apart.
[13:34] <OvenWerk1> My server has been downgraded to a 300mhz pentium :P
[13:37] <OvenWerk1> It looks like I will have to go through all my service startup scripts and add 120 second delays so that the if is actually running
[14:08] <OvenWerk1> zequence: You have probably seen this.. but: http://git.kernel.org/linus/e194401783
[15:16] <OvenWerk1> zequence: sent a note to the qjackctl author. Asking if it is possible for qjackctl before starting jackdbus, to check for a running jackd server.
[15:18] <OvenWerk1> If found, qjackctl could either just run jackd mode till next jackd stop or stop that instance and restart. It could put up a dialog to ask which to do or be a setting.
[15:19] <OvenWerk1> It should look to see that the running jackd has the same sever name as what it wants to start... just in case someone is trying to run two jack servers :)
[15:42] <NickG> In regards to Cubs statement: I installed Kazaam (a screenshot tool) and it too defaulted to the media playback submenu.  I was looking everywhere for it.
[16:14] <OvenWerk1> NickG: Kazam was not something I thought of I will probably have to change that. I have to install both of them to make sure I get the right desktop file name.
[16:15] <NickG> Right on.  It's easy enough for me to change what menu that appears in, it just kinda threw me off there for a few minutes.
[16:16] <OvenWerk1> I guess I had better do "recorditnow" (for KDE while I am at it.
[16:26] <OvenWerk1> NickG: recordmydesktop is already moved to video. I will do kazam and recorditnow as well.
[18:16] <zequence> OvenWerk1: I had a talk with Rui about qjackctl
[18:17] <zequence> according to him, qjackctl was never featured to stop jack, if not started by qjackctl
[18:17] <zequence> I made a case about why it should
[18:26] <zequence> OvenWerk1: I'll have a look at if that patch got through to our kernel, or not
[19:51] <OvenWerk1> zequence: Ya, but even if qjackctl alerted the user there was another one running it would be helpful. Also, I have found that not true :) It will always stop a jackdbus version started by jack_control for example. (at least it has for me) I think if qjackctl is in jackd mode it does too, but I would have to look.
[19:52] <OvenWerk1> I think people just don't expect something to be running if they didn't start it.
[19:52] <zequence> it doesn't
[19:52] <zequence> It only stops jackd that it started itself
[19:52] <zequence> it appears to stop jackd, but it doesn't
[19:52] <zequence> jack is often started by jack applications
[19:52] <OvenWerk1> dbus is probably what I was thinking of then.
[19:53] <zequence> which I think is how it should work anyway
[20:00] <OvenWerk1> In any case, I think qjackctl should detect that jack is running as a d even if it is set up for dbus. Give a dialog offering to just use the one that is running, or not and fail in an obvious manner if the user asks to start anyway and the device is being used by the first jack already running.
[20:01] <OvenWerk1> The dialog should tell the user that qjackctl settings will not affect an already running jack as well.
[20:02] <zequence> That I believe it does. If you change a setting, and click OK, it let's you know that
[20:02] <OvenWerk1> I don't know if the non-dbus jack has a way for a process to tell it to exit
[20:03] <OvenWerk1> Ya but there is no dialog that says "there is already a jackd running, I may not be able to start a new server, <connect to the running jack> <start a new jack server> <Cancel>"
[20:04] <zequence> when you start qjackctl, and jack is already running, qjackctl is in active mode
[20:04] <zequence> you can make conections and everything
[20:04] <zequence> when you click stop, it looks like you stopped jack
[20:04] <zequence> but you didn't
[20:05] <zequence> when you click start, you just make qjackctl active with jack again
[20:05] <OvenWerk1> Only if qjackctl is in non-dbus mode and the one already started is also jackd. If jackd is running and qjackctl is set to jackdbus, it doesn't seem to know there is one running.
[20:06] <OvenWerk1> If qjackctl has dbus turned off, it will find a running jackd or running jackdbus
[20:06] <zequence> That's not how it works for me
[20:07] <zequence> the only difference is, when you stop and then start, starting again will start jackdbus
[20:07] <zequence> So, you end up having both jackd and jackdbus running
[20:09] <OvenWerk1> Not here. I started jackd with jackd -d  alsa -d hw:1 in a terminal.
[20:09] <zequence> OvenWerk1: Which release is that?
[20:10] <zequence> or, which version of qjackctl
[20:10] <OvenWerk1> Then I started qjackctl. Nope maybe he has already fixed that.
[20:10] <zequence> he didn't say he had to me
[20:10] <OvenWerk1> That should fix our problem then
[20:10] <zequence> OvenWerk1: Could you please let me know which qjackctl version you are running before stating problem fixed
[20:10] <OvenWerk1> You are right it doesn't stop the server though
[20:11] <OvenWerk1> .3.10
[20:11] <zequence> ok. I'll try it soon too
[20:12] <zequence> though, if jack is running, a jack control application should always show it
[20:12] <zequence> and be able to stop it, no matter which kind of jack it is
[20:13] <OvenWerk1> Also, if I tell qjackctl to stop jackd, it says it does... which as you say it shouldn't... but if I restart qjackctl it again shows jackd running.
[20:13] <zequence> yes, as I just said
[20:13] <OvenWerk1> So yes qjackctl should confirm that jackd has gone away. And it should be able to force it to go away
[20:13] <zequence> it appears to be stopping jack, when it in fact qjackctl is just being deactivated
[20:16] <OvenWerk1> qjackctl does stop a jackdbus started by jack_control though.
[20:18]  * OvenWerk1 wanders off for lunch
[20:18] <zequence> jackdbus is designed for a single instance only, so that makes sense
[20:41] <cub> I couldn't find the background image for the web site in the ubuntustudio-art, could I get a copy somewhere?
[20:41] <zequence> cub: it's in the website source
[20:41] <zequence> just a minute
[20:42] <zequence> https://code.launchpad.net/~ubuntustudio-website/ubuntustudio-resources/website-wordpress
[20:43] <zequence> cub: ^
[20:43] <zequence> It's not a background image though
[20:43] <zequence> there's at least two graphical elements
[20:43] <cub> Excellent, thanks
[20:46] <cub> Hmm I see that now
[20:46] <cub> I thought it would look good as a background for the intro of tutorial videos
[20:47] <cub> to get some familiarity
[20:47] <zequence> cub: if you need to use a background image, use the G+ cover
[20:52] <cub> There's not much space for the information about the video, such as title
[20:52] <cub> I'll see what I can come up with..gotta go
[21:38] <holstein> OvenWerk1: im just getting back.. but i think i missed what you pinged /me about
[23:16] <OvenWerk1> holstein: Ya, it was a firewire issue, but turned out to be just jackd already running.