Looks like RME and Cakewalk were talking about the delayed recording arm issue and not a performance issue. Cakewalk is making a fix for that delayed arm issue from what I understand.
 
Now how are we going to get the performance issue with RME devices handled?

"Cakewalk is making a fix for that delayed arm issue from what I understand."
 
Source or did you just make this up?
 
As I said this is a absolute classic drivers issue, and it's not the first time bugged drivers have done this and it probably will not be the last.
 
OK want evidence? Do you notice any similarities here which turned out to be buggy drivers?
Notice I wasn't initially convinced either... Not until post #68 (well in fact later than that even). So if I took this long to convince I suppose you will never be convinced ;)
http://forum.cakewalk.com/SOLVED-FOCUSRITE-BUG-Record-arm-buttons-are-slow-to-respond-m2391347.aspx
 
That is my compelling evidence from just over a couple of years ago, the comparison here is uncanny, please supply yours...! :)
Ask yourself why my drivers work and yours don't ;)... and once upon a time your drivers may have worked and mine didn't.... and the symptoms here are almost identical.
 
DISCLAIMER - I still maintain an open mind as no official statement has been made from either party (we are just going on hearsay), all I can do is present what I perceive to be a smoking gun drivers issue.. Until Cake or RME officially confirms this anything anybody says (inc me) should be taken with a pinch of salt.

I got that info directly from RME on their forum.
 
Why would I make anything up? I do not need to hype myself or lie to impress anyone here. I resent that you even suggested that Alex.

CakeAlexS
"Cakewalk is making a fix for that delayed arm issue from what I understand."
 
Source or did you just make this up?
 
As I said this is a absolute classic drivers issue, and it's not the first time bugged drivers have done this and it probably will not be the last.
 
OK want evidence? Do you notice any similarities here which turned out to be buggy drivers?
Notice I wasn't initially convinced either... Not until post #68 (well in fact later than that even). So if I took this long to convince I suppose you will never be convinced ;)
http://forum.cakewalk.com/SOLVED-FOCUSRITE-BUG-Record-arm-buttons-are-slow-to-respond-m2391347.aspx
 
That is my compelling evidence from just over a couple of years ago, the comparison here is uncanny, please supply yours...! :)
Ask yourself why my drivers work and yours don't ;)... and once upon a time your drivers may have worked and mine didn't.... and the symptoms here are almost identical.
 
DISCLAIMER - I still maintain an open mind as no official statement has been made from either party (we are just going on hearsay), all I can do is present what I perceive to be a smoking gun drivers issue.. Until Cake or RME officially confirms this anything anybody says (inc me) should be taken with a pinch of salt.

look at the RME forum and you will see.

Like I say I reserve the right to be wrong. I apologise for being abrupt.

Do you have a specific link and ideally post number please? I am not familiar with RME forums and I do not want to get quotes muddled. Or just paste the quote here with reference.

If there is indeed a bug I would hope Cake to comment about it at this point so me and others stop speculating (in short shut me up!). If indeed it is true that would be a bit of a bombshell as other drivers may be effected. I can't see for the life of me why other drivers work differently unless they all coded workarounds around the problem. In short "we have a right to know" as Tom Waits would say :) Is this baloney or well founded?

The truth may very well be something none of us are foreseeing.

Thanks.

Anyway, here is the forum post:
http://www.rme-audio.de/forum/viewtopic.php?id=19003
 

Guitarmech111
I got that info directly from RME on their forum.
 
Why would I make anything up? I do not need to hype myself or lie to impress anyone here. I resent that you even suggested that Alex.

I agree. Alex I appreciate your efforts on this forum to troubleshoot and document issues, but your self-appointed role as "forum police" goes too far at times. Feel free to not engage in this discussion if you find the information too unconfirmed for your high standards.

RME just confirmed this on their public forum yesterday. See post 13 at the linked thread below. Prior to this it was confirmed to me in a private email. I chose not to copy and paste the exact quote here in a public forum because it was *private* and I felt this would cross a line and be rude. We should encourage other users to do research and share info, not accuse them of making things up.

http://www.rme-audio.de/f../viewtopic.php?id=19003

Enough about that.

I am curious if others have tried what works for me - changing from ASIO to Wdm drivers, selecting the new Wdm- based outputs (this option will pop up automatically), then switching back to ASIO and selecting ASIO-based outputs. I have no idea why this works, but it does 100% of the time.

I should also note that the driver switching workaround mentioned above cures both the slow arming and the glitchy audio on my system. So despite RME's statement that the fix CW developed (and hopefully present in x3e) is only for slow arming and should not affect any performance issues, I hold out hope that the fix will address both.

neirbod
I am curious if others have tried what works for me - changing from ASIO to Wdm drivers, selecting the new Wdm- based outputs (this option will pop up automatically), then switching back to ASIO and selecting ASIO-based outputs. I have no idea why this works, but it does 100% of the time.

It would be nice to get a bakers thoughts on this procedure. I have not done that.
 
It was mentioned a while back, in another issue, that a particular setting needed to be changed and then immediately changed back so that SONAR would enable that parm as the user specified and not what was migrated or default.
curious...

Sorry Neighbod but I'm not telling people how to post and I have a right to an opinion as do you but you seem to be telling me what to do. BTW I should have been quoted as well if you were going to quote a response, I said "Source or did you just make this up?". I did not say "You are making things up", and it turns out in the end there (eventually) was a source. You are all trying to make it appear worse than it actually was by turning my question into some sort of statement. I also apologised for being abrupt (which I was).
 
> Thank you Matthias, I was confirming because we have SONAR fanboys that have trouble admitting SONAR has flaws.
 
Calling me a fanboy is another forum Conley is sort of weird to be honest (Really???? I have trouble admitting Sonar has flaws? There's plenty of things you can say about me but that doesn't hold any ground whatsoever). What I do have is trouble seeing an issue without the full evidence to back it up, I have a rather scientific approach here which may seem a little over the top to you but sometimes you do need it in a thread that seems to make a lot of assumptions to maintain balance. I'm sorry my immediate apology wasn't good enough for you and I shall apologise again.... I apologise. Now...
 
> Please correct me if I am wrong. The fix, coded by cakewalk, was to address the long time it took for tracks to actually arm and has not much to do with the performance issue SONAR users are having with SONAR X3 and the RME interfaces.
 
This seems to imply that other users who are not using RME interfaces are having delay issues when arming and RME seems to be nodding along to this statement. But I haven't seen any recent evidence of this, is there any sources to show this as an issue away from RME interfaces?
 
Again DISCLAIMER (as I've said all along), these are of course just my opinions, not Cake's or RME's. I will be happy to be proven wrong if indeed that is the case, I do not see this as a point scoring exercise about who is right or wrong, chances are I will fall flat on my face, I just want to get down to the facts here.
 
Could Cakewalk please confirm that there will be a bugfix? Like said if this is indeed true an issue with ASIO/transport is an extremely serious issue I would have thought (although most of us don't see the symptoms it seems). At least we all agree we want to hear from Cake.
 
Thanks...