RME UFX, why is Sonar using "Generic ASIO Low Latency Driver"???

I have an RME UFX, ASIO Fireface set as master device.  The Generic driver is greyed out an unselected. 
 
However, whenever I change audio settings, a popup appears that says "Generic ASIO Low Latency Driver" and in the box "Checking RME . . . "
 
Leads me to believe Sonar is using a generic asio driver.  WTF.  Seriously.  RME has the best drivers in the business and Sonar is forcing to use the generic?  Latency performance seems relatively poor.
 
If it IS using the RME drivers, how can I get SONAR to stop displaying the pop up?

I have the RME unit and I have come across the problem you describe. I was able to chase it down to a MIDI device (Fishman Triple Play) in standalone mode. However I don't believe I ever came across it while utilizing the device while I was in Sonar. As Karhide mentions make sure your preferences are set.
 
And make sure that your MOBOs sound card is configured correctly. On my DAW that item is disabled, disconnected and dissed permanently.
 
Hope you get it figured. Regards,

I've just thought you might be class compliant mode. 
 
Check out this on the RME site: 
 
http://www.rme-audio.de/en_support_techinfo.php?page=content/support/en_support_techinfo_cc_mode
 
 

As far as I know,there is no "Genetic ASIO" drivers. Only thing remotely generic asio is ASIO4ALL. And if Sonar were to use that driver, it would say ASIO4ALL.

karhide
I think this is something to do with your configuration.
 
This is what mine looks like for my UFX:
 

My panel looks mostly like that except I am using the XLR pair 11/12 to my monitors, so 11 is set as the master (odd that it only shows the first of the stereo pair).

The pop up shows up for about 3 seconds and I can't even do a print screen of it.  Just doesnt appear in the image.  
 
But it hapens every time I exit from the preferences.
 

mmorgan
I have the RME unit and I have come across the problem you describe. I was able to chase it down to a MIDI device (Fishman Triple Play) in standalone mode. However I don't believe I ever came across it while utilizing the device while I was in Sonar. As Karhide mentions make sure your preferences are set.
 
And make sure that your MOBOs sound card is configured correctly. On my DAW that item is disabled, disconnected and dissed permanently.
 
Hope you get it figured. Regards,

I have disabled all midi devices in SONAR.  Still having the problem.
 
Its not running in Class Compliant mode, because TotalMix is working.

Teal

 
Also, why do you need two separate tracks for a VSTi?  Samplitude has combined midi/audio tracks, just enable a VSTi and everything works.  

Then use Samplitude. Problem solved!

I am using a UFX and my drivers are defined as expected. I would try to uninstall the drivers and plug the UFX as a USB device with up to date drivers and BIOS. You are doing something wrong.. Start from scratch with your UFX driver setup.

Teal
This software has a very "garbagey" feel.  Will give another 15 minutes of my time then write this POS off as a loss.  Shame  because the upgrade is cheap for former SONAR users.
 
Also, why do you need two separate tracks for a VSTi?  Samplitude has combined midi/audio tracks, just enable a VSTi and everything works.  Things that make you go . . .
 

SONAR has simple instrument tracks as an option - I use them all the time for one input/one output soft synth instances, though if you spent a bit of time with the program you would realize there are benefits to SONAR's approach of separate tracks for MIDI and audio. 
Your attitude blows (and the "garbagey" feel is from your post) - "Things that make you go..." (At least figure out whether or not a feature exists before you dismiss the program for not having it).
Enjoy Samplitude. Bye bye.
 

Guitarmech111
I am using a UFX and my drivers are defined as expected...You are doing something wrong...

I've reviewed lots of RME interfaces over the years with Sonar, and never had a problem (except affording the high-end ones )
 
Have you ever had Cubase installed on your system? If so I may have an explanation for what you're seeing. 

If you have Samplitude installed, it installs a Generic ASIO driver.
Set Sonar to use ASIO driver mode... and select the RME ASIO driver.
That's all there is to it...

Anderton

Guitarmech111
I am using a UFX and my drivers are defined as expected...You are doing something wrong...

I've reviewed lots of RME interfaces over the years with Sonar, and never had a problem (except affording the high-end ones )
 
Have you ever had Cubase installed on your system? If so I may have an explanation for what you're seeing. 

I had the Cubase demo installed.  And the Studio One 2.6.   And Ableton.  Now Sonar x3.  Trying everything out there.
 
The fact that the software is using a driver I have deselected indicates a software bug or glitch, or at the very least poorly documented feature.
 
RME has been rock solid and works perfectly with every other app, multiple apps open at once, it is updated to latest drivers and firmware, that its a reasonable to assume a software issue.
 
This is like a test drive where a part of the car falls off.  Most of them may be good cars, but the one I drove had/has issues.

Jim Roseberry
If you have Samplitude installed, it installs a Generic ASIO driver.
Set Sonar to use ASIO driver mode... and select the RME ASIO driver.
That's all there is to it...

NO such driver appears in Smplitude.  ASIO4All not installed.

Teal
 
Sorry for my poor attitude, but time is money and I cant get bogged with a buggy application or a protracted conversation.

Or apparently, the time required to find out the source of the problem and fix it. And that's fine; you can make music with any DAW. I use Sonar because time is money for me as well, and of the DAWs I own (which is basically all of them), for my needs Sonar gets projects done faster, whether it's narration, a remix, or straight ahead recording. But you certainly don't NEED to use Sonar. 
 
However I'd still recommend trying to find the source of the problem. It's possible that there is some incompatibility with Sonar that relates uniquely to your system and how it's configured, but it's also possible that whatever Sonar is flagging could influence other programs as well. 
 
As to your attitude, you're not thinking logically. There are many people on this forum who use RME interfaces. If there was a problem with Sonar and it was a "buggy application," your problem would have shown up before or you at least wouldn't be getting a bunch of RME users saying they don't have problems. FWIW I've never been able to get the Generic ASIO driver that Cubase installed off my system, and believe me, I've tried because it wants to take over if I boot any program without remembering to turn on an audio interface first. I'm sure Steinberg's motivations were good - "We will make sure you can run using ASIO even with a laptop" or whatever - but not everyone uses Cubase.
 
I would never install multiple trial versions all at once. I would set a system restore point, evaluate a program for a week, restore, then evaluate the next program.