We should move this post to another thread, because it's growing more and more off topic to this thread ...Maikan wrote: That's odd (but ultimately good news), because i seeming can't switch between presets/patches without having some kind of issue.
Do you encounter latency problems when synched with a DAW? When i synch to Protools with the Sub 37 receiving clock and the sequencer of the sub 37 putting out midi back into protools, i find that the midi data arrives significantly later than it should/later than the audio. My midi setup is a bit convoluted (connecting 7 synths and a DAW) and involves a lot of cable length and a MIDI signal splitter, could the cables themselves be the issue? Is there a way to compensate for this lag in protools (i'm running PT 10 and/or 11)?
My setup is a hardware-only thing. Midi-clock is generated by my workstation or alternatively by my Octatrack and fed into the midi-network. All hardware is connected via the traditional 5 pole cables. I use a midi-patch bay and this makes the midi-network to be a "star-like" layout - one master in, many slaves out. I don't use midi-in to midi-through chains. I switch the Sub37 patches directly at the Sub37 panel.
As you mentioned already, it's a well known fact, that too long cabling can cause issues, but bad electrical contacts, and too long midi-chains also. Decent midi-splitter and midi-merger should work fine, when used properly.
To find the culprit in your setup, you might want to isolate the Sub37 and connect it to your computer directly, or alternatevly, to an external hardware midi-clock-master. Workstations and some synths can be used to supply the midi-clock. If your hardware works fine, then you should check your midi-network and your midi-settings in protools. I don't have protools myself, but my two DAWs in use have latency compensation properties to be changed in the setup-dialog and I think that protools has this feature too.