Here is the additional info given to me by both Jazzmutant and Cycling74. One of them addresses your question about the MIDI Port addressing as well.
------------------------------
>Thank you so much for the personal response. This is what I
>suspected (the editing the XML file is probably the best
>way to set up the parameters). It seems pretty clear in the
>sample document, so I may just plunk down and get one of
>these these week and continue to work on it. I would be
>happy to provide you guys feedback as well assuming you
>need anymore than you may already be recieving.
>>
>
>
>
>>Hello Rob,
>>
>>A friend of mine pointed me toward your post on ableton
>>forum. Your
>>remarks about our pet Lemur sound pretty relevant and
>>interesting.
>>Therefore, although the email you quoted has been
>>initialy sent to our
>>friends at cycling74, I couldn't help replying it by
>>myself. So, here is
>>the answers to your couple of questions :
>>
>> 1) after setting up my preferred interface windows in
>>the
>> JazzEditor application, I still do not understand how
>>to:
>> a) create additional MIDI assignments beyond the 39 or
>>so
>> that are already listed in the application. Looking at
>>the
>> Traktor example it is clear that additional MIDI
>> assignments were created to facilitate the extra
>>controls.
>> Was this done in the Variable area? And if so...
>>
>>A : Nowadays, there is 3 different ways to do that.
>>method 1 : use a text editor and modify the XML file by
>>hand (copy and
>>paste existing MIDI messages).
>>method 2 : Edit the 40 existing midi messages (you can
>>change their
>>name so that it fits the parameter you want to control
>>). Save your
>>interface and open it again : 40 new MIDI messages has
>>been
>>automatically created again.
>>method 3 : Be patient and wait we'll have added a "new
>>Midi Message"
>>button to JazzEditor!
>>
>>
>> b) how do you assign the MIDI assignment to a particular
>> object? Do you use the name of the object as a variable
>> parameter and then the software links the two?
>>
>>A : you can use any existing variables (whether local or
>>global). For
>>instance, you can assign the value of a fader called
>>'Bob' to a CC by
>>typing 'Bob.x*128' in the 'value' field. If you want to
>>change on the
>>fly the control number Bob is supposed to be assigned
>>to, just create
>>another fader called 'Jim' and type the expression
>>'Jim.x*128' into the
>>'control' field. By this way, if 'Jim' is equal to 0.5,
>>then Bob will
>>control CC# 64, while if 'Jim.x=1', Bob will control CC#
>> 127.
>>
>>We're preparing a bunch of cool examples using different
>>applications
>>(Live, reason, absynth...) that will help you to
>>understand the OSC to
>>Midi Mapping.
>>
>> 2) Don't know if you can answer this one, because it is
>> application specific, but my guess is that you can use
>>the
>> MIDI learn command found in many applications like Live,
>> Reason, or Traktor to latch a particular object to a
>> function in the host application. Is this how it is
>>done?
>>
>>
>>A: I think I can reply this question. As you might have
>>noticed, for any
>>messages (Midi or OSC), you can decide wether or not
>>it's sent out by
>>clicking the corresponding check box. To learn a
>>JazzEditor MIDI message
>>to Live, just check its sent box and ensure that all
>>other MIDI messages
>>are unchecked. Then move the corresponding object and
>>it's ready.
From Cycling74:
---------------------------------------------------
Hi Robert,
Thanks for your email. The JazzEditor doesn't seem to have this
function yet, but new MIDI objects can be added by opening the xml file in a
text editor and copy/pasting the MIDI lines, renaming the "name="
value to something unique. The MIDI features are still in development at
JazzMutant, so expect to see a more convenient method in the near
future. I am currently working on implementing Lemur MIDI controls in Live,
and it appears to be pretty straightforward so far. I'm hoping to have
more info on this soon. MIDI is assigned by giving the name of an
object parameter as the value (objectname.x for example).
-----------------------------------------------
Selling some extra gear right now and should be able to purchase this thing next week. I'll try to work through the issues and post to this thread as I find out new things, etc.
rob.