[Jack-Devel] Jack Problems

[Kjetil Matheussen]

On Wed, Mar 27, 2019 at 5:19 PM John Rigg <jd at jrigg.co.uk> wrote:
>
> On Wed, Mar 27, 2019 at 03:44:07PM +0100, Kjetil Matheussen wrote:
> > Clutterered or not, this functionality is something
> > pulseaudio/windows/osx all provide, but not jack. Is jack better
> > because it doesn't provide this? No, it's worse.
>
> No, it's decidedly better IMO. Complexity isn't always an improvement.
>

This should be considered an essential feature expected to be there.
Do you think the windows/pulseaudio/osx peple don't know what they are
doing? Do you think Fons' zita-mu1 program is not an improvement?



> > Probably not. You would need many many thousands of jack ports, or run
> > some kind of tiny embedded device, for the memory usage to be of any
> > size anyone would care about.
>
> Memory usage isn't the only concern. There's also the additional
> processing time involved.

Sorry, no there isn't.
In addition, you don't need it? Then don't use it, and don't get the
additional processing time. But even if you use it, the processing
overhead for this is absolutely nothing to care about.



> > Most people probably have no more than
> > around 20 custom ports + sound card ports at any time.
>
> In 14 years of jack use I've hardly ever used such a small
> number of ports. I'm probably not 'most people', but I'd
> expect a pro audio application to cater for typical
> multichannel recording and mixing as encountered in a
> professional studio. If you want to make it easier for
> more casual use fine, but please don't hobble it for more
> serious use.
>
Why do you assume anyone is trying to hobble jack for "more serious use"?