11 Apr
2015
11 Apr
'15
9:43 a.m.
But again, I wasn't proposing "one jack
client per effect" ... I was
proposing only a single JACK client per application, and NOT using JACK's
audio graph capabilities within your application: you would need to compute
execution order yourself or use a nice library for this (not that there
necessarily are any nice libraries).
Need to ask once more. Assuming I'll do this - one jack client and zynaddsubfx as a
plugin. Nonetheless, if I have 40 instances of zyn, I'd like to (actually must)
compute them concurrently. So how to do this with one client?
The best way I can see is using an array of jack clients, and hoping they'll process()
at the same time. However, this sounds very tricky...
11 Apr
11 Apr
9:49 a.m.
New subject: [Jack-Devel] Avoiding spinlocks in a parallel sequencer
On Sat, Apr 11, 2015 at 10:43 AM, Johannes Lorenz <
johannes89(a)mailueberfall.de> wrote:
By using your own internal graph mechanism that has parallel capabilities.
See, for excample, https://github.com/flowprogramming/dspatch
But again, I
wasn't proposing "one jack client per effect" ... I was
proposing only a single JACK client per application, and NOT using JACK's
audio graph capabilities within your application: you would need to
compute
execution order yourself or use a nice library
for this (not that there
necessarily are any nice libraries).
Need to ask once more. Assuming I'll do this - one jack client and
zynaddsubfx as a plugin. Nonetheless, if I have 40 instances of zyn, I'd
like to (actually must) compute them concurrently. So how to do this with
one client?
The best way I can see is using an array of jack clients, and hoping
they'll process() at the same time. However, this sounds very tricky...
There can be very good reasons for using JACK 1. If a user is doing that,
you won't get any parallelization at all.
3543
days inactive
3543
days old
jackaudio@lists.linuxaudio.org
1 comments
2 participants
participants (2)
-
Johannes Lorenz -
Paul Davis