[04:30] <coelebs> is line out/headphone jack switching hard wired or can i have monitoring output on jack?
[04:34] <coelebs> i'd like to monitor input for sooperlooper at my headphones while it plays on speakers
[04:35] <coelebs> it would be easier to buy a splitter cable or usb audio interface but dx it's sunday and i'd need to order them online
[04:43] <OvenWerks> take a look at alsamixer
[04:43] <OvenWerks> I think they are labeled
[04:44] <OvenWerks> On my netbook (HDA audio) there was a master level, line out level and headphone level and they could all be up at the same time.
[04:55] <coelebs> thx
[04:55] <coelebs> that at least got signal splitted
[04:56] <OvenWerks> no problem
[04:57] <coelebs> i cannot find separate outs on jackctl but i guess i need to get myself some audio interface/sound card anyway
[04:58] <OvenWerks> That may be true. What does aplay -l say?
[04:59] <OvenWerks> you may be able to use zita-j2a to get the other outputs.
[04:59] <OvenWerks> It depends on how your audio interface is wired.
[05:00]  * OvenWerks has his internal audio interface turned off in bios...
[05:04] <coelebs> http://pastebin.com/PGhtSSBF
[05:06] <OvenWerks> It looks like you could have a second stereo out anyway.
[05:08] <OvenWerks> It looks like you are using hw:0.0 now and maybe zita-j2a -d hw:0.2
[05:08] <OvenWerks> would get some more. I don't know that would be your HP or some other output though
[05:10] <OvenWerks> alsamixer may see them all as one card. As I said I don't play with internal audio stuff much.
[05:10] <coelebs> it says invalid value for a card, where can i find the identifier?
[05:11] <coelebs> an't open ALSA playback device 'hw:0.2'.
[05:11] <OvenWerks> when you go to qjackctl setup...
[05:11] <coelebs> can't*
[05:11] <OvenWerks> there is a small > next to the box by Interface
[05:12] <OvenWerks> it should give you a list.
[05:12] <coelebs> ach so
[05:12] <coelebs> hw:Intel:0.2
[05:13] <OvenWerks> Try that then
[05:14] <coelebs> still says can't open but identifier is right
[05:15] <OvenWerks> Which output is jack using?
[05:15] <OvenWerks> Or I guess I should ask if jack is running
[05:15] <coelebs> hw:Intel
[05:15] <coelebs> yes it is
[05:15] <OvenWerks> OK. Not sure then.
[05:16] <coelebs> i'll tinker with these settings
[05:16] <OvenWerks> I don't have one that complex to play with.
[05:16] <coelebs> maybe i'll bruteforce my way there
[05:17] <OvenWerks> You can try setting input and output separately in jack and then you can switch the outputs around
[05:17] <OvenWerks> zita-j2a -h gives other options too
[05:18] <OvenWerks> I am assuming you would be using 48k for example.
[05:18] <OvenWerks> if you have jack set to 44.1k zita-j2a may not be able to set the same device to 48000
[05:20] <coelebs> at first i used to hate jack but i'm getting to like it
[05:21] <OvenWerks> I run it all the time. On this machine it starts with the session and pulse always goes through jack.
[05:22] <OvenWerks> By The way, 48k is the design speed for the internal audio. Most audio interfaces sound best at that speed.
[05:28] <coelebs> ok i think i got 44.1k
[05:29] <OvenWerks> they will probably both have to be the same
[07:06] <scvxx_> nice new look..
[07:19] <ElphXR> hi
[07:20] <ElphXR> question-  I'm using 14.04 ubuntu studio..  and trying to load xsynth-dssi with jack-dssi-host  .. I get an error .  failed to load plugin library.
[07:21] <ElphXR> does this work on ubuntustudio 14.04 ?    wondering how to troublshoot.
[07:27] <ElphXR> nevermind.  env not set for DSSI_PATH