Running multiple interfaces on Music Creator 6

Welcome to the forum!
If you use the most recommendable driver, ASIO (NOT ASIO4ALL, which is a WDM wrapper), you can only use one interface at a time.
WDM driver allows using several interfaces, and I think ASIO4ALL does as well. Using several interfaces often leads to synchronising/clocking problems.

Welcome!
 
Just as the audio driver may be MME or ASIO, the ASIO audio driver may be built to one of two standards, V1 or V2.  The V1 standard only allows one audio interface at a time while the V2 standard allows multiple interfaces.  The trouble is few audio driver engineers bother to tell which standard they followed so you don't know how the audio driver works until you use it.
 
Music Creator 6 and 6 Touch are limited to two inputs while Music Creator 7 is limited to eight mono or four stereo inputs.  The online Music Creator documentation lists inputs in a chart comparing MC7 to Sonar.  A link is provided below.
 
You may notice in my signature I continue to use MC6.  That is because MC6 Touch and MC7 require Windows 7 or higher and my computer is still running XP Pro.
 
https://www.cakewalk.com/...p;help=Comparison.html

Kalle Rantaaho
You just can't help getting wiser here on the forum! I did not know of the ASIO V2.

 
Yup... I just heard about it too.... and supposedly, it's been out for a few years now.
 

I'm going to have to disagree on the statement that ASIO v2 allows for multiple devices.  as glen said above, ASIO4ALL allows for multiple devices, but not the ASIO standard.  
 
*ASIO4ALL is not a true ASIO protocol - it actually uses a soundcard device's WDM drivers and wraps them into an ASIO wrapper causing the host software to be able to use the ASIO internal calls, but the native uses on the computer are actually WDM.  WDM DOES allow for multiple devices.
 
*ASIO does not limit the number of devices under certain circumstances.  If a soundcard manufacturer creates hardware and software which are capable of running "as one device" under their ASIO compatible software drivers, then you can use more than one.  you cannot, however, mix and match soundcards under ASIO drivers (such as the 44VSL and the UR22).
 
for example:  MOTU creates ASIO drivers and hardware capable of being used together.  one thing that needs to be done when doing this is one of them needs to be a slave and the other a master.  several things play into this but the most important is the clock.  one of them has to use the clock signal from the other device, so there has to be a connection between the two using the same clock signal.  this could be through a PCIe, USB or Firewire bus or through an external cable connecting the two.  each card could use its own clock independently as a stand alone unit under ASIO, but if using both together, one of them has to relinquish it's clock signal and use the clock from the other device.
 
If, however, you connect a MOTU soundcard and a Presonus soundcard and try to select ASIO in Sonar (or any other host), you will be forced to select either the MOTU ASIO driver or the Presonus ASIO driver - not both and both soundcards will not operate under Sonar (or any other DAW) using ASIO.
 
you can select WDM and use both soundcards under this scenario.  However, as I mentioned above regarding the clocks when using ASIO - it is not possible to use the same hardware clock system in two cards which are not designed to be used as "one card."  so if you select WDM drivers for a MOTU and a Presonus, you will still have to select ONE of them to be the master clock - but since they are not hardware physically using the same clock - they will drift away from each other when recording.  small recordings might not ever matter.  but a 5 minute song might very well show you that the clocks are not sync'd when using an input from each and an output set from one of them.  longer recordings than that will absolutely show drift between the input channels.
 
ASIO standard is a consortium and held by Steinberg.  it is a paper and a standard to which manufacturers design their software (and can design their hardware in conjunction with).  the current version is 2.3.  Software can share ASIO drivers if the software is designed to do so.  Hardware (soundcards) can only share with other hardware if the hardware AND the software ASIO drivers from that manufacturer can support it.  different manufacturers of soundcards will NOT support multiple ASIO devices.

I was under the impression that ASIO 2.0 was a newer version of ASIO1.0 that has multiple client support and that this was a true ASIO driver and not the A4A wrapper.
 
See this link:  http://www.thesycon.de/eng/usb_audiodriver.shtml
 
I have not attempted to DL the ASIO 2.0 driver..... so I'm not speaking from first hand knowledge. Just from what I see on the page...   6th one down under ASIO Features.

Herb - there's nothing to download for ASIO 2 unless you're talking about the SDK (which I referenced above) or ASIO4ALL.
 
the only reason I mentioned downloading the ASIO 2.3 SDK is so that if one is curious about reading the ASIO Specification they could find it in the SDK.
 
SDK is not necessary to be downloaded by anyone except developers (SDK stands for Software Development Kit).
 
there is now and always has been a "one driver at a time" restriction for the ASIO spec.
 
I'll show you a screen shot of what Sonar/MC does when it sees 2 ASIO drivers if you want, but bottom line is that you can only CHECK one of them.  if I have 2 devices connected to my PC which use ASIO drivers (which I often do with my MOTU and my yamaha keyboard) - sonar will only allow me to use one of them and the other is grayed out.