[00:52] <holstein> velho: the "actual" risk is.. its *not* ubuntu anymore
[00:53] <holstein> velho: they are not our sources, and we (ubuntu/ubuntustudio) cant say they are stable or not
[00:53] <holstein> velho: now, i *do* know, and trust falk, as i said before.. falk is the kxstudio developer
[04:14] <velho> holstein, I wish to have the best of both UbuntuStudio and KXStudio worlds. If I see any incompatibilities, I'm willing to resolve them. Solving problems = learning :)
[04:14] <holstein> velho: you will be running kxstudio
[04:14] <holstein> which is fine
[04:15] <velho> holstein, I'm still running UbuntuStudio. I didn't add the kxstudio desktop (yet), just the apps+plugins repos
[04:16] <holstein> velho: if you added the repos, then, thats what you are using.. *not* ubuntustudio
[04:16] <holstein> velho: which again, is fine.. but, its *not* ubuntustudio anymore.. they are not the ubuntustudio applications anymore
[04:17] <velho> It seems to me that the kxstudio has more programs and plugins, but after updade, upgrade, and distro-upgrade everything, I didn't see ardour3. I found it very strange... thought if would be a default to US and KXS
[04:17] <holstein> velho: it is
[04:18] <holstein> falk packages and maintains an ardour3, and ubuntustudio has been shipping with it since it was released
[04:18] <velho> holstein, it was not on my system. had to install it alone
[04:18] <holstein> velho: its on mine,
[04:19] <holstein> velho: it ships with ubuntustudio
[04:19] <velho> holstein, I thought so! that's why I found it so strange...
[04:19] <holstein> velho: sure.. but, its not so strangs
[04:19] <holstein> strange*
[04:20] <holstein> velho: you "play around" with the system, a lot.. which is fine, but, you can remove things and change things and not realize what is happening in the background
[04:20] <velho> holstein, I'm a danger to myselt in Linux, lol :D
[04:22] <velho> still learning how its supposed to work. want to understand the core system, specially for audio
[04:22] <holstein> well, it ships as its supposed to work.. but, you are welcome and encourages to change it as you please
[04:23] <holstein> i always install ardour from the ardour site directly, anyways.. i pay for the prebuilt binary rigth from paul
[04:24] <velho> holstein, are there aditional ardour packages in synaptic?
[04:24] <holstein> velho: check and see.. ardour2 should still be there
[04:24] <holstein> there is just ardour..
[04:24] <velho> I only installed ardour3. Any problems if I install ardour allong ardour3?
[04:25] <holstein> velho: i have them both installed.. you should be careful with your sessions..
[04:25] <velho> holstein, by "carefull" you mean: separate project folders for different ardour versions, I guess?
[04:26] <holstein> why guess?
[04:26] <holstein> i can only tell you what i do.. which is, what i read to do at the ardour site..
[04:26] <velho> holstein, gonna check the site ;)
[04:26] <holstein> a2 (which is ardour2) sessions open in a3 (ardour3).. but, you get a new session name
[04:27] <holstein> so, what do i do? i copy.. and i maintain different copies
[04:27] <holstein> though, i dont use ardour3 anyways..
[04:27] <holstein> i just keep it for testing.. i personally use the commercial product mixbus, which is based on ardour2, and the sessions are ardour2 sessions
[04:28] <holstein> i am equally careful with those sessions. i always make a backup, using the 3 2 1 rule, for missions critical data
[04:29] <holstein> i'll track, then, i'll *immediately* make a copy onto a drive or 2 and let someone else have a copy at a different location, if its that important
[04:29] <holstein> if its something im paid to make sure happens, i make sure it happens..
[04:30] <holstein> im actually quite experiemental as well.. but, i have backups, and test as much as i can before doing anything in production
[04:30] <holstein> when i ran the kxstudio ppa's on my system regularly, i ran 2 machines.. i would update one, and test *everything* before updating my production machine
[04:31] <holstein> now, i go with more of an AVlinux "appliance" approach, and just dont update my production rig, and dont have it online anyway
[04:31] <velho> holstein, inteligent stratergy ;)
[04:32] <velho> holstein, why don't you use ardour3, except for testing? is it buggy?
[04:32] <holstein> velho: no
[04:32] <holstein> velho: i dont need anything it provides, so i dont use it
[04:32] <holstein> velho: im not interested in doing midi with it.. and i like/understand/am-comfortable-with ardour2, so why upgrade?
[04:33] <holstein> when i need something ardour3 provides, or, when mixbus is based on ardour3, and i move on to it, then, i'll use it
[04:33] <holstein> otherwise, im used to a2..
[04:35] <holstein> when i read "new version released", these days, i'll ask "do i need/want a new version?" and "whats my upgrade path?" and "how long to train myself to use the new stuff?"
[04:45] <velho> holstein, well, I hope not to take too long to start making music in linux
[14:53] <delt> Hello
[14:54] <delt> quick question about dns... how can i force the resolver to use my /etc/resolv.conf and not overwrite it?
[14:54] <delt> i'm having problems with some hosts on my network if it just contains "nameserver 127.0.0.1"
[15:06] <rustyraptor> I just installed some programs for cuda. Mainly named "libcuda"
[15:06] <rustyraptor> and xorg crashed.
[15:07] <rustyraptor> it seems like it uninstalled a lot of other packages too.
[15:07] <rustyraptor> I am able to get onto the guest account from recovery mode but I can't fix anything because it doesn't let me sudo or anything.
[15:07] <rustyraptor> what do?
[15:46] <delt> problem solved: moved the file (symlink), made a new copy of it, and did chattr +i on it
[15:49] <delt> btw holstein: i found what was causing that problem with qjackctl
[15:50] <delt> .... there's a "notification area" and an "indicator plugin" - it depends on which one the icon appears, which on my desktop machine is always the indicator plugin, and on my laptop, the notification area
[15:50] <delt> for some reason.
[20:26] <studio_> im very close but still cant get any sound from any linux distro using ardour...
[20:27] <studio_> presently using ubuntu studio
[20:28] <studio_> didnt think that coming from windows 7 cakewalk to linux would be soooo dificult
[20:29] <holstein> studio_: sure
[20:29] <holstein> studio_: you are promised, explicitly, support for windows 7 and cakewalk
[20:29] <holstein> the creators of your hardware dont promise you the same support for linux
[20:30] <holstein> what i suggest is, unplug any audio interfaces, and learn to use jack on the internal audio device
[20:30] <studio_> what should be my first steps  to get midifiles running in ardour?
[20:30] <holstein> *dont* start with ardour.. close it as well.. and start with something like audacious set to the jack driver
[20:30] <holstein> studio_: or, yoshimi
[20:30] <studio_> ok
[20:30] <holstein> studio_: hear literally *anything* on *any* device.. step one
[20:31] <holstein> simlify the applications and devices as needed..
[20:31] <studio_> so ok
[20:32] <studio_> i can gear sounds fine when using hydrogen
[20:32] <holstein> studio_: sure.. but, over JACK?
[20:33] <studio_> not sure  ill check brb
[20:38] <studio_> i cant see in hydrogen where the sounndfad is coming from but i can hear it from the laptop speakers by de
[20:38] <holstein> sure.. so, what i suggest is, unplug any extra audio devices.. usb or firewire.. stop *everything*, and make sure jack isnt running
[20:39] <studio_> ok
[20:39] <holstein> lauch *only* qjackctl or jack control.. set up jack with the default device.. see that jack starts when clicking the start button and runs with no errors
[20:39] <holstein> *then* only after jack is running.. start yoshimi
[20:40] <holstein> you can go back to qjackctl connect and see that the audio is routed properly
[20:40] <studio_> starting jackctl
[20:40] <holstein> then, you can go to yoshimi and use the keyboard in the menu, the virtual keyboard, to generate sounds
[20:42] <studio_> qjackctl started with no errors
[20:42] <holstein> studio_: no
[20:42] <holstein> studio_: qjackctl is the GUI to start jack with
[20:42] <holstein> studio_: qjackctl would launch without errors.. you would the use that tool to configure JACK and press the start button, which would attempt to start JACK
[20:43] <holstein> is that what you mean?
[20:43] <studio_> i have started qjackctl as you suggested
[20:44] <holstein> studio_: ok.. *so*.. following the steps above.. *please* in setup, select the default audio device.. and start jack
[20:44] <studio_> ok
[20:45] <holstein> !proaudio
[20:46] <studio_> starting jack produces a drumbeat.1...2....3....4....etc
[20:49] <studio_> jack started
[20:49] <holstein> studio_: ok. so looking above where i mentioned steps, you *then* can open yoshimi
[20:50] <holstein> studio_: in qjackctl, you'll see "connect".. there, you can connect then things that show up in JACK
[20:50] <studio_> ill try brb
[20:50] <holstein> studio_: in "connect", you connect yoshimi to your audio device.. in the "audio" tab
[20:51] <holstein> *then*, you go to yoshimi, and open, as i stated above, the virtual keyboard from the menu.. you can then click notes on it, and see that you are hearing them
[20:51] <holstein> you shouldnt hear a drumbeat when starting jack, since, nothing else should be on, or open. because i asked you to close everything
[20:52] <holstein> you should literally have qjackctl open.. and now be opening yoshimi
[20:52] <holstein> *nothing* else
[20:54] <studio_> ok yoshima open
[20:55] <studio_> clicked on connect and have connected left and right to yoshma
[20:55] <holstein> *great*.. thats how you connect *everything*
[20:55] <studio_> gotit ok ta
[20:56] <holstein> if you hear yoshimi, then, JACK is working properly..
[20:56] <holstein> do you?
[20:57] <studio_> not sure how to produce notes with yoshima
[20:57] <holstein> studio_: as i stated, in the menu you will see "virtual keyboard"
[20:57] <holstein> studio_: you click on the menu item to launch it.. then, when you click on the virtual keybaord, you hear yoshimi..
[20:57] <studio_> gotit
[20:57] <holstein> *if* things are working
[20:58] <studio_> shows playing but cant hear anything
[20:58] <holstein> studio_: so, you *dont* have jack working properly, then
[20:58] <studio_> it seems so
[20:58] <holstein> studio_: there is *no* reason to go opening ardour, or *anything* else
[20:58] <holstein> studio_: you stay *right* there, til you hear something
[20:59] <studio_> ok
[20:59] <holstein> studio_: open a terminal, and run "alsamixer" see that nothing is muted, and eveything is up to some level
[20:59] <studio_> ok
[20:59] <holstein> studio_: check *all* mute buttons and hardware switches
[21:02] <studio_> cannot see if anything is muted...doest look as if it is
[21:02] <studio_> all meters say 100
[21:02] <holstein> studio_: in "connect", see that you are connecting properly
[21:02] <studio_> one meter says mm
[21:03] <holstein> studio_: you cant trust *any* labels
[21:03] <holstein> studio_: so, just tweak *all* of those settings
[21:04] <studio_> ill have a good fiddle
[21:04] <holstein> thats step one
[21:09] <studio_> gotit yoshima playing...coulnt hear the lower register notes
[21:09] <holstein> studio_: ok.. so, now you know
[21:09] <holstein> studio_: thats how you route things..
[21:09] <studio_> gotit
[21:09] <studio_> thanks a lot
[21:12] <studio_> to play midi do i connect midi capture to midi playback?
[22:25] <LinuxGold> what is the command line for pulseaudio manager (volume control)?
[22:25] <LinuxGold> trying to set up samson c01u mic for audacity
[22:29] <LinuxGold> nvm, got it
[22:29] <LinuxGold> thanks
[22:29] <Unit193> pavucontrol? or paman?  padevchooser?  Depends on what you want to do.
[22:30] <LinuxGold> alsamixer got it done.
[22:30] <Unit193> Heh, that's a handy one.
[22:30] <LinuxGold> oh yes
[22:30] <LinuxGold> :)
[22:30] <LinuxGold> http://vxlabs.com/2013/04/24/samson-c01u-usb-condenser-microphone-on-ubuntu-12-04/