May this thread rest in pieces...

I'm bookmarking it!

Man, do you have a crew of people log on to your ID or do you just not sleep, or work??  ;)

All of the above. today was a "training day", just finished FM8 tutorials from Groove3.
Tomorrow video editing session, you won't hear a peep (well unless I get bored with the video which is likely to happen even though I'm getting paid). I have at least 3 virtual versions of me that sleep around the clock. Next week I think I'm working on some website.
 
Nite!

X3D implemented full support for VST3 factory preset management which is a new feature that didn't exist in X3C. When we did that it exposed problems with bi-directional support with some VST3 plugins.

Thank you Noel!!! That is what we expected all along - that something changed in X3d. Of course that doesn't mean Cakewalk is right or wrong - but the plugin devs have to know this, so they know what to fix.
 
Dave @ DMG said you were really helpful when he talked to you!
A lot of us are feeling a lot better about this

jbraner
Thank you Noel!!! That is what we expected all along - that something changed in X3d. Of course that doesn't mean Cakewalk is right or wrong - but the plugin devs have to know this, so they know what to fix.
 

Nice angle, but not really what was said by Cake. The plugins code were at fault. I suggest you re-read the thread from the beginning and maybe you will take heed a little more about what was written to gain a little more understanding on how it all works together, next time your perceptions might not get in the way of what people are trying to say.

Cheers..

Alex,
I know we have a peace deal, but what part of "X3D implemented full support for VST3 factory preset management which is a new feature that didn't exist in X3C." means that there was no change between X3c and X3d?
 
That is all I ever said! Nothing is anybody's "fault" but when something changes there are ramifications, so some plugins stopped working. Noel seems to know exactly what this is all about - and has actually done something about it and is working with the devs. We all applaud him - and it's a good day for all of us. (in spite of you needing to get the last word in)
 
Now please get your last word in...
 
 
 

Selective highlights that draw to the wrong conclusion. Read Noel's post #78 which by the way references what I referenced in my very first post.
 
> That is all I ever said!
 
Those reading this thread may beg to differ.

Thank you.

"X3D implemented full support for VST3 factory preset management which is a new feature that didn't exist in X3C."
X3c = < full support for VST3 factory preset management
X3d = full support for VST3 factory preset management
 
X3c != X3d
Which part of this don't you understand? This is not selective.
You are being "selective" in that you cannot seem to deal with anything other than you are 100% right, and everyone else needs your help. This is not the case - and, actually, nothing is ever 100% or "always" or "never".
 
As an example - some day, you might be able to help me, and some day, I might be able to help you. Some day I may not think you are blowing it out your ass. But today (and yesterday) I feel like you are being stubborn, petty and obstinate (in the quest to be 100% right all the time)
 
It won't always be like this though. I won't let the poison from this thread spread to other ones - I can't vouch for you though - only you can do that.
 
This thread is not about you. You just joined in, and gave your opinion (quite a few times) - but it's not about you. The waves problem is about to be solved - but not because of anything you did.
 
I would still like to continue with the "reset and rescan" joke though. You never commented on that. Even Bapu and Noel had a laugh with that one. I think it could endear you to other people - and I won't take credit for it. Maybe I'll take credit for lightening things up a little - Lord know I keep trying with you. I keep getting annoyed with you and trying to have a truce or a peace plan - but you must get the last word in.
 
So finish off this thread with the last word - I won't reply any more, and I sure as hell won't carry it into any other threads. As I mentioned, life is too short...
 

You are trying to reinterpret or deflect from the point what Noel actually said (and what I said to some extent) to suit your incorrect point and the general theme of your posts throughout this thread, so you feel vindicated or something ... Once again you are telling me what I should or should not be doing to add yet a pointless distraction (pretty much every single post you did), you made this thread about me and are now attempting to inverse this, so I'll simply paste in #78 here, this is all that matters (rather than your reinterpretations) ... Main points highlighted in bold. Good day.
 

Noel Borthwick [Cakewalk]

Guitarmech111
Alex, Logic would preclude that something broke X3D if it works as expected in X3C. I understand code and release processing of code as well as regression of code. I am waiting for feedback still on my trouble ticket. I know Waves and Cakewalk have a good communication established and we shall get an answer on this soon I hope.
Let's just agree to wait and find out what the bakers or Waves confirms and let this thread breathe a little. ;)

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.
 
I have debugged this issue and the root problem is that the preset mechanism in several VST3 plugins is not fully implemented according to the VST3 spec. Presets can be changed in a bi-directional way - via the plugin UI or from the host UI. When the host sends a preset change request the plugin should change its preset and update its UI and internal state. Conversely when a preset is changed from the plugin UI it is up to the plugin to send a notification to the host to allow it to sync up its state and UI to the plugin. What is broken here is that the plugin's are not sending the notification back to SONAR and this puts it out of sync. Now when you save the project we save the state that SONAR knows about which is incorrect and when you load it back you get the incorrect state that you are seeing.
 
In the case of Waves plugins it appears that they never update the current program state when it is changed from their internal UI. I have reported this to their engineering team for review.
In the case of DMG plugins they do update the current state, but never notify the app so we don't know it was changed.
I have passed on information to both DMG and Waves about how to send back a preset change notification to the host.
See the section on Bi-Directional setting of programs here. 
 
Additionally I have added some failsafe code for the next update to prevent settings being lost even if the preset is out of sync (the UI will display the wrong preset name but the plugin state will always be intact when you load a project). I've also added code to make the bidirectional communication work using a different method. This also translates to VST2 so its nice that VST2 plugins will also stay in sync when presets are changed from the plugin UI.