2015/06/12 06:25:33
Alex B.
For now, I can only drink coffee and enjoy the few minutes when SONAR working properly ...

 
2015/06/12 18:09:20
Alex B.
Hey guyz, sorry for multi posts.
This time, this is about some screens i've done, maybe you can see something wrong...





 
 

 
Note that the sound of the reverb (for example) continues to play when SONAR Stope.
The problem certainly comes from VS700R because even plugged alone , Sonar bug. Is there any alternative to plug it maybe ?
2015/06/12 20:05:47
Alex B.
Ok everyone, i have an interesting news.
I tried to connect another interface ( Babyface RME ) to test the system ... who knows ... well it bug the same way ! So the problem is not from the interface but from my new system (either the motherboard or the processor or RAM or the SSD - This is what I changed) . Sonar crash with this system. Someone has already had a problem with some of this material?
SSD : No. Windows does not crash and explorer is fine.
The RAM does not move either. That would be surprising.
And the processor and the motherboards seems to work correctly ... How to explain all this then?
2015/06/13 08:51:18
azslow3
AppHangB1 is not a crash in common sense, it is "stuck". So, processor/RAM/SSD are 99.99% are not the reason.
 
An application can stuck 2 ways:
1) internally (endless loop) in Sonar, any VST, any Control surface plug-in
2) communicating with the system (audio/video/MIDI drivers)
 
I would try to first reproduce the bug with huge ASIO buffers. Note that the reason still can be in Sonar/plug-in in case you no longer has hangs then. Next step is to disable ALL audio devices.
 
If it still stuck, you have to find the problematic software component. Sonar will not help you there, just try to either remove some plug-ins (from the project) or better start from empty project and add components, heavy testing every time. In any case, remove ALL Control surfaces from the list and uncheck all MIDI devices. Final target is to hang Sonar with the smallest possible components/vsts you want to use.
2015/06/13 21:47:05
Alex B.
I will be back to the studio monday. I will try. Thank you azslow for your help :)
2015/06/14 22:38:17
Alex B.
Hi.
I took the opportunity today to update the bios. Then Sonar, I tried to increase the buffer size and ... it is unfortunately always the same. As you advised me I removed all the plugs in Sonar. I worked about 15 minutes, without crashing. I had to leave the studio, but I retry tomorrow. 
2015/06/15 23:52:20
Alex B.
Hello
 
I'm back. I removed all the plug in in Sonar. The Vst list is empty.

I worked 10 minutes today and...still crashing.
The problem come from somewhere else...
 
2015/06/16 18:36:54
Alex B.
Hi everyone !
Great news today !
I found the solution :)
 
In fact , it was a completely stupid thing, I had never noticed it before, but SONAR creates xxx.cwp.assets files. These files are not very usefull because I removed them altogether ALL my projects, and everything is fine now :)
When asked why I did it from the start even after formatting and new project, well that's just my because my normal.cwt template file is a custom made file I had created a moment and the asset file was linked ...
 
So now, everything is fine.
 
I'm really happy I will do a huge scream in my recording booth and make it my hymn.
 
Thank you for your help everyone !
Problem solved !
2016/05/19 19:27:30
Alex B.
I come to you for those who are in the same situation as me : It was (perhaps not only) assets. My master keyboard ( Kawai VPC1 ) was reset due to formatting the machine, it conflicted with my config in a few minutes. To solve the problem , install the VPC editor and click a bottom number ( i put 3). And everything works fine now . I knew it was the piano because I have used it with my laptop and it did also buggy .
 
Bye !
 
NOTA : Win 10 + VS700 (personnal) asio drivers are not stable with huge projects with SONAR. Win 8 is perfect.
12
© 2024 APG vNext Commercial Version 5.1

Use My Existing Forum Account

Use My Social Media Account