[Jack-Devel] Is JACK suitable for this?

[Mechamania]

Thanks for the answers! Helps me a lot! I'm glad JACK can do this number 
of channels with low latency :-)

But this remarks about 'if you have bad luck' scares me a little bit. 
And I hope that setting up a real time kernel is not needed. Isn't audio 
in general driven (timed) by the final target device? E.g. the audio 
output of the computer?

Maybe I should explain a little what we want to do:

We want to use SuperCollider to generate hunderds of sounds. Then this 
should be streamed to our game engine using JACK where there will be som 
processing and mixing. The final result is 2 channel audio that should 
be routed to some audio output (USB Dac for instance).

Do I need to set up my own real time kernel for this?

Suppose we use JACK for the connection to SuperCollider and to the final 
audio output. Will that be easy? Is the audio timing in this case 
controlled by the audio output? If not, then there need to be some audio 
resampling. That will cause latency and probably distortion. So I want 
to prevent that.

B.T.W., we are running on Windows 10.


Op 4-9-2019 om 18:06 schreef Ralf Mardorf:

> On Wed, 4 Sep 2019 17:09:49 +0200, Robin Gareus wrote:
>> The hard part is usually setting up JACK and tweaking a system for low
>> latency.
> Hi,
>
> IMO setting up jack is no issue at all (assuming there are no other
> sound servers installed, that could cause trouble), but I agree that
> tweaking the system for lowlatency could be hard, but not necessarily
> is hard to do. In my bad and good experiences it depends on luck related
> to the mobo and audio device.
>
> If you should have good luck, all you need is a vanilla kernel booted
> with 'threadirqs' or a real-time patched
> kernel, https://mirrors.edge.kernel.org/pub/linux/kernel/projects/rt/
> and what ever kernel you run, the rtirq script,
> https://github.com/rncbc/rtirq .
>
> If you should have bad luck with the hardware, you could try a lot of
> other things that might or might not improve audio latency and/or MIDI
> jitter. For me migrating from AMD based hardware, to Intel based
> hardware and avoiding the usage of a professional, but bad supported RME
> PCIe card by an USB class compliant prosumer device was the most
> successful step.
>
> "hundreds of audio channels", at least when using Ardour, are no big
> deal, even not with an energy-efficient CPU, with less horsepower.
> However, I wonder what you consider to be "lowlatency" and what else
> apart from the amount of audio channels might have impact on the load.
> Some people expect latency way lower, than any usual digital stomp
> box or 19" effect provides.
>
> YMMV!
> Ralf
>