New X1b Audio Engine Behavior: Sample-rate Mismatch Causes Audio Dropout

I run an E-MU 1820m synced to external ADAT clock from an Alesis QS8 running at 48kHz. Since the clock source is external, SONAR cannot force a clock-rate change to match the project sample rate the way it can with many interfaces using an internal sample clock.
 
In that past, if I inadvertently loaded a 44.1kHz project without changing the clock source to match, SONAR would play the project just fine, but at a proportionally higher tempo and pitch.
 
In X1b, the audio enigne now drops out as soon as a 44.1kHz project is opened.
 
This is actually okay with me - now that I understand it - as it gives an indication that something isn't right before I get too far down the road running a project at the wrong clock rate. But it would be nice of it warned specifically that the cause of the dropout was sample-rate mismatch.
 
Just thought I'd mention this in case anyone else runs into it. And it's an indication that something significant has changed in the audio engine logic, which may have other consequences, good or bad.
 
EDIT: I may file a problem report on this, just to get feedback on whether it's Working As Designed. 

Thanks for the response, Noel. Attempting to restart the audio engine, either directly or by starting playback, results in repeated dropouts. I have to change the external clock rate at the source (QS8) to get the project to play.

So previous versions didn't try to reset the interface to match the project?

Noel,
Sorry to hijack this thread but.....
You seem to fill your coffee right to the top, while using a beautiful score as a coaster.
Have you ever spilled coffee on your score, making it unreadable?