My apologies if this has been answered before or posting in the wrong place. I've searched through the forum here, PlanetZ and on the net but couldn't get a clear answer as to why the SCOPE 5.1 ASIO drivers only give me one input and one output and the WDM drivers give me the expected four and four (stereo - which, in Platinum are now actually labeled correctly so you see the mono and stereo choices). This may be a stupid question but I have not used SCOPE for almost 6 years but I recall having multiple IOs with SCOPE 4.5 in Win XP SP1 32 bit and not sure if they were ASIO or WDM. I thought there was an advantage to using ASIO but if not I can stick with WDM as I cannot hear any difference or see any stability differences. Thanks in advance! I do not need to sync at anything higher than 48Khz and I'm on Windows 7 Pro 64 bit if that somehow has something to do with it.
 

Use whatever works best, doesnt matter.

Right. Does anyone know why WDM gives 8+ I/Os and ASIO only gives 2 on SCOPE 5.1 with Platinum?

The ASIO drivers suck?
 
Speaking of which did you verify you have the latest drivers?

Never said they suck. Do they? Is that why the ins and outs are limited? They are the latest Scope 5.1.

On my Roland Studio-Capture, the ASIO drivers are better.  I can get lower latency than with the WDM drivers.

Sorry if I was not clear but I'm referring to SCOPE ASIO exclusively.

I don't get it, from your post I would have figured Scope was an obscure brand of audio interface but I see it's just software? 
http://sonic-core.net/joomla.soniccore/index.php?option=com_content&view=article&id=138%3Ascope-51-for-64-bit-version-of-windows-7&catid=36%3Afaq-scope-dsp-audio-platform&Itemid=56&lang=us
 
What audio interface are you using? 
 
And the story goes is there is no difference in audio quality between ASIO or WDM. But generally speaking audio interfaces that use ASIO drivers have better performance and latency.
Cakewalk recommends you try both and see which one works best for your set up.
Sounds like WDM is working better for you. And this might be like  Dave is saying,  I think he's being funny so don't take it wrong, A more polite answer  might be the company never wrote proper ASIO drivers for what ever audio interface your using. 

I'm confused as well, Johnny.
Scope appears to be something like ASIO4All. It, looks like, for whatever reason, the ASIO inputs are not being properly communicated to Sonar.
 
Ron, I see you have the MOTU interface. Is there a reason you are not using its native ASIO drivers?

I plan on using two integrated systems. A Prostar i7 Windows 8.1 notebook with SONAR Platinum and VSTs on top of the MOTU with native ASIO. The other system is an HP XW4600 Quad Core Win 7 64 with Platinum on top of SCOPE 5.1. The two systems communicate via ADAT and MIDI.
Recording is done on either one or both depending on the project. Everything is sync'd at 48Khz over ADAT and MIDI so control surfaces work across the board and either system can be the main transport controller.  It's a bit complex but the SCOPE system is really the workhorse because of its pristine native DSP processing which no DAW can touch before crashing and stuttering, etc.  I use the SONAR notebook without overloading the CPU (which is overclocked at 3.5 Ghz with 32GB worth of RAM and dual SSDs so it's pretty max headroom) for VSTs like AVOX and Guitar Rig and Kontakt 5 etc., which consume a lot of CPU. It's pretty solid with the MOTU which I also use as a direct box and pre's.  Between the MOTU and SCOPE cards it gives me over 224 channels of which 40 are analog. The most I would use is a mix of tops 32-40 with mostly digital including MIDI.
 
Now it's back to tweaking. So far so good now that I remembered how to set the ASIO2 channels in SCOPE! Doh!