Re: [LAU] Dual Delta Setup

Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
To: Ben Bell <bjb-linux-audio-user@...>
Cc: <linux-audio-user@...>
Date: Sunday, December 30, 2012 - 4:55 pm

On Sun, December 30, 2012 6:22 am, Ben Bell wrote:

> On Sat, Dec 29, 2012 at 01:28:47PM -0500, drew Roberts wrote:

That seems pretty good actually. Using pulseaudio for the same job pretty
much triples the cpu load. That is, if jack is using 10% on it's own,
bridging pulse to jack raises CPU to about 28%. (over using pulse and jack
separately, don't bother ranting about pulse please, I am NOT suggesting
it's use in this case... or any other, just relating my experience) If you
think about it at all though, connected or not, each port/channel needs to
be fed silence at 48k all the time. Jack needs alsa-in to run at the same
latency as jack is too.

In my mind, the problem is that jack only deals with one device. Jack is
for pro or semmipro IFs which do have the possibility of sync. This seems
to be a common use so Jack _should_ handle it. It would seem that if jack
was aware there were two devices it would initialize both correctly when
it started rather than initializing one and hoping the other followed.
Certainly the user would then be able to tell jack which of two devices
was the master (for example) which _should_ be able to make a more stable
system. Maybe there are other problems that I am not aware of that keeps
this from being a reality as audio signal coding is not something I have
dealt with... or maybe in jackd3?

Really, Jackd is a great tool that just works for me. I am glad we have it.

BTW one more thing with the "multi" setup from before. If you are using
the setup from J Rigg's page. hw0 should be the clock master, I think. If
hw1 is the clock master then the:
ctl.playback24 {
type hw
card 0
}
(and similar section in capture) should reflect that, would be my guess.

--
Len Ovens
www.OvenWerks.net

_______________________________________________
Linux-audio-user mailing list
Linux-audio-user@lists.linuxaudio.org
http://lists.linuxaudio.org/listinfo/linux-audio-user

Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
[LAU] Dual Delta Setup, Ben Bell, (Sat Dec 29, 11:43 am)
Re: [LAU] Dual Delta Setup, drew Roberts, (Sat Dec 29, 6:29 pm)
Re: [LAU] Dual Delta Setup, Ben Bell, (Sun Dec 30, 2:22 pm)
Re: [LAU] Dual Delta Setup, Len Ovens, (Sun Dec 30, 4:55 pm)
Re: [LAU] Dual Delta Setup, Fons Adriaensen, (Sun Dec 30, 2:46 pm)
Re: [LAU] Dual Delta Setup, Ben Bell, (Sun Dec 30, 7:27 pm)
Re: [LAU] Dual Delta Setup, Fons Adriaensen, (Sun Dec 30, 11:33 pm)
Re: [LAU] Dual Delta Setup, Devin Anderson, (Sun Dec 30, 11:51 pm)
Re: [LAU] Dual Delta Setup, Len Ovens, (Mon Dec 31, 1:50 am)
Re: [LAU] Dual Delta Setup, Devin Anderson, (Mon Dec 31, 3:12 am)
Re: [LAU] Dual Delta Setup, Len Ovens, (Wed Jan 2, 11:35 pm)
Re: [LAU] Dual Delta Setup, Joe Hartley, (Thu Jan 3, 12:26 am)
Re: [LAU] Dual Delta Setup, Fons Adriaensen, (Thu Jan 3, 12:05 am)
Re: [LAU] Dual Delta Setup, Len Ovens, (Thu Jan 3, 3:15 am)
Re: [LAU] Dual Delta Setup, John Murphy, (Thu Jan 3, 5:04 am)
Re: [LAU] Dual Delta Setup, Len Ovens, (Mon Dec 31, 2:47 pm)
Re: [LAU] Dual Delta Setup, Paul Davis, (Mon Dec 31, 2:58 pm)
Re: [LAU] Dual Delta Setup, Len Ovens, (Mon Dec 31, 10:33 pm)
Re: [LAU] Dual Delta Setup, Paul Davis, (Tue Jan 1, 4:06 am)
Re: [LAU] Dual Delta Setup, Paul Davis, (Mon Dec 31, 2:03 am)
Re: [LAU] Dual Delta Setup, Devin Anderson, (Mon Dec 31, 2:40 am)
Re: [LAU] Dual Delta Setup, Fons Adriaensen, (Mon Dec 31, 9:24 am)
Re: [LAU] Dual Delta Setup, Paul Davis, (Sun Dec 30, 3:52 pm)
Re: [LAU] Dual Delta Setup, Fons Adriaensen, (Sun Dec 30, 4:27 pm)
Re: [LAU] Dual Delta Setup, Ben Bell, (Sat Dec 29, 10:35 pm)
Re: [LAU] Dual Delta Setup, Len Ovens, (Sat Dec 29, 6:23 pm)
Re: [LAU] Dual Delta Setup, Ben Bell, (Sat Dec 29, 10:31 pm)