I found out how grid groove works but I'm not sure ye if it is the solution to my problem?

In a song SONG I have 2 tracks, drumkit (played by MOX directly) and a percussion track (sent to VST through midi channel 2)
-I use AU Lab as a host. I have a macbook pro core 2 due 2.5ghz, 8gb ram regular 5200rpm hdd.
-Sforzando is the sampler plugin. I set the polyphony to 128, pre-caching to 32kb, max RAM 512 (although samples I'm using at the moment are less than 2MB!)
I attached two pics to this post that shows my settings for the sound interfaces. Interestingly, the latency of MOX is greater than internal sound card.

This is all well and good but is meaningless to us. I don't know AU Lab, nor do I know Sforzando, so I cannot help you here.

If you are using the Yamaha Steinberg USB driver then say so - then we can address perhaps your MOXF issue.

Also disturbing to us is your referring to the Yamaha as MOXF in some places and MOX in others... Prompting this question: which one are we talking about, please?

Well I haven't tried Cubase yet (don't have it installed). If you were in my shoes where would you tweak first? Is the sound interface not good enough? The lap top is old? Is there a way I introduce a little bit delay in the MOX sequencer? I played with groove settings but it seems I'm unable to get it work. How should I use groove?

If I were in your shoes looking for help here, I'd use Cubase for the following reasons.
1- we can help you here on this site.
2- if you have problems running you other items we know we can refer you to help with Cubase, if we cannot answer you directly
3- I know the latency issue will be non-existent as a problem.

I see your point. I'm using Steinberg USB version 1.9.7. I have MOX but I don't have cubase. I started with the simplest setup: MOX and AU Lab(AU Host). Sforzando is a AU sampler. AU Lab is an app developed by Apple long time ago but since it's minimalistic (~9MB) I gave it a try. For me, MOX sequencer is enough (only wish this groove feature had copy paste capability!!!). I will definitely look into items 2 and 3. Meanwhile I wanted to test Steinberg UR22mkII but I'd appreciate if you tell me how or where should I look for detailed comparison of between MOX and UR22mkII hardware and performances beyond the sample and bit rates?

There are two issues, is there a place that I can find a proper set up tutorial for VST+MOX? I set the midi channels in MOX and cubase but i still get all the tracks sent to my VST. Also it only plays when I click on the specific track. What am I missing here?
I installed the bundled cubase (v 6.x) and there is still latency. The latency is almost identical to AU Lab for Sforzando sampler. Without using groove the VST percussion is not in synch with the internal drumkit track in MOX.

Most VSTi receive on all (or I should say, "any") incoming MIDI channel. This is so that users don't get confused by having to match channels. You can learn to use your computer applications usually by reading the documentation that comes with it, because each can vary greatly in how it deals with Midi. Some are multi-timbal and can receive on multiple channels discreetly for each part. Others are simple single part devices that simply respond to incoming Midi no matter which channel is received. And there are some that receive everything coming in, because they expect/anticipate you will be using them as designed (which is triggered from a host program).

You may never find a tutorial specific to MOX + your specific VSTi applications. There are simply too many different possible VSTi. What you will want to do is use your host application (the one running the VSTi) to filter all incoming Midi channels except the one going to your VSTi. Many VSTi do not allow you to select a single channel... Again to make it "easy to use". (I always find this annoying, assuming Midi channel matching is too difficult for users, alas, they don't ask me :)...

My suggestion learn to use your host application. Read the documentation that is provided with your VSTi.

If your are using a full version of Cubase, for example, you could use the "INPUT TRANSFORMER" to filter all channels but one going to your VSTi. A DAW typically allows you to dedicate a track to a VSTi, and you can, depending on how you setup, isolate the data routed to that VSTi.

Sorry, but again we don't know anything about the software you are using. Does it not tell you how it deals with Midi channels?

We are not certain what your goal is exactly... If you are trying to use your computer as a hardware module, be prepared to deal with the issues of how it is not so much designed to do that. If you use a DAW as the source for your MIDI tracks the computer will be in charge of routing things... and you'll find that things work more smoothly... (Software designers typically ASSUME you are working "in the box" (computer) and not that you Midi tracks originate externally.

You mention nothing about synchronization of the Clocks... Simply setting a tempo to the same value does not mean synchronization is in play. In general, the computer wants to be master clock... Use it to send MIDI CLOCK OUT to the MOX port 1.

In Cubase this is accomplished by going to TRANSPORTS > PROJECT SYNCHRONIZATION SETUP... > MIDI CLOCK OUT > Destination = MOX port 1

In the MOX set MIDI SYNC = auto
[UTILITY] > [F6] MIDI > [SF3] SYNC = MIDI SYNC = auto

Set the tempo in Cubase. The MOX will now sync to Cubase's clock. Sync is an absolute, it either is in Sync or it is not... There are no degrees of being in sync. It is or it ain't.

Thanks Phill for this comprehensive answer. Well Cubase Artist is the cheapest version that has MIDI Transformer plugin and not in AI/LE. I don't know about the complexity of it but I wish It was in AI/LE or I could buy just the plug in. The economy is not good to pay 300+ for a new software 😛

About the DAW, I meant Cubase. AU Lab is not a DAW and it only loads AU Plugins pretty simple and that's why I like it. Like a VST rack. I can also sync it with MOX sequencer, but this doesn't address the sample latency playback. I wish there was a simple way of introducing a little amount of delay in MOX initially.

For some reason MOX sequencer is more convenient to me compared to Cubase. Everything is almost a button away (may be I'm just not used to it). I want to use MOX's sequencer and VOICEs in conjunction with few VST instruments that MOX doesn't offer or I prefer a different one such as oriental percussions and instruments. So I'll eventually use 3-5 VSTs. It seems Cubase sort of compensates the latency when I record and playback with Cubase sequencer. I found some latency plugins, but first I want to know If in AI/LE, is there a way to use external (MOX) sequencer and avoid triggering all the tracks in Cubase at the same time?

first I want to know If in AI/LE, is there a way to use external (MOX) sequencer and avoid triggering all the tracks in Cubase at the same time?

Yes, any track of the MOX sequencer can be turned off from going out via MIDI. YES, definitely.

You are maybe looking into the wrong end of the telescope! As I explained because (as you say) the software you are using is simple, it is designed to be used where typically you don't have to worry about the incoming MIDI channel or even Note Limits. That's what I don't like about some VSTi... They've made it so "easy", and in doing so it becomes more difficult to creatively alter your workflow. For example, say you want to use your MOX for piano and your VSTi for bass in a split situation using one Midi channel... If the VST does not have the ability to set Note Limits - then it will respond to all incoming notes on the channel, naturally. Note Limits would allow it only play above or below a specific note (the Split Point).

This means the way you have to solve this to either add some kind of filter... Or you use something like the MOX Master mode with is Zone system. And as you should know, this works fine for note-on generated by the keys directly. You run into problems when it is not the KEYBOARD that is the source of the Note-ons, instead it is a Track of the SEQUENCER that is the source. There is no way to filter just some of the notes coming from the Track... as you could with the Keyboard.

You can prevent the entire Track from sending MIDI notes by setting the OUT SWITCH = OFF.

Say you want to use the MOX and all its cool Arps and grooves from a Performance, well, the magic that the MOX performs is going to difficult, if not impossible externally... It depends.

You are looking for a solution in the MOX for something lacking in an external computer based system. Things like the Input Transformer are not available in the free version of AI (understandable). The upgrade path to the full version of Cubase, however, is a lot less than you think. Remember register you Cubase and you get a big discount when you upgrade.

The MIDI events that travel out via Midi from the MOX sequencer are encoded with the MIDI channel.
The MOX allows you to turn OFF the MIDI stream on any MIDI channel, by setting the MIDI OUT SWITCH for that Track to OFF.
SONG > [F3] TRACK > [SF2] OUT SW...

Now, if the data on the tracks is triggering the VSTi in spite of you turning the Track's OUT SW = OFF, then perhaps what you are missing is that if you are using arpeggios or created those MIDI Tracks using the multiple Arpeggios of a Performance, (Direct Performance Record) then there is data on those tracks that you may not be realizing. Certain Parts of a Performance are simply not responding by outputting sound because of the aforementioned NOTE LIMITS or some Parts may only respond to notes above or below a certain velocity (VELOCITY LIMITS).

So without really have all the information about what you are doing we can only guess about why your OUT SW = OFF is causing your VSTi to sound other Part's data... It probably is responding to notes the "LIMIT" parameters of MOX are filtering.

What many folks don't realize is when you are playing a Performance, the MOX transmits on a single MIDI channel. Yet four Parts seem to sound separate musical parts when you record it to the sequencer... The direct Performance record features splits what you play to four different tracks... Some many be recorded directly others simply record the output of the arpeggio phrase assigned to the Part. If you press EDIT and view the Event list in the MOX sequencer you many notice as you scroll through the data that Note on event don't trigger the internal tone generator. Try it!

Try creating your MOX track by playing each one directly, one at a time, see if you get the same results. Let us know.

When I set up Cubase for multi-VST+MOX project:
-Set MOX to SONG or PATTERN mode (I made sure MIDI settings are properly set).
-adjust all the tracks and midi channel switches( Track 1 drums (IN), Track 2 VST(OUT), Track 3 VST(OUT) )
-Then in cubase, I create VST tracks, set the MIDI IN/OUTs and activate the tracks (push the little record button so that I can hear them all otherwise selected track will only play).

When I hit play on MOX the tracks that are set to internal and external work as expected in MOX but in Cubase, VST tracks play all incoming MIDI data simultaneously! I can't find any way to say hey organ track, just use channel 3 or sforzando just get track 2. Sforzando and Organ play every incoming midi event. I guess this is where I should use the midi plug-in I don't have to filter out the midi channel?
AU Lab has no problem mapping MIDI channels and defining note limits (please see the pictures). So I'm seeking 2 things here, get rid of latency (by introducing a manual latency) and proper MIDI settings. "All MIDI Inputs" is where I can't figure out. It does not matter wether I acheive it in cubase or au lab.

When I set up Cubase for multi-VST+MOX project:
-Set MOX to SONG or PATTERN mode (I made sure MIDI settings are properly set).
-adjust all the tracks and midi channel switches( Track 1 drums (IN), Track 2 VST(OUT), Track 3 VST(OUT) )
-Then in cubase, I create VST tracks, set the MIDI IN/OUTs and activate the tracks (push the little record button so that I can hear them all otherwise selected track will only play).

when you say you "adjust all the tracks and Midi channel switches... ??? What do you mean, please explain further, what are you talking about? This is not clear.

When I hit play on MOX the tracks that are set to internal and external work as expected in MOX but in Cubase, VST tracks play all incoming MIDI data simultaneously! I can't find any way to say hey organ track, just use channel 3 or sforzando just get track 2. Sforzando and Organ play every incoming midi event. I guess this is where I should use the midi plug-in I don't have to filter out the midi channel?

I'll ask again, is the data on these tracks originally created using the Direct Performance Record feature?

AU Lab has no problem mapping MIDI channels and defining note limits (please see the pictures). So I'm seeking 2 things here, get rid of latency (by introducing a manual latency) and proper MIDI settings. "All MIDI Inputs" is where I can't figure out. It does not matter wether I acheive it in cubase or au lab.

Again I have no idea what AU Lab is or does, I see no mention of it in the screenshots or is that what I'm seeing? Please let us know. Or is the screenshot of Sforzando? Or is that AU Lab defining data for AU Lab. Please explain. Thanks.

You define what "All Midi Inputs" is for Cubase by going to
DEVICES > DEVICE SETUP > MIDI > MIDI PORT SETUP

Here in the column to the far right mark the items (and only the items) you want as MIDI controllers. So for example, the MOX probably has 4 or 5 ports, you only want to mark Port 1. Because Port 1 is the Port that generates note-on events. You do not want Ports 2, 3, 4 or 5 sending data to your MIDI track.

ONLY ports that you want to input to your MIDI TRACK need be marked here!

Here is the whole setup/procedure:
I go to pattern mode, create 3 tracks:
Track1: Drumkits (internal voice)
Track2: VST
Track3: VST
Push REC to record 2 PHRASEs in the selected PATTERN on TRACK1, then TRACK2 and TRACK3
From TRACK (F3):
Set
INT SW On Off Off ...
EXT SW Off On On ...

I then go to Cubase, create 2 MIDI Tracks with VSTs by hitting F11 (I forgot the menu location but F11 brings it up). I can have up to 8 VSTs and it asks me if I want to create a MIDI track for it as well. Now here is where the problem starts. MOX send the midi data correctly but Cubase receives all midi data in without filtering and assigning or matching the TRACKs on MOX to the tracks on Cubase. So basically whatever I have in TRACK1,2 and 3 will be played simultaneously in every VST. For example If track 1 in Cubase is assigned to only oriental percussion VST (Sforzando), and track 2 to some melody for a sampled oriental instrument (Sforzando again) (in mox they are set to TRACK2 and TRACK3 ) the data from TRACK2,3 are routed to track1,2 in Cubase together and there is no way to rout TRACK2 midi data to track1 in Cubase and TRACK3 midi data to track2. It seems apple mainstage can do what I want but I'll miss the organ and prologue VSTs.

If you cannot select midi channels in your VSTi they are probably single (rather than multi part) instruments when you press F11 choose an "Instrument Track" rather than a "Rack Instrument"...