• SONAR
  • X3 Pro - RME FF800 - Device Disconnecting?? (p.4)
2014/03/04 22:16:49
choinga
Guitarmech111
I have gotten that error with my RME FF800 using FW and with my RME UFX using USB. I think Cakewalk needs to get with RME again and see if they can hash this thing out.




I agree - at this point I'm not sure who to dump.  That said, I downloaded a trial of the PreSonus StudioOne and had weird drops using my FF800 with that too...no error messages like Sonar gives but no idea what the culprit is.
 
At this point I've disabled everything on my machine.  Defender is turned off, internet is disabled, shut everything off on 'startup' except the RME drivers that show up in the tray, power setting is high performance and nothing will turn off or go into stand-by...  Running another test now to see if that does anything but I'm afraid it's all in vain at this point - someone...Sonar or RME has some issues that need to get worked out.
2014/03/04 22:29:07
Lynn
choinga
Another issue I have is that anytime I use or enable a 64 bit engine (on export for example or in the device preferences to use the 64 bit engine) I get this weird high pitch buzzing in the background.  As soon as I uncheck the box - it goes away.
 
Thanks in advance!


Are you using X3D?  That's supposed to solve the problem with the 64 bit double precision engine.  I feel for you because I get these messages, too, and though they don't stop production, they're annoying.
2014/03/04 22:30:51
choinga
yeah, brand new install as of this evening.  Win8.1, X3d, latest RME drivers.
 
I was having weird buzzing problems with the 64 bit precision engine checkbox on previously (and when exporting with 64 bit checkbox enabled) but now I can turn that on without any problems.  But, still having the RME error.
 
I've been running a loop with everything shut down (see previous post) and so far so good...been running about 8 minutes now without stopping.
2014/03/04 23:11:50
choinga
...well, it was looking pretty good there for awhile.  Had a loop running for about 20 minutes without the audio dropping out...but alas, eventually it did.  
 
I literally have everything turned off on my machine.  Windows Defender disabled/service shut off, internet adapter disabled, all the Intel tools that get installed/video tool that all run in the tray I disabled them in task manager/startup.  Literally the only things running in task manager were system stuff that I can't do anything with, sonar and RME.
 
Power management set to high perf, no screen saver, don't turn the disks off.  WU done - latest 8.1 drivers/updates installed.  Sonar is set to not share the driver with anything else so not sure what else could be 'stealing' it.  I did notice when switching cables around that the error I see randomly is exactly the same error I see when I unplug the FW cable.  So, it seems that in some way Sonar or RME see's a physical disconnect in some way?  
 
I don't know what else to do, if anything.  Clearly something is wrong here.  I pointed the RME support guy (Jeff - seems like he's the only one in the US?) to this thread when I emailed him so if/when he ever returns my email/call he has some insight into what's going on and that there are multiple others dealing with the same issue.
 
Certainly if I or we ever resolve this I'll share back on this thread.  My guess is it's a driver issue.  The latest firmware I see for the FF800 is pretty old but the driver is very new - as in a few weeks old.  So, maybe they fixed a few things and broke some others with this latest driver release...who knows.
2014/03/04 23:17:43
Guitarmech111
I am not sharing my drivers either.  I have no sound scheme set for the computer also. The devices are defined to windows but the on board sound card is default for all audio recording and playback.
2014/03/05 01:38:44
Splat
Please consult your windows event viewer for errors.
Thanks.
2014/03/05 02:53:53
choinga
no event viewer errors.  This is a brand new install so not much to weed through...nothing on the warning or error side that would even remotely be in the realm of this issue.
 
I've got a loop setup to run using PreSonus StudioOne and I'm about to go to bed and we'll see if it's still going in the morning when I wake up.  I've seen it die a couple times (had it setup briefly before the re install) but the transport just stops...no error message or windows popup like Sonar does and I had to completely restart the app to get anything to come back up.  We'll see...
 
I am using a Syba SD-PEX30009 PCIe-to-FireWire adapter card right now - just bought a SIIG-NN-FW0012-S1-Firewire-800 and going to see if that makes any difference.  I was reading through UA's Apollo's site tonight thinking of changing (still sucky Thunderbird support for Windows...) and saw they are recommending this SIIG card or the Sonnex card and are not testing with the Syba anymore.  So, figured I'd try that and see if it fixes anything...
2014/03/05 07:23:50
Zig
Late to the party here and of no practical use except to testify occasional but annoying replications of exactly the same as the OP: (Motu 4Pre firewire on a TI chipset PCIe with latest 64-bit drivers, W7Pro64(SP1), Sonar x3 Producer 64bit(d),.
    My present personal experience is that I'm more likely to trigger the FW interface's thowing-in of its towel by periods of cycling through Dimension Pro progs. I've no idea if this of universal significance.
 I've presently got a headscratching list of other odd behaviours(now including my own as well as those of the trio of X3, W7, and the Motu )...thus, my present, though head-in-a-bucket "workaround", is plenty of saves, close X3 when the Motu quits, turn off Motu, turn on Motu, fire up X3 and rock+roll.
  (Turning off my firewire device whilst  Sonar is running, even when X3 informs me my device is no longer available, then turning the FW on again, has no effect).
 I have little knowledge and even less time, so as to presently allow me to do an Enterprise-Picardian level 3 diagnostic of all variables in W7, X3 and my Motu FW...I'm merely chipping in to say that a) I do feel your pain, as my experience tallies with yours; b) my feeling is that this is not an RME-specific error; c)my wild, wild and supernatural guess is that there is still some default W7 desire to attempt to wrestle back default audio control from a firewire device to the onboard audio...but of course this doesn't explain random behaviour(in my case) of soundcard hari-kiri whenever I get crazy with Dimentia Pro.
2014/03/05 07:37:20
Guitarmech111
Well, looks like it is not only an RME issue. The problem has gone on for a while now. I am surprised that no one has reported a bug number yet.
 
 
2014/03/05 07:42:09
Guitarmech111
Noel Borthwick [Cakewalk]
SONAR listens to device change notification messages from Windows. These indicate when audio devices are added or removed from the system. For device removal specifically we listed to the DBT_DEVICEREMOVECOMPLETE event. If this is being triggered, it means that something caused the low level WDM driver to send this event to Windows. Most typically this could be caused by a faulty connector (USB or firewire) or a bad controller. If its happening on a good system then it could be a fault in the driver that is generating this message.
What happens if you ignore the message - does the audio continue to work? If not then it was really disconnected from the system somehow...


My system goes on without issue when I hit NO
© 2026 APG vNext Commercial Version 5.1

Use My Existing Forum Account

Use My Social Media Account