[Logic Pro 9 Waves Plugins Torrent
Sharif Garmon
I have done multiple uninstalls and reinstalls via Waves Manager, full restarts, and still I only see two plugins in Logic in my Waves folder when inserting a plugin on a track: The free CLA echo-reverb and the Kings Microphone lol. I have used the full Abbey Road collection on my 2013 MBP 15" Retina, no issues. Easy install and authorizing process.
We are working to qualify and update our software to work there, but this may take some time and I do not have an ETA.
In the meantime, I cannot offer any troubleshooting steps or help resolve this.
Do you still own a previous Mac with Intel processor where the plugins run properly?
Heya Simon. I worked out that I needed to migrate logic and waves plugs from the intel machine to the M1, then open logic in Rosetta and validate the plugs to the M1. All present and accounted for and running very well. That will hold me over nicely until I can go native when waves is rockin the M1.
one of my collabs is on logic 10.7.4, and says she's having no issues running waves v13. obvious question, but have you rebooted? you could move the AU cache file to the desktop, reopen logic, rebuild the cache, see if that helps...
Well folks.... after loading 10.6.3 and going through the process of rescanning my plugins, I came to the realization that the problem all along was that I had not properly activated the trial plugin licenses.
Are you still running things in 32-bit?? As support for that was deprecated a little while back by both Apple and most major developers including Waves. The other thing to look out for is moving their plugins from the default install locations as that can break interdependencies, leading to buggy behaviour or plugins not working at all.
Another thing you can do is try the AUReg app inside the Waves plugins folder within Applications. Some times Logic won't see then until you run that.Inside Waves Central's Settings tab there are a few options you may want to have a look at too, including Fix Permissions and Ownership. Dodgy permissions can also cause behaviour like this. Just make sure you have the latest version of C
I tested an empty project with only battery loaded and the knobs seems to work fine. Did a test by loading a WAVES plugin V10 and the knobs are not working anymore. I'm aware some people are still facing some problems after updating their waves plugins. Is there a fix for this?
@Pampy if it's truly only V14, I think updating your Waves library will fix it. But I can confirm it's not just Waves. Battery has this interaction problem with other plugins. Another user mentioned Ohm Force but I've had it in sessions that don't use Ohm Force or Waves, and I've been on V14 for some time now.
Support has been genuinely trying to help but the automatic ticket closing makes it very difficult because when I'm working on a production I don't always have time to make them videos and test uninstalling, reinstalling, deleting and remaking all my patches, etc. By the time I have some feedback the ticket is closed and I have to start a new one.
@Jeremy_NI There are other plugins that Battery interacts with in this fashion. I realize you can't get too detailed on a public forum, but is this due to other companies using old tools, or proprietary workarounds, or what? I emailed Kilohearts to make them aware of this but it would be nice to know why this is happening.
Hey guys! So, I just got a brand new max MacBook Pro M2 maxed out on every god damn level :D. I have all the latest waves plugins and all the latest updates on all NI plugins. I've experimented a bit, and even with all the latest updates, the Battery knobs will go crazy, and as someone already mentioned, it's not only waves. KiloHearts plugins will make Battery react the same way. I've tried a bunch of other plugins (SoundToys, Slate Digital and more) But looks like only KiloHearts and Waves are the only bad apples here.
Just as Thommytippy posted on Octover 2022, in addition to the stuck knobs in Battery, I'm experiencing the same problem in Komplete Kontrol. My Waves and Pro Tools are on the latest versions (V14 and Pro Tools 2022.12 respectively). I really wish Native Instruments would just own the problem and find a solution, it's ridiculous at this point. Adding insult to injury, they recently released a Youtube tutorial, "How to use everything in KOMPLETE KONTROL software," where I learned a few things but the stuck knobs makes it impossible to use the software in a real world setting. Seriously guys, get this problem straightened out, you're going to start losing paying customers.
I using the Waves plugins (by waveshells vst) in Ardour5.8 on Windows platform. And they works perfect, almost.
The graphic interface and proformance on aspect of effect and automation is normal, nothing different than operating them in other DAW.
You are talking about vendor lock in. Every big company will do everything in their power to lock your data into their proprietary format / service. Then it becomes so expensive and painful to change your software vendor that it is easier to just pay up and stay where you are. That is not a new phenomena, every video tape machine manufacturer locked customer data into their cassette format, microsoft did this with office formats, etc.
Just choose only software that has a free license (if you can) and free yourself from all of the above (and copy protection), or be prepared to pay again and again for the privilege of having your tools working.
It's been a year and there is still no change. I rely heavily on Waves plugins and they are still not exporting as track effects or clip effects. All that is exported is the raw audio with no effects applied. When I play the timeline, the audio plugins work fine. Would you please fix this already?
I'm having the same issue with some Waves and Izotope plug-ins, but for me when I export directly out of Premiere the plug-in works, it's only an issue if I send it to AME. Really frustrating, I would like to batch export several sequences, but for now I can make it work by individually exporting directly from Premiere.
Im having the same issue! Plus lots more. Not impressed at all with premiere this far. So much buggs i dont even know what im paying for really. Just a laggy beta version? Man, dissapointed in adobe. Thinking of switching plattform all together.
I hope this will help you. The only thing you have to do is setup your plugin manager inside Audition, same way as you did in Premiere. I realized it when I tried to fix the export problem using Premiere's feature "open sequence in Audition". Basically, it ended with a message saying "there are plugins... and Audition is not able to find them". After this corection, export from Premeire using 3rd. side plug-ins works without problems for me, either through the Media encoder, or the connection between Premiere and Audition as well.
Yeah I'm noticing this too. While working Waves plug-ins work fine, but when QC'ing the export I notice that the audio is not properly exporting. I especially notice it when tracks are locked. When I have to unlock the audio tracks for Premiere to properly export with compression etc. and eventhen its flaky as hell. Theres nothing worse than having zero confidence in the apps, there is no consistency with this issue. Sometimes I have to go in and change a parameter to make the plug-in "wake-up" for export. Just not professional at all.
At this time The Adobe Creative cloud Suite is not a reliable nor professional set of apps. Such a shame, all that cash from our subscription... I had high hopes that there would be so much cash flow into Adobe that the apps would just work. Nope.
In order to get this sorted for you and anyone else that is having especially audio plugin troubles, we would really need for you to give more and specific details so we can get information to the devs on what's very specifically screwing up.
There's no way that they can know and test with every combination of hardware, media, and plugins out there. So when it's not working with one, they need information very specific to that to even have a clue where to go looking in the code.
Also, this forum is primarily a user-to-user peer support, people like me trying to help other users. The place to post for when one has good and specific details on what's going on badly, is of course their UserVoice system. That board is ported directly to the engineers, it pops onto their Slack channels immediately as it's posted by the users.
At NAB and MAX, I've had the opportunity to talk with program supervisors and especially with engineers. I've filed um ... quite a few, actually ... bug reports over the years. Or piled on with a supporting 'vote' and typically comments. To the point the engineers are familiar with my posts.
And they like mine, because ... I give full details. Deep details. They know specifically how to setup on what gear and what media/effects to get X unfortunate result. Sadly, most bug reports are "X is broken, fix it" ... and they don't know what gear it's on, what media, what other effects ... and such comments are unfortunately a total waste of time for troubleshooting/bug hunting.
I wish Adobe would spend some of the money each of us send to them every month on R&D. They should have the resources to make the best software in the world. Perhaps the real answer here is publishing approved and qualified system setups so that some of these issues pertaining to inferior systems can be rooted out. Anyway, my Friday whine.... and now for the wine. Cheers to you.
Hey, you wanna post a whine, c'mon, give us a good long one! I've certainly posted some epic rants here when I think a decision was ... less than optimal. And rants and whines are at times a cathartic part of the process.
795a8134c1