[03:44] <studio-user261> Hello!
[03:45] <studio-user261> My installation of Ubuntu Studio 12.10 seems to be stuck on this step: Dec 15 00:43:29 ubuntu-studio ubiquity: update-initramfs: Generating /boot/initrd.img-3.5.0-17-lowlatency
[03:45] <studio-user261> anyone have any ideas? it's been about 3 hours..
[03:46] <studio-user261> and this is the second time it's done this
[03:46] <holstein> studio-user261: sure... install from a minimal CD and add the packages... try 12.04.. check the md5 sum. try 32bit
[03:47] <holstein> test the hardware
[03:47] <studio-user261> boo 32 bit :( hehe. I did have vanialla Ubuntu 12.04 working fine. Could I perhaps install Ubuntu Studio 12.04 and upgrade it to 12.10? i've never done an upgrade over an existing installation before so I'm not sure how it works
[03:48] <holstein> studio-user261: i would just use 12.04
[03:48] <studio-user261> really? is 12.10 not worth the upgrade, I take it?
[03:49] <holstein> no... especially if its not working for you
[03:49] <studio-user261> haha fair point
[03:49] <holstein> i still have 10.04 installed here on my studio machine
[03:49] <holstein> i very recently installed 12.04 on there beside it
[03:49] <holstein> i will not run any of the development releases there
[03:49] <holstein> i do test them for the team
[03:50] <holstein> what would i do? 12.04.. what do i suggest you do? 12.04
[03:50] <studio-user261> cool! well i'll try that. i'm going to have to leave chat since I'm on the system that's trying to install right now. I'll come back in and tell you if it worked or not. Thanks for the advice!
[03:51] <studio-user261> i'll change my nick to Robut when I come back.. that's much easier to remember than random numbers :)
[04:08] <robut_> installing 12.04 now.. fingers crossed! :)
[04:11] <holstein> well, you know it used to work so it should again
[04:12] <robut> well vanilla did. i never installed studio before. im installing Ubuntu Studio 12.04 this time instead of vanilla :)
[04:13] <robut> well hopefully i am lol
[04:14] <holstein> ubuntustudio is ubuntu.. though it is using xfce instead of unity
[04:14] <holstein> you can always just installl ubuntu and add what you want from our packages
[04:15] <robut> yeah. i thought about doing that, but i never had much luck with Jack specifically, so i figured since it came with studio it might work better out of the box
[04:15] <robut> well, installation just completed! so i guess it worked! Thanks for the advice, holstein !
[04:16] <holstein> things are different since JACK is in the main repos, and we dont have/need a different kernel as ba as we used to
[04:17] <robut> well hopefully i'll have better luck with it this time. I really love the idea of a complete open source workflow, but if it doesnt work reliably i'll have to use winblows *shudder*
[04:18] <robut> well thanks again for the advice! i gotta take off. have a good one!
[05:47] <Chamunks> alsamixer has completely stopped recognizing my onboard audio.
[05:47] <Chamunks> I dont know how to get it back.
[06:44] <ubuntu-studio> hi
[16:42] <prpl> hi, I would like to add "open as administrator" to the nautilus context menu, but need help, thanks
[16:54] <Woogie> Hola!
[16:59] <Woogie> So I'm telling Ardour to sync to jack clock (I'm not sure wether time master bar should be on or off), but how do i set tempo on jackq? Thanks
[19:24] <Woogie> has anyone used ninjam?
[19:30] <len-1304> No, but it does sound interesting.
[19:31] <len-1304> It would lend itself to a particular kind of music.
[19:32] <len-1304> Playing around one chord or related chords
[19:36] <len-1304> Woogie, it looks pretty simple to use. It seems it would require at least one machine with an IP that is visible direct for the server.
[19:38] <len-1304> While a static IP would be handy, static would work ok too with a bit more work.
[19:40] <len-1304> Sorry the second "static" should be dynamic...
[19:47] <len-1304> However there some public servers around... but I don't know how busy they are.
[19:57] <len-1304> Listening to some of the examples, it is obvious that it is easy to make some truly bad sounding stuff. Some of that would be that there are less than talented people trying it. Some is that it takes time to get to know a stranger's playing.
[19:59] <len-1304> I'm listening to one now though that is reasonable though.
[20:20] <MaynardWaters> anyone have thoughts on my troubles mounting a smb read only share?
[20:20] <MaynardWaters> sudo mount -t smbfs smb://set/everything-viewonly /media/everything
[20:20] <MaynardWaters> Mounting cifs URL not implemented yet. Attempt to mount smb://set/everything-viewonly
[20:20] <MaynardWaters> and does not mount
[20:52] <Woogie> len-1304: Yeah, it seems quite fun, I'm giving a shot at compiling the source, these are dark waters to me
[20:52] <len-1304> Woogie, the server or the client?
[20:53] <Woogie> client
[20:53] <len-1304> Makes sense. Do you have friends you are planning to play with or just join the online community of whoever is there.
[20:54] <Woogie> the latter
[20:54] <len-1304> That is probably a good way to start.
[20:56] <len-1304> It seems that as the same set of people play together things get better. I think an open chat channel or even a low BW video channel could be useful.
[21:05] <Woogie> i can't "make" the source package
[21:05] <Woogie> http://pastebin.com/Fz5Ph3ry
[21:06] <len-1304> It looks like you need to have the vorbis dev packages installed.
[21:07] <len-1304> That should include the vorbis *.h files.
[21:08] <len-1304> probably libvorbis-dev is the package you are looking for.
[21:09] <len-1304> After you get that one you find others in the same way that you need.
[21:10] <Woogie> installing...
[21:11] <len-1304> The web page say it needs ALSA, ncurses, libogg, libvorbis installed. I would assume that means the -dev packages would be needed too.
[21:11] <len-1304> (welcome to compiling)
[21:14] <Woogie> *ahem* http://pastebin.com/EYmjJCxp
[21:15] <len-1304> asound.h will be found in alsa something...
[21:17] <len-1304> libasound2-dev?
[21:18] <Woogie> maybe libasound2-dev?
[21:19] <Woogie> sorry, I did not see your previous line
[21:19] <len-1304> Have you installed that package?
[21:19] <Woogie> just done it
[21:19] <Woogie> did it
[21:20] <len-1304> Ok.
[21:20] <Woogie> lemme make
[21:22] <Woogie> yet another dependency not met
[21:22] <Woogie> is there a way to check what's missing all at once
[21:23] <len-1304> I thought ./configure did that.
[21:23] <len-1304> Normal build is to do:
[21:23] <len-1304> ./configure
[21:23] <len-1304> make
[21:23] <len-1304> sudo make install
[21:24] <len-1304> There is normally an INSTALL text file in the root directory of the archive that gives the steps to use.
[21:25] <len-1304> Anyway the ./configure step should list missing things.
[21:25] <Woogie> bash: ./configure: No such file or directory
[21:26] <Woogie> there's no install text file
[21:26] <len-1304> I would have to download and look.
[21:27] <len-1304> However, my wife has come home and I will be spending some time with her.
[21:27] <Woogie> that's ok mate
[21:27] <len-1304> There doesn't seem to be many people around right now, zequence is probably better at doing compiles.
[21:29] <Woogie> I did not paid attention to the website, it list it's dependencies