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. 


Firstly, heed my advice about over-writing preset kits... Use only kit numbers higher than eight (ie. in the second display box as you scroll thru kit patches)  
You don't have to assign a map, there are no maps..  Possibly you mean preset-mapped zones..and presets may be the width and length of the fingerboard (I don't know as I have never ever inspected them or used them)  If you are intent on editing presets, then first copy them to a location higher than kit #8. and change the name..  


Start at kit #9, set up a few zones, using 2 x key presses only to assign a zone. (top and bottom notes on the neck) , and  save everything before you move the cursor (ie. at every step)  Then give your new patch a name.. Then go to another patch, and then back to #9 and check that all has been saved.


Then let me know how you are getting on.   You should be able to assign say a dozen either overlapping or discrete zones easily (if you are not trying to write to ROM in kits 1 to 8.) If you are trying to write to kits 1 to 8, (ROM, instead of RAM) then no amount of help will lead to any success, ever. 

As I told you before, start with the basics..and proceed from there. 


If you are now adding airpad to cubase and kontakt, and all to receive from a Ztar OS in which you cannot assign anything correctly, then you are doomed to failure..(or alternatively prolonged dementia) 


The Ztar is a very wonderful but simple instrument to set up, once you know what you are doing, and once you have made a working patch that does what you want on the neck, then you can easily copy it to other locations, and then change the names and the voices. (and save) then edit some of those user settings in their new locations. (and save)

Maybe other Ztarists here can help? or perhaps Harvey might give you some assistance.. 


richard 
bg (Bulgaria)


________________________________
 From: "[email protected]" <[email protected]>
To: [email protected] 
Sent: Saturday, 22 March 2014, 10:03
Subject: Re: [midiguitar] 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.