Export Sample Rate Weirdness X1b

That's odd, because X1b has made it harder than ever (if not impossible) to record (or even play back) with the sample rate not matching the project rate.

I also use an external ADAT clock source, and SONAR's audio engine won't even start now if I inadvertently load a 44.1 project with the clock running at 48. It used to be that SONAR would happily record at the wrong rate for the project with the result you're describing, but X1b won't do it; when it detects the discrepancy, it tries to change the sample rate of th interface, but it can't because the source is external, and it just stops with an immediate dropout error.

Nevetheless, it sounds to me like one way or another, your clock source is not matching your project sample rate. So, what's the ADAT source, and can you confirm that SONAR shows 44.1 in the transport display and that the MOTU is set to "external" for its clock source? Also, it seems it's now sometimes necessary to have the "Default [Sampling Rate] Setting for New Projects" in Preferences set to match the current project rate, even if it's not "new".

I'm actually not too happy with the new implementation. For me it causes more problems than it prevents.

Oh and just to note, the display of the MOTU shows (when sample rate clock source as ADAT) whatever the Ocatane Sample rate is set to. I am inclined to think that its Sonar that has stopped looking for the driver setting before opening a project.  

bug or buggered? 

Isn't it funny how that word does not translate across the water? In England its something your Grandmother might say while smoking a fag.  <- and there is another one !  

Happy Days...

What "Default"? I only have values and there is nothing that refers to a default.  I don't quite understand this but its only Win 7. I just popped Vista drive back in its all working great.  

If I have my audio devices set at 44.1 and the default is 48 in Sonar it takes 48. End of story for me. X1 takes no notice of the drivers reported value.

Whats the score?

Noel Borthwick [Cakewalk
]

Also, it seems it's now sometimes necessary to have the "Default [Sampling Rate] Setting for New Projects" in Preferences set to match the current project rate, even if it's not "new".

 
If you can illustrate a case where this is true please contact me. The default sample rate technically shouldn't be required to match the project sample rate. It was the case in the past due to certain problems.

The issue arises when I launch SONAR with the Default Sample Rate set to 48kHz, and my external ADAT clock running at 48kHz. If I then change the external ADAT source to 44.1kHz and open a 44.1KHz project, it will not play back until I go into Preferences and set the default to 44.1kHz. If I start SONAR with the external clock already running at 44.1kHz, there's no problem; the project will play without my having to touch the Default Setting of 48kHz.

Maybe this is working as designed for interfaces using an external clock source that can't be changed by SONAR. But it means I either have to restart SONAR to change sample rates or temporarily change the Default Setting for New Projects.

Maybe this is working as designed for interfaces using an external clock source that can't be changed by SONAR.

 
Not really, its not intentional. Please log a bug (whenever the bug submission system is back online) and I'll try and figure it out. There is probably some unwanted dependency on the default sample rate. That should only be enforced when creating a NEW project.

OK so sounds like I have something very similar but mine actually plays and does not stop the engine.  I am using ASIO as my driver.   Not sure if that makes a difference. Inidentally, is that still the driver of choice for Win 7 ?

Yes you are correct but I cant put it the other way round as the sound is all distorted and pops and crackles.  It was fine in 8.5 all the way back as far as I can remember and even switched project formats when selecting on the Octane.