By THE ADVERSARY
Sun Sep 28, 2014 1:31 pm
Sike Low wrote:I am curious to know of all the people who are having issues with loading waves plug ins do any of you have the paid version. Maybe it is because the new scanner does not allow cracked vsts
My whole reason for reporting it was because my plugs are all legit and the 1.7 scanner crashed while I could go back to the 1.6 scanner with no problem.
This was why I said it made no sense to talk that nonsense about hacking your plugs with shell2vst.
Shell2vst was created for the cracked plugs so why would someone who paid for their plugs even consider using it?
The Waves V9 plugs work fine in other apps and in 1.6, the problem only comes about when you try to scan with 1.7 scanner.
If you don't scan with the 1.6 scanner they work fine within 1.7.
If you look at the 1.7 scanner it has a new error reporting system and somewhere within this is the problem.
Someone post in another thread that Pete was saying it's a Wave thing but it's not and he should have never made that statement.
Should have simply said 1.7.1 has a fix for it.
Pete Goodliffe @petegoodliffe · 10h
@mreese06 Waves plugins do something unusual that crash the new scanner. 1.7.1 resolves it; we had to make a workaround.
Someone needs to warn him about slipping back to old Akai ways after working hard to get away from them.
I know your Moms told you to believe in yourself but d@mn lets be realistic
