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