simon

It really depends on what bundle you have and how many were added since you last WUPed. It's worked out much cheaper for me the last few times. But yes you need to 'do the math' True !

^^^^ def worth checking. You can find the upgrade deals in your Waves account. either way everyplugin.com will be cheapest EDIT also - don't feel pressure to WUP just because you Waves tell you to The reasons to WUP are: - They have added plugins to your bundle so it's cheaper to WUP than buy them - There is a new version of a plugin that fixes an issue you are having In general the version updates don't usually add any more features... I can't tell the difference between 11/12/13 etc (apart from resizing of window?) You can WUP at any time in the future too..so no rush

my licence has just magically appeared

FWIW I pulled the trigger about 6 or 7 hours ago and still haven't received a licence, it's showing 'being processed' - I wonder if they have run out of keys and are requesting more from XLN ?

it's fairly random there's a version history here https://download.steinberg.net/downloads_additional_content/Steinberg_Library_Manager/SLM_Version_History.pdf one of the features recently added was: "There is a new information line on the right side of the Search/Sort bar, that shows the total number and size of all installed libraries in a category" I've never seen that part work either ? I've spoken to SB about the library manager - quite a while back now. They really don't seem to see any problems with it at all - I have (gently) pointed out how some other companies do it so very much better. They didn't agree . They were very proud of it. I tend to avoid it as it doesn't really tell you anything useful and it's a bit klunky to use (IMO!) Unfortunately you need to use it now that SB issue 'download codes' instead of 'licence codes' I'm sure it will improve as they slowly move over to the new licencing model.

Everything now prepped so I suspect we'll see Cubase 12 very soon

at the risk of derailing the thread (sorry) - I'm not sure I totally agree with your analysis. VST3 isn't 'better' in every regards...actually lots of developers find it much worse than VST2. And VST3 is nearly as old as VST2, you could say it's just as. 'legacy'...there are good reasons that many devs failed or refused to move over to it. There were other factors in dropping DX/32bit plugs that don't apply here (IMO)...but even then, SB created a wrapper in Cubase (up to version 8?) to run 32 bit plugins to ease the transition. I don't treat audio/studio software or technology to be 'disposable' in the way people treat cell phones and other modern technology. In my view there needs to be a very compelling reason to change a good working standard that is universally adopted and works well....MIDI 1.0 would be a good example of this. It's not perfect but it works well in practice. Steinberg should have open sourced VST2 when it was released - they should NOT be the guardians of the format...it's a conflict of interest. Imagine if Yamaha owned the MIDI standard and told people companies they couldn't use it any more or made it difficult for them to develop products using the technology. Don't be fooled - Steinberg are not dropping VST2 because they can't make it work - there are other political and business reasons for this. Essentially forcing developers (check the T+C of the VST3 SDK) to move to VST3 are 100% to benefit Steinberg as a business NOT to help or support the 3rd party developers, the users or customer. I'm an early adopter and welcome positive change but this is a cynical and unpleasant move worthy of Apple not Steinberg. I say this a very, very, very long term and loyal Steinberg customer. (apologies for the rant ! - promise not to whinge about it any more)

very true although I don't want to lose Altiverb XL (or Indoor) or the Gforce stuff ...or Jamstix....or Addictive drums...or Superior Drummer...etc I'm sure some will get a PAID (?) update and I'd probably update anyway but still very poor show by Steinberg (and it's 99% political NOT technical, trust me I've spoken to people with much more inside knowledge than me). Bear in mind VST2 working well in other hosts...including M1 native. I could rant much more about some of SB decisions - and it's not the developers fault, but I'll just leave it there In the meantime I'm avoiding non-VST3 plugs...which is exactly what SB wants me to do ?

yes - although wrappers can be a bit cumbersome (IMO) and you wouldn't want to run them in a wrapper if you didn't have to - hence, now, if I'm sat on the fence about a plugin lack of VST3 is enough to tip me to the 'don't buy' side. This doesn't apply to RC20 of course but I wonder how some of the wrappers deal with surround/atmos formats too. Lots of stuff I use isn't just 2 channels. Also doesn't Unify show as just a VSTi plugin so you couldn't insert it as a FX in cubase/nuendo ? Bl**dy Steinberg - why do they make so many unfriendly choices ?

I'm assuming it's VST2 not VST3 ? - the XLN website isn't clear. (thinking future Steinberg plans)

not only is SD3 the very best drum VST out there - TTs change logs are actually useful and detailed too ?

didn't happen with Mtron Mkii (and yes I know it's a different type of Mellotron)

so of the GForce stuff has a resize but not minimonsta TBH some of the gui choices are 'idiosyncratic' to say the least

Gforce have said that that all 'non-legacy' plugs will be updated to VST3 the question is 'what is legacy' ? the suggestion is that they are: Oddity, impOSCar and original M-Tron. It would be a real shame if these weren't updated but nothing is set in stone. Although worth bearing it in mind.

and because Apple are going to drop Rosetta from upcoming versions of MacOS - it's seen as a short term, stop gap solution.

I agree with everything you posted - and sorry, I was being a bit flippant (it was very late over here ?) and yes ,your BF posts are hugely helpful both at the time and as a reference source.

seems a bit mean I'm a big fan of Gforce but I think they'd make more profit if they cut existing owners a deal or were slightly more realistic on price (I refer you to Larry's 2nd Law of Plugin Pricing: 1000x$29.99 > 100x@$249.99)

why not just pay Larry for all the amazing work he does ? if it ain't broke etc.

I feel unloved anyway I noticed that lots of their plugins have 2022 updates - all the ones marked 2022 on this page (more 'stating the bloody obvious!') https://www.pspaudioware.com/products the change logs here (you need to be logged in) are all totally out of date but it looks like all the 2022 plugs get M1 native https://www.pspaudioware.net/UserArea/demos probably the same basic change log that you had emailed to you (favouritism....!!! )

I wonder how you get on their update email list - I have 'product updates' ticked in my PSP account newsletter prefs ? and (at the risk of stating the bloody obvious) if you log into your account you'll see the new iLok activation code next to the download link in the 'my plugins' section of the website.

IF they combine ALL 5 of the Fusion plugins into 1 and charge $149 then I'm interested.

I've noticed that most of these elicenser updates are just "License database updated" in the change log https://download.steinberg.net/downloads/Release_Notes.pdf when you run (autorun?) the elicenser maintenance it updates the licence database anyway - I wonder if all these minor updates are actually needed or do anything. maybe just Steinberg's slightly clumsy way of making sure you have the latest database ? (incidentally there wasn't an update on the mac - haven't tried the PC yet...but I tend not to use it anyway as it's still very klunky...c'mon Steinberg give it some love )

I would imagine that if you're eligible then it would show in your Focusrite account - if not then you're probably not eligible. I was just pointing out that the reason you don't have it is not because you've already claimed a Pro Tools First licence or that you bought your Focusrite product before November 2021....both of which are true for me.

no - you should never give out passwords ! obviously you need an avid account before you can enable the 3 month subscription and also obviously you need to have your ilok account linked to your avid account so they know where to put the licences. Avid DO NOT request your ilok password - they certainly don't need it to deposit licences