AFTER X1B - My audio device keeps getting disconnected RME FF800

This did not happen BEFORE the update.
 
I have only had the update on for 30 mins and I have had my audio device disconnect on 3 different projects. Not only that, I get the error about no midi devices yet they are defined.
 
What irritates me most is the disconnect of the audio device. Something in X1B is causing this to happen.

Guitarmech111


This did not happen BEFORE the update.
 
I have only had the update on for 30 mins and I have had my audio device disconnect on 3 different projects. Not only that, I get the error about no midi devices yet they are defined.
 
What irritates me most is the disconnect of the audio device. Something in X1B is causing this to happen.

I have a FF 400, and I've been getting this for the last month on X1a for both audio and MIDI.  I'm using the latest driver, and I'm otherwise stable.  I read this morning on the RME forum that they are pushing this off on Sonar.  It doesn't happen on every project, so I'm wondering if there's a certain plug in that's responsible.  I'll just have to take notes. 

crap!!!! X1B is freakin useless to me if my audio card can't keep attached!!! I just got 3 additional disconnects during playback of one project.

I find it hard to believe that this was even tested with a FF800 or FF400.

Why don't you try calling customer support? Unfortunately things go bad at times, and with that comes the need to troubleshoot and spend time with the problem. I would call customer service asap if I was you and then go from there.

I have BEEN ON THE PHONE, on hold,  waiting TO TALK TO THEM SINCE before I posted the thread. I have also opened up a trouble report. 

There is NO FREAKIN WAY X1B WAS TESTED with any RME FF800 or FF400 cards. I expect better quality after installing an update. I expect that SONAR X1B would be able to keep an audio card attached so playback of a SIMPLE song with 2 audio tracks and SD2 could work.

Are you loading projects at non default sample rates? If so SONAR will now switch the device to the new sample rate. When that happens some devices throw a spurious Windows message indicating that they were unloaded (when in fact they were just reset by SONAR to the new sample rate). The message can be ignored for such devices and it doesn't really mean that the device was disconnected. All SONAR is doing is reporting when a device signals disconnection or connection and allows you to reload the engine to see the new device list.

Hi Noel, It looks like this current project is 16 and 32 bit audio with 44.1 on both. For some reason, they each got recorded at different bit depths. I never got the error dialog before X1B. I am able to reproduce this now with some regularity on this single project. Just hitting play eventually leads to that dialog. I would not like that to keep coming up when in front of paying folk.

Try swapping out interface cables. I had an intermittent USB cable once, and the havoc that caused drove me nuts.

A bad cable is very likely NOT the problem, but it's so easy to check it's worth checking.

It looks like this current project is 16 and 32 bit audio with 44.1 on both.

 
What is the default sample rate set in Options Audio? We definitely had RME users testing X1B and nobody saw this particular issue. I'm not sure why this would be happening only on your interface specifically. The only thing I can think of is for some reason the device is asking SONAR to reset it every time you press play and then sending the notification when we respond to the reset request.
 
Also please check that you have "MinimizeDriverStateChanges=1" in your audio configuration file.

Guitarmech111


It looks like this current project is 16 and 32 bit audio with 44.1 on both. For some reason, they each got recorded at different bit depths. .

You need to fire the guy that let THAT happen. 

I was able to reproduce it pretty statically with one of my projects. If you run into it, change the default sample rate for new projects to match your current projects sample rate. That worked for me.

Noel Borthwick [Cakewalk
]

It looks like this current project is 16 and 32 bit audio with 44.1 on both.

 
What is the default sample rate set in Options Audio? We definitely had RME users testing X1B and nobody saw this particular issue. I'm not sure why this would be happening only on your interface specifically. The only thing I can think of is for some reason the device is asking SONAR to reset it every time you press play and then sending the notification when we respond to the reset request.
 
Also please check that you have "MinimizeDriverStateChanges=1" in your audio configuration file.

Noel, is that the official fix or a workaround?

From what I have experienced, if the value for new projects sample rate does not match the actual sample rate of a current project, you will see that dialog.

I wonder if the bakers will give us a final account of what is really the issue.

Guitarmech111


From what I have experienced, if the value for new projects sample rate does not match the actual sample rate of a current project, you will see that dialog.

I wonder if the bakers will give us a final account of what is really the issue.

I'm getting this message although my bit and sample rate hasn't changed for years.  RME offers no help at all, but once I reestablish the connection, all is well.

mech, X1b did add a 'feature' bug fix that was supposed to address different ASIO settings and such so it should, in theory act differently than X1 and X1a and that may be what you're up against and it could explain the differences between this new release and previous X1 versions.

"ASIO Improvements have been made to the way SONAR handles dynamic sample rate changes with ASIO devices. If an ASIO driver supports changing its sample rate dynamically, it will be possible to load SONAR projects at different sample rates. SONAR will automatically switch the device sample rate when playback is started without requiring a restart of the application."

I guess 'improvements' is a relative term eh?