get a room guys

Broke was an incorrect statement, I should have said changed. That would have been more correct. REGARDLESS, X3D does not work like X3C and THAT is what this thread was intended to determine.
 
Please don't hijack this thread any more guys.

Sorry you wanted to know what was wrong with your plugins, and as Noel said the plugins were at fault, the VST 3 code was incorrectly implemented at the third party end.
 
Of course X3D does not work like X3C, everybody knew that from the start (see the changelog), however X3D did not cause this issue as has been said several times now. The plugin code was at fault and this was exposed with X3D. None of this was down to Cake or X3D, I say again none of it.
 
Cheers...

I wanted to know what was changed in SONAR to cause the issue, not what was wrong with my plugins. We eventually found that out though.

X3D caused a different behavior in the product compared to X3C and an end users expectation. X3D DID cause the issue exposure. We know why now. If something works in X3C and does not behave the same in X3D, then there is a perception things are not working and X3D caused the issue.

From the release notes on VST3 - Improved VST3 Plug-in Preset Support

improved vs. more fully VST3 spec implemented, as Noel eluded to, is not the same to the end user who casually reads this release note.
 
I have faith that this will be resolved by Cakewalk and the plugin developers.

Guitarmech111
I wanted to know what was changed in SONAR to cause the issue, not what was wrong with my plugins.

 
Let me just state again nothing that was changed in Sonar caused the issue, that is just your perception. Sonar exposed an existing issue with your plugins.
 

Guitarmech111
X3D caused a different behavior in the product compared to X3C and an end users expectation. X3D DID cause the issue exposure. We know why now. If something works in X3C and does not behave the same in X3D, then there is a perception things are not working and X3D caused the issue.
" If something works in X3C and does not behave the same in X3D, then there is a perception things are not working and X3D caused the issue."

 
... and that perception is wrong which is I have been saying all along this thread, and what Noel confirmed, and X3D did not "cause a different behaviour in the product", Sonar exposed an issue with your plugin which was not visible before.
 

Noel Borthwick [Cakewalk
That logic is flawed. While it can be used as a thermometer for general troubleshooting, in the software world you cannot compare two different inter-operating components A and B and conclude that if a problem arises after a change in A it can be implied with certainty that the change in A is the root problem. In this case a change in A to add a new feature exposed a bug in B that causes the problem.

 
Sorry to emphasise the point, I appreciate you didn't outright disagree with me, I just want to make this point very clear.

You are wrong. X3D changed and caused a different behavior. I am not trying to blame anyone, I am just saying that things were working in X3c with the presets and then they were not behaving the same in X3D. I believe this is for the better, but you are missing my initial question that I asked.
 
I find it odd that all of the plugin manufacturers who have been implemented in a VST3 supported host for quite a while now are not doing it right.
 
If My bottom question was answered more directly in #6, I would have been happy with that. I still stick by my assumption that X3D is the cause for which it is.

Then you clearly believe what Noel wrote is wrong also (which is weird)... You need to get your head around this sorry.. I am a developer myself and I know exactly what he is talking about...  If you can't get your head around this I would just take it as gospel (developers will know exactly what is going on here).
 

Noel Borthwick [Cakewalk
That logic is flawed. While it can be used as a thermometer for general troubleshooting, in the software world you cannot compare two different inter-operating components A and B and conclude that if a problem arises after a change in A it can be implied with certainty that the change in A is the root problem. In this case a change in A to add a new feature exposed a bug in B that causes the problem.

 
There is a difference between "cause" and "expose", if you can't see the cat it doesn't mean it doesn't exist (unless you are in the quantum world). I believe your question in #6 was clearly answered but you aren't getting your head around this as you are still stuck in the opinion that there was something "caused" your plugin not to work, whilst Noel said the opposite and clearly explained why.

I knew it, you do own a cat!
 
For the sake of others, let's agree to disagree. My 2 original posts express what I needed to get information on. X3D changed and that is what caused the different behavior in my, and a few others, work flow.

Omg