Re: [Jack-Devel] filtering for jack net clients

PrevNext  Index
DateTue, 22 Jul 2014 11:21:17 +1000
From Matt Flax <[hidden] at flatmax dot org>
ToPaul Davis <[hidden] at linuxaudiosystems dot com>
CcDevelopers JACK <[hidden] at lists dot jackaudio dot org>
In-Reply-ToPaul Davis Re: [Jack-Devel] filtering for jack net clients
Follow-UpAdrian Knoth Re: [Jack-Devel] filtering for jack net clients
OK I understand.

Here is the problem. We have a jack server running on a remote computer. 
It is running some form of netjack.
My computer running a netjack driver connects to it and wants to play or 
acquire audio. It can't because the ports aren't connected to anything.
A solution to this problem is to run a client for port monitoring on the 
remote computer which autoconnects netjack clients.

Are there other solutions ?

Matt


On 22/07/14 11:17, Paul Davis wrote:
>
>
>
> On Mon, Jul 21, 2014 at 9:08 PM, Matt Flax <[hidden] 
> <mailto:[hidden]>> wrote:
>
>     Hi there,
>
>     Is there a way to detect whether a server's client is a net client ?
>
>     One possibility is to find clients with ports named '*slave*',
>     however what if a local client (non-net client) names its ports
>     with slave in their names ?
>
>
> We deliberately attempt to obscure such things. The model is supposed 
> to hide details like this. Any technique you find will just be a 
> heuristic that could break in the future. There are also other kinds 
> of "jack over a network" than just netjack (e.g. jack.trip).
>
>
PrevNext  Index

1405992440.3111_0.ltw:2, <53CDBC8D.1070303 at flatmax dot org>