I've decided to try an external midi interface since I'm still having problems with unstable midi using the Scope midi ins. I've bought a second hand Midisport 2x2 but was wondering about the best way to set it up to work both with Scope but also with VST instruments. Am I right in thinking since it's USB it will not input directly into Scope but will need a midi router and then I use the midi seq ins?
In VST/ASIO hosts however I presume it would show up as 2 "normal" midi ins/outs?
I was also wondering since I have a midi keyboard and a Phatboy controller ideally would like to be able to use them both at the same time (one to play notes, one to tweak knobs) so since the Midisport has 2 ins can I merge them inside the Midisport into one midi out to route into Scope and ASIO apps or is it only possible to have seperate ins/outs?
<font size=-1>[ This Message was edited by: Kymeia on 2006-09-11 09:51 ]</font>
Midisport
all these things are possible, just try some...
in order to get another midi interface into scope, there are a couple of possible routes. one would be, if the midisport allows it's outputs to act as thrus for inputs, conntect from the physical connectors. this should be quick and solid.
another would be through a piece of software. you can use something like midiox or the sequencer(make a track with scope as the input and output and record enable it). either way, the midi information will be availeable at the sequencer midi source module.
in order to get another midi interface into scope, there are a couple of possible routes. one would be, if the midisport allows it's outputs to act as thrus for inputs, conntect from the physical connectors. this should be quick and solid.
another would be through a piece of software. you can use something like midiox or the sequencer(make a track with scope as the input and output and record enable it). either way, the midi information will be availeable at the sequencer midi source module.
It does have a direct midi through mode but surely if I'm routing the midi from the midi sport into the Creamware cards hardware midi in's how is this any different from routing the midi directly from my controllers? Isn't the point to avoid using the problematic Creamware midi ports essentially or does going through the Midisport add something that stabilises the midi information somehow?if the midisport allows it's outputs to act as thrus for inputs, conntect from the physical connectors. this should be quick and solid.
well, you can connect directly. the problem happens between the cw midi port and the software app. things like active sensing and midi clock fill midi buffers to overload. the idea would be to use the midisport to connect to the sequencing app. the midisport can connect to scope thru that app or midiox or directly....
The problems that creamware midi ports have are fairly confirmed to be: Hyperthreading issues and problems with Active Sensing. Both together (a controller that sends active sensing AND the pc using HT) are certain to cause issues, but even separately (HT or A.S.) there have been problems for people.
That doesn't mean there aren't other bugs, but in ALL of the other cases I've seen the 'fix' was usually to wipe & reinstall or force the machine into 'standard mode' which imo isn't determining & fixing the root cause of the problem, but rather changing the base of the whole setup (often needlessly imo since I've eliminated midi lockups myself from all pc's I've had it on).
Adding a midisport 4x4 was my personal solution for keeping my Roland jd800 around, since it sends active sensing and it can't be turned off. I could have used a midi filter (external box connected inline on the midi out) but since it isn't my primary controller I chose the midisport. These days I just use the midisport entirely, with midi-ox or the sequencer to go between scope & my external gear (as garyb suggested).
That doesn't mean there aren't other bugs, but in ALL of the other cases I've seen the 'fix' was usually to wipe & reinstall or force the machine into 'standard mode' which imo isn't determining & fixing the root cause of the problem, but rather changing the base of the whole setup (often needlessly imo since I've eliminated midi lockups myself from all pc's I've had it on).
Adding a midisport 4x4 was my personal solution for keeping my Roland jd800 around, since it sends active sensing and it can't be turned off. I could have used a midi filter (external box connected inline on the midi out) but since it isn't my primary controller I chose the midisport. These days I just use the midisport entirely, with midi-ox or the sequencer to go between scope & my external gear (as garyb suggested).