[01:34] <ubuntu-studio> ubuntu-sutdio
[02:51] <designbybeck> how do change the resize windows, to be like Ubuntu? aka Alt+MMB for resize not Alt+RMB
[02:56] <holstein> designbybeck: i would look in the xfce keyboard shortcuts.. or just use unity and whatever software you want from ubuntustudio
[02:57] <ubuntu-studio> jgjhg
[02:57] <ubuntu-studio> oyfoutfuf[f[9f[9gug'
[02:57] <designbybeck> hmmmm How well does that work holstein? To use Unity with UbuntuStudio?
[02:57] <holstein> designbybeck: pretty well, if you want unity
[02:57] <designbybeck> can I juse sudo apt-get that ? and it be like Unity?
[02:57] <designbybeck> I do like Unity
[02:58] <holstein> designbybeck: ubuntu-desktop
[02:58] <holstein> designbybeck: i dont use it, so i dont know, but it should work fine.. and it is reported to work fine
[02:58] <designbybeck> holstein:  do you just use the XFCE?
[02:58] <designbybeck> it's not bad, and it is snappy
[02:59] <holstein> designbybeck: i use many things
[02:59] <designbybeck> ;) keep it adventurous!
[03:00] <designbybeck> wow! though that is 800mb+
[03:01] <designbybeck> I'll remove all the scopes this time though!
[06:50] <keith_> Need help figuring out why I lose screen background image and icon font settings between boots. Anyone with a suggestion as to where to start looking for problems?
[13:22] <dave_> Does anyone know what I use to connect my epson artisan 725 printer to ubuntu? I used the printer software inside ubuntu 13.10 already it did not work.
[13:32] <dave_> another quick question which program in Ubuntu Studio 13.10 is a sequencer program?
[14:50] <dpy> hi guys
[14:50] <dpy> is it also possible to use ubuntustudio as a ppa for regular ubuntu?
[14:50] <dpy> brb reboot
[15:13] <OvenWerks> dpy: If you are asking if you can use the ubuntustudio metas in another ubuntu the answer id yes
[15:13] <OvenWerks> I would first instal ubuntustudio-installer and use that to load the workslow you want
[15:16] <dpy> ehm
[15:17] <dpy> OvenWerks: what's the PPA uri to add?
[15:17] <OvenWerks> None needed
[15:17] <dpy> it's already part of ubuntu?
[15:17] <OvenWerks> All the ubuntustudio apps are in the ubuntu repos
[15:18] <dpy> apt-cache search ubuntustudio-installer
[15:18] <dpy> yields no results here
[15:18] <OvenWerks> You can add any app you like to any of the flavours
[15:18] <dpy> I'm on 12.04LTS btw
[15:19] <dpy> (it's also a work laptop, see)
[15:19] <OvenWerks> That would be why :)
[15:19] <dpy> I'd like to avoid having to dual boot this system
[15:20] <OvenWerks> The installer should work on 12.04 so you could download it and insrall manually.
[15:20] <OvenWerks>  It may not be able to install the menu though
[15:20] <OvenWerks> The menu is later too.
[15:20] <dpy> ok
[15:20] <dpy> because I did see there was/is an ubuntustudio 12.04.3LTS also
[15:22] <OvenWerks> The five metas are ubuntustudio-audio *-video *-graphics *-photography and *-publishing
[15:22] <OvenWerks> 12.04.3 is 12.04 with all the updates.
[15:22] <OvenWerks> They are both LTS
[15:24] <OvenWerks> If it is a work computer you have to it pretty stock I would guess
[15:24] <dpy> no, it's not that strict
[15:24] <dpy> but I cannot, say, go go 13 or something
[15:24] <dpy> go go=go to
[15:24] <OvenWerks> The one other package you may need if you are doing audio is linux-lowlatency
[15:25] <dpy> just installed that one
[15:25] <dpy> -hence- the reboot
[15:25] <OvenWerks> Ok
[15:25] <dpy> I still cannot find those packages though
[15:26] <holstein> dpy: what package are you looking for?
[15:26] <holstein> dpy: i would open a GUI package manager such as synaptic and search "ubuntustudio"
[15:26] <dpy> ah wait
[15:26] <holstein> or, just install the individual applications you want
[15:26] <dpy> found it
[15:26] <holstein> !info ardour
[15:26] <holstein> !info gimp
[15:26] <OvenWerks> holstein: Just don't use USC
[15:26] <dpy> had to add the -audio
[15:26] <holstein> ^^ like those
[15:26] <dpy> for apt-cache
[15:27] <holstein> OvenWerks: the software center doesnt show them, correct?
[15:27] <OvenWerks> It is wierd, unless the search is just right it doesn't
[15:28] <dpy> yes
 or, just install the individual applications you want <<--  I yeah I'm going for this route
[15:29] <dpy> I first thought I needed the -rt kernel from ubuntustudio
[15:29] <holstein> dpy: then you need not install any meta packages
[15:29] <dpy> but just read on the wiki that everybody switched to lowlatency
[15:29] <holstein> dpy: you dont "need" the rt kernel.. unless you do need it
[15:29] <dpy> because most rt patches have by now be merged in vanilla
[15:29] <holstein> dpy: no.. "everybody" doesnt switch.. only use it or add it if you need it.. as i suggest with any packages
[15:30] <OvenWerks> There is no RT for 12.04 I have found the lowlatency works for me if I am careful how I set things up
[15:30] <dpy> well I'm trying to run pianoteq in a bit
[15:30] <holstein> dpy: i would start with the generic kernel, and move up as needed
[15:30] <dpy> I'm-I'll be
[15:30] <holstein> dpy: when i use pianoteq, as an appliance, i dont use JACK..
[15:30] <dpy> you don't?
[15:30] <dpy> because It just kinda told me I should
[15:30] <holstein> dpy: correct.. i dont need the overhead, so i dont use it
[15:31] <holstein> dpy: "should" is a matter of use case
[15:31] <dpy> ow.. k
[15:31] <holstein> dpy: if im running it all on the same machine, then i use JACK, and route pianoteq.. but, as an appliance, i dont need JACK, so i done run it
[15:31] <holstein> dont*
[15:31] <dpy> well if pianoteq works really nicely, I might even consider creating some dedicated box that only runs pianoteq
[15:32] <dpy> and just loads pianoteq from upstart
[15:32] <holstein> dpy: it works as advertised
[15:33]  * dpy was thinking of stuffing some old headless laptop inside a 19" 1U rack or something
[15:33] <dpy> to turn pianoteq into a true appliance again
[15:34] <holstein> laptops come with screens attached
[15:34] <dpy> holstein: yes, and sometimes those screens break, and the leftover bit is something I'm considering to put into the 1U rack case
[15:34] <dpy> but it's an idea, not really working on it or something
[15:35] <holstein> should work fine
[15:35] <dpy> holstein: so you just use the ALSA device output?
[15:36] <holstein> dpy: in that scenario, i did.. since i didnt need pulse or jack to do what i was doing
[15:37] <dpy> what is a reasonable value for the buffer size?
[15:37] <dpy> It says 512 by default
[15:37] <dpy> that sounds large
[15:37] <holstein> dpy: i experimented with *many* settings to get the lowest acceptable latency for the hardware
[15:37] <holstein> dpy: that will depend on the hardware
[15:38] <dpy> I'm using a dell precision m4400 with stock audio hardware (intel)
[15:38] <holstein> doenst matter.. all things are a factor.. alsa driver support, system config.. kernel.. whatever
[15:39] <holstein> i can say i tried *many* settings til i found what was appropriate for my needs and the hardware specs
[15:39] <holstein> the latency was around 3 or 4 ms IIRC
[15:40] <holstein> this was an old netbook ...an EEEPC with a 900mhz celeron proc and a gig of ram
[15:40] <dpy> ehh
[15:40] <dpy> without crackling?
[15:40] <dpy> on 900mhz?
[15:41] <holstein> dpy: cracking is not acceptable
[15:41] <dpy> which polyphony?
[15:41] <holstein> crackling.. popping.. none of that
[15:41] <dpy> no it is not, but eeepc sounds awfully underpowered to run pianoteq
[15:41] <holstein> dpy: i dont remember the specifics.. but, it was acceptable
[15:41] <holstein> dpy: i configured the machine to do the job i wanted it to do
[15:41] <holstein> and it did it well
[15:42] <dpy> ok
[15:42] <holstein> polyphony was default IIRC
[15:42] <holstein> i didnt limit it that way
[15:42] <dpy> ok pianoteq seems to run
[15:42] <dpy> let's see if I can find my midi interface (M-audio) to work again
[15:43] <holstein> if i held the sustain pedal down, and laid into all the keys with my forearms repeatedly, i could get it to crackle
[15:43] <holstein> that was acceptable to me
[15:49] <dpy> oh, how nice wouldn't this have been for it to just "work" when I plugged it in
[15:51] <holstein> dpy: the midi usually does.. i would try and test things independently.. get a synth like yoshimi or something you are comfortable with making sound with JACK, for example, then route the midi to it to test the controller and interface
[15:51] <dpy> ah yess
[15:51] <dpy> apt-get install midisport-firmware
[15:51] <dpy> and it worked!!!!!!!!!!!
[15:52] <dpy> holstein: well... pianoteq without even a restart now lists my midisport
[15:52] <dpy> so far so good
[15:54] <dpy> ok, my RD 700 also still boots up (after 1+ year of inactivity)
[15:56] <holstein> not sure that i would bother routing that unit through anything
[15:56] <holstein> i would probably just use it as the sound module and route it back in through an audio device
[15:57] <holstein> i definitely wouldnt bother making a haul-around appliance for a sound from pianoteq if i had that unit
[15:57] <dpy> brilliant
[15:57] <dpy> it works
[15:58] <dpy> ok
[15:58] <dpy> I like the pianoteq's pianos
[15:58] <holstein> sure.. and thats fine, but for me, its not worth the hassle, since those roland ones are quite nice
[15:59] <holstein> im not as knocked out my pianoteq as other folks tend to be though
[15:59] <dpy> ok
[16:00] <holstein> i think *all* fake pianos are pretty much "meh" and a compromise, so i tend to factor in more things.. like simplicity
[16:00] <dpy> but this RD 700 is now 9 years old
[16:00] <holstein> sure.. but what has happened since then in the industry?
[16:00] <holstein> nothing to lug around a stand-alone appliance about, in my opinion
[16:01] <dpy> I agree
[16:01] <dpy> but I now am going to evaluate pianoteq
[16:01] <dpy> haven't bought anything yet
[16:01] <holstein> the roland V is nice, and i would probably have one in some situation.. if i were made of money, or whatever
[16:01] <holstein> and pianoteq *is* nice.. and they support linux officially
[16:01] <holstein> i bought it, and dont regret it at all.. all im saying is, if i had that unit, i would be searching for another piano sound..
[16:02] <holstein> but, its nice to have a piano sound in the box too.. one that is very nice
[16:02] <dpy> great so I plug in my headphone, no audio!
[16:03] <holstein> i would test all of that independently..
[16:03] <holstein> load up a known good audio file in a known good player like vlc and figure out what is up with the headphone port that way
[16:04] <dpy> fixed, headphone channel was muted
[16:04] <dpy> it works now
[16:04] <holstein> sure.. and for the record, thats not a "fix" ;)
[16:04] <dpy> :)
[16:07] <dpy> Okay, this doesn't sound too convincing yet, indeed
[16:09] <dpy> okay, one thing it definately does better than the RD 700 piano is sustain
[16:09] <dpy> this is a proper sustain
[16:10] <dpy> on my RD 700 I can just press sustain forever and it will just decay quickly anyhow
[16:12] <dpy> ah now I have presets that sound definately better than the RD 700
[16:13] <holstein> cool
[16:13] <holstein> no doubt, pianoteq is a good value
[16:14] <dpy> what's the AB/BA thing?
[16:14] <holstein> AD/DA ?
[16:14] <dpy> no they are piano presets
[16:14] <dpy> Foo AB
[16:14] <dpy> and Foo BA
[16:14] <holstein> mic config..
[16:15] <holstein> http://www.forum-pianoteq.com/viewtopic.php?id=2252
[16:15] <holstein> fake mic placement tweaks
[16:15] <dpy> ah merci
[19:07] <djbatman> hello
[19:07] <djbatman> wow still installing ubuntu studio and this already works? :)
[19:08] <GridCube> djbatman, it should :)
[19:09] <djbatman> yes yes
[19:09] <djbatman> amazing
[19:17] <djbatman> :)
[21:59] <keith_> hey folks. Got a problem with sound getting crackly when using alsa directly. Any idea why that would happen?