From: Werner S. <ws...@se...> - 2005-05-16 18:09:45
|
On Monday 16 May 2005 07:19, Robert Jonsson wrote: > On Sunday 15 May 2005 23:39, mat...@br... wrote: > > .... <snip> (using the webmail, it messes up the mails completely) > > > > > Secondly, perhaps more importantly, I'm not sure if it's really right > > > to do this. The bug is really in the synths... we cannot make it fully > > > work however we try. > > > > > > Any thoughts? > > > > > > /Robert > > > > Without understanding this fully my opinion is that if the problems are > > in the synths we shouldn't spend time on a solution that will not be good > > in the end. > > Right, still it does not look good that all synths with the same name will > be grayed out in the connection dropdown as soon as one of them is > connected. i added some code to identify midi ports by port id instead of port name to fix this. But it does of course not help for session management functionality. Ideally the port name semantic of ALSA should be the same as for JACK. > > > Is there actually any recommendation out there stating that each > > client should have a unique name, regardless of client id (or am I just > > lost here)? > > I'm not sure if it's written anywhere, but it must be the truth. The client > id is only valid during the session so it's not usable on for managing > connections when launching a song. > Though, the same is true if the synth-name is automatically changed if the > name already exists. To be absolutely sure that it's valid the synths must > have a unique name set manually for each instance. > > like: > ./zynaddsubfx -name primaryZyn > ./zynaddsubfx -name secondaryZyn > > /Robert > > > /Mathias |