Jeremiah.
3) The user builds his or her template, or tune, and 'creates' a new port in each staff preferences. Staff 1=port1, Staff 2=port 2 selectable by a drop down numerical list. Once all staves are built in the initial score, the user hits a button (keystroke) marked 'activate ports.'
If the user then wants to add or remove staves, he hits the button (keystroke) marked 'deactivate ports.' The staves that are still present keep the port assignations they have, the user adds or removes, then hits 'activate ports.'
4) Take a look at the Linuxsampler setup. We 'create' a midi device, then select how many ports we want. We can then assign, in channel preferences (the equivalent of staff preferences in denemo) by port and channel. I would think something like this, that simply gives the user the choice by port, would be sufficient, but if we wish to assign multiple channels from an assigned port, to articulation channels in LS in the future, then staff preferences might take on a different role, as an 'articulation by channel' selector as well.
Staff 1.
Port 0
1st violin legato up bow release=mcha1, port0
1st violin legato down bow release=mcha2, port0
1st violin legato up bow non release=mcha3, port0
1st violin legato down bow non release=mcha4, port 0,
and so on.
So you could have a port selector, and a small 'articulation dictionary' in staff preferences, in which the user can add text specifying the articulation and matching midi channel. Do this by 16, and there's a port and channel selector per staff, without the hassle of trying to 'autoconnect' and autodisconnect' jack ports.
just a couple of thoughts for discussion.
Alex.
- Show quoted text -
On Mon, Feb 23, 2009 at 9:11 PM, 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. 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
--
Parchment Studios (It started as a joke...)