gabriele93 | hi | 07:53 |
---|---|---|
gabriele93 | ubuntustudio 12.04 have installed XFCE | 07:53 |
gabriele93 | can i replace it? | 07:55 |
gabriele93 | but with the same options? | 07:55 |
=== Anthony is now known as Guest94728 | ||
Guest94728 | Hey Guys. I've install last version of Ubuntu Studio and I can't find something like System->Preferences->Keyboard Shortcuts | 09:22 |
Guest94728 | I would like to open even terminal using shortcuts but standard Ctrl +Alt +T does not work | 09:23 |
Guest94728 | i've reconnected from Xchat.. | 09:29 |
an-y | so, if anyone know how to set up key shortcuts in ubuntu studio please answer, thanks. | 09:30 |
mighty_aboba | This jackd is killing me %) | 14:35 |
ailo | mighty_aboba: Why us that? | 14:39 |
ailo | is* | 14:39 |
mighty_aboba | The errors on stop | 14:39 |
mighty_aboba | and on start | 14:40 |
mighty_aboba | it don't want to start | 14:41 |
ailo | mighty_aboba: There's a bug with qjackctl not being able to stop jackdbus (which is the default) | 14:43 |
ailo | mighty_aboba: In a terminal do: killall -9 jackdbus | 14:43 |
ailo | Then use qjackctl to start jack again | 14:43 |
mighty_aboba | yes, i have script in settings | 14:44 |
ailo | mighty_aboba: We are hoping to backport the newer version of qjackctl as soon as possible, which hopefully will not suffer from this issue | 14:44 |
ailo | It is an annoying bug :P | 14:45 |
len-dt | Using jack_control from commandline seems to work better. | 14:45 |
mighty_aboba | when i press on exit in qjackctl it is killing jackdbus | 14:45 |
len-dt | That is one of the changes. | 14:45 |
mighty_aboba | but it is not main problem now | 14:45 |
mighty_aboba | I don't understand one thing | 14:46 |
mighty_aboba | I kill jackdbus | 14:47 |
mighty_aboba | and start qjackctl again but jackd is not starting | 14:47 |
holstein | for troubleshooting, i use "gksudo qjackctl" | 14:47 |
ailo | holstein: This is not a privilege issue. | 14:48 |
holstein | i also just suggest not using JACK if you dont need it | 14:48 |
ailo | mighty_aboba: So, is jackdbus still running after you quit jack? Did you check? | 14:48 |
holstein | ailo: sure.. i just do it first to make sure i have the device configured | 14:48 |
mighty_aboba | http://ShareText.org/D5NX | 14:48 |
mighty_aboba | it is the output | 14:48 |
holstein | if it starts as root, then i *know* its supposed to start | 14:48 |
len-dt | I have found jackd to be more temperamental of late. | 14:49 |
mighty_aboba | when i'm start it | 14:49 |
holstein | could have the settings set too extreme as well | 14:50 |
ailo | mighty_aboba: I think jackdbus is probably still running | 14:50 |
ailo | To make sure, check for the process in whatever app you prefer | 14:50 |
holstein | yeah, that too... if you didnt stop it, or issue the kill command ailo suggested mighty_aboba | 14:50 |
mighty_aboba | ailo: Yes I check | 14:50 |
mighty_aboba | It is not still running | 14:51 |
holstein | mighty_aboba: drop us some error messages | 14:51 |
ailo | mighty_aboba: Did you try restarting pulseaudio? Could be the pulseaudio jack module is causing problems | 14:51 |
ailo | Just killall pulseaudio, so it restarts | 14:51 |
holstein | mighty_aboba: restart the computer if you cant sort out what it what | 14:51 |
ailo | mighty_aboba: Also, do you need pulsaudio to connect to jack? If not, disable dbus support in qjackctl, and you will not get this problem | 14:52 |
holstein | bigger question is, do you need JACK... if not, just dont use it and you wont have this problem ;) | 14:53 |
mighty_aboba | yes, i need | 14:53 |
mighty_aboba | very much | 14:53 |
ailo | mighty_aboba: pulseaudio, or jack? | 14:54 |
mighty_aboba | I kill pulseaudio | 14:54 |
mighty_aboba | now | 14:54 |
mighty_aboba | and tryied to start jackd | 14:54 |
mighty_aboba | same results | 14:54 |
mighty_aboba | errors on start | 14:55 |
mighty_aboba | I kill pulseaudio and jackdbus before | 14:55 |
mighty_aboba | http://ShareText.org/D5NX | 14:55 |
mighty_aboba | error messages | 14:55 |
holstein | i would look in "ps aux" for it | 14:56 |
holstein | looks like hw:2 is selected? | 14:56 |
mighty_aboba | yes | 14:56 |
mighty_aboba | i select my second card | 14:56 |
holstein | good luck!.. i gotta run, but ailo and len-dt are on the case! | 14:57 |
holstein | i usually suggest disabling one card in the bios if possible | 14:58 |
ailo | He can start it, but not twice | 14:58 |
ailo | After quitting, it won't start again | 14:58 |
len-dt | in pavucontrol try configuring the card you are not using to off | 14:58 |
ailo | Usually, it's jackdbus that needs to be killed. My second guess was PA making trouble. What else is there? dbus? | 14:58 |
mighty_aboba | My secondcard is USB | 14:59 |
len-dt | minr too. | 14:59 |
len-dt | I have to go to the PA mixer and turn off my first card. | 14:59 |
ailo | holstein: Hey, you need to be relieved once in a while. Catch you later | 14:59 |
mighty_aboba | My pulseaudio is killed now | 15:00 |
len-dt | PA respawns | 15:00 |
ailo | mighty_aboba: Do you need pulseaudio to connect to jack? | 15:00 |
len-dt | as soon as you kill pulse it restarts. | 15:01 |
ailo | Yeah, killing pulseaudio should reset it | 15:01 |
mighty_aboba | ok, last news) | 15:03 |
mighty_aboba | if i select not alsa in settings | 15:04 |
mighty_aboba | press OK | 15:04 |
mighty_aboba | and again enter to settings and select alsa and hw:2 | 15:04 |
mighty_aboba | it is working | 15:04 |
ailo | weird | 15:04 |
ailo | That sounds like a bug | 15:04 |
mighty_aboba | very strange behavior | 15:05 |
len-dt | Its pulse trying to do too much and jack being too dumb :-) | 15:05 |
len-dt | same stuff we were just talking about ailo | 15:05 |
ailo | Not qjackctl? | 15:06 |
ailo | He gets it working by adjusting qjackctl settings, but not starting jack | 15:06 |
ailo | mighty_aboba: If you have the time, please report it here https://sourceforge.net/tracker/?group_id=86211&atid=578826 | 15:06 |
ailo | That's the bug tracker for qjackctl | 15:07 |
ailo | I would assume it's a qjackctl bug | 15:07 |
mighty_aboba | Just second | 15:07 |
ailo | Wow, only one bug reported this year | 15:08 |
mighty_aboba | I think it is not a bug | 15:08 |
mighty_aboba | i'm trying to repeat all actions | 15:09 |
mighty_aboba | Now i don't understand why it didn't start | 15:10 |
ailo | mighty_aboba: If it does happen again, do consider reporting it as a bug. | 15:13 |
mighty_aboba | Okey:) | 15:13 |
mighty_aboba | I think it is not a bug, because it problem is effect of "on stop" bug | 15:15 |
mighty_aboba | I think so | 15:15 |
mighty_aboba | Does anyone know why "on stop" bug has appeared in this release? | 15:19 |
ailo | mighty_aboba: You mean, "Execute script on Shutdown"? | 15:19 |
ailo | I would add "killall jackdbus -9" as a "..after Shutdown", to make sure qjackctl is no longer doing anything with jackdbus | 15:20 |
ailo | I meant "killall -9 jackdbus" of course | 15:22 |
mighty_aboba | ailo: You mean, "Execute script on Shutdown"? | 15:24 |
mighty_aboba | yes, but 'after Shutdown' | 15:24 |
len-dt | if there is trouble qjackctl never gets to after | 15:25 |
ailo | len-dt: Are you saying the "after" doesn't happen, if jackdbus is not stopped as it should? | 15:27 |
len-dt | That is what seems to be the case. | 15:27 |
ailo | How so? | 15:28 |
len-dt | qjackctl goes nonresponsive | 15:28 |
ailo | jackdbus was not running | 15:28 |
mighty_aboba | It is happen | 15:28 |
ailo | qjackctl was working, but just not starting jack again | 15:28 |
mighty_aboba | When i press stop | 15:28 |
len-dt | qjackctl only knows what dbus tells it. | 15:28 |
mighty_aboba | i have error messages | 15:29 |
mighty_aboba | it is "on stop" bug | 15:29 |
len-dt | Part of the problem is with the dbus to jack stuff not sure if that is dbus or jack. | 15:29 |
mighty_aboba | but i have script "after shutdown" which kill jackdbus on exit | 15:30 |
len-dt | I tested this quite a bit with jack_control from command line and saw some of the same issues. | 15:30 |
mighty_aboba | and on new start all ok | 15:30 |
ailo | len-dt: I see it now. | 15:31 |
ailo | len-dt: I just tried using the "after shutdown" script to stop jackdbus | 15:32 |
len-dt | I am not sure if the bug has been filed against jackd, but it should. because the problem happens when using all jackd package tools. | 15:33 |
ailo | Actually, now I can't make the bug happen | 15:34 |
ailo | I need to check more | 15:34 |
ailo | It seems that the "after shutdown" actually does work for me | 15:35 |
ailo | nope | 15:36 |
len-dt | Ya I found if I did start stop many times the problem happened less than farther apart | 15:36 |
ailo | I finally got it to hang with the script | 15:36 |
len-dt | Anyway, I have to go... | 15:37 |
ailo | But... | 15:37 |
ailo | jackdbus was killed | 15:37 |
ailo | It was just qjackctl that hung for me | 15:37 |
ailo | Well, I would need to test more.. See you len-dt | 15:38 |
licensed | hello. i would like to buy a USB soundcard.. anyone can tell me one good? | 23:06 |
len-dt | licensed, How many channels? | 23:46 |
licensed | len-dt, don't matter.. do you know if usb soundcard haves bigger delay than pci soundcards? | 23:46 |
licensed | i need midi input only | 23:46 |
len-dt | Midi I don't know. | 23:47 |
len-dt | I have heard that usb midi can be a problem. | 23:47 |
len-dt | My USB IF is audio only. | 23:48 |
len-dt | The only report I have heard licensed, is that the timing was "all over the place" Not late only but varying amounts. | 23:52 |
licensed | len-dt, what you recommend for use midi? | 23:54 |
licensed | i need midi soundcard | 23:54 |
len-dt | licensed, I use an old ensoniq card game port | 23:54 |
len-dt | licensed, I have not been able to play with a USB midi IF, so I haven't had a chance to play with settings. I have heard that CPU timer settings are important | 23:55 |
len-dt | In particular the hi rez timers. | 23:56 |
licensed | yes it's very important | 23:56 |
len-dt | licensed, By default UbuntuStudio does not come with the hi res timers readable in user space. | 23:56 |
licensed | i'm starting with home studio.. i would like to record some songs, with my piano | 23:57 |
len-dt | Do you have a USB midi port? | 23:57 |
len-dt | This site has the info on letting userspace read timers: http://wiki.linuxmusicians.com/doku.php?id=system_configuration | 23:58 |
licensed | no i don't have.. I use onboard soundcard from my gigabyte motherboard | 23:59 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!