KVR Audio

Iva · Post by **Iva** » Mon Oct 11, 2021 11:53 am

It's here...

https://www.waves.com/v13

M1 and W11 support. As I don't have either one, I'll skip this update as I did with v11. Going to stay with my i7 and Big Sur for a while.

LoveEnigma18 · Post by **LoveEnigma18** » Mon Oct 11, 2021 12:05 pm

Yeah, wasn't a necessary update for me either, but most of my stuff was convered under WUP, so I updated them to the latest V13 version and installed them. The process was smooth and everything seems to be working fine. Only thing I am unhappy with is that I was expecting a significant number of plugins to get the Hi-DPI update in V13, but only 3 were updated to have Hi-DPI.

Note for FL Studio users: You need to do a "full plugin scan with verify" first and then things will work as before.

AC222 · Post by **AC222** » Mon Oct 11, 2021 1:41 pm

As far as I am aware a lot of the newer plugins launched after v12 will not work in qny capacity with a windows computer that isn't windows10 or higher anyways. I wonder if v13 will fix this. Guessing no

chrisstiles · Post by **chrisstiles** » Mon Oct 11, 2021 1:52 pm

AC222 wrote: Mon Oct 11, 2021 1:41 pm As far as I am aware a lot of the newer plugins launched after v12 will not work in qny capacity with a windows computer that isn't windows10 or higher anyways. I wonder if v13 will fix this. Guessing no

I doubt that they'd introduce additional backwards compatibility in a newer release of the software.

kidslow · Post by **kidslow** » Mon Oct 11, 2021 2:47 pm

Interested to follow reports of whether the native M1 plugins report less CPU load than Rosetta equivalents under an ARM-native build of Reaper. If there is enough proof of greater efficiency on the CPU of say the Abbey Road plugins, might justify WUP. I'm not convinced so might wait a year for v14 ... and the next 3 HiDPI updates

Funkybot's Evil Twin · Mon Oct 11, 2021 9:34 pm

So they went though version 12 and version 13 now and only have like 8 or 9 plugins with HiDPi graphics? Did I read those release notes right?

I'll keep my V9 and V10 plugins exactly where they are thanks. Maybe someday they'll get me to WUP some or all of my Waves plugs (not many) but holy crap, not offering anything worth paying for isn't getting me to scratch that itch.

bmanic · Post by **bmanic** » Mon Oct 11, 2021 9:46 pm

This is the first time I may actually update my WUP to get access to my waves plugins on my Mac M1.

Wasn't there a cheaper shortcut tho, like buying a single cheap 30€ plugin and thus renewing WUP for all.. or something like that? Anybody remember the shortcuts?

Aloysius · Post by **Aloysius** » Mon Oct 11, 2021 9:51 pm

You can generate an upgrade code at waves and for example submit the code to audiodeluxe for a cheaper price.

cryophonik · Post by **cryophonik** » Mon Oct 11, 2021 9:54 pm

Funkybot's Evil Twin wrote: Mon Oct 11, 2021 9:34 pm ...but holy crap, not offering anything worth paying for isn't getting me to scratch that itch.

That was my thought exactly!

Fortunately for me, I had to update my WUP last year for Big Sur compatibility, so I get v13, but I didn't see one benefit in the change log for me, my computer/OS, or my plugins

Funkybot's Evil Twin · Mon Oct 11, 2021 10:47 pm

bmanic wrote: Mon Oct 11, 2021 9:46 pm This is the first time I may actually update my WUP to get access to my waves plugins on my Mac M1.

Wasn't there a cheaper shortcut tho, like buying a single cheap 30€ plugin and thus renewing WUP for all.. or something like that? Anybody remember the shortcuts?

I'm planning on getting an M1 Macbook once the new ones are announced (should be any day now) so I'm tempted but then I remember....wait, it's been years since I've actually used one of my few Waves plugins in a song. Maybe by V14...

bmanic · Post by **bmanic** » Tue Oct 12, 2021 2:25 am

Actually I'm in a bit of a similar situation. But I do miss the unique flavors of the Abbey Road Vinyl Cutting plugin thing. I can't really duplicate it's results with anything else. It'd cost me 18$ to update the WUP for that single plugin and I'm seriously considering it.. but my dislike of Waves as a company in general makes it hard to part with even that amount.

I'll just sleep over the decision for a few days.

jamcat · Post by **jamcat** » Tue Oct 12, 2021 2:27 am

EDIT: problem is resolved and V13 plug-ins are loading as expected in songs saved with V12.
_______________________

So I updated my Waves plugins from V12 to V13, and now my songs with Waves plugins say they are missing when I open them. So it looks like I am going to have to reload all of my Waves instances.

But according to Waves:

Why does Waves charge for updates?

At Waves, we are committed to ensuring that the same plugins you are using in your sessions today, will continue to serve you 5, 10, 20 years from now – always and without limitation. We have been providing updates to keep our plugins compatible since 1992, and are committed to continuing to do so. When you use Waves, you can be confident that your sessions will open the way you want them, now and in the future, with your plugins and your sound fully intact.

I had V12 VST3 instances loaded, and the V13 VST3 versions are now installed. According to Waves' justification for charging for updates, they should load right up.

Am I missing something?

Funkybot's Evil Twin · Tue Oct 12, 2021 2:31 am

I read that same paragraph earlier today. The good news is that WUP entitles you to "VIP support” so reach out and see what they say.

jamcat · Post by **jamcat** » Tue Oct 12, 2021 2:46 am

EDIT: In the end this wasn’t necessary, so I did not do it.
_______________________

OK, So I found this XML data inside my Studio One .song file:

<MetaInfo>
<Attribute id="VST3UniqueID" value="565354543532377472352065712D3831" type="string"/>
</MetaInfo>
List Comp0 Ð Cont Info œ PK q™=S?‡-/ 8 Presets/Channels/JCM 800/3 - Kramer HLS Stereo.vstpresetVST3 56535448454C536B72616D657220686C¿
Ð HELSsetA
°XPst<PresetChunkXMLTree version="2">
<Preset Name="" GenericType="HELO">
<PresetHeader>
<PluginName>Kramer HLS</PluginName>
<PluginSubComp>HELS</PluginSubComp>
<PluginVersion>12.7.0.209</PluginVersion>
<ActiveSetup>SETUP_A</ActiveSetup>
<LoadMenuCategory>Factory</LoadMenuCategory>
<ReadOnly>true</ReadOnly>
</PresetHeader>

So I should be able to do a search and replace of the "VST3UniqueID" to update it with the V13 version, and also update the <PluginVersion> data to whatever the current numbers are for each Waves plugin (I only have 3), and in theory, that should get my plugins showing up again without having to reload and reconstruct my settings.

monomox · Post by **monomox** » Tue Oct 12, 2021 3:02 am

jamcat wrote: Tue Oct 12, 2021 2:46 am OK, So I found this XML data inside my Studio One .song file:

<MetaInfo>
<Attribute id="VST3UniqueID" value="565354543532377472352065712D3831" type="string"/>
</MetaInfo>
List Comp0 Ð Cont Info œ PK q™=S?‡-/ 8 Presets/Channels/JCM 800/3 - Kramer HLS Stereo.vstpresetVST3 56535448454C536B72616D657220686C¿
Ð HELSsetA
°XPst<PresetChunkXMLTree version="2">
<Preset Name="" GenericType="HELO">
<PresetHeader>
<PluginName>Kramer HLS</PluginName>
<PluginSubComp>HELS</PluginSubComp>
<PluginVersion>12.7.0.209</PluginVersion>
<ActiveSetup>SETUP_A</ActiveSetup>
<LoadMenuCategory>Factory</LoadMenuCategory>
<ReadOnly>true</ReadOnly>
</PresetHeader>
So I should be able to do a search and replace of the "VST3UniqueID" to update it with the V13 version, and also update the <PluginVersion> data to whatever the current numbers are for each Waves plugin (I only have 3), and in theory, that should get my plugins showing up again without having to reload and reconstruct my settings.

I'd contact support first, but if you're going to do it your way, backup your existing files

Waves 13