=== `Fibz is now known as j4jackj
[01:02] <dustyh> so I am new to ubuntu and looking for some help, am I in the right place?
[01:09] <dusty_> I am have a heck of a time getting jackd to work correctly
[01:19] <dusty_> ?
[01:35] <dusty_> i installed a few updates and restarted the computer and still no luck with jackd working
[02:01] <dusty_> anybody able to help me setup an input device?
[02:02] <p5gcmx> ASSIS
[02:02] <p5gcmx> AS
[02:02] <p5gcmx> S
[02:02] <p5gcmx> S
[02:02] <p5gcmx> S
[02:02] <p5gcmx> S
[02:02] <p5gcmx> S
[02:02] <p5gcmx> S
[02:03] <`Fibz> my knowledge is limited to turning up the volume and boost for input devices in alsa and configuring inputs/outputs with qjackctl
[02:03] <p5gcmx> S
[02:03] <p5gcmx> S
[02:04] <holstein> dusty_: just ask
[02:05] <holstein> !proaudio > dusty_
[02:05] <ubottu> dusty_, please see my private message
[02:05] <`Fibz> the volume control is under Launcher Menu -> Media Playpack -> pule audio volume control. jack control is under Launcher menu -> audio production -> qjackctl
[02:05] <holstein> dusty_: i suggest trying with the internal audio device.. something that is well supported in linux, that works well
[02:05] <holstein> dusty_: use only it.. unplug any other USB or firewire audio devices
[02:05] <dusty_> i have no idea what to ask, it just does not work. I am sorry i try to start a session and it says
[02:06] <holstein> dusty_: no need to troubleshoot a new, potentially unsupported device *and* jack at the same time
[02:06] <dusty_> Cannot connect to server socket err = No such file or directory
[02:06] <holstein> dusty_: sure
[02:07] <holstein> dusty_: so, make sure you have no other audio devices plugged in
[02:07] <dusty_> the card works fine with pulse(output) I can not however get the input to register at all
[02:07] <`Fibz> in alsamixed is the inputs turned up?
[02:07] <dusty_> no just the onboard is all it is, mic in(front and rear) along with a line in
[02:07] <dusty_> yes they are all up to or past 100
[02:07] <`Fibz> if i remember the inputs are at 0% by default
[02:07] <`Fibz> k
[02:07] <holstein> dusty_: use *only* the internal audio device for this test, and make sure you have it selected.. its easy to use the dropdown menu in the qjackctl to try many of the outputs
[02:08] <holstein> dusty_: then, you can try "gksudo qjackctl" to troubleshoot permissions
[02:08] <holstein> dusty_: if jack starts as root, and not your normal user, you know its permissions related
[02:08] <holstein> dusty_: if its not working as root, then you have the configuration incorrect
[02:09] <dusty_> if i go through adour it seems to come on and work, but I can not get the input to work
[02:09] <holstein> dusty_: that can be the issue right there
[02:09] <dusty_> ?
[02:09] <holstein> dusty_: you start jack *before* opening ardour or anything else
[02:10] <holstein> dusty_: if you open ardour, it tries to start jack,t hen, you close ardour, and jack can be left running in the background and not work anymore
[02:10] <holstein> dusty_: i would use..
[02:10] <holstein> !proaudio
[02:10] <dusty_> well thats just it i tryed MANY times before anything else and when I click start every time I get that error so I try just going to adour and it worked
[02:10] <dusty_> proaudio?
[02:10] <holstein> after restarting, if you are unsure about how to check for JACK running
[02:10] <holstein> dusty_: the link  i linked you in PM from the bot
[02:11] <holstein> dusty_: there is no need to start ardour til you get jack running
[02:11] <holstein> dusty_: does jack start as root using "gksudo qjackctl" ?
[02:13] <dusty_> yes it does
[02:16] <holstein> dusty_: ok.. so, its permissions related with your user
[02:17] <holstein> dusty_: *or*, you are having issues with it running in the background
[02:17] <holstein> dusty_: you could be starting it, and not understanding that it needs to be stopped, or how to stop it, or that it has been started, and is still running
[02:17] <holstein> dusty_: i would try making sure your user is in the audio group, then, try and follow the wiki page i gave you for troubleshooting
[02:18] <dusty_> i think it is still running right now because i am now getting an error, d-bus: setparametervalue
[02:18] <dusty_> i am on that page now and going through the steps
[02:19] <dusty_> can someone please explain to me how to make sure that it is closed? is there a -kill command or something i can run?
[02:21] <holstein> dusty_: there are many kill commands
[02:21] <holstein> dusty_: theres "sudo killall jack".. theres "ps aux | grep jack" and look and kill the PID
[02:21] <holstein> dusty_: you can just reboot and *dont* start it
[02:22] <holstein> start it only with qjackctl after checking to see that your user is in the audio group
[02:22] <holstein> dusty_: did you check to see if you user is in the audio group?
[02:22] <dusty_> no im searching right now how to do it
[02:22] <holstein> sudo adduser "you" audio
[02:23] <holstein> replacing "you" with your username, without the quotation marks
[02:23] <holstein> it wont hurt anything to run that command and check
[02:23] <dusty_> it says im already a user of the group
[02:24] <holstein> dusty_: ok... if i were you, on your current level, i would reboot, and make sure you reference the link i gave, and start jack with qjackctl
[02:25] <holstein> dusty_: dont open *any* audio apps for any reason til jack is running
[02:25] <dusty_> will do thank you for the help
[02:25] <holstein> dusty_: try as normal user.. if that fails.. try as root.. gksudo qjackctl
[11:13] <Terrance1arrior> let pus put control and z next to each other on the key and let us assign those keys 'EXIT'.
=== Terrance1arrior is now known as TerranceWarrior
[14:03] <holstein> TerranceWarrior: im not sure what you said before, if that was a support question or a design request.. please rephrase.. thanks
[21:15] <p9> ok
=== ubuntu-studio is now known as len-1404