[02:59] <Tooncenator> holstein - well not so fast. :( Unfortunately I had not yet tried video playback with jack running. I'm almost there with config, but video keeps freezing after about 8 seconds when I try playing it while jack is turned on. Furthermore, I can't actually hear any audio during playback either. As soon as I stop the jack server, everything is good.
[03:00] <holstein> Tooncenator: jack doesnt to video.. you shouldnt need it
[03:00] <holstein> what are you trying to playback? and why? and why are you using jack?
[03:01] <holstein> if you dont need, jack, dont use it, and as you say, all will be good
[03:01] <Tooncenator> Just trying to watch video tutorials on youtube as I learn how to use Ardour.
[03:01] <holstein> Tooncenator: sure.. but, you dont *need* to do that, and i would expect issues
[03:01] <Tooncenator> so i'll just have to remember to stop jack when viewing. No problem. :-) You 'da man!
[03:01] <holstein> i am able to route pulse audio sources through jack, using the included jack dbus,but, i personally disable that
[03:02] <Tooncenator> keeping things simple for now is good for me.
[03:02] <holstein> you should see, in qjackctl, in "connect" pulse audio sources that you can route to your jack output on the right side
[03:02] <holstein> in the audio tab
[03:04] <Tooncenator> it's routed to both playback channels on the right
[03:04] <Tooncenator> i should specify 'system' output on the right
[03:06] <holstein> thats how i  would do it.. i would then, isolate and test, as i said before
[03:06] <holstein> Tooncenator: its quite challenging, since, you could literally be the only person with that exact hardware tyring to use jack
[03:06] <Tooncenator> ok thanks. for now, i'll work around it like you originally suggested.
[03:07] <holstein> Tooncenator: i cant, for example, just look in my system, and tell you exactly what to do to make the functionality you want
[03:07] <Tooncenator> lol...that is quite true!
[03:07] <Tooncenator> gotcha
[03:07] <holstein> so, i will do this isolation and testing on *every* system i encounter
[03:07] <holstein> til i see how linux/alsa/jack are on the hardware
[03:08] <Tooncenator> in your experience, is latency of 46 msec good or bad?
[03:09] <holstein> latency is neither good nor bad. it just is the time it takes for audio to process
[03:10] <Tooncenator> ok - but it shouldn't affect live track layering - to use computer as both playback and record at the same time?
[03:10] <holstein> there are *only* 2 reasons for low latency.. software instruments, samplers.. realtime synths, as an instrument.. *or*, realtime effects.. such as adding a reverb in "realtime" to a guitar, on the way in the computer, for example
[03:10] <holstein> *if* i need low latency, for either of those, i need 8ms..
[03:10] <holstein> maybe, i can tolerate 12
[03:10] <Tooncenator> ok
[03:10] <holstein> i test that, again, by actually using my ears, and seeing what works
[03:10] <holstein> i set the settings, i route, i listen.. i either can use it, or not
[03:10] <holstein> you'll have to decide what works for you.. i can do 5ms stable, so i do *when* i want/need low latency
[03:11] <holstein> otherwise, i set my system at quite high latency, since, its not making anything any "better"..
[03:11] <holstein> you dont get "better" recordings, or sound, or anything, from setting the latency lower
[03:11] <Tooncenator> gotcha. thx
[03:11] <holstein> if you want to overdub, or "layer" tracks, the latency *should* be corrected
[03:12] <holstein> automatically, even. though, i have found that a bit unreliable, personally, so i suggest trying that for yourself, as well
[03:12] <Tooncenator> ok - will do.
[03:14] <Tooncenator> holstein - if you ever travel to Colorado, I owe you a beer - or two. :)
[03:14] <holstein> lol