chris.r

NI is not much better in doing the same.

2. Ability to use FX outside of AT Now that would be something! I guess they'd keep the TERC chorus being mono IN unfortunately, just like the original hardware. But still useful as a single anyway.

Still trying, wondering who else is still hiding there...

And I can't enter. Think I need to wait for Fleer leaving first, there might be not enough space for us all...

Thanks for posting, shawker! And please keep us updated if the issue gets solved. Issues with projects that already use waves plugins is my main suspect when deciding if I should update or not. I have a bunch of V9 and another bunch of V11, of which some I could update to V12 but few would have to stay at 11.

Didn't even think about that, and it's a good possibility!!! Wondering what it could sound like, given that we have already so many sample-based guitars like those from orange tree, acousticsamples, isw etc...? And no, no spanish guitar on offer .

I was thinking about rack extension versions for my son.

It reads like fighting a malicious software infection out of your operating system.

Is there any extra offer for those who own these synths as VSTi already?

Oh that's bad, sorry to hear that. Are you sure you have your controller enabled in the settings prior to any MIDI learn? Maybe try with another keyboard, that's what I would do just to rule out any hardware failure.

At least a good news for some people like me, really glad to hear that.

You have to assign the controller. Click the 'MIDI' button next to the MIDI diode on the bar below then 'control change' tab and click ADD. Then you have to find the Leslie that you have loaded and pick it's 'Speed'. Next click Learn button and move your controller. It should work now assuming you have enabled the controller in the preferences first. Edit: apparently I can't find it under Control Change>Global tab, must use the Project tab unless I'm missing something too. It is convoluted, have to admit.

I saw a sneak peek of an articulation manager for Cakewalk. Can't wait to see a new beta announced soon!

For me it's always the first one or two scans per windows session then it get's quicker. I blame defender.

No worry... I'm getting known for some 'pathetic' posts, occasionally

Thanks, I was wondering what kind of game was it . Yes, I should be more clear it's my subjective opinion and I understand those who will benefit from it but I also noticed that if you want to (edit: have to) keep more and more legacy versions there is an additional wrapper added with each version and that can obscure computer resources quickly in a dense project, so I don't like it. Furthermore there is always much mess with updating my installed collection after buying a new plugin especially after announcing a new version like today. I like my waves plugins but I don't like the confusion with their authorizing method and the constant anxiety that they will drop support for legacy versions like v9 one day. Edit: and I think Matthew was spot on with the change in their approach in his post above.

? sorry could not follow what you mean

So basically they added GUI resizing and preset browser and that was enough reasons for stepping up the version... and giving more headache to those who don't regularly WUP-ing their collections. Lame.

Larry is back and now all of a sudden I've got a backlog of pages with deals unread. Thank you Larry!

I have a habit to let the installers run through their paces in a sandbox first and see what kind of mess they do on my disk. As an example the installation path folder can be the a folder where developer pours out all of their library dlls and all sort of config files for one developer and puts another subfolder with a single dll plugin in it for another, you can only try guessing what an installation folder means for them. But with this, new to me, updating from within the gui I'm vulnerable again.

Good luck with the recovery!

Just found an explanation from Dan @ Cherry Audio on kvr: https://www.kvraudio.com/forum/viewtopic.php?p=7911717#p7911717

I just checked and my VST2 installed into separate folder, guess I left the default path untouched when installing. Theoretically I should be safe, but no, I'll wait until this gets confirmed being safe to update.

I have the impression XX century was more mindful.

Say whaaaat?! Really, what going wrong with this programming of today... Thanks for the warning, Zinc. Did you update in the plugin or standalone?