[07:16] <studio-user032> ciao a tutti!
[07:17] <studio-user032> sono appena entrato nel mondo ubuntu studio
[10:15] <tjingboem> goodmorning
[10:15] <tjingboem> i tried 13.04 and nvidia in different ways
[10:15] <tjingboem> but was unable to get it working
[10:16] <tjingboem> is this the place to report things like that?
[15:07] <tjingboem> i tried 13.04 and nvidia in different ways
[15:07] <tjingboem> but was unable to get it working
[15:08] <holstein> tjingboem: 13.04 is not released.. try #ubuntu+1
[15:10] <holstein> tjingboem: you tried the drivers from nvidia?
[15:14] <tjingboem> yes, i found 3 different versions in Synaptic, tried them all -no luck
[15:14] <holstein> tjingboem: and the drivers *not* from the repos? the ones from nvidia?
[15:14] <tjingboem> even tried to upgrade from 12.04
[15:15] <tjingboem> i tried the ones that i found in Synaptic after a clean install
[15:16] <tjingboem> did not try the ones from nvidia
[15:16] <holstein> tjingboem: ok.. there are ones at nvidia you can try.. the most recent
[15:16] <tjingboem> that is one step too difficult for me :)
[15:17] <tjingboem> in 13.04 i tried, from the repo, version 173, 304 and 310
[15:18] <holstein> tjingboem: ok.. its not released yet, so thats not a problem
[15:18] <holstein> tjingboem: that is also not ubuntustudio specific
[15:18] <tjingboem> now i'm back to 12.04
[15:19] <tjingboem> i'd rather wait for the release of 13.04 :)
[15:19] <holstein> if you want to run the upcoming releases, you need to hang in #ubuntu+1 and expect breakage
[15:20] <tjingboem> i understand, holstein, but i do not have the time and have to set priorities
[15:21] <tjingboem> i awaiting the Maudiophile Delta 1010LT
[15:21] <holstein> sure, im just saying, in the future.. there is no reason to run a non-stable release unless you are into spending a lot of time with it
[15:21] <tjingboem> that will surely need all my attention to get it to work etc.
[15:22] <tjingboem> you're right...i was too curious
[15:22] <tjingboem> and if the nvidia drivers from the repo worked i would have stayed with 13.04
[15:22] <holstein> they might
[15:22] <holstein> who knows
[15:25] <tjingboem> but i'lll report to ubuntu+1, maybe it is good information..
[15:26] <holstein> i doubt it
[15:26] <holstein> i wouldnt bother unless you have a lot of time
[15:26] <holstein> you get "open a temrinal and run" and you have no 13.04 to test with
[15:26] <tjingboem> okay, holstein, i will keep my mouth shut
[15:27] <holstein> tjingboem: you can search for a bug report, and add yourself if you want
[15:28] <Len-nb> tjingboem, What are you running that needs the nvidia driver?
[15:29] <Len-nb> for most audio work, the open driver is fine
[15:30] <tjingboem> i want 2 monitors
[15:30] <Len-nb> I have an old nvidia TNT2 and none of the nvidia drivers work for that
[15:30] <tjingboem> twinview
[15:30] <Len-nb> Are you sure the open driver doesn't do that?
[15:31] <Len-nb> I can run two monitors with the open driver
[15:31] <tjingboem> no i am not sure, but i never found that information anywhere
[15:31] <holstein> i cant.. i have to have the proprietary one, or so its seems
[15:31] <Len-nb> Plug a second monitor in and check settings manager display to see if it is listed
[15:32] <Len-nb> They default to one on top of the other, but can be moved to side by side
[15:34] <tjingboem> i re-installed 12.04 and the nvidia drivers were installed automatically
[15:34] <tjingboem> i'll look in Synaptic - they are called the nouveau drivers, right?
[15:34] <Len-nb> Ya
[15:34] <Len-nb> They are probably already installed
[15:35] <tjingboem> yes they are
[15:35] <Len-nb> they are part of the kernel modules
[15:35] <tjingboem> i see
[15:36]  * Len-nb wishes I had some newer hardware
[15:36] <Len-nb> I would like to try more stuff out
[15:36] <tjingboem> well - i just bought a 10 year old soundcard :)
[15:36] <tjingboem> new
[15:37] <Len-nb> The ice1712 based cards are good
[15:37] <holstein> those are nice.. good value.. i didnt get it because of the lack of phantom power, and the pci interface
[15:37] <tjingboem> because it just works with linux
[15:37] <holstein> yup.. good linux support
[15:37] <tjingboem> i got a good external mixer with phantom
[15:37] <Len-nb> I have a delta 66
[15:37] <holstein> also, no balanced ins
[15:38] <tjingboem> i just read you can set jumpers on the Delta so that accepts XLR line level
[15:38] <holstein> if i want to use an external mixer, i have to connect unbalanced
[15:38] <Len-nb> my spdif pre has all that
[15:38] <holstein> that will help though.. ^^ and i read that as well
[15:38] <holstein> the jumpers
[15:38] <holstein> that'll get you 2 channels in balanced.. and good quality, and good value
[15:39] <Len-nb> the mackie mixer has enough preamps for the other ip.
[15:40] <Len-nb> The D66 has balanced line ins. but really, with line levels and short cables, there is not enough difference to worry about.
[15:41] <Len-nb> for home use it is possible to make sure electrically noisy stuff is turned off while recording.
[15:44] <IntuitiveLeap> good day all, anyone here have experience with setting up the sound servers on Studio 12 LTS  with Integrated Audio ALC888S-VD?
[15:46] <Len-nb> IntuitiveLeap, does the that interface show up if you type arecord -l in a terminal?
[15:46] <Len-nb> (and aplay -l)
[15:48] <tjingboem> Len-nb, i'm looking at the display setting, but there is only one monitor there
[15:48] <IntuitiveLeap> **** List of CAPTURE Hardware Devices ****
[15:48] <IntuitiveLeap> card 0: SB [HDA ATI SB], device 0: ALC888-VD Analog [ALC888-VD Analog]
[15:48] <IntuitiveLeap>   Subdevices: 1/1
[15:48] <IntuitiveLeap>   Subdevice #0: subdevice #0
[15:48] <IntuitiveLeap> card 0: SB [HDA ATI SB], device 2: ALC888-VD Analog [ALC888-VD Analog]
[15:48] <IntuitiveLeap>   Subdevices: 1/1
[15:48] <IntuitiveLeap>   Subdevice #0: subdevice #0
[15:48] <IntuitiveLeap> thats what i get from arecord
[15:48] <tjingboem> i guess it is because of the nvidia driver?
[15:49] <tjingboem> is there a place where i can choose for the nouveau driver?
[15:49] <holstein> i usually specify in xorg.conf
[15:49] <Len-nb> IntuitiveLeap, then it should just work pretty much.
[15:50] <tjingboem> perhaps i have to de- install the nvidia driver?
[15:50] <IntuitiveLeap> it does work, 'pretty muc', but i have this issue with my analogue microphone just going straight through to the speakers, no volume control, etc.
[15:50] <Len-nb> tjingboem, I am not sure. What holstein just said makes sense though
[15:50] <tjingboem> perhpas there is some info in the ubuntu pages...
[15:51] <IntuitiveLeap> nothing i do with jack or the alsa/pulse settings affects it! >.<
[15:51] <Len-nb> tjingboem, yes this is common to all ubuntu and there are more people doing ubuntu than studio
[15:52] <tjingboem> i will investigate....i have to wait for my Delta 1010LT and can spent my time on issues like these :)
[15:52] <holstein> !ati
[15:52] <tjingboem> so you keep telling me holstein - thanks!
[15:52] <Len-nb> IntuitiveLeap, there may be a monitor level that you can see from alsamixer
[15:53] <IntuitiveLeap> i dont see any monitors listed when i run alsamixer
[15:54] <Len-nb> View: F3:[Playback]
[15:54] <IntuitiveLeap> even the main volume control for the PC doesnt impact the analogue mics volume at the speakers. the only way i can adjust the volume is at the input device (my digital mixer unit)
[15:55] <Len-nb> if you see anything listed as mic, that is a monitor level
[15:55] <Len-nb> (micboost is different)
[15:55] <IntuitiveLeap> so, 'Front Mi' is a monitor?
[15:55] <Len-nb> if it is listed on the Playback screen yes
[15:56] <IntuitiveLeap> yep, that's what im looking at
[15:56] <Len-nb> The mics input level will be on the capture screen
[15:57] <IntuitiveLeap> i wonder why the 'Master' volume on the playback screen doesnt impact the output from Front Mic
[15:57] <Len-nb> That would be HW dependent.
[15:57] <IntuitiveLeap> i have Master set to 0 and 400 deibels coming out my speakers!
[15:58] <Len-nb> There are a lot of different HDA HW that are mostly the same and use the same driver, but have little differences
[15:58] <IntuitiveLeap> it seems as if there is a direct hardware connection between my analogue mics and the speaker output
[15:59] <Len-nb> That would be atypical :)
[16:00] <IntuitiveLeap> lol yes
[16:01] <IntuitiveLeap> aside from this issue though, i like studio ubu. it's a much nicer interface than that unity
[16:01] <Len-nb> Realtek makes a lot of codecs, I would be surprised if they made one like that.
[16:02] <IntuitiveLeap> i am a noob at setting up with jack, likely i am missing a setting that will fix this seeming issue.
[16:07] <Len-nb> I don't think this is a jack issue.
[16:07] <Len-nb> you need to get it right in alsa first.
[16:08] <Len-nb> The alsa stuff seems to think it is the same as ALC886
[16:08] <Len-nb> anyway, getting things set in alsamixer so that mic does not go straight through is the first step.
[16:09] <IntuitiveLeap> any suggestions for changes i can make in alsamixer?
[16:09] <Len-nb> next question is how are you getting the mic into the computer? are you using an external mixer or anything?
[16:10] <IntuitiveLeap> i have a guitar plugged into a Zoom digital mixer/effects board, plugged into my front mic on PC
[16:10] <IntuitiveLeap> (waiting for my s/pdif wires to be delivered)
[16:11] <Len-nb> Ok, and it is not also plugged into your amp?
[16:11] <IntuitiveLeap> im using the mixer as an amp, basically
[16:12] <Len-nb> Second thing, is there a line level input you can plug into?
[16:12] <IntuitiveLeap> it has built in amp modelling, etc
[16:12] <IntuitiveLeap> line in?
[16:12] <Len-nb> Your zoom will have a level that is higher than a mic in is built for.
[16:13] <IntuitiveLeap> i have tried the Line in plug also, unfortunately i only have a stereo connector and line in is mono lol
[16:13] <IntuitiveLeap> but i had the same problem with no volume control using line in
[16:13] <Len-nb> I am guessing that you have guitar->zoom->mic in?
[16:14] <Len-nb> or do you have guitar->zoom->mixer->micin?
[16:15] <IntuitiveLeap> guitar->zoom->mic in is correct
[16:15] <IntuitiveLeap> the zoom is an amp/mixer all in one
[16:16] <IntuitiveLeap> it has stero RCA master out jacks that i am using with a Y adapter to stereo mic in
[16:16] <Len-nb> Are you using it to amplify your output as well then?
[16:17] <Len-nb> or what is your output chain?
[16:17] <IntuitiveLeap> it is doing all the signal processing at the moment, yes
[16:17] <Len-nb> so output is computer out->zoom->speakers?
[16:17] <IntuitiveLeap> i dont have a problem with distorted sound (too high level)
[16:18] <IntuitiveLeap> the audio output is going to my PC's speakers
[16:18] <IntuitiveLeap> which is what i want lol
[16:18] <Len-nb> Just making sure :)
[16:19] <IntuitiveLeap> the problem i am having is that the only way i can control the volume is by adjusting at the mixer, not on the PC
[16:19] <IntuitiveLeap> i mute the PC and it still comes lol
[16:20] <Len-nb> micboost should be 0... mic in the playback panel should be MM. Then in capture..your mic level may show as capture rather than mic.
[16:21] <IntuitiveLeap> on the alsamixer?
[16:21] <Len-nb> yes
[16:21] <IntuitiveLeap> what do you mean MM?
[16:22] <IntuitiveLeap> not sure how to MM it
[16:23] <Len-nb> if you move the cursor over to the mic at the bottom there is a 00 hit m and it should change to MM
[16:23] <Len-nb> means mute
[16:23] <IntuitiveLeap> oh, im in terminal alsamixer
[16:24] <Len-nb> yes
[16:25] <Len-nb> I forgot there is a gui one too. I can't play with that right now though to see how it works on this machine.
[16:25] <IntuitiveLeap> ok i have front mic set to MM on playback and on Capture screen i have input source set to front mic and capture set to 18
[16:25] <IntuitiveLeap> its all good, i am on terminal
[16:26] <Len-nb> ok so you through level works now?
[16:26] <IntuitiveLeap> gonna test it now, gotta fire up everything again
[16:30] <IntuitiveLeap> hmm, now no sound
[16:32] <Len-nb> good.
[16:32] <Len-nb> That is how it should be
[16:32] <IntuitiveLeap> ok , whew
[16:33] <Len-nb> The next thing to do is open up the pulse controler
[16:33] <IntuitiveLeap> im there
[16:34] <Len-nb> if you go to input devices tab
[16:35] <Len-nb> you should see the meter bar on the bottom show activity when you play the guitar
[16:35] <Len-nb> you can adjust the level there too
[16:35] <IntuitiveLeap> do i need to set it as fallback?
[16:36] <Len-nb> I don't see fallback here
[16:37] <IntuitiveLeap> hmm , dont see activity on the meter
[16:37] <Len-nb> But the main thing is to see a level first. If you are going to use jack a lot of the pulse settings don't matter
[16:37] <Len-nb> Are the level lines blue?
[16:37] <Len-nb> can you adjust the levels?
[16:37] <IntuitiveLeap> front left and right are at 'Base'
[16:38] <IntuitiveLeap> yes i can adjust them
[16:38] <IntuitiveLeap> doesnt impact the meter tho
[16:38] <Len-nb> Hmm, does changing the level effect the level on the alsamixer?
[16:39] <IntuitiveLeap> one question ... on the input devices, which device is it that i want?
[16:39] <IntuitiveLeap> monitor of analogue or built in analogue lol
[16:39] <Len-nb> What do you have?
[16:40] <Len-nb> Are you looking at the port or you you have more than one input section?
[16:40] <IntuitiveLeap> yes changing the built in levels moves terminal alsamix
[16:40] <Len-nb> good.
[16:41] <Len-nb> Do you have a line that says port?
[16:41] <IntuitiveLeap> i see three input devices. HDMI (which isnt connected) monitor of built in audio, and built in audio
[16:41] <IntuitiveLeap> nothing says port
[16:41] <Len-nb> you are at the Input devices tab?
[16:42] <IntuitiveLeap> yes in pulseaudio
[16:42] <Len-nb> should be the built in audio
[16:42] <IntuitiveLeap> oh i see port now, its set at front mic
[16:42] <IntuitiveLeap> it was off the screen (too many windows!)
[16:44] <Len-nb> In my case on the meter bar even with no sound plugged in I can see slight bit of blue jiggling at the very left side of the meter bar
[16:44] <Len-nb> when I have the level at 100%
[16:44] <IntuitiveLeap> on  mine it is all the way full , even with the input mixer powered down
[16:44] <Len-nb> at base there isn't
[16:45] <IntuitiveLeap> im at Base
[16:45] <IntuitiveLeap> even at silence it is showing a full meter
[16:45] <Len-nb> What options does port give yoou?
[16:46] <IntuitiveLeap> front mic , rear mic, line in
[16:46] <Len-nb> You want to use line in.
[16:46] <IntuitiveLeap> will it draw from the front mic jack?
[16:47] <Len-nb> Because you are using an external preamp.
[16:47] <Len-nb> Also the mic input will have 5v on it that your pre may be shorting.
[16:47] <Len-nb> This is to power the cheap computer mics
[16:48] <Len-nb> you line in is likely on the back. But it would be in your MB manual.
[16:48] <IntuitiveLeap> i didnt have any issues with distortion on front mic before
[16:48] <IntuitiveLeap> yea i have it connected line in now
[16:49] <IntuitiveLeap> problem is my plug is stereo and line in jack is mono
[16:49] <Len-nb> I am using a netbook and the audio in can be switched from mic to line.
[16:49] <IntuitiveLeap> ok i am connected to Line In now, and still show a full meter
[16:49] <IntuitiveLeap> preamp is no powered at all
[16:50] <Len-nb> that is not normal, normal would be a mono mic and stereo line.
[16:50] <Len-nb> does it make any difference unplugged?
[16:50] <IntuitiveLeap> im using the master out jacks from the preamp
[16:50] <IntuitiveLeap> they are stereo
[16:51] <Len-nb> Your line in should be stereo too
[16:51] <IntuitiveLeap> lets pretend it is :P
[16:51] <Len-nb> That is HDA standard as far as I know
[16:52] <Len-nb> But a stereo plug would still work.
[16:52] <IntuitiveLeap> at any rate, i am plugged into Line In
[16:52] <IntuitiveLeap> port shows Line In
[16:53] <IntuitiveLeap> volume is set to 'Base' and the meter is full, pre-amp is powered off
[16:55] <Len-nb> Does moving the level towards silence do anything?
[16:55] <IntuitiveLeap> nope
[16:56] <Len-nb> Does the mute button work?
[16:57] <IntuitiveLeap> it doesnt change the meter
[16:57] <SunStar> would changing to OSS have any effect you suppose Len-nb?
[16:58] <IntuitiveLeap> brb 1 minute, phone
[16:58] <Len-nb> I wouldn't want to go there :)
[16:58] <Len-nb> I am not sure what is being seen
[16:59] <Len-nb> muting the signal should not be card specific as I think that part is internal to pulse.
[17:00] <Len-nb> OSS is not easy to deal with in jack either, and we want to use jack at some point
[17:01] <IntuitiveLeap> im back
[17:02] <IntuitiveLeap> i unmuted the monitor of Line In on alsamixer and i have straight thru. i remuted it
[17:02] <IntuitiveLeap> so i do have sound
[17:02] <IntuitiveLeap> just not where i want it lol
[17:02] <Len-nb> I find it odd that the meter shows full.
[17:03] <IntuitiveLeap> yea, even when i power doen the external amp and unplug the line in jack on pc
[17:03] <SunStar> have we tried recording a sound check to rule out meter malfunction?
[17:04] <IntuitiveLeap> should i restart pulse u think?
[17:04] <Len-nb> You could try that, open audacity and record
[17:04] <Len-nb> pulseaudio -k
[17:04] <Len-nb> it won't hurt anything
[17:05] <IntuitiveLeap> -k restarts it?
[17:05] <Len-nb> kills it then it auto respawns
[17:12] <IntuitiveLeap> ok so, i restarted pulse, now i have meter at 0 lol
[17:12] <IntuitiveLeap> should i maybe restart alsa too?
[17:13] <Len-nb> does moving the level to full give at least something?
[17:13] <IntuitiveLeap> nada
[17:13] <IntuitiveLeap> i can see it moving in alsamixer though
[17:13] <IntuitiveLeap> the capture moves synchronous with pulse
[17:14] <Len-nb> Ya, HDA audio does.
[17:14] <IntuitiveLeap> as i adjust the pulse Line In, it also moves in alsa
[17:14] <IntuitiveLeap> but the meter still 0
[17:14] <IntuitiveLeap> which is weird cuz if i unmute the monitor of Line In on playback, i hear sound lol
[17:15] <Len-nb> tyr recording something
[17:15] <Len-nb> *try
[17:15] <Len-nb> Audacity is probably easiest
[17:16] <IntuitiveLeap> yea audacity records it no problem
[17:16] <Len-nb> Ok, so it looks like things work except for PA.
[17:17] <Len-nb> What use do you want to put this to?
[17:17] <IntuitiveLeap> yea the pulse meter must be torqued
[17:17] <IntuitiveLeap> well, i have all the standard audio apps with Studio
[17:17] <Len-nb> The PA meter may be looking at the wrong thing
[17:17] <IntuitiveLeap> i was thinking Ardour
[17:17] <Len-nb> Ok, next step is jack.
[17:18] <Len-nb> close audacity :)
[17:18] <IntuitiveLeap> basically i have a bunch of tracks on this mixer that i would like to mix and master, so ardor sounds about right, dont u think?
[17:18] <Len-nb> Can you DL through USB? or do you need to transfer as audio?
[17:18] <IntuitiveLeap> i have to trasnfer as audio sadly
[17:18] <Len-nb> Either is fine
[17:19] <IntuitiveLeap> i didnt buy the SCSI interface
[17:19] <Len-nb> audio just takes longer
[17:19] <Len-nb> qjackctl is the best way to start jack.
[17:19] <IntuitiveLeap> so ... jackctl?
[17:19] <IntuitiveLeap> yea what u said
[17:20] <IntuitiveLeap> do i still need pulse and alsmixer open?
[17:20] <Len-nb> I would leave alsamix open, but not pavucontrol
[17:21] <Len-nb> before you start jack make sure it is using the right device
[17:21] <IntuitiveLeap> it says (default)
[17:21] <Len-nb> There is a > beside that, click there
[17:22] <IntuitiveLeap> what is HDA ATI SB?
[17:22] <IntuitiveLeap> that the software sound card?
[17:23] <Len-nb> HDA should be the one you want, what others do you have?
[17:23] <IntuitiveLeap> i aslo see ALC888-VD
[17:23] <IntuitiveLeap> which is listed on my hardware specs
[17:23] <Len-nb>  you should be looking for hw:0 or hw:1
[17:24] <Len-nb> not hw:0:0 or 0,1
[17:24] <IntuitiveLeap> i have hw:0 hw:0,0 and hw:1
[17:24] <Len-nb> Generally those work best
[17:24] <IntuitiveLeap> hw:0 is the ATI SB
[17:24] <IntuitiveLeap> ill try that one
[17:24] <Len-nb> ok
[17:25] <IntuitiveLeap> that was on the interface tab, yes?
[17:25] <Len-nb> set sample rate to 48000.
[17:25] <Len-nb> yes
[17:25] <IntuitiveLeap> do i need to adjust input or output device?
[17:25] <Len-nb> interface sets both input and output
[17:25] <IntuitiveLeap> they say (default)
[17:25] <Len-nb> no just interface
[17:25] <IntuitiveLeap> ok
[17:26] <IntuitiveLeap> 48000 check
[17:26] <Len-nb> the input and output section is for those who have a separat inout and output
[17:26] <IntuitiveLeap> frames/period?
[17:26] <Len-nb> Probably the latency is fine for what you are doing
[17:27] <IntuitiveLeap> 42.7 msec
[17:27] <Len-nb> 1024 is fine
[17:27] <IntuitiveLeap> wont that be echoey if i try to actually play guitar through the pc?
[17:27] <Len-nb> Ya, you would go less for using the computer as an effects box but for recording that is fine.
[17:27] <IntuitiveLeap> what's a good latency for play thru?
[17:28] <Len-nb> Probably the lowset you will get is 128
[17:28] <IntuitiveLeap> how do i determine what is my lowest?
[17:29] <Len-nb> go lower till jack won't start :)
[17:29] <IntuitiveLeap> lol
[17:29] <Len-nb> 64 is really good
[17:29] <IntuitiveLeap> well, i had it starting at 32
[17:30] <IntuitiveLeap> before
[17:30] <IntuitiveLeap> ill try 64
[17:30] <Len-nb> good. you find that at 32 you get more xruns though, but that means at 64 things should be stable
[17:31] <Len-nb> I can get as low as 16, if I tweak well enough
[17:31] <IntuitiveLeap> says it started fine
[17:31] <IntuitiveLeap> check messages for xruns?
[17:32] <IntuitiveLeap> oh dear
[17:32] <IntuitiveLeap> lots of them lol
[17:32] <Len-nb> they will show in red
[17:32] <IntuitiveLeap> so i should hit stop and adjust things till i see 0 xruns?
[17:33] <Len-nb> Ya, there are some things you can do with the rest of the system to help too
[17:33] <Len-nb> My wireless gives xruns
[17:33] <IntuitiveLeap> prolly need to install a realtime kernel lol
[17:34] <IntuitiveLeap> this one is low latency, but i dont think 'realtime'.
[17:34] <Len-nb> if you are using studio you should already have lowlatency
[17:34] <holstein> you shouldnt need it.. realtime
[17:34] <IntuitiveLeap> ok
[17:34] <Len-nb> I can do very well with lowlatency
[17:35] <Len-nb> Like I said 16 frames while running guitarix. no xruns.
[17:35] <IntuitiveLeap> so ... i switch to 32 and no xruns
[17:35] <Len-nb> old P4 computer
[17:35] <Len-nb> good
[17:35] <IntuitiveLeap> 16, no xruns
[17:36] <borodino> hello
[17:36] <Len-nb> if you look in your connections window you should see all your inputs and outputs
[17:36] <Len-nb> hello
[17:36] <borodino> i need some help
[17:36] <Len-nb> borodino, please explain, we can try
[17:36] <IntuitiveLeap> hiya boro
[17:36] <borodino> haha
[17:36] <borodino> thanks
[17:37] <borodino> i am trying to use Tor
[17:37] <borodino> for firefox
[17:37] <IntuitiveLeap> im in your boat boro. too noobish to live
[17:37] <Len-nb> IntuitiveLeap, you should see 2 ins and 6 or 8 outs
[17:37] <borodino> my problem is
[17:38] <borodino> i need to configure the proxy
[17:38] <borodino> i am using this as a guide
[17:38] <borodino> http://www.ubuntugeek.com/how-to-configure-ubuntu-desktop-to-use-your-proxy-server.html
[17:38] <borodino> problem is...
[17:38] <holstein> !tor
[17:38] <Len-nb> What is Tor? So I have at least some idea where this is going :)
[17:38] <holstein> borodino: i would go to #ubuntu or #xubuntu ...since that is not ubuntustudio specific
[17:40] <IntuitiveLeap> which are the ins?
[17:41] <Unit193> You can also pretty much do http_proxy="http://bleh:8888" firefox   and it'll work.
[17:41] <Len-nb> Capture
[17:42] <Len-nb> system->capture
[17:42] <IntuitiveLeap> i only see 'readable clients' and 'writeable clients'
[17:42] <Len-nb> Readable, click on system
[17:42] <Len-nb> it should expand
[17:42] <IntuitiveLeap> oh ok, i see now
[17:42] <Len-nb> Start meterbridge
[17:43] <IntuitiveLeap> shows capture 1 and 2 going to PA jack source (front left and front right)
[17:43] <Len-nb> It should show up in Writable
[17:43] <IntuitiveLeap> meterbridge?
[17:43] <Len-nb> Yes
[17:43] <IntuitiveLeap> that an app?
[17:43] <Len-nb> yes
[17:44] <Len-nb> It will give you two analog looking meters
[17:44] <IntuitiveLeap> ok got it
[17:45] <Len-nb> click on capture 1 and then chanel 1 on the meter in connections
[17:45] <Len-nb> connect button on the bottom should ungrey
[17:46] <Len-nb> hitting that should pop a line across
[17:46] <Len-nb> you can do channel 2 as well
[17:46] <IntuitiveLeap> system (capture_1) -> bridge-17445 (meter_1)     that sound right?
[17:47] <Len-nb> yes
[17:47] <IntuitiveLeap> ok done that
[17:47] <IntuitiveLeap> for both captures
[17:47] <Len-nb> The idea is that the meters should show your audio in
[17:47] <IntuitiveLeap> they do!
[17:47] <IntuitiveLeap> yayy
[17:47] <Len-nb> play something back on the zomm
[17:47] <Len-nb> good
[17:48] <Len-nb> I would disconnect the 4 or more pulse lines :)
[17:48] <IntuitiveLeap> disconnect everything pulse?
[17:48] <Len-nb> If you are not going to be using pulse I would disable it.
[17:49] <Len-nb> yes everything pulse
[17:49] <IntuitiveLeap> oh wow i have like 20 pulse connections
[17:49] <Len-nb> For what you are doing you don't need it
[17:49] <Len-nb> That is fixed in 13.04 when we get it out
[17:50] <IntuitiveLeap> this will disable sound from things like youtube etc?
[17:50] <Len-nb> pulse now defaults to stereo
[17:50] <Len-nb> Ya as long as jack is running, but as soon as jack stops pulse will send youtube direct to the device.
[17:50] <IntuitiveLeap> ok
[17:51] <IntuitiveLeap> now i have only 2 connections, the bridge to the sys
[17:51] <Len-nb> You probably don't need to listen to utube while recording though
[17:51] <IntuitiveLeap> lol nope, just a point of interest
[17:52] <IntuitiveLeap> sometimes i jam along with youtube stuff, so one day ...
[17:52] <Len-nb> Ok, you are all set to use ardour now.
[17:52] <IntuitiveLeap> ardor should auto connect to jack?
[17:53] <Len-nb> Ardour has it's own stuff for connecting to jack
[17:53] <Len-nb> you don't need the meter bridge either as ardour has it's own metering as well
[17:54] <IntuitiveLeap> so all i use the qtjackctl connections for is to disable the pulse stuff?
[17:54] <IntuitiveLeap> guessing i wont need the bridge except for testing new connections
[17:54] <Len-nb> could be. Though you can use it for connecting ardour stuff if you want
[17:55] <Len-nb> it is possible to set PA to not connect by default... I would have to look though as I don't remember exactly how I did it :)
[17:55] <IntuitiveLeap> to not connect in jack u mean?
[17:55] <Len-nb> Ya.
[17:56] <IntuitiveLeap> yea they dont play well together it seems
[17:56] <Len-nb> It will make the jack ports but not connect
[17:56] <Len-nb> The pa-jack bridging is improving... but it has a bit to go yet
[17:56] <IntuitiveLeap> maybe when i am doing this in the future i should just disable PA before i light up jack?
[17:57] <Len-nb> If you wish to do so The best way is to disable respawning
[17:57] <IntuitiveLeap> killall -9, right
[17:57] <Len-nb> That way you can use pulseaudio -k to stop it
[17:57] <IntuitiveLeap> ?
[17:57] <IntuitiveLeap> oh u mean something else
[17:58] <Len-nb> if you killal -9 that would work but it will just restart.
[17:58] <IntuitiveLeap> nasty! lol
[17:58] <Len-nb> The config file has a respawn yes or true or something
[17:59] <IntuitiveLeap> i guess there is a manpage or something that shows how to disable respawning of a specific app
[17:59] <Len-nb> that needs to be set off. Then the pulse mixer will restart pulse when opened
[18:00] <Len-nb> /etc/pulse/client.conf is the file. You need root access to edit
[18:00] <IntuitiveLeap> is there not a decent front end for alsamixer that could be used instead of PA?
[18:01] <Len-nb> qasmixer is nice
[18:01] <IntuitiveLeap> will Ubuntu Studio still function without PA?
[18:01] <Len-nb> I happen to have an app specific to my sound card
[18:01] <Len-nb> Yes, but the desktop sound will not work easy
[18:02] <IntuitiveLeap> for the regular things, like watching a youtube or listening to netradio, w/e
[18:02] <Len-nb> firefox, etc. expect pulse
[18:02] <IntuitiveLeap> ok
[18:02] <IntuitiveLeap> so prolly best to keep pulse and figure out a simple way to make it turn on and off and stay that way
[18:02] <IntuitiveLeap> :)
[18:03] <Len-nb> edit the file  /etc/pulse/client.conf look for autospawn
[18:03] <IntuitiveLeap> you're a great tech assistant for this btw. i was getting near to blowing up my pc lol
[18:04] <Len-nb> remove the ; at the front of that line and change the yes to no
[18:04] <Len-nb> it is hard to know what the other person sees at there end :)
[18:05] <Len-nb> Before anything you do in this file will have effect you may have to logout/in, but pulseaudio -k may work as well
[18:06] <IntuitiveLeap> cool thank you, gonna try that now
[18:10] <IntuitiveLeap> what does the ';' in the pulse config file do? is it a commented out line?
[18:10] <IntuitiveLeap> oh nevermind i see it is lol
[18:14] <Len-nb> ya
[18:14] <Len-nb> in unix ; and # are the comment characters
[18:15] <IntuitiveLeap> just been always used to seeing just # for commenting
[18:15] <IntuitiveLeap> every day, something slightly new :P
[18:16] <Len-nb> So pulseaudio -k to kill probably pactl stat will restart it
[18:16] <Len-nb> or just open pavucontrol
[18:17] <Len-nb> Anything that uses dbus to talk to pulse
[18:18] <IntuitiveLeap> do u find patchage helpful?
[18:19] <Len-nb> It can be it is sort of a nicer layout than the qjackctl connect screen
[18:20] <Len-nb> It also allows setting latency on the fly
[18:20] <IntuitiveLeap> but is showing the same information, right? they are interchangeable, aside from the layout?
[18:20] <Len-nb> I have had it crash on me though
[18:20] <Len-nb> Ya same info, it is not needed
[18:20] <Len-nb> just a personal choice
[18:21] <IntuitiveLeap> understood
[18:22] <Len-nb> 44.1k and 48k... just so you know. Lots of people recommend 44.1k, but your sound card will work best with 48k.
[18:22] <IntuitiveLeap> 44.1 would give you more leeway on the xruns wouldn't it?
[18:23] <Len-nb> 48k it the HDA standard, it will work ok but 48k will sound better
[18:23] <Len-nb> the difference in xruns is not going to be noticable
[18:24] <Len-nb> The HDA bus is 48k anyway.
[18:25] <Len-nb> goin higher than 48K will get you nothing, unless you are doing live sound where it can get lower latency... not better quality
[18:28] <Len-nb> feel free to try both. You will probably not hear any difference :)
[18:28] <IntuitiveLeap> do you use patchbay in qtjackctl?
[18:28] <Len-nb> ya
[18:29] <Len-nb> It is already open so why not?
[18:29] <IntuitiveLeap> is it like saved profiles for the connections?
[18:29] <Len-nb> Yes,
[18:29] <Len-nb> it uses jack session
[18:30] <Len-nb> It is good for systems using odd outputs and inputs by default.
[18:31] <Len-nb> most apps expect 1 and 2 to be left and right. My spdif preamp ends up as 9 and 10
[18:31] <IntuitiveLeap> might be good too if you are moving your sound hardware (guitar , preamp etc) to someone elses house to hook up.
[18:31] <Len-nb> yes
[18:31] <Len-nb> or if you use guitarix or rackarak for on stage
[18:33] <Len-nb> Or any live use... I only pointed out guitar use because I know you do that at least. but for softsynths too
[18:33] <Len-nb> You can save more than one profile of course
[18:34] <Len-nb> Ardour will be your next thing... I'm not going to try and help there. I don't have it on this machine.
[18:35] <Len-nb> there is a good tutorial on the ardour site though
[18:36] <IntuitiveLeap> i have been messing with it (using the manual at the ardor site) i feel much more confident about it than i did all this PA / jack mess
[18:37] <Len-nb> great!
[18:38] <Len-nb> If you have done tracking before it is easy enough.
[18:40] <IntuitiveLeap> yea, it not so different from using the hardware mixer i have.
[18:40] <IntuitiveLeap> has a lot more capabilities though
[18:41] <IntuitiveLeap> my mixer is ... 2nd generation Zoom lol
[18:41] <Len-nb> The hardest part might be lining the tracks up once they are transferred
[18:41] <IntuitiveLeap> its an MRS-1044 if that helps
[18:41] <Len-nb> You will have to do that by ear probably
[18:41] <Len-nb> I don't know the zoom models at all.
[18:41] <IntuitiveLeap> about 10 years old now i guess
[18:42] <IntuitiveLeap> but it has an awesome pre amp ability
[18:42] <Len-nb> Just about any preamp is way beyond what comes with a computer
[18:42] <IntuitiveLeap> makes my guitar actually sound 'good' lol
[18:43] <Len-nb> The average computer mic per is made for skype
[18:43] <IntuitiveLeap> i have another hardware question
[18:43] <Len-nb> k
[18:43] <IntuitiveLeap> the zoom unit has s/pdif optical out
[18:43] <Len-nb> OK
[18:43] <IntuitiveLeap> and my PC has a coax s/pdif jack
[18:44] <IntuitiveLeap> which i dont even know if it is in or out lol
[18:44] <IntuitiveLeap> how can i verify this?
[18:44] <Len-nb> I have the oposite problem.
[18:44] <Len-nb> The HDA standard has a spdif out
[18:44] <IntuitiveLeap> can i use alsamixer to verify if the pc's jack is inbound or outbound (or both)?
[18:44] <Len-nb> spdif in is not common
[18:45] <Len-nb> Can't be both
[18:45] <Len-nb> If you don't have two, it will be out.
[18:45] <IntuitiveLeap> meh
[18:45] <IntuitiveLeap> so i will need a new sound card if i want to use the digital connection on my mixer, huh
[18:45] <Len-nb> Yes
[18:46] <IntuitiveLeap> is there such a thing as an external sound card that would go thru USB or something?
[18:46] <Len-nb> Yes lots of them.
[18:46] <IntuitiveLeap> ok cool
[18:46] <IntuitiveLeap> my boat isnt sunk
[18:46] <Len-nb> How much do you wish to spend...
[18:47] <IntuitiveLeap> lol isnt that always the ?
[18:47] <Len-nb> they go from les than $20 to $1k or more
[18:47] <IntuitiveLeap> is USB a good type of connection to consider?
[18:47] <Len-nb> There is great 8i/o unit for about $500.
[18:48] <Len-nb> there is a nice one for $100 or so with 2 i/o
[18:48] <IntuitiveLeap> so that would be ... stereo duplex?
[18:48] <Len-nb> USB is a bit tricky to set up
[18:48] <Len-nb> Yes
[18:49] <IntuitiveLeap> what type of connection would be better than USB for a common desktop pc?
[18:49] <Len-nb> For USB Audio IF you need to find a USB port that is not used for anything else and has a no other IRQs it is sharing with.
[18:49] <IntuitiveLeap> through the router on ethernet?
[18:50] <Len-nb> ether net audio interfaces are pricey
[18:51] <Len-nb> And there are no linux drivers for them at this time.
[18:51] <IntuitiveLeap> so, best option is really an internal sound card u think?
[18:51] <Len-nb> the ice1712 devices for pci are very good. (what I use by the way)
[18:52] <Len-nb> And the PCIe devices are starting to show up now. I don't know what the state of linux compatibility is
[18:53] <Len-nb> Fire wire devices are good, just be sure to get a FW interface that works well with Linux. holstein uses a FW IF and is happy with it.
[18:55] <Len-nb> When I say FW IF, I mean the FW adaptor it self
[18:55] <Len-nb> , not the firewire sound box.
[18:55] <IntuitiveLeap> i dont have firewire on this pc
[18:56] <IntuitiveLeap> had it on my last pc and i dont think i ever jacked into it even once lol
[18:56] <Len-nb> Personally, I take my computer to the music store and try out different things
[18:56] <IntuitiveLeap> mines a desktop, so prolly not gonna happen
[18:56] <Len-nb> mine is disabled too
[18:57] <Len-nb> Some places have rentals
[18:57] <IntuitiveLeap> it was funny, me getting this pc
[18:57] <Len-nb> There are PCI(e) FW cards
[18:58] <Len-nb> The ALSA sound card matrix is a good place to start
[18:58] <IntuitiveLeap> i had bought a nice new PC about 2 years ago, which basically never worked at all. it crashed at the drop of a hat and the service dept had no clue why
[18:58] <IntuitiveLeap> so they set me up with a different new one
[18:58] <IntuitiveLeap> and i immediately slapped linux on it
[18:59] <IntuitiveLeap> it was made for windows originally of course
[18:59] <Len-nb> Win is the os it comes with that is just so it has something on it, I throw it out as soon as I get home too.
[18:59] <IntuitiveLeap> so i sometimes run into some weird hardware issues, like this pulseaudio thing
[19:00] <Len-nb> At least it plays back ok
[19:00] <IntuitiveLeap> oh we have it working well now
[19:00] <Len-nb> And, the alsa part works
[19:00] <IntuitiveLeap> just without PA
[19:00] <IntuitiveLeap> im not very linux savvy as of yet
[19:00] <IntuitiveLeap> lol
[19:00] <Len-nb> it sounds to me the pa output part works. That is the more important part
[19:00] <IntuitiveLeap> i tried archlinux
[19:01] <Len-nb> Ubuntu is easy.
[19:01] <IntuitiveLeap> so i got a little experience on terminals using that os
[19:01] <Len-nb> I used to use Slackware
[19:01] <IntuitiveLeap> i actually rlly like arch, its just a bit beyond my skill lvl for audio set up etc
[19:01] <Len-nb> I started back before Slackware 1.0 in the mid 90s
[19:02] <IntuitiveLeap> actually i rlly like this studo ubuntu also
[19:02] <Len-nb> Terminal mode was standard.
[19:02] <IntuitiveLeap> i took a computer class in grade 9 way back when
[19:03] <IntuitiveLeap> with punch card data entry
[19:03] <IntuitiveLeap> so :P
[19:03] <IntuitiveLeap> but then i never took another one
[19:03] <IntuitiveLeap> so :p @ me
[19:03] <Len-nb> I learned on paper tape in the 70s on a pdp8
[19:04] <IntuitiveLeap> realistically i have only been using linux for about a year and a half
[19:04] <IntuitiveLeap> i just got fed up with paying for virus scan software and being bombarded with advertising
[19:04] <IntuitiveLeap> and now i get to learn some terminal, aint it great!
[19:05] <Len-nb> There are some blind people who do recording on linux all terminal
[19:05] <Len-nb> they use nama as a daw
[19:07] <IntuitiveLeap> nama?
[19:11] <Len-nb> http://juliencoder.de/nama/music.html check out some of these
[19:11] <Len-nb> home page: http://freeshell.de/~bolangi/cgi1/nama.cgi/00home.html
[19:11] <IntuitiveLeap> North American Mycological Association, a learned society devoted to mushrooms and other fungi
[19:16] <IntuitiveLeap> wow, that is a gory interface
[19:16] <Len-nb> Anyway, nice chatting, however I should get some things done around here.
[19:16] <Len-nb> think about if you are blind
[19:16] <IntuitiveLeap> copy that, thanks again for your help
[19:16] <Len-nb> np
[19:16] <IntuitiveLeap> i guess they can use terminal with braile
[19:16] <IntuitiveLeap> and never have to look at it lol
[23:34] <airlynx> I have a question about recordmydesktop packaged in Ubuntu Studio 13.04, should I ask the question here or in #ubuntu+1?
[23:38] <airlynx> I'm going to ask anyways cause I've had the same problem with 12.04 and 12.10, I can never get recordmydesktop to work with JACK (exits with status 2816, improper window specification) but I noticed today that the settings window mentions that it must be compiled with Jack support, so I was just wondering if it was or not (is it worth my time to compile it myself?)
[23:40] <zequence> airlynx: Interesting. I don't think anyone has been testing it, so if there's a problem with the jack support but that could be worked out with repackaging, that is something we should look at
[23:41] <zequence> airlynx: If you are able to solve it by rebuilding, please let me know
[23:41] <airlynx> zequence: there is a bug filed on recordmydesktop about my exact issue, but zero response to the bg
[23:41] <airlynx> *bug
[23:42] <ubuntu-studio> anybody know anything about the ardour 3 release date?
[23:42] <zequence> airlynx: I guess this one bug #621188
[23:43] <zequence> ubuntu-studio: It's released now, but 13.04 is so late in development, that it won't be included
[23:44] <zequence> It was released about a week ago, or so
[23:44] <ubuntu-studio> i guess I can download the source a take a stab at it.Thanks!
[23:45] <airlynx> zequence: that's the same bug, but I had a different bug report, hadn't been marked duplicate yet, but yes.  https://bugs.launchpad.net/gtk-recordmydesktop/+bug/1037402
[23:46] <zequence> airlynx: Thanks. I'll have a look at this tomorrow.
[23:46] <airlynx> zequence: I'd appreciate it, I'll try to recompile recordmydesktop, but my experience with compiling is limited at best
[23:58] <airlynx> zequence: while reading the bug report I noticed that autostatic published a patched version of recordmydesktop on his ppa, however it doesn't support raring