Re: Re: Assigning Midi in Cubas and Kontakt 4 for Z-tar

You wrote that you didn't understand what I meant when I said I could turn notes off outside the zone. After I've set up a zone, then you have to assign a map to it. I would think the map would be as small as the zone but none of them are. They're always the complete length of the fingerboard and just as wide regardless of what the zone parameters are. 

I don't misunderstand the basics of Ztar programming as much as you imagine. I saved from kit 1 to kit 1 because the manual says I can. And I thought the Ztar would say "Kit Saved" because the manual says it will. But they wrote it a while back and things have changed it seems but they didn't bother to tell the rest of us. 

I was successful to get an older version of Midi Ox working. At first, it didn't even show "Airpad" which seems to be the name for my Ztar in Cubase also. But after I futsed around in Midi Ox, It showed in a 4 quadrant window. Starting in the upper left hand corner;

In 
1; Line 6 UX2
and 2; Airpad

in the lower left hand corner;

Out
2; Line 6 UX2
4; Midi Mapper
1; Microsoft GS Wavetable Synth
3; Airpad

in the upper right hand corner for Port Mapping;
UX2 has Airpad in it's submenu

In the lower right hand corner it has

Port Map Objects;
Channels
System
Midi8-Ox Events
Moxsysmap1.oxm

(The Channel submenu has 16 channels plus sys ex etc...)

In the lower right hand corner it shows 1 input device and 1 output device.

I performed one of the "actions" and could see in the monitor data coming in with this break down;

Timestamp(blah-blah)/ Input(IN2)/ Status(90)/ Data1 (29)/ Data 2 (4D)/ Chan(1)/ Note (F2)/ Event (Note On).

Both input and output ports light up in the midi port activity window.

The midi port routing window has Airpad routed to Airpad again by a line from running from left to right, then another routing line going from the airpad on the right to Midi Ox Event port below.