[03:14] <TresEquis_> I've somehow lost my jackd sound in US oneirc
[03:15] <TresEquis_> I was happily recording last weekend, but no joy tonight
[03:15] <TresEquis_> pulse can play to / record from the mixer, but not jack
[03:16] <TresEquis_> I'd love to kill off pulse, but it appears to be revenant
[03:18] <TresEquis_> any theories on what I can poke?  The only recent install which looks at all relevant is usbmuxd
[03:23] <TresEquis_> and that looks completely unrelated
[03:41] <holstein> TresEquis_: cool... try gksudo qjackctl
[03:41] <holstein> hit start... report error messages
[03:43] <TresEquis_> no error messages either on terminal or the qjackctl Messages window
[03:43] <holstein> TresEquis_: then, its likely running, and you just need to route things to where ever you want,and go for it :)
[03:44] <holstein> TresEquis_: you mean, no errors messages as root?
[03:44] <holstein> try starting it as normal user and see
[03:44] <TresEquis_> right, sames as my normal qjackctl
[03:44] <holstein> TresEquis_: it'll just run...
[03:47] <TresEquis_> how should the connection graph look?  Currently, system:capture{1,2} are wired up to PA Jack Source front:{left,right}
[03:48] <TresEquis_> and likewise, PA Jack Sink (7 ports?) are wired to system playback:*
[03:48] <holstein> TresEquis_: depends
[03:48] <holstein> if you want to record some pulse source, thats how it could look
[03:49] <TresEquis_> I'd really rather ignore pulse altogether
[03:49] <holstein> or if you want to route your capture to something via pulse, which i wouldnt think you would want to do
[03:49] <holstein> TresEquis_: then, un-hook pulse
[03:51] <TresEquis_> OK
[03:51] <holstein> TresEquis_: its challening to get started using JACK... or can be
[03:51] <holstein> check out #opensourcemusicians if you like
[03:51] <TresEquis_> now when I start Hydrogen, for instance, it has outputs routed to system:playback*
[03:51] <holstein> TresEquis_: sure
[03:52] <TresEquis_> but no sound goes to the card
[03:52] <holstein> thats default so you can hear it
[03:52] <holstein> TresEquis_: try the other outputs
[03:52] <holstein> make sure the card is up, on, plugged in or whatever
[03:52] <holstein> if you have more than one out, try the other outputs
[03:52] <holstein> open a terminal, and check in alsamixer
[03:52] <TresEquis_> its there -- I can tap the mic and hear output on the monitors
[03:53] <holstein> TresEquis_: cool
[03:53] <holstein> so, just H2 isnt working then?
[03:53] <holstein> i would step back or forward a version
[03:53] <holstein> i remember having a buggy version of H2 in 9.10
[03:55] <TresEquis_> is there a simple jack client tone generator I can test with?
[03:56] <TresEquis_> I only know Ardour and Hydrogen at all well
[03:57] <holstein> TresEquis_: i use zynaddsubfx
[03:57] <holstein> or anything really
[03:57] <holstein> audacious has JACK output
[04:02] <TresEquis_> zsynaddsubfx appears to be OSS only
[04:03] <holstein> TresEquis_: ?
[04:03] <holstein> TresEquis_: try audacious
[04:03] <holstein> TresEquis_: just try things til you find something you can use
[04:03] <holstein> there are configurations in H2
[04:04] <holstein> if its set to use pulse or alsa, it wont use JACK of course
[04:04] <holstein> JACK needs to be running as normal user, then you start zynaddsubfx
[04:04] <holstein> you should see zyn in the audio tab, and in the MIDI tab
[04:06] <TresEquis_> audacious is happily playing to JACKD, but no sound
[04:06] <holstein> TresEquis_: cool
[04:06] <holstein> im about 99% sure its a routing issue
[04:07] <holstein> TresEquis_: double *double* check that its routed properly
[04:07] <TresEquis_> I'm using hw:1 (my USB mixer) for both input and output in jackd
[04:07] <holstein> TresEquis_: are you?
[04:07] <holstein> try with teh internal card
[04:07] <holstein> the*
[04:09] <TresEquis_> that works (plugging headphones into front jack)
[04:10] <holstein> TresEquis_: cool.. thats how it'll work when you have the USB device configured properly
[04:10] <holstein> i suggest just using the internal card for a bit
[04:10] <TresEquis_> the USB device was working last week
[04:10] <holstein> TresEquis_: cool
[04:10] <TresEquis_> internal card isn't capable of what I want
[04:10] <holstein> TresEquis_: im sure you'll aquire the skill to get it working again
[04:11] <holstein> TresEquis_: then, you'll need to troubleshoot the connection in JACK
[04:11] <holstein> TresEquis_: there are 2 different dropdown arrows near "device" in jack
[04:11] <holstein> try looking there for the USB device
[04:12] <TresEquis_> that is where I picked hw:1 before -- it still shows there
[04:12] <holstein> TresEquis_: OK
[04:12] <holstein> then, it *should* be working
[04:12] <holstein> JACK is working
[04:12] <holstein> if you upgraded, or changed kernels or alsa versions, that could cause breakage
[04:13] <holstein> im sure its just something fiddly though
[04:13] <TresEquis_> no new packages since last weekend except openssl
[04:13] <holstein> TresEquis_: OK
[04:14] <holstein> then its just a configuration issue
[04:14] <TresEquis_> and I'm pretty sure *that* isn't the culprit
[04:14] <holstein> TresEquis_: OK
[04:14] <holstein> the only thing it can be is the configuration of that device with JACK
[04:14] <holstein> JACK is working
[04:14] <holstein> the apps are working
[04:14] <holstein> JACK doesnt work with that bunk config to that USB device
[04:17] <TresEquis_> one oddity is that I'm seeing 8 system:playback ports, but the device only does stereo
[04:17] <holstein> TresEquis_: right.. you are *not* choosing that USB device
[04:17] <holstein> its mis-configured
[04:18] <TresEquis_> ok
[04:18] <TresEquis_> I'l try powering it down and back on again
[04:19] <holstein> TresEquis_: sure.. try something
[04:19] <holstein> JACK is working though
[04:23] <TresEquis_> qjackctl seems to be leaving jackdbus processes running, and needing kill -9
[04:25] <TresEquis_> hmm, trying to run jackd from the command line:
[04:25] <TresEquis_> $ cat .jackdrc
[04:25] <TresEquis_> /usr/bin/jackd -dalsa -r44100 -p64 -n2 -D -Chw:1 -Phw:1 -i2 -o2
[04:26] <TresEquis_> $ . .jackdrc
[04:26] <TresEquis_> ...
[04:26] <TresEquis_> control device hw:1
[04:26] <TresEquis_> the playback device "hw:1" is already in use. Please stop the application using it and run JACK again
[04:26] <TresEquis_> Cannot initialize driver
[04:26] <TresEquis_> and now pulseaudio is running again
[04:26] <holstein> TresEquis_: not sure man
[04:26] <holstein> you *know* JACK works though
[04:26] <TresEquis_> not against hw:1
[04:27] <holstein> TresEquis_: those can change
[04:27] <holstein> i would reboot with the USB unplugged
[04:27] <holstein> or, disable the internal in the bios
[04:28] <TresEquis_> OK, I just tried disabling both cards in the PA volume control
[04:28] <TresEquis_> and restarting jackd from the command line
[04:28] <TresEquis_> that works (at least, it doesn't bomb out
[04:29] <TresEquis_> yep, I'm hearing sound in the tape-to-headphone channel of the mixer
[04:29] <holstein> you mean, have conflicts with servers already running?
[04:30] <TresEquis_> when I try to start jackd (no pulseaudio or jackd already running), pulseaudio starts up and grabs the port
[04:30] <TresEquis_> unless I disable it from using the USB device at all
[04:30] <holstein> TresEquis_: sure
[04:30] <holstein> that sounds about right
[04:30] <TresEquis_> I knew I hated pulseaudio
[04:30] <holstein> TresEquis_: yeah?
[04:30] <holstein> i mean... you dont have to like it
[04:30] <holstein> but its doing what its supposed to
[04:31] <TresEquis_> No, it is stepping on jackd
[04:31] <holstein> i regularly use alsa-only and pulse systmes
[04:31] <holstein> i have issues with both
[04:31] <holstein> TresEquis_: sure
[04:31] <TresEquis_> *I* didn
[04:31] <holstein> its supposed to
[04:31] <holstein> its a server
[04:31] <TresEquis_> t ask it to run
[04:31] <holstein> its already running
[04:31] <TresEquis_> no, I killed it
[04:31] <holstein> TresEquis_: you can strip it out though
[04:31] <holstein> TresEquis_: right, but the JACK sink module is starting it up again
[04:31] <holstein> as configured
[04:32] <holstein> thats what i dont need.. i dont need pulse and JACK running at the same time
[04:32] <holstein> but, if it gets seemless, i think its great
[04:34] <TresEquis_> somehow, when jackd starts, if PA has the device enabled in its config, PA starts too
[04:34] <TresEquis_> which is not what I want
[04:34] <holstein> right... thats the pulse sink module
[04:34] <holstein> it runs, or tries to run pulse
[04:34] <holstein> you can strip it all out
[04:41] <TresEquis_> thanks for the help
[04:41] <holstein> TresEquis_: sure... anytime
[05:30] <TresEquis_> holstein, I see from http://opensourcemusician.com that you are a bassist
[05:30] <TresEquis_> I'm not one, I'm just a guitarist who fakes it :)
[05:31] <TresEquis_> but I was just able to lay down the bass line I wanted against the drums from Hydrogen
[05:43] <TresEquis_> thanks again.  Nytol
[15:20] <raven_> hi
[15:20] <raven_> what is the best way to sync rosegarden, ardour and jack?
[15:44] <holstein> raven_: using JACK
[15:45] <holstein> depends on what you are trying to do with them
[15:45] <holstein> they should sync with each other using JACK
[15:45] <raven_> ok ill try that tnx
[15:45] <holstein> though, when i have done that, i get things working together, and i track my MIDI as audio in ardour
[15:45] <holstein> you can also ask in #opensourcemusicians