Doktor Avalanche
And what does X3 working and Platinum not working help you eliminate exactly?

if something changed in sonar between x3 and platinum, it's a hot lead
if nothing changed in sonar between x3 and platinum, it's a hot lead
tl/dr, it helps us eliminate sonar
/eli5

Doktor Avalanche
And what does X3 working and Platinum not working help you eliminate exactly?

 

pwalpwal
if something changed in sonar between x3 and platinum, it's a hot lead
if nothing changed in sonar between x3 and platinum, it's a hot lead
tl/dr, it helps us eliminate sonar
/eli5

A hot lead to what? As you can see this issue was nothing to do with X3 and ended up being driver configuration (deleting AUD.INI cleared the issue apparently).
 
I suggest you click on the link I supplied above and read what a baker has to say on this as clearly you aren't going to pay any attention to what I have to say, your assumptions are totally way off. You can't rule out anything whatsoever just because something "works" with other software. It is just is not that simple.

I deleted aud.ini and cakewalk.ini as the OP did and it was no go for me. I then went into Sounds in control panel and set my "speakers" output for shared mode in Windows to default (which is 48000hz and 24bit) and now it is working as it should. I am running on ASIO again.
 

teego
I deleted aud.ini and cakewalk.ini as the OP did and it was no go for me. I then went into Sounds in control panel and set my "speakers" output for shared mode in Windows to default (which is 48000hz and 24bit) and now it is working as it should. I am running on ASIO again.

 
In windows sounds you might want to set your internal sound chip to default (you will still need to route the sound afterwards), and disable your audio interface. Or just disable all the interfaces in there (side effect is no sound in windows). Lots of options anyway looks like you have chosen what is suitable for you...
 

Doktor Avalanche
 
I deleted aud.ini and cakewalk.ini as the OP did and it was no go for me. I then went into Sounds in control panel and set my "speakers" output for shared mode in Windows to default (which is 48000hz and 24bit) and now it is working as it should. I am running on ASIO again.

 
In windows sounds you might want to set your internal sound chip to default (you will still need to route the sound afterwards), and disable your audio interface. Or just disable all the interfaces in there (side effect is no sound in windows). Lots of options anyway looks like you have chosen what is suitable for you...
 


I only have the one set of speakers so I have to use them for everything. The thing is it always worked seamlessly for me in Windows 7. Seems like Sonar and Windows 10 want to fight each other for the driver .

teego
I only have the one set of speakers so I have to use them for everything. The thing is it always worked seamlessly for me in Windows 7. Seems like Sonar and Windows 10 want to fight each other for the driver .

Just buy a lead, one end get the output of your soundcard, the other end get the inputs of your saffire pro 24 at the back. Then set up mix control accordingly. That is assuming you have a couple of free inputs. I do this with my pro 40, if I need the inputs for recording I unplug them temporarily.
 
 

That is a good idea Doktor A  ! Thanks!
 

Doktor Avalanche

Doktor Avalanche
And what does X3 working and Platinum not working help you eliminate exactly?

 

pwalpwal
if something changed in sonar between x3 and platinum, it's a hot lead
if nothing changed in sonar between x3 and platinum, it's a hot lead
tl/dr, it helps us eliminate sonar
/eli5

A hot lead to what? As you can see this issue was nothing to do with X3 and ended up being driver configuration (deleting AUD.INI cleared the issue apparently).

a hot lead to some difference in those sonar versions, in this case the aud.ini file

Doktor Avalanche
I suggest you click on the link I supplied above and read what a baker has to say on this

i did; i suggest you do the same, and maybe even read it a 2nd or 3rd time, sometimes that helps? maybe you'll notice that i said the same as noel - it's a process of elimination?

Doktor Avalanche
as clearly you aren't going to pay any attention to what I have to say,

bingo! can we go home now?

Doktor Avalanche
your assumptions are totally way off. You can't rule out anything whatsoever just because something "works" with other software. It is just is not that simple.

i didn't make any assumptions, that's your job; i merely suggested that immediately assuming it's not sonar (which, as it turned out, it was: the aud.ini file) is bad advice
cheers etc

pwalpwal
i didn't make any assumptions, that's your job; i merely suggested that immediately assuming it's not sonar (which, as it turned out, it was: the aud.ini file) is bad advice
cheers etc

AUD.INI is the driver configuration file where the audio interface gets configured, it is NOT the Sonar application code. I said all along the issue was pointing towards the interface itself or the way it is configured (in Sonar preferences). I had already said " the settings may need to be reviewed in Sonar preferences." and all along I said this was pointing towards the audio interface. At which point along the chain it was yet to be worked out at that stage.
 
I did not jump to your conclusions...
 

pwalpwal
it does make one wonder, with audio driver handling being such a low-level requirement in any daw, what could have changed between versions in the way the daw handles the driver, what was wrong with the x3 implementation? maybe someone from cakewalk could comment what changes were made?

Doktor Avalanche
AUD.INI is the driver configuration file where the audio interface gets configured, it is NOT the Sonar application code.

now there's a distinction you never made before... tell me, is aud.ini a part of the sonar installation? does it affect how sonar uses the device driver? do you get out much?