Re: [Denemo-devel] Interfacing multiple jackmidi ports

[Nils Gey]

On Mon, 23 Feb 2009 13:11:31 -0600
Jeremiah Benham <address@hidden> wrote:

> I want to create multiple ports for jack midi ports. I have been giving
> it some thought. Since I can't seem to find a way to dynamically add a
> new port once a new staff is created because the jack ports would need
> to be reactivated if new ones are added. Unless I am missing something
> the ports are first created then activated. If you later try to create a
> new port it destroys all ports. 

I did a quick research and It seems that you are indeed missing something.
Other apps are capable of creating and deleting new jack-midi-
ports (and audio) on the fly. Jack_mixer does it, zynjacku/lv2rack does it and 
Ardour(3 - svn version) does it too.

I had a talk in #lad on freenode.org (with nedko, the author of jack_mixer)and 
not the ports are activated, the client is activated.
Midi ports are created as jack audio ports, only type parameter is different.

For more information please join IRC #jack or #lad on irc.freenode.net or the 
LAD mailing list.

Nils



>From my understanding we have these
> options. 
> 
> 1) The user decided on a static number of midi outputs that will be set
> in preferences. The negative of this is that if a user decides they need
> more than $x number of staffs/voices. 
> The preferences would need to be changed and jack would need to be
> reactivated. Then in staff properties the user selects which port to
> assign. It may default to 0 (or the first midi port). Later once the
> staffs are assigned the ports may be able to be renamed to the staff
> name. If I am understanding this correctly we can have the name of the
> voice/staff and the jack ports match. So we can have jack midi ports
> named things like 0:Violin, I 1:Violin II, etc...
> 
> 2) The user creates the staffs/voices, Names the staffs in staff
> properties, Then clicks on a reactivate jack option. This will then
> create all new output ports containing matching names to the
> staff/voices. The problem I see with this method is that the user would
> most likely loose whatever connections to the existing denemo midi
> output ports. They would have to be reassigned. 
> 
> Please give me some feedback. Should I add support for both options? I
> am not sure which of these options will work well with lash. My guess
> would be option 1. 
>  
> Jeremiah
> 
> 
> 
> 
> _______________________________________________
> Denemo-devel mailing list
> address@hidden
> http://lists.gnu.org/mailman/listinfo/denemo-devel
> 


-- 
Nils Gey <address@hidden>