If bristol is started twice, for example, both invocations may attempt to use the same port - 5028, the default. This may be desirable however if the user has requested a separate engine, or, put more specifically, has not explicitly requested the use of the same engine, then bristol should not limit itself to this default port but should search for another available one. The user is typically not concerned with what is used so either look for the nearest one to 5029 or take the nearest available to the explicitly provided one.
The other side is that multiple requests to start an engine will typically want to use different jack interfaces, the use of TCP ports is the access mechanism to attach multiple bristol engines with the -audiodev option for the regisrtration identifier. This will have to be well documented for the few users who do want multitimbral engines however I think that is rare since there are not reports of the known unrelated issues with that functionality.
Log in to post a comment.