hi everyone!
 
some update on performance:
 
* installed new driver for sound card (TC Electronic Konnekt 6). its a release candidate for win10 now
* with playing latency settings it now seems to be that no dropouts occur (at least so noticable as before)
 
however now one of projects is always failed to load:
* Sonar hangs when opening the project
* memory is allocated (3+ GB)
* CPU is still used (19-20%)
 
but nothing happens :(
 
I've tried to open it in safe mode.
the result is pretty much the same, only
memory usage is very small and CPU usage us up to 8% instead.
 
what can be done here?
how to fix/repair project?

*the sonar hangs somewhere after "opening the project" status line in the UI is shown and then hidden

biozel
hi everyone!
 
some update on performance:
 
* installed new driver for sound card (TC Electronic Konnekt 6). its a release candidate for win10 now
* with playing latency settings it now seems to be that no dropouts occur (at least so noticable as before)
 
however now one of projects is always failed to load:
* Sonar hangs when opening the project
* memory is allocated (3+ GB)
* CPU is still used (19-20%)
 
but nothing happens :(
 
I've tried to open it in safe mode.
the result is pretty much the same, only
memory usage is very small and CPU usage us up to 8% instead.
 
what can be done here?
how to fix/repair project?

after you opened in safe mode, did you remove any of the plugins?  the main reason safe mode exists is to be able to open the project with minimal resource usage and this enables you to "find the culprit" which is causing the problem.  most of the time there will be a third party plugin (either VST or VSTi) which is causing the "hang up"
 
try opening in safe mode, deleting a softsynth or a plugin (I'd definitely start with non-sonar or non-included plugins), save it under a different name, open it in regular mode and see if it still hangs up.  if it does, try another one and continue the process until you determine which one is causing your problem.

Beagle
 
after you opened in safe mode, did you remove any of the plugins?  the main reason safe mode exists is to be able to open the project with minimal resource usage and this enables you to "find the culprit" which is causing the problem.  most of the time there will be a third party plugin (either VST or VSTi) which is causing the "hang up"
 
try opening in safe mode, deleting a softsynth or a plugin (I'd definitely start with non-sonar or non-included plugins), save it under a different name, open it in regular mode and see if it still hangs up.  if it does, try another one and continue the process until you determine which one is causing your problem.

the problem is that Sonar hangs before showing project window.
so i have no possibility to turn off or remove something.
 
when opening project in Safe mode it asks to disable plugins
(either one by one, or all, i tried both ways). after that it hangs
just as in usual mode.

biozel

Beagle
 
after you opened in safe mode, did you remove any of the plugins?  the main reason safe mode exists is to be able to open the project with minimal resource usage and this enables you to "find the culprit" which is causing the problem.  most of the time there will be a third party plugin (either VST or VSTi) which is causing the "hang up"
 
try opening in safe mode, deleting a softsynth or a plugin (I'd definitely start with non-sonar or non-included plugins), save it under a different name, open it in regular mode and see if it still hangs up.  if it does, try another one and continue the process until you determine which one is causing your problem.

the problem is that Sonar hangs before showing project window.
so i have no possibility to turn off or remove something.

did it do this before you installed the "beta release" drivers for the Konnekt 6?  if not, uninstall them.  it's likely causing the issue.

 
when opening project in Safe mode it asks to disable plugins
(either one by one, or all, i tried both ways). after that it hangs
just as in usual mode.

even if you disable all of them?

Beagle
did it do this before you installed the "beta release" drivers for the Konnekt 6?  if not, uninstall them.  it's likely causing the issue.
 

 
this also does not help.
the behavior is the same :-(
 

Beagle
 even if you disable all of them?

yes.

I would suggest you try to troubleshoot in a more methodical manner and in a more controlled environment.  For example, start up your computer and disable pretty much everything (printer drivers, wireless internet drivers, etc).  Open Sonar and start a new project using some simple .wav files.  Then you will be more able to see if something is causing a spike in cpu usage.  In your original example, I think you have too many variables for troubleshooting.
 
Also, the fact that you are using ASIO4All and that there's no Windows 10 driver for your soundcard yet is highly suggestive that it's a driver / hardware issue.
 
Also, in your original post, it's unclear what your baseline CPU usage is before Sonar is open?  Maybe there's another program that's taking a lot of CPU power that's not related to SONAR.

biozel
CONCLUSION: when not hitting Play button even once i have Sonar taking 60% of CPU (this number varies of cause)
for the project and lots of dropouts (while i made items 1-14 i had about 30 dropouts).
i believe this is not normal.
 
----------------------- OTHER ISSUES ------------------------------------
* when turning on/off plugins in Console view audio dropouts occur
from time to time. note that i'm talking about situation when
nothing is played - i'm just enabling/disabling plugins.
interesting thing: when dropout occurs the CPU usage goes down to 1-2% or so.
in other words it becomes as expected
one more interesting thing: if after drop out you switch to some other application
and then back to Sonar, CPU usage starts increasing again and in couple of seconds
come to the state that was before drop out
* audio dropouts also occur when not playing but doing some
trivial actions: saving project, scrolling console view

Also I'm not clear what you mean by "dropouts" above.  Can you be more specific about what these "dropouts" are?  Typically it would mean that either the audio is glitching when you're running playback, or that you're trying to play an instrument in real-time and it's glitching.  But above you say that as you go through each step, you get dropouts without the transport running, which I'm not understanding.

rlared
I would suggest you try to troubleshoot in a more methodical manner and in a more controlled environment.  For example, start up your computer and disable pretty much everything (printer drivers, wireless internet drivers, etc).  Open Sonar and start a new project using some simple .wav files.  Then you will be more able to see if something is causing a spike in cpu usage.  In your original example, I think you have too many variables for troubleshooting.
 
Also, the fact that you are using ASIO4All and that there's no Windows 10 driver for your soundcard yet is highly suggestive that it's a driver / hardware issue.
 
Also, in your original post, it's unclear what your baseline CPU usage is before Sonar is open?  Maybe there's another program that's taking a lot of CPU power that's not related to SONAR.

i don't use asio4all.
as for project opening problem, the problem is that only one project is not open (Sonar goes to some kind of infinite loop always doing something but never finished). other projects can be successfully opened both in usual and safe modes.
 
i will try to run Sonar while disabling everything like wi-fi today.
however i don't think that problem is in windows.

rlared

biozel
CONCLUSION: when not hitting Play button even once i have Sonar taking 60% of CPU (this number varies of cause)
for the project and lots of dropouts (while i made items 1-14 i had about 30 dropouts).
i believe this is not normal.
 
----------------------- OTHER ISSUES ------------------------------------
* when turning on/off plugins in Console view audio dropouts occur
from time to time. note that i'm talking about situation when
nothing is played - i'm just enabling/disabling plugins.
interesting thing: when dropout occurs the CPU usage goes down to 1-2% or so.
in other words it becomes as expected
one more interesting thing: if after drop out you switch to some other application
and then back to Sonar, CPU usage starts increasing again and in couple of seconds
come to the state that was before drop out
* audio dropouts also occur when not playing but doing some
trivial actions: saving project, scrolling console view

Also I'm not clear what you mean by "dropouts" above.  Can you be more specific about what these "dropouts" are?  Typically it would mean that either the audio is glitching when you're running playback, or that you're trying to play an instrument in real-time and it's glitching.  But above you say that as you go through each step, you get dropouts without the transport running, which I'm not understanding.

well, dropouts are situation when Sonar shows popup message about audio engine dropout