1.7.1 is here!!!

DJ Hellfire wrote:However, these are things that legit Waves plugin owner should know if you've ever logged into your account to download the updates.

I look after a couple of sets of legit Waves, and have never taken that much notice, I just download whatever the latest version is when I need to.

Having two different version numbering schemes is seriously mentally incapacitated!

THE ADVERSARY wrote:I hate when someone tries to explain someone else statement and get it totally wrong.

Sorry Hellfire you missed on this one.

Seriously though, I was referring to the fact that Waves just post it and Pete was already making a reference to it that quick.
You know like Pete stays on top of things.

THE ADVERSARY wrote:Sometimes it seems like Pete is on a different planet.

Waves released their last all bundle on 10/06/2014 so anyone still having a problems should try downloading this new Waves.

The previous was August (v9r20) so this new v9r21 may solve your problems.

No, pretty sure I didn't miss anything. Waves v9r20/9.3 has been out since August, which Pete is saying Akai now supports. What Waves posted yesterday, v9r21, is just the second update to version 9.3, which includes their new synth. So what Pete is referring to has nothing to do with what Waves just posted yesterday. I think this whole version number shit is where the confusion is. v9r19 and lower were not 9.3.

SimonInAustralia wrote:Having two different version numbering schemes is seriously mentally incapacitated!

Yeah, it's completely confusing. I'm not sure why they did it like it. It even has a complete different installer for 9.7 plugins.

pk1 wrote:

However, these are things that legit Waves plugin owner should know if you've ever logged into your account to download the updates.

indeed, but something us with the 6,000 {on sale} bootleg are stoked to learn.

I have had many bootleg software. And if I like the software i have purchased. so, of all my software, waves is the only boot. and it scans just fine. and will remain a boot.

Big ups to the cats that can afford such a beast. even bigger ups for the cats that provide crumbs for the poor.

Hey man, I'm not judging! Do yo thang!

I initially thought I was a responsible WAVES plugin owner.

I actually checked my account for the proper download version when I had the problem after 1.7 and 1.7.1. However, my upgrade plan showed my Gold Bundle was upgradeable to 9.2rx which I thought I was running that at the time.

I misunderstood it just as DJ Hellfire stated. Once I did the upgrade (offline), I was able to update to 9.3 and then re-register my licenses.

Honestly- I hate the whole update process for Waves Plugins... absolutely! Seems too convoluted to figure out what is really needed. They could use the example of how Native Instruments does it with their software updater.

Thanks again guys.

dj felix wrote:I just install version 1.7.1
I did scan my pluguins
and all are gone
were only expansions mpc
someone had the same problem?

Its a feature.

jk

Gugleme wrote:I initially thought I was a responsible WAVES plugin owner.

I actually checked my account for the proper download version when I had the problem after 1.7 and 1.7.1. However, my upgrade plan showed my Gold Bundle was upgradeable to 9.2rx which I thought I was running that at the time.

I misunderstood it just as DJ Hellfire stated. Once I did the upgrade (offline), I was able to update to 9.3 and then re-register my licenses.

Honestly- I hate the whole update process for Waves Plugins... absolutely! Seems too convoluted to figure out what is really needed. They could use the example of how Native Instruments does it with their software updater.

Thanks again guys.

The other confusing thing I notice is that my licenses in the license center still show my licenses as 9.2. But I think that's just the way it tracks when your update plan expires.

My original post clearly showed what the Aug version was and what the version released the day someone referenced Pete's statement was.
So I was saying it was a new version for people to try.

Right now it's like you trying to act like you are smarter than someone HOWEVER that's not the way you go about things so I'm not taking it that way.
You aren't someone who does that so I understand you are just trying to be helpful.

The problem with it still is that the shell that was crashing is the 9.3 but it doesn't crash under 1.6 and is still crashing under 1.7.1.

What also needs to be understood is we are not talking about crashing the software, we are talking about the Scanner reporting that it crashed the Waveshell 9.3.dll.

So the real question is why the 1.6 Scanner has no issue only the 1.7x Scanners?

DJ Hellfire wrote:

THE ADVERSARY wrote:I hate when someone tries to explain someone else statement and get it totally wrong.

Sorry Hellfire you missed on this one.

Seriously though, I was referring to the fact that Waves just post it and Pete was already making a reference to it that quick.
You know like Pete stays on top of things.

THE ADVERSARY wrote:Sometimes it seems like Pete is on a different planet.

Waves released their last all bundle on 10/06/2014 so anyone still having a problems should try downloading this new Waves.

The previous was August (v9r20) so this new v9r21 may solve your problems.

No, pretty sure I didn't miss anything. Waves v9r20/9.3 has been out since August, which Pete is saying Akai now supports. What Waves posted yesterday, v9r21, is just the second update to version 9.3, which includes their new synth. So what Pete is referring to has nothing to do with what Waves just posted yesterday. I think this whole version number shit is where the confusion is. v9r19 and lower were not 9.3.

THE ADVERSARY wrote:My original post clearly showed what the Aug version was and what the version released the day someone referenced Pete's statement was.
So I was saying it was a new version for people to try.

Right now it's like you trying to act like you are smarter than someone HOWEVER that's not the way you go about things so I'm not taking it that way.
You aren't someone who does that so I understand you are just trying to be helpful.

No, my whole response to you is about you saying Pete is from another planet because he mentioned Akai now supports 9.3 the same day Waves announces v9r21, when the two announcements aren't even related. Just looked to me like you didn't know that 9.3 has been out since August. Looked like you thought What Waves announced on 10/6 was 9.3 and that you found it strange for Pete to announce support for it so soon. Maybe I'm reading into it wrong?! It's definitely not about me "acting" smarter than anyone. With me it's ALWAYS about the facts, and eliminating misinformation.

THE ADVERSARY wrote:Sometimes it seems like Pete is on a different planet.

Waves released their last all bundle on 10/06/2014 so anyone still having a problems should try downloading this new Waves.

The previous was August (v9r20) so this new v9r21 may solve your problems.

THE ADVERSARY wrote:I hate when someone tries to explain someone else statement and get it totally wrong.

Sorry Hellfire you missed on this one.

Seriously though, I was referring to the fact that Waves just post it and Pete was already making a reference to it that quick.

You know like Pete stays on top of things.

THE ADVERSARY wrote:The problem with it still is that the shell that was crashing is the 9.3 but it doesn't crash under 1.6 and is still crashing under 1.7.1.

What also needs to be understood is we are not talking about crashing the software, we are talking about the Scanner reporting that it crashed the Waveshell 9.3.dll.

So the real question is why the 1.6 Scanner has no issue only the 1.7x Scanners?

As for the waveshell failing the scan, I was the one that originally reported this to Akai. As of 1.7.1, my Waves 9.3 scans perfectly fine now. So I'm not sure why you're still having issues. Somethings you can try is reinstalling Waves. Deleting your MPC Settings file (will require you to unlock the software again). Rescan all your plugins. We have verified 9.3 passing the scan on both Mac and PC. Again, I personally think this is something that Waves changed with their Waveshell as other software users are reporting the same issue with the VST. Plus the fact that all 9.2 and 9.1 Waveshells (v9r1-v9r19) scan fine in 1.7. Plus the fact that AU scans fine in 1.7.

As for why it works in 1.6, the 1.6 scanner works differently. It scans all plugins in the same process thread as the application itself is running in. So when a plugin crashes in the scan, it takes down the entire application. In 1.7, the plugin scanner runs in it's own process thread so if something crashes, the application is unaffected. I have no idea why Waves 9.3 doesn't like this. My guess is that it likes to be scanned in the same thread as the host application.

Where is this MPC settings file??? im having probs with my waves plugs but i wanna reinstall everything and re-unlock the software.

DJ Hellfire wrote:
Maybe I'm reading into it wrong?!

Seems to happens in many threads on this forum in general.
Could be because we have always seen dedicated trolls trying to stir things up?

DJ Hellfire wrote:As for the waveshell failing the scan, I was the one that originally reported this to Akai. As of 1.7.1, my Waves 9.3 scans perfectly fine now. So I'm not sure why you're still having issues. Somethings you can try is reinstalling Waves. Deleting your MPC Settings file (will require you to unlock the software again). Rescan all your plugins. We have verified 9.3 passing the scan on both Mac and PC. Again, I personally think this is something that Waves changed with their Waveshell as other software users are reporting the same issue with the VST. Plus the fact that all 9.2 and 9.1 Waveshells (v9r1-v9r19) scan fine in 1.7. Plus the fact that AU scans fine in 1.7.

So you saw it in BETA testing and reported it or after it was released to the streets?

Still the crazy part is no other Windows programs that use VSTs like LIVE, Maschine, etc have problems scanning the Waves plugs, only the MPC software.

There are still plenty of people reporting that the 1.7.1 scanner still didn't resolve their issue and even some who say it freezes the application.

DJ Hellfire wrote:As for why it works in 1.6, the 1.6 scanner works differently.

We all know that the 2 scanners are different the point is for them to resolve the issue.
Honestly users just want to be able to scan their plugs as needed without having issues.

DJ Hellfire wrote: Somethings you can try is reinstalling Waves. Deleting your MPC Settings file (will require you to unlock the software again). Rescan all your plugins.

I have been in contact with Waves, done a full clean up of their files.
Cleaned up the Akai stuff which caused the software to request unlock, plus decreased my setup from Ren and Studio to just Ren.
I put 2 complete days into looking for what could have caused 1.7.1 to not make a difference.

THE ADVERSARY wrote:

DJ Hellfire wrote: Somethings you can try is reinstalling Waves. Deleting your MPC Settings file (will require you to unlock the software again). Rescan all your plugins.

I have been in contact with Waves, done a full clean up of their files.
Cleaned up the Akai stuff which caused the software to request unlock, plus decreased my setup from Ren and Studio to just Ren.
I put 2 complete days into looking for what could have caused 1.7.1 to not make a difference.

If thats the case then im good! I soend way too much time updating all my plug-ins etc,i was up till 4am installing plug-ins and tryna figure this stupid waves crash problem out lol.I dont fully depend on waves plug-ins myself anyways so i can live without.I trackout my beats in reaper anayways so i can use waves from there.No big deal to me but i hope everyone else gets thru this with no probs and we get some type of update on it

optik415 wrote:Where is this MPC settings file??? im having probs with my waves plugs but i wanna reinstall everything and re-unlock the software.

If you're on Windows... It's in hidden folders. First you have to UNHIDE those folders by opening windows explorer and Organize>Folder and Search Options.

After that look for a folder on C: called Program Data>Akai>follow your nose.

I have MPC Element and updated Essentials to 1.7.1. Saw a message that it couldn't be unlocked without owning a MPC Ren or Studio. Is that the case with trying to update Essentials?

What's the difference between MPC Essentials and Software?

Thanks!