Hi Alexey,
Thank you for posting ,though I am not able to open the files you mentionned ( I am on an I pad at this time) I think there is some common issue with what I am confronted with,but....
I have the chance to have Noel looking at the problem and I will wait his return to make up my mind.
By the way,I would like to thank again Noel in perticular and the Cakewalk brand in general because in my sense,having a recognised professionnal taking care of the case of a customer who posted a topic in the generic forum of the compagny is amazing.
Most part of the time you have to pay for a professionnal to have a ( sometime quick) look at your case, here you do not pay and the professionnal ( Noel) makes the first step and on a sunday evening and I'm sure the look will be sharp.
Hats off to the level of implication that is met here
All the best.
Olivier

Vilovilo
Hi Alexey,
Thank you for posting ,though I am not able to open the files you mentionned ( I am on an I pad at this time) I think there is some common issue with what I am confronted with,but....
I have the chance to have Noel looking at the problem and I will wait his return to make up my mind.
By the way,I would like to thank again Noel in perticular and the Cakewalk brand in general because in my sense,having a recognised professionnal taking care of the case of a customer who posted a topic in the generic forum of the compagny is amazing.
Most part of the time you have to pay for a professionnal to have a ( sometime quick) look at your case, here you do not pay and the professionnal ( Noel) makes the first step and on a sunday evening and I'm sure the look will be sharp.
Hats off to the level of implication that is met here
All the best.
Olivier

Exactly.  +1000 to the staff at Cakewalk

It would be very helpful to have a "Tool" within Sonar that could "Check Project for Errors".  I suspected that my memory (overwrite) was causing "start/stop" screen freezes, but not until replacing half the hardware in my computer at significant cost.  Third Party plugins also seem to be buggy, including Waves TG12345.  I am running three projects that all contain midi, audio, and softsynths, and they are all presenting problems.  It could be that the project itself has become corrupted...due to the insertion and then removal of plugins.  If I had a tool to diagnose the project I could at least know where to start fixing...or just rebuild the project if the tool indicates too many corruptions.

Thedoccal
It would be very helpful to have a "Tool" within Sonar that could "Check Project for Errors".  I suspected that my memory (overwrite) was causing "start/stop" screen freezes, but not until replacing half the hardware in my computer at significant cost.  Third Party plugins also seem to be buggy, including Waves TG12345.  I am running three projects that all contain midi, audio, and softsynths, and they are all presenting problems.  It could be that the project itself has become corrupted...due to the insertion and then removal of plugins.  If I had a tool to diagnose the project I could at least know where to start fixing...or just rebuild the project if the tool indicates too many corruptions.

If you are having issues with TG12345, you may have deeper system issues. I've used that Waves plugin many times without any issues. Waves plugins are probably some of the most used on the planet and with that exposure get lots of testing. I'm not saying there are no bugs in Waves products, only that if you are running into a problem, so should many others using the same plugin.Have you contacted Waves support?
 
The same goes for project corruption. I've never had a project get corrupted. Ever. However, I also only insert and remove plugins with the transport stopped. I know you spent time and money swapping PC parts, but have you run memory and CPU testing utilities on your rig?
 
While I agree that a tool to validate a project might be useful, it would only be safe to trust it if run on a machine other than the machine giving you problems.
 
Regards,
Dan

Thedoccal
It would be very helpful to have a "Tool" within Sonar that could "Check Project for Errors".  I suspected that my memory (overwrite) was causing "start/stop" screen freezes, but not until replacing half the hardware in my computer at significant cost.  Third Party plugins also seem to be buggy, including Waves TG12345.  I am running three projects that all contain midi, audio, and softsynths, and they are all presenting problems.  It could be that the project itself has become corrupted...due to the insertion and then removal of plugins.  If I had a tool to diagnose the project I could at least know where to start fixing...or just rebuild the project if the tool indicates too many corruptions.

The "tool" is built in in a sense. When we load projects we automatically check for common errors and fix them automatically. However loading a project in safe mode can also fix some other kinds of errors. In this case however I don't think this is specifically project corruption. Most likely some plugin related incompatibility.

dcumpian
The same goes for project corruption. I've never had a project get corrupted. Ever. However, I also only insert and remove plugins with the transport stopped.

One corrupted project was linked before is this thread... you can check yourself that it is really corrupted
 
Small example: I hit one severe bug with my own AZ Lua plug-in yesterday. With this plug-in in FX chain, if I "swipe" by mouse over Virtual Keyboard in Sonar (and only in this case... not when I swipe in PRV or on MIDI controller), after a while associated VSTi stop producing any sound (sometimes followed by Sonar crash, sometime not, looks like a memory corruption...). Even in case I then remove AZ Lua from FX, save project and restart Sonar, the VSTi keep silence after the project is loaded again.
 
I am going to have an interesting evening to find why that happens, but the point is different. It is possible to produce something which is kept in the Project File and continue coursing problems. May be in my case I will find how to "fix" the project without rebuilding it, but with linked before project I have failed to do so (note that the linked project is effectively "empty"). But assuming quite specific way to reproduce my bug (I am using that plug-in without problems for a while), it could take months till I hit it in real live. I mean it is possible to do something no one else is usually doing and so have troubles while other can be "happy" and never hit the same.

Alexey, you should track down that developer and badger them till they fix it, and don't accept "All software has bugs!" as an answer

azslow3

dcumpian
The same goes for project corruption. I've never had a project get corrupted. Ever. However, I also only insert and remove plugins with the transport stopped.

One corrupted project was linked before is this thread... you can check yourself that it is really corrupted
 
Small example: I hit one severe bug with my own AZ Lua plug-in yesterday. With this plug-in in FX chain, if I "swipe" by mouse over Virtual Keyboard in Sonar (and only in this case... not when I swipe in PRV or on MIDI controller), after a while associated VSTi stop producing any sound (sometimes followed by Sonar crash, sometime not, looks like a memory corruption...). Even in case I then remove AZ Lua from FX, save project and restart Sonar, the VSTi keep silence after the project is loaded again.
 
I am going to have an interesting evening to find why that happens, but the point is different. It is possible to produce something which is kept in the Project File and continue coursing problems. May be in my case I will find how to "fix" the project without rebuilding it, but with linked before project I have failed to do so (note that the linked project is effectively "empty"). But assuming quite specific way to reproduce my bug (I am using that plug-in without problems for a while), it could take months till I hit it in real live. I mean it is possible to do something no one else is usually doing and so have troubles while other can be "happy" and never hit the same.

Well, then I guess I've been lucky. That and the fact that I rarely, if ever, experiment with an untested plugin on a real-live project.
 
Dan
 

Sorry for near completely off-topic. May be the only relevant point in this message is: what looks like a "buggy project" sometimes is not really buggy...
 

mettelus
Alexey, you should track down that developer and badger them till they fix it, and don't accept "All software has bugs!" as an answer

I could not sleep well last night... AZ Lua was written with care and love... But what you propose has already happened and now I can watch EM and sleep well then
 

dcumpian
Well, then I guess I've been lucky. That and the fact that I rarely, if ever, experiment with an untested plugin on a real-live project.

In may case that does not work, since I am the developer, the (only) tester and the user
 
It happens that when you slide Virtual Controller key by mouse, it produce Mon Wheel changes. That is (may be) nice feature when you expect it, but I was not. It also happens that my AZ Lua had a one character typo in processing Control Changes in live mode. And it also happens that resulting CC (incorrectly converted CC1, ModWheel, changes) was silencing VSTi and probably doing other unusual changes.
 
So what I was thought to be "99%" memory corruption, somehow leaking into saved project, was CC number conversion bug in one plug-in (and the "damage" was saved as completely legit VSTi configuration).

Waow, the thread goes its way far beyond my understanding. It often goes like this,you throw a stone in the water and the circles go and go..
In my case ,as it has been confirmed,it is a matter of plug-in struggling one against the other.
The main character in the pitch is Rx5 which is the ultimate tool when you track things like miked acoustic guitars but it must have been coded in too a modern manner for my old set-up.
Anyway I'm confident that an update ( from Izotope or from Cakewalk) will allow all thoose tools to work side by side.
Alexey,good luck. I do use quite a lot Voxengo's plugs ( which are in the loop with my issues but I like to work with theese tools) and I heard the y are managed by an Alexey...
Dan, i must admit that I am not always careful with plugs and the fact is that some stuff are not secure,for me it is a trial and errors process.
Noel,thanks again for the job done and for taking time to give a hand. I do believe that the pleasure I and other people have to work with Sonar is due to the people who are working backstage.
All the best.
Olivier.