Any success with using a Dante Rednet PCIeR card as an interface with sonar? High CPU?

PC desktop win 7 (studio cat)
 
With no issues, I've been using Protools and Cubase with a Dante PCIeR card from Focusrite as well as a Lynx aurora 16 with the Dante Card in it. It works flawlessly in PT and Cubase..... Sonar not so good... at all. My CPU usage (as shown in task manager) goes SKY HIGH. like between 40 and 98% when sonar is open. close sonar and it goes away. I do get audio playback and record but my computer soon gets psychotically HOT due to the insane cpu usage. In other Daws,as well as adobe premiere i am seeing a normal CPU usage of about 4% sometimes 8%. super different from the 98% that sonar causes.
Sonar has been out of commission since the studio upgraded to Dante (which has been AMAZING other than sonars issues) which was about 4 months ago. would love to get sonar up to date like the rest of the Daws out there!
The issue was confirmed by Audinate (dante chip manufacturer) and Focusrite to be on sonars end and im really hoping they can figure this one out. after all sonar is the best.

Did you ever get this resolved?

still no resolution of this issue, even with the new release from Bandlab.

jimoliver
The issue was confirmed by Audinate (dante chip manufacturer) and Focusrite to be on sonars end and im really hoping they can figure this one out. after all sonar is the best.

I really don't see how a Dante issue could be caused at the DAW level. Its just exposed as an ASIO driver right? SONAR doesn't even know its a Dante interface. Just noticing a problem in one host doesn't necessarily mean the issue lies in the host. However if they have "confirmed" it to be a problem in SONAR then I'd be very interested in knowing what they think the issue is and will work with them to resolve it if it indeed is on our end.
We'll need them to send us an interface to test with obviously since we don't have any Dante interfaces to test with.
Feel free to put whoever is concerned on their end in touch with me.

Hi Noel, thank you for your reply!
The problem seems to be with How Cakewalk uses the ASIO driver for the Focusrite Rednet PCIeR Dante card. I have used Protools 12, Cubase 9, Studio one 3 artist, Ableton live 8, Reaper 5, Adobe Audition CC, Adobe Premier, and Sadly, to my surprise and dismay, SONAR/Cakewalk has been the only daw to respond this way. The CPU gets driven to seriously freaky levels (40-100%) and often will lock up the whole computer when setting I/O in sonar. Seen this happen on multiple, very nice computers yet not a trace of an issue with protools or others. I am not a fan of PT and I've had to use it and Reaper for tracking for a year (since switching the  production studio to Dante PCIe). For editing i still LOVE and use Sonar/Cakewalk with Dante Virtual Soundcard (software made by Audinate that uses a computers existing ethernet port for digital audio traffic rather than the dedicated/ advanced PCIe card). Though the latency performance is marginal with DVS it does work with cakewalk and theoretically the ASIO driver is either similar or identical which is what confuses everyone especially Audinate! Clearly there is someone out there that can figure this out considering i have read reports that the Odeus driver wrapper called ASIO LINK PRO did provide a complicated workaround that did allow the use of a PCIE card without the CPU issue. It seems like its no longer a viable approach at this time due to their site getting badly hacked. The specifics of the performance quality were never determined before the software became unavailable. Only a trial version was tested to my knowledge.
 
Back when Cakewalk was owned by Gibson Focusrite did offer to connect with Cakewalk to get to the bottom of this but do to the impending transition of Cakewalk there was little to no effort made by cakewalk to get in touch with Focusrite. Perhaps now that Cakewalk is in good hands again i can reconnect with Focusrite and see if they will be able to offer an interface and card. Not sure they will based on the cost of the units. Interfaces are like $4,000. and the PCIeR card is $1000 and you also need to setup a configurable network switch (cisco SG 300 if i remember right) with with proper QOS settings and disable EEE. 
 
I know its a pain to track this down but Cakewalk by Bandlab deservers to stand among the rest and offer compatibility with this truly superior means of Recording.
 
I use a Lynx aurora 16 DNT (dante) with the Rednet PCIeR card in a Studio Cat Computer, i believe you're familiar ;) running win 10 pro 64 bit. I have also verified with Focusrite and Audinate that my motherboard, GPU and overall specs of the computer are compatible with Rednet/Dante and again the only problem i have running other DAWS with my setup is that they aren't Cakewalk.
 
Thanks again for your help and i can't even begin to tell you how happy i am that Cakewalk still exists and has a chance to be polished!
 
- Jacy oliver
 

Just a follow up that this issue has been resolved. I did several troubleshooting sessions with Jacy remotely and was able to find the root cause of the issue which is that the Audinate driver doesnt respond well to specific ASIO call sequence which was resulting in excessive threads being created by the ASIO driver leading to CPU drain.
I have also reported this to the Audinate engineers and they are also investigating it from their end. ASIO is notorious for being a loose specification and this results in numerous incompatibilities due to different interpretations of state management.
 
I was able to work around this from our code and after we do more regression testing we should be able to release the fix in our next update. Jacy has already verified that the fix works on his system. I'm glad that this is resolved and Dante users will be able to use CbB. Performance is actually very good after this fix and Jacy reported better CPU performance that ProTools on the same system with similar project load. Thanks Jacy for hanging in there and allowing me to troubleshoot your PC remotely. It was an interesting issue to debug :)