KWILD....the problem it's still there.

OK, thanks for the info.
 
One thing I do notice is the CPU meter in Sonar goes crazy when doing anything Rewire related.. CPU meter in Reason is fine..
 
Will put aside some time on the weekend to get on to Cakewalk Support.
 

plainfaced
 
One thing I do notice is the CPU meter in Sonar goes crazy when doing anything Rewire related.. CPU meter in Reason is fine..
 
Will put aside some time on the weekend to get on to Cakewalk Support.
 

Same here,CPU goes crazy!
 

Anyone from Cakewalk chime in? @Anderton? - Before I submit a  Problem Report..
 
Not sure why im trying to tag people.. This is not a Slack channel plainfaced :(

If you have more than one ReWire library dll in your system it can go crazy. When I had problems I did a search on ReWire.dll and found four different ones. I eliminated all but the most recent and everything has worked perfectly ever since, and not just with SONAR.

Also remember that although ReWire itself takes almost no CPU, your computer has to be able to run two substantial programs simultaneously. Although you don't give your computer specs, you may have to resign yourself to increasing latency and because Reason's samplers don't stream from disk, you may not have enough RAM if you're running several instances of the NN-XT.

Really appreciate you input Craig.
 
The ReWire.dll is an interesting one.. I'll be sure to have a look tonight..
 
Apologies for not providing the Specs.. Ive only just got back into the Windows DAW world after being on OSX for so long.. In 2007 my PC could run Rewire projects 3 times as big, so wasnt sure why in 2016 things would have got worse.. I suppose Applications get more taxing on CPU and RAM, as both CPU and RAM capability increases..
 
Im running -
OS: Windows 10
CPU: Intel Core i7 4790
RAM: 8GB Corsair Vengeance Pro
OS/Application drive: 120GB SSD
Sonar Project folder drive: 750GB Hybrid drive
 
Im actually thinking now, that Project Folder drive might be a little slow.. Although Sonar/Reason was failing on playback - So I would assume that its only reading from the OS/Application drive?
 
Might think about upping my RAM too..
 
I would still question why adding 3 Reason instruments (not sample based) cause Sonar CPU usage to spike on an Intel Core i7 4790?
 

As amazing as it may seem, 8 GB can be kinda marginal these days. I have 32 GB, well worth the investment.

So I had a little bit more success tonight.
 
The issue of some Reason Instruments playing back at twice the speed: For now, solved. I stopped using Mix Channels in reason, and simply threw each instrument into a Combinator.. Then routed the Combinators to their own audio channel.
 
The Issue of CPU load/Audio chugging is... still an issue: While raising the buffer helps a little, obviously this doesn't help in real world when trying to record.
 
I did better performance a little by removing some modules in the Pro channel of a Bus I created (remembering I only have two audio, two midi channels and a single Bus in Sonar).. I found the CPU load dramatically decrease when I removed two of the Style Dial FX.
 
Why a Core i7 4790 would drown with a few Pro Channel modules? I'm not sure... I have ordered more RAM.. However throughout these tests RAM usage is only ever at 30%..

Man,the extra ram don't solve nothing.It's a bad developement of rewire with Sonar Platinum.To be honest i remember having the problem with the latest versions of Sonar pre-platinum too,but now i don't remember.
They must investigate about that strange behaviors on Sonar,the problem is there more than one year for sure,im really skeptical on how they do their betatest,sorry but i loose so much time behind that and other crazy problems that im really upset about!
Do you try to disconnect cables in reason,and connect to an audio output to another and then doing the same in sonar and then back to when it was?I've fix the problem doing that,several times,let it a try.

KWILD
Do you try to disconnect cables in reason,and connect to an audio output to another and then doing the same in sonar and then back to when it was?I've fix the problem doing that,several times,let it a try.

 
Tried that.. Didn't solve anything.
 
I'm back now with the double speed issue.. So ive given up..
 
Well not given up.. Ive resorted to routing ALL reason devices to the Master Section and then to Audio 1+2 - And only having a Single Reason Audio track in Sonar...
 
This limits me to writing all my instrument parts - Then bouncing each track to a separate Audio track.. Then mixing from there.. Not ideal, but my PC handles the load with this setup with ease.