Hi,
I have noticed a peculiar behaviour in SONAR x3 producer that is making it impossible to use multiple audio devices with asio4all.
 
I have my primary sound device, a Behr UMC204HD and also a Boss GT100 USB device that I want to use for reamping over usb.   The goal is to use the UMC's outputs to my monitors while using the GT100 usb for reamping. 
 
Unfortunately, sonar won't display more than one asio4all driver set at a time.  For instance, with both devices attached to the computer, it will allow me to select IN: asio4all(Gt100).  The only output driver I can select is OUT: asio4all(Gt100).  The problem is that asio4all(unmc204hd) never shows up in the lists, UNLESS I disconnect the gt100, then asio4all(UMC204hd) will show up.
 
The whole point of using asio4all is to aggregate different audio devices, but Sonar seems to be putting a limitation on ASIO4ALL.  It only allows one asio4all device to show up in the list at a time.   I have verified that asio4all works independently with each device, which leads me to believe this is a sonar issue.  BOTH devices show up in the asio4all control panel.
 
Anyone have experience with this sort of thing? 
 

I have tried searching but apparently search is broken.  When I type in ASIO4ALL into search, it doesn't even find the thread I created with ASIO4ALL in the title.  Only finds two unrelated threads. 

The ASIO specification only permits one I/O driver to be used by the host at a time. If there are two devices shown in SONAR using ASIO mode, SONAR follows the ASIO specification. The aggregation must happen inside ASIO4All so that SONAR only works with one instance of ASIO4All.

I played around with it, and by selecting only an asio4all input device, when I attempted to close audio options, sonar gave an error saying I needed to select an output device.. .and lo and behold, both asio4all devices showed up in the lists. 
 
I'm now able to use my soundcard as output and perform reamping with the GT100 over usb, but Sonar had to be restarted and/or tricked into finding the alternate asio4all outputs.
 
I'm 99% sure this is a sonar bug, as both devices always show up within asio4all control panel.
 

Wow, this works great!  I finally got this working the way I always wanted it.
 
The GT100 is physically cabled with my amp so its difficult/inconvenient to re patch it every time I want to use it for computer recording.  Now I can use the GT100 for direct recording/reamping over USB without having to touch the cables.  Very cool, and surprisingly respectable latency. 

asio4all gets a lot of criticism in this forum, so it's nice to hear a success story :-)
i use asio4all but never for multiple (different) devices as i never had any useful success with that, so it's good to hear that it can work... care to share which devices you're using it with? i use it regularly (but only one device at a time) with an onboard realtek laptop soundchip, and a usb alesis photon x25 (recognised by windows as a generic usb audio device)
cheers
p
 

It works great, but its not clear that Sonar is able to load both asio4all devices the first time it runs.  I think the trick is to set one device as input, save, restart sonar and then both devices will show up both as input and output on the second start.  Once the project has been saved, it seems to work properly with both devices without any configuration.
 
I am using a Behringer UMC204hd as primary soundcard.  When I want to reamp, I select an asio4all device (as above) and then I'm able to use the I/O on a GT100 guitar processor for reamping, and use the UMC204HDs output to my monitors.  Two devices at once.
 
The round trip latency when running both devices is 24ms which is not ideal, but if I use it this way just for reamping, it is a non issue.
 
I have found that if I want to use asio4all while tracking, a good workaround is to use analog inputs to my soundcard and "real time monitoring" to monitor the recorded signal.
 
The real benefit of this is that I don't think I need my Radial X-amp reamping box any more.  The signal out to the GT100 (via usb) is routed to my amplifier which I then record with mics routed back to my soundcard.  This avoids an extra stage of conversion and guarantees levels are the same.
 

WDM, WASAPI would work.  Not a fan of ASIO4ALL which is really a WDM driver.

I used to suggest ASIO4ALL to anyone with latency issues who couldn't afford an audio interface.
once I started seeing problems with it in Windows 8 and Windows 10 I stopped suggesting it to others.
IMO, ASIO4ALL is simply a band aid until one is able to treat the real problem, a soundcard.

chuckebaby
I used to suggest ASIO4ALL to anyone with latency issues who couldn't afford an audio interface.
once I started seeing problems with it in Windows 8 and Windows 10 I stopped suggesting it to others.
IMO, ASIO4ALL is simply a band aid until one is able to treat the real problem, a soundcard.

I have a soundcard.  My new UMC204HD has incredible performance, almost as good as the RME I owned for several years.
 
The reason for me to use asio4all is so I can use two separate devices together.
 
I didnt even think to try WDM.  It will come down to which one provides better performance.  Its good to have options.  I can't see any reason to hate on asio4all.