[00:27] anyone know if it is possible to record your own samples to use as presets in lmms? [03:35] i converted a windows .fon to .bdf and then to .pcf but i can't figure out how to install it [03:36] i mean.. i do "fc-cache -f -v" and it still doesn't get listed, do i have to reboot or something? [03:59] hopla? [04:00] ./join adsfwer [04:25] holstein: isn't the dev channel #ubuntu-studio-dev? [04:26] i'm on a different install, having problems getting online in ubuntu studio right now [04:26] maybe without that dash [04:28] Len-nb: hey, i had problems with raring again, and also, my ubuntu-studio will not go online now. I am booted into Mint at the moment [04:28] wth [04:28] Ok [04:29] had fstab-decode i/o error [04:29] before you left you were saying the file size was 1.9M [04:29] ?? [04:29] that is a .part file [04:29] our ISOs are 2.3 Gig [04:30] i repaet. it was a part file [04:30] So the ISO you used was bigger then OK [04:30] the after running zsync, 2 copies of the iso were in the dir. both identical in size [04:30] one had extension.old [04:30] Makes sense [04:31] yup [04:31] .part smells like firefox ;] [04:31] so anyway, i had same issues as before, but different inode this time [04:31] This is with a DVD or USB stick? [04:31] and something changed my wifi card configuration [04:32] usb [04:32] i cannot initiate wifi in ubuntu studio 12.10 now [04:32] USB stick is 4gig? [04:32] 16 [04:32] OK [04:32] vfat? [04:32] fat32 [04:32] same as i always use [04:33] i have never had this issue [04:33] No I haven't either. [04:33] what exactly is the dev channel id? [04:33] #ubuntustudio-devel [04:33] i have tried #ubuntu-studio-dev #ubuntustudio-dev [04:33] and that [04:33] no one was in them [04:34] my computer is going whacky [04:34] Have you made sure you wer set to freenode... must be now... [04:34] of course [04:34] you are here. [04:35] as I recall on first startup of xchat freenode is not selected [04:35] it is on my other machine [04:35] but no, it's... some other one in mint [04:36] I will download the daily iso here. I can only use the 32 bit though [04:36] anyway, I had some functionality of the system this time, but kept getting i/o errors for everything [04:37] I almost feel like saying try another stick just to be sure [04:37] and wifi would not initiate. [04:37] but the base FS is supposed to deal with bad spots. [04:38] I am using wifi right now. [04:38] i believe something has happened on my other install and changed the mac address of the connection somehow [04:38] Back in a minute [04:38] k [04:38] i'm in devel channel now [06:54] Hi all [06:58] Hi Mick_ === zequence_ is now known as zequence === Haohmaru is now known as antto [13:25] salve a tutti [13:25] aslve a tutti [13:26] avrei bisogno di un aiuto per collegare una chitarra elettrica a ubuntu [13:26] ce qualcuno ce potrebbe darmi una mano?? [13:26] studio-user887: Hi. This is an English speaking channel. I think there might be an Italian one, for regular Ubuntu [13:26] !ubuntu-it [13:27] !it [13:27] Vai su #ubuntu-it se vuoi parlare in italiano, in questo canale usiamo solo l'inglese. Grazie! (per entrare, scrivi « /join #ubuntu-it » senza virgolette) [13:27] thx:) [13:27] You're welcome to ask your question in English too :) [17:49] anyone uses retroshare? [17:59] Alguien que hable español??? [22:24] hello. Does anyone work with JACK and/or Ardour in here? [22:25] mc5: Sure. There are channels for both jack and ardour too #jack #ardour [22:26] Yeah. I was sent here from the #ardour room [22:26] err. channel [22:26] Really? [22:26] yeah [22:26] Apparently not many of them work with Ubuntu [22:26] I guess they're saying Ubuntu does funny things to ardour [22:27] I'm pretty sure that whatever question you have has little to do with the platform you are on [22:27] What kind of problems are you having? [22:27] mostly problems with JACK for right now [22:27] I may have some future problems with the interface I'm running as well, a Line 6 UX1 [22:27] What kind? [22:27] Starting problems [22:27] jack crashes sometimes when you try to stop it [22:28] It's frozen in the background. Could that be it? [22:28] Kill it with: killall -9 jackdbus [22:28] pastebin.com/CCwmxntu [22:28] That is, if you're using jack with qjackctl, and default settings [22:28] I'm using Qjackctl [22:29] Try killing jackdbus: killall -9 jackdbus [22:29] What I just pasted is what popped up when I just opened it [22:29] Then start jack again [22:30] I got this from Terminal: "jackdbus should be auto-executed by D-Bus message bus daemon. If you want to run it manually anyway, specify "auto" as only parameter" [22:30] mc5: Don't start jackdbus from the terminal, just kill it there [22:30] Then use qjackctl to start it [22:31] I'm trying to kill it with that command and nothing [22:31] just that message [22:31] You're doing something wrong [22:31] killall -9 jackdbus [22:32] that did nothing [22:32] Then it worked [22:32] Otherwise it would say, no such process [22:32] ok [22:32] Now, try starting jackw with qjackctl [22:32] jack* [22:33] "D-BUS: JACK server could not be started. Sorry" [22:33] "Could not connect to JACK server as client. - Overall operation failed. - Unable to connect to server. Please check the messages window for more info." [22:34] mc5: Any windows open that uses audio? Like w webbrowser [22:34] mc5: Ever get this error when booted into a fresh session, and trying nothing else but starting jack with qjackctl? [22:35] By open, do you mean on the Launcher? [22:36] Skype is the only window running that would utilize audio [22:36] Ok, that could be a problem [22:36] Close everything down [22:36] Would even save some trouble if you just rebooted [22:37] Also, do you have multiple audio devices? [22:37] just the Interface and the Speakers [22:38] I mean, do you have more than one audio card? [22:39] I should really write a script and let users run it to get some info :) [22:40] not that I'm aware of [22:41] You mentioned a Line6 device [22:41] What do you get from: cat /proc/asound/cards [22:42] 0 [PODStudioUX1 ]: line6usb - POD Studio UX1 Line6 POD Studio UX1 at USB 3-2:1.0 1 [SB ]: HDA-Intel - HDA ATI SB HDA ATI SB at 0x92300000 irq 16 2 [HDMI ]: HDA-Intel - HDA ATI HDMI HDA ATI HDMI at 0x92210000 irq 19 [22:42] er [22:43] http://pastebin.com/RUzArjBa [22:43] Ok, so you have three audio devices [22:44] The line6, your onboard, plus the hdmi out [22:44] mc5: Have you selected a device in qjackctl? [22:44] !proaudio [22:44] For information on professional audio tools in Ubuntu, see https://help.ubuntu.com/community/UbuntuStudio/ProAudioIntro [22:44] That's a page I wrote about the audio systems on Ubuntu Studio [22:45] Input and Output are recognized as Line 6 UX1 [22:46] mc5: Have you ever got that device working with jack? [22:47] I mean, it recognizes it but I haven't been able to really start JACK so I'm not sure [22:47] Ardour recognizes it as well [22:48] Ardour doesn't recognize audio devices itself. It uses one of the audio systems it supports. ALSA or jack [22:48] jack uses ALSA drivers [22:48] So, they're really the same deal in that regard [22:49] mc5: Have you tried starting jack with the HDA ATI SB? [22:50] Before you try, always kill jackdbus, just in case: killall -9 jackdbus [22:50] I have one of those, and I can't get it to work (HDA ATI SB) [22:50] try to start jack with HDA ATI SB and then kill? [22:51] No, first kill, so we don't have a frozen jack in the background, then start jack with the HDA ATI SB [22:51] It would be nice to know if you can start jack at all [22:52] ok just tried switching the Input & Output to HDA ATI SB and it didn't start [22:53] mc5: Don't set input and output separately [22:53] mc5: set them to default, and use "interface" instead [22:54] mc5: Have you changed any other settings? [22:54] came up with the same problems [22:54] if you'd like me to copy and paste the messages, I can [22:56] mc5: Try this in a terminal.. [22:56] pasuspender -- jackd -d alsa -d hw:1 [22:56] Or wait [22:57] First do: killall -9 jackdbus [22:57] Then that command [22:57] pasuspender -- jackd -d alsa -d hw:1 [23:01] mc5: A reboot? [23:02] no. Flash crashed and I didn't realize it [23:02] did you get any of my last messages? [23:02] no [23:02] You should close down any flash videos [23:02] Anything that uses audio [23:02] ok. done [23:03] So, first, just so we can be sure [23:03] killall -9 jackdbus [23:03] Then we try jack from the terminal: [23:03] pasuspender -- jackd -d alsa -d hw:1 [23:03] well. I tried starting with HDA ATI SB in the Input and Outputs [23:03] didn't work [23:03] This is not the same thing [23:03] ok [23:04] I don't want to waste anymore time than you [23:04] The quicker you are, the better [23:05] ok. I got some errors [23:05] Ok, I'll let you know what you've been doing, so you can try stuff yourself [23:05] Let's you know what cards you have: cat /proc/asound/cards [23:06] They aren't always in the same order after rebooting [23:06] I haven't rebooted [23:06] Didn't say you did [23:06] Suspending Pulseaudio can be smart to try, since it sometimes doesn't let go of the audio device otherwise [23:07] pulseaudio == desktop audio [23:07] If pulseaudio is using a different card than jack, than that would be no problem anyway [23:07] I just tried posting this: cat /proc/asound/cards [23:07] in the Terminal and now I cannot type anything else [23:08] Ok, I'm not getting through here. [23:08] What I would do if I were you is reboot [23:08] Then only use qjackctl [23:08] try starting some devices [23:09] Use the command to kill jackdbus in between [23:09] killall -9 jackdbus [23:10] instead of qjackctl, you can also use this command: [23:10] pasuspender -- jackd -d alsa -d hw:1 [23:10] Replace the "1" with whatever card you want to start [23:10] The number you get from reading the output from: cat /proc/asound/cards [23:10] That's it [23:14] # in spanish please [23:14] alright. I'll copy your text right here, reboot, and go from there. [23:14] in spanish please [23:15] mc5: Hope it works out [23:15] mc5: btw [23:15] mc5: one part of the command I showed you: pasuspender -- jackd -d alsa -d hw:1 [23:15] is for suspending pulseaudio [23:15] and that is: pasuspender .. [23:16] pasuspender -- [23:16] The actual command to start jack is: jackd -d alsa -d hw: [23:16] where is your audio device number [23:16] This is not jackdbus [23:16] Anyway, good luck [23:29] just tried using 'pasuspender -- jackd -d alsa -d hw:1' and replaced the 2 to see what would happen with the LIne 6 and I got these messages [23:29] http://pastebin.com/SGzqbeC2 [23:29] mc5: Seems like you're not on Ubuntu Studio [23:30] you don't have realtime privilege [23:30] you need to add yourself to audio group [23:30] ah [23:30] right [23:30] ok. Can you tell me how to do that? [23:30] sudo usermod -a -G audio $USER [23:30] That will add your name next to the audio group in the file /etc/group [23:30] You'll need to logout and login again for the change to happen [23:31] Though, starting jack should work even without rt privilege [23:31] hmm [23:35] "sudo usermod -a -G audio $USER" [23:35] what do I do after that? [23:35] log out and then log back in? [23:35] Yeah [23:36] ok [23:38] alright. so where do I go from here? [23:39] ok JACK is actually starting now [23:41] zequence: so Jack starts now [23:41] I had it going for 20 seconds and then stopped it [23:41] mc5: using your usb device? [23:42] it's actually set on HDI ATI SB [23:42] Well, good to know you can get jack running [23:42] Try the same command with the usb device [23:44] it's starting with Line 6 UX1 [23:45] just tried to start Ardour and it's giving me the same problems [23:46] If you get jack starting with the usb device, it works [23:46] What you do is you start jack, keep jack running, then start ardour [23:47] mc5: If you got the usb device running, you should be able to get it running with qjackctl as well [23:47] qjackctl, using default settings, will start jackdbus, not jackd [23:47] jackdbus is the one that crashes sometimes when you try to stop it [23:47] I'm getting problems now [23:47] out of nowhere [23:48] Well, you have the tools to sort this out now, I think [23:48] The usual workflow is, you start jack first, then whatever jack application you want to use, such as ardour [23:49] actually I don't have the tools [23:50] It was working fine and then I stopped JACK, tried to run Ardour and back to the same problems. [23:50] mc5: I told you. Don't stop jack [23:50] start jack. Then start ardour [23:51] You do have the tools. you just need to make sense of it [23:52] Read this page also [23:52] !proaudio [23:52] For information on professional audio tools in Ubuntu, see https://help.ubuntu.com/community/UbuntuStudio/ProAudioIntro [23:52] It's not starting now [23:52] Should clear some things up [23:52] If jack crashed, and is frozen, kill it [23:52] it hasn't done either [23:52] either it's jackd, or jackdbus [23:53] Well, you'll sort it out [23:53] Time to sleep for me [23:53] I'm fairly certain that I won't but ok [23:53] thanks