ASIO - in relation to Cakewalk Sonar and Scope
Posted: Wed Oct 08, 2008 5:21 am
I have a question (or questions) related to ASIO functionality in general, but also in relation to Sonar, Samplitude, Cubase and whatever other DAW's there are out there.
There is a primary problem for me that has to do with Sonar - especially the most recent version of it - V8. Cakewalk seems to have changed something about the program that is affecting the way I open and close projects.
I have these default projects set up in Scope for various recording and mixing tasks. Usually, the way it works is I open Scope, load a project, then open Sonar, load a default recording template and get to work. When a song is finished I close that project and open a new fresh default project and keep on working. Now I have to completely shut down Sonar when changing projects because the program seems to lose synchronization withe ASIO drivers in Scope. In previous versions I never had to completely shut down Sonar. I would just load up a new recording template or existing project and started working.
I don't have ths problem with Samplitude Pro 10 (which I also have) - it works as expected. I can shut down a project and open a new one without having to completely exit the program first. It seems to maintain connection to the ASIO drivers in Scope. It used to work this way in previous versions of Sonar too.
I guess I'm curious if what sort of behavior I should expect to see in other DAW's. Is there a normal function in regards to what I'm talking about (I hope I'm explaining it properly). I realize my method of working may be different than anyone else's method but maybe someone is doing similar things like me and knows what I'm referring to. I'm trying to figure out if the problem is with the latest version of Sonar or am I doing something that is not kosher?
Thanks
There is a primary problem for me that has to do with Sonar - especially the most recent version of it - V8. Cakewalk seems to have changed something about the program that is affecting the way I open and close projects.
I have these default projects set up in Scope for various recording and mixing tasks. Usually, the way it works is I open Scope, load a project, then open Sonar, load a default recording template and get to work. When a song is finished I close that project and open a new fresh default project and keep on working. Now I have to completely shut down Sonar when changing projects because the program seems to lose synchronization withe ASIO drivers in Scope. In previous versions I never had to completely shut down Sonar. I would just load up a new recording template or existing project and started working.
I don't have ths problem with Samplitude Pro 10 (which I also have) - it works as expected. I can shut down a project and open a new one without having to completely exit the program first. It seems to maintain connection to the ASIO drivers in Scope. It used to work this way in previous versions of Sonar too.
I guess I'm curious if what sort of behavior I should expect to see in other DAW's. Is there a normal function in regards to what I'm talking about (I hope I'm explaining it properly). I realize my method of working may be different than anyone else's method but maybe someone is doing similar things like me and knows what I'm referring to. I'm trying to figure out if the problem is with the latest version of Sonar or am I doing something that is not kosher?
Thanks