Jump to content

abacab

Members
  • Posts

    9,210
  • Joined

  • Last visited

  • Days Won

    59

Posts posted by abacab

  1. 1 minute ago, trager said:

    I wonder if perpetuals will all be at list price now.

    Interesting question...

    I doubt that they will ever be full retail list price (as in they need to remain competitive), but also doubt that we will see the $29 forever sale resume.

    • Like 1
  2. 3 hours ago, lawajava said:

    From the Waves announcement on their site: “we’re working to get perpetual available again as soon as possible”.

    I wonder if Waves is going to resume working with third party distributors and new product registration codes (you know, the ones that everyone was giving away the other day)?

    • Like 1
  3. 2 minutes ago, cclarry said:

    Windows defender doesnt' like it.  It keeps preventing the install claiming that it contains a Trojan

    Yeah, there are miles of comments in a few threads regarding that issue over at the NI forum. The PM for Native Access has come out with a statement that it's a false positive and a Windows Defender issue. Here's the official statement: https://community.native-instruments.com/discussion/11699/known-issue-windows-defender-flagging-products-as-trojans/p1

    I concur with the Defender false positive theory, as there have been reports of applications from other manufacturers that got flagged for the same Trojan name. It also appears to only flag zip files for some reason.

    • Like 1
  4. 57 minutes ago, John Maar said:

    I just figured that out and installed v2. I guess that I expected Native Access to inform me of new versions like all of the other app managers. Not so for this major upgrade. Live and learn.

    And...never mind. 😄

    They haven't pushed NA2 out to all NA1 users yet. It's still opt-in by manually downloading the new version.

    The reason is that there are apparently a small group of users with incompatibility issues with NA2, so NI are not forcing a migration just yet.

  5. 1 hour ago, dumbquestions said:

    Side question, it seems like updating OS & software versions is really important to most people. So another question I have is, do those people’s (maybe even you as the reader) reasons for upgrading software or OS truly warrant losing their entire waves plugin library? Asking because I’m still on an old operating system, & don’t foresee myself updating anytime soon especially after this.

    At this time, Mac users are probably the main group to be concerned with OS upgrade compatibility. That sounds like a biggie!

    But as far as I know, there are no issues with running the existing Waves plugins on Windows 10 or 11. So if you are still using Windows 7 or 8 it shouldn't be a problem upgrading to one of the current Windows versions.

  6. 2 hours ago, dumbquestions said:

    With all the changes to Waves Central, Is it possible at this point to switch your waves licenses to a usb key, if your current plugins/licenses are already stored directly on your hard drive? In other words is it too late you think?

    The latest Waves Central still includes the function to manage your license storage locations, such as your local drive or a USB key.

    • Thanks 1
  7. As the shock and awe of the announcement sinks in, even though I am firmly in the camp of "no subscription ever", I have taken stock of my perpetual plugin inventory.

    Even though these plugins should continue to work for the foreseeable future, I will still have the feeling that I have been screwed. I think the only way to get over this feeling will be to stop using them, as I doubt that they will ever "inspire" me again. They will just be a reminder of "argghhh"!!! 🙄

    • Like 1
  8. 6 minutes ago, ArcRex said:

    I did the update this morning and when I check in my DAW, I see all of my Waves plugins, but when I put them in my tracks, most won't load. I am pretty sure that is a result of the update as my older version plugins do load. I suspect they made a change (location) that I need to point my DAW, so probably not a huge issue, but it is a headache.

    Not sure what your "my DAW" is, but selecting "Update Plug-in List" in Studio One (forces a re-scan of the Wave Shells at DAW start-up).

    That did the trick for me in Studio One. The updated v14 Wave Shells were not automatically scanned at startup until I did this.

    Cakewalk had no issues with the updated plug-ins, as it always seems to check the Wave Shells. But in Reaper VST preferences I had to "Clear Cache and Re-scan" to get v14 working.

  9. 3 minutes ago, smallstonefan said:

    They bugged something in the installer when it comes to selecting individual plugins to install. It's hiding and showing things and changing my selections. Wierd.

    Waves Central only installs v14 plug-ins now. But it should show all of your activations.

    https://www.waves.com/support/how-to-install-waves-v12?utm_source=Waves-Central&utm_medium=referral&utm_campaign=learn-more

  10. 6 minutes ago, Bapu said:

    I'll check that out and report back.

    I figured it out! I had to open the Studio One Plug-in Manager and "Update Plug-in List" to pick up the new Wave Shells. They scanned on S1 restart.

    All good now! :)

  11. Just now, Bapu said:

    That is correct for me.

    IOW installed!

    Did you update your v14 plug-ins yet? I did, and the v14 plug-ins are visible in Studio One, but won't launch... I'm thinking that the updated plug-ins didn't get scanned.

    The v13 plug-ins still work as good as ever, and they were not updated.

×
×
  • Create New...