Replies: 11 comments 5 replies
-
|
Nobody? Really? |
Beta Was this translation helpful? Give feedback.
-
|
I am using an NLS chain and it is going bananas! spikes only on VST client. |
Beta Was this translation helpful? Give feedback.
-
|
Sorry you're having trouble. But you're ahead of me. I can't get Waves version 15 to work at all. Is that the only plugin failing for you? And is it version 15? |
Beta Was this translation helpful? Give feedback.
-
|
It's the only plug-in I use in AG because usually they are very light on CPU. |
Beta Was this translation helpful? Give feedback.
-
|
I keep all the Waves on server, and also on DAW machine for use when I "freeze" or render the file. I have cleared the cache, reinstalled both AG and waves central along with the plugins. Even tried offline installer. Nothing is working. Any luck on your end? |
Beta Was this translation helpful? Give feedback.
-
|
I am on vacations now so there is no progress in that eradicated behavior on DSP meters. If I were you and have tried all that, I would just roll back to 14 to see how things are there. Assuming you don't need the V15. Can't think of anything else |
Beta Was this translation helpful? Give feedback.
-
|
Looks like I am having the same problem with Waves v15. I think it was working (or working better) under v14. But I had not used it very much. So not totally sure. After installing v15 the other day. Now most Waves plug-in's are not loading in to AG Server. Has anyone compiled AG using VS 2022? I have VS on the same computer. Is there anything I need to do or know about stepping through the code to try and locate the problem? For example, which cpp module should I focus on? If so, please let me know, and I will try to report back. Thanks, Tim |
Beta Was this translation helpful? Give feedback.
-
|
You're talking to the wrong guy with code! I stopped all that years ago, although my son works as a coder so I get good help when needed.
I'm still having the same problem. AG won't even recognize the Waves 15 plugins. Please let me know if you learn anything. And thanks!
…________________________________
From: TimReago ***@***.***>
Sent: Saturday, September 28, 2024 7:40 PM
To: apohl79/audiogridder ***@***.***>
Cc: mcaudio ***@***.***>; Author ***@***.***>
Subject: Re: [apohl79/audiogridder] Waves Ver.15 Update (Discussion #1373)
Looks like I am having the same problem with Waves v15. I think it was working (or working better) under v14. But I had not used it very much. So not totally sure. After installing v15 the other day. Now most Waves plug-in's are not loading. Has anyone compiled AG using VS 2022? I have VS on the same computer. Is there anything I need to do or know about stepping through the code to try and locate the problem? For example, which cpp module should I focus on to try and find the problem? If so, please let me know, and I will try to report back. Thanks, Tim
—
Reply to this email directly, view it on GitHub<#1373 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AVNU72NCAESEB2CRTEUFLMLZY5EBJAVCNFSM6AAAAABJ4TN652VHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTANZYGY2DOMA>.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
|
Hi,
I have not started to step through the code yet. I was hoping someone would be able to tell me where to set a break point, or at least which cpp file I should start focusing on to try to get Waves v15 working. I did drop back to Waves v14, and that is still working. I had copies of Waves v14 on offline install disks.
I am working on a lot of computer code that is new to me right now, over 2 million lines of new code. My time is already way over scheduled. It really would helpful to know where to focus the attempt to discover why AG is not loading Wave v15. Poking around from scratch could cost a week or two or more of work, and I would prefer to use that time more wisely. If anyone can tell me which cpp file(s) I should focus on, or even better, which loader function name(s) to set break points on. Then I may be able to locate the problem within a reasonable amount of time. If so, I will let you know what I find. And I may or may not also some additional help in figuring out how to fix the problem.
I have yet not looked at the AG code in any detail. But, just guessing, Waves may have changed it's file and/or interface format for v15. If so, some feature in VST3 may not have been included in AG that Waves started using as of v15. Like maybe a call to a VST3 interface function that is failing.
It would be helpful to me, if I could get v15 up and running inside of AG. But if the fix is going to turn out to be too great of a drain on time, I may have to rely on v14.
Thanks,
Tim
From: "mcaudio" ***@***.***>
To: "apohl79/audiogridder" ***@***.***>
Cc: "TimReago" ***@***.***>, "Comment" ***@***.***>
Sent: Thursday, October 24, 2024 7:05:37 PM
Subject: Re: [apohl79/audiogridder] Waves Ver.15 Update (Discussion #1373)
You're talking to the wrong guy with code! I stopped all that years ago, although my son works as a coder so I get good help when needed.
I'm still having the same problem. AG won't even recognize the Waves 15 plugins. Please let me know if you learn anything. And thanks!
…________________________________
From: TimReago ***@***.***>
Sent: Saturday, September 28 , 2024 7:40 PM
To: apohl79/audiogridder ***@***.***>
Cc: mcaudio ***@***.***>; Author ***@***.***>
Subject: Re: [apohl79/audiogridder] Waves Ver.15 Update (Discussion #1373)
Looks like I am having the same problem with Waves v15. I think it was working (or working better) under v14. But I had not used it very much. So not totally sure. After installing v15 the other day. Now most Waves plug-in's are not loading. Has anyone compiled AG using VS 2022? I have VS on the same computer. Is there anything I need to do or know about stepping through the code to try and locate the problem? For example, which cpp module should I focus on to try and find the problem? If so, please let me know, and I will try to report back. Thanks, Tim
—
Reply to this email directly, view it on GitHub< [ #1373 (comment) | #1373 (comment) ] >, or unsubscribe< [ https://github.com/notifications/unsubscribe-auth/AVNU72NCAESEB2CRTEUFLMLZY5EBJAVCNFSM6AAAAABJ4TN652VHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTANZYGY2DOMA | https://github.com/notifications/unsubscribe-auth/AVNU72NCAESEB2CRTEUFLMLZY5EBJAVCNFSM6AAAAABJ4TN652VHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTANZYGY2DOMA ] >.
You are receiving this because you authored the thread.Message ID: ***@***.***>
—
Reply to this email directly, [ #1373 (comment) | view it on GitHub ] , or [ https://github.com/notifications/unsubscribe-auth/BIMSAW2UKKHU5AYRZQEHYHTZ5F4MDAVCNFSM6AAAAABJ4TN652VHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTCMBUGYYTSOA | unsubscribe ] .
You are receiving this because you commented. Message ID: < ***@***.*** >
|
Beta Was this translation helpful? Give feedback.
-
|
I have not started to step through the code yet. I was hoping someone would be able to tell me where to set a break point, or at least which cpp file I should start focusing on to try to get Waves v15 working. I did drop back to Waves v14, and that is still working. I had copies of Waves v14 on offline install disks. I am working on a lot of computer code right now, over 2 million lines of new code. My time is already way over scheduled. It really would be helpful to know where to focus the attempt to discover why AG is not loading Wave v15. Poking around from scratch could cost a week or two or more of work, and I would prefer to use that time more wisely. If anyone can tell me which cpp file(s) I should focus on, or even better, which loader function name(s) to set break points on. Then I may be able to locate the problem within a reasonable amount of time. If so, I will let you know what I find. And I may or may not also need some additional help in figuring out how to fix the problem. I have yet not looked at the AG code in any detail. But, just guessing, Waves may have changed it's file and/or interface format for v15. If so, some feature in VST3 may not have been included in AG that Waves started using as of v15. Like maybe a call to a VST3 interface function that is now failing. It would be helpful to me, if I could get v15 up and running inside of AG. But if the fix is going to turn out to be too great of a drain on time, I may have to rely on v14. Thanks, |
Beta Was this translation helpful? Give feedback.
-
|
Plugin scanning happens mostly in JUCE. Take a look at Server::scanPlugin() in Server.cpp. AG server calls itself to scan a plugin. Check App.cpp for the cli interface. Not sure if a newer version of JUCE works better with the latest waves version, buts thats where you could get started. Upgrading JUCE requires porting some patches AG relies on, but it is usually not a big deal. |
Beta Was this translation helpful? Give feedback.
-
|
I was able to install Waves V15 stand-alone plugins on Win 10 22H2 into the latest AudioGridderServer, including: regular Waves plugins and StudioVerse. I tested on about 10 of the Waves plugins, and they appear to be accessible. What I am thinking is that the Waves "Bundles" are where the V15 loader problem is. May be something specific to the bundle packages, not yet being handled properly by JUCE. Or maybe it might have been an installer error. Not sure. In any event, if you use V15 stand-alone plugins, it looks like they work in the current AudioGridder. |
Beta Was this translation helpful? Give feedback.
-
|
Incredibly cool of you to keep me in mind! Wow! You're a kind man!!!
Never occurred to me that it could be the bundle. I can see that being the issue. I'll try it.
I really appreciate this! I owe you one just for your kindness. Rare thing anymore. If I can do you any favors please reach out. I'll let you know how it works.
Michael
…________________________________
From: TimReago ***@***.***>
Sent: Thursday, January 16, 2025 2:21 PM
To: apohl79/audiogridder ***@***.***>
Cc: mcaudio ***@***.***>; Author ***@***.***>
Subject: Re: [apohl79/audiogridder] Waves Ver.15 Update (Discussion #1373)
I was able to install Waves V15 stand-alone plugins on Win 10 22H2 into the latest AudioGridderServer, including: regular Waves plugins and StudioVerse. I tested on about 10 of the Waves plugins, and they appear to be accessible. What I am thinking is that the Waves "Bundles" are where the V15 loader problem is. May be something specific to the bundle packages, not yet being handled properly by JUCE. Or maybe it might have been an installer error. Not sure. In any event, if you use V15 stand-alone plugins, it looks like they work in the current AudioGridder.
—
Reply to this email directly, view it on GitHub<#1373 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AVNU72IOISGKQVVDZZIBQYT2LAIDJAVCNFSM6AAAAABJ4TN652VHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTCOBVHEZDGMA>.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
|
Quick question. Have you tried re-installing the version 15 bundle? I went try installing the stand-alones and it occurred to me that I can install the version 14 bundle with no problem, yet fifteen hasn't worked. I'm going to try it tomorrow. Session tonight. I'll let you know what happens.
…________________________________
From: TimReago ***@***.***>
Sent: Thursday, January 16, 2025 2:21 PM
To: apohl79/audiogridder ***@***.***>
Cc: mcaudio ***@***.***>; Author ***@***.***>
Subject: Re: [apohl79/audiogridder] Waves Ver.15 Update (Discussion #1373)
I was able to install Waves V15 stand-alone plugins on Win 10 22H2 into the latest AudioGridderServer, including: regular Waves plugins and StudioVerse. I tested on about 10 of the Waves plugins, and they appear to be accessible. What I am thinking is that the Waves "Bundles" are where the V15 loader problem is. May be something specific to the bundle packages, not yet being handled properly by JUCE. Or maybe it might have been an installer error. Not sure. In any event, if you use V15 stand-alone plugins, it looks like they work in the current AudioGridder.
—
Reply to this email directly, view it on GitHub<#1373 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AVNU72IOISGKQVVDZZIBQYT2LAIDJAVCNFSM6AAAAABJ4TN652VHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTCOBVHEZDGMA>.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
|
I don't think I tried to re-install V15 bundle. I think I installed it once (or possibly twice) and it did not seem to work. Although, as of tonight, I have seven of my cluster machines set up for running plugins. And only one of the seven is doing something odd that is similar to the V15 bundle problem, where it is showing bundles highlighted in red and instead of individual plugins. And for that one machine AG and the Waves plugins are not working as they are on the other six machines. All of the machines have fresh installs of Win 10 22H2. But some of the machines, including the one that is failing, were not a full reinstall where all Apps and Files were replaced. That suggests to me, that if a bundle was previously installed, and even after a reinstall of Windows 10 + 22H2 update. If Keep All Apps and Files was selected, and if an older version of the non-working V15 bundle was already present on that machine. Then maybe it continues to be corrupted (non-loading). |
Beta Was this translation helpful? Give feedback.
-
|
Very ingenious and probably correct. It seems ridiculous that I can install UAD and Plugin Alliance bundles with no hitch and this is a persistent problem.
I do need a better server. Mine barely supports Win 10 but is still working very well. I don't really do much with virtual instruments (although moving more in that direction) so the machine is not heavily taxed. I think I will try a fresh Windows install and see what happens. Everything else has failed. I can't even get the version 15 stand-alone plugins to work.
Note: After uninstalling ver 14 I did notice Audiogridder was still looking for that version even after re-installing AG. Lends creedence to your theory!
…________________________________
From: TimReago ***@***.***>
Sent: Friday, January 17, 2025 12:18 AM
To: apohl79/audiogridder ***@***.***>
Cc: mcaudio ***@***.***>; Author ***@***.***>
Subject: Re: [apohl79/audiogridder] Waves Ver.15 Update (Discussion #1373)
I don't think I tried to re-install V15 bundle. I think I installed it once (or possibly twice) and it did not seem to work.
Although, as of tonight, I have seven of my cluster machines set up for running plugins. And only one of the seven is doing something odd that is similar to the V15 bundle problem, where it is showing bundles highlighted in red and instead of individual plugins. And for that one machine AG and the Waves plugins are not working as they are on the other six machines.
All of the machines have fresh installs of Win 10 22H2. But some of the machines, including the one that is failing, were not a full reinstall where all Apps and Files were replaced.
That suggests to me, that if a bundle was previously installed, and even after a reinstall of Windows 10 + 22H2 update. If Keep All Apps and Files was selected, and if an older version of the non-working V15 bundle was already present on that machine. Then maybe it continues to be corrupted (non-loading).
—
Reply to this email directly, view it on GitHub<#1373 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AVNU72LVEQT37U473PBE7F32LCOCDAVCNFSM6AAAAABJ4TN652VHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTCOBWGI4DMOI>.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
Having a lot of trouble with AG and Waves ver. 15 update. Anyone else? Or workaround?
Beta Was this translation helpful? Give feedback.
All reactions