Just installed Wl 13.0.20. I cannot render my FABFILTER PRO-EQ. WL does a “render” but the output is not changed. I then did the whole process again on WL12 and everything worked as expected. Suggestions??? I tried it with FABFILTER 3 and 4 FWIW…
There are 4 different places in WaveLab where you can insert a plugin and numerous different methods of rendering.
Nobody will be able to help you without more details.
Fab-Filter Pro-4 renders OK in my setup.
I am on windows 10 with a I7 processor and 32 gigs of memory. I am using the rendering in the “editing window” just like I have done for years. I just checked and my setup is exactly the same in WL12 and WL13. I believe you are on a Mac and I am on a PC.
If you need additional information please let me know.
BTW I render “in place” if that makes a difference.
Are you eluding to the fact that you insert the plugin in the Master Section?
All of these trickling details matter if you want to help solve the issue.
Just saying “it doesn’t work” is not enough info to go off of.
This is probably not much help but i have tried to replicate the problem you describe but with different plugins although still from FabFilter.
Tested with the only two i have (Pro-DS and Pro-G).
Everything worked fine.
Edit window, applied the effects as “Render-In-Place” and the result was rendered.
Tried with one plugin at a time.
WL 13.0.20 with Windows 10.
FWIW
OK
I open the file in WL13.0.20 in the edit window. I choose Fabfileter ProEQ 3 in the master section. I have my rendering set for “render in place” I tell the computer to “render” by pushing the “render button” and the Editing window closes and I get another window and to the right of the screen is a button that says “start” and the progress bar at the bottom left of my screen shows it is processing. I save the file using “save as” and when I open it nothing has changed. I am trying to get out a really bad “spike” at 18,500 Hz but it is still there after rendering. WL12 works fine. I have had nothing but problems with WL13 since I first installed it on my machine. I uninstalled it numerous times and reinstalled it. I have had audio problems and for some reason parts of the editing window that have been changed will not save so it goes back to the window it first opened when I first installed it. Honestly I am sorry I ever updated to WL13 and that is the first time I have felt like this since I started using WL 30+ years ago. Any additional questions??? and if so could you be specific in what you need to now. Thanks!
YES I DO. I have WL13 setup exactly like WL12. In this instance WL12 renders and WL13 will not. FWIW
If that is the case, you will have to select the whole file (double click) and render, or WL will render a portion of your file that you might have had as a small selection.
Or you will have to change option to render whole file as in the picture below.
It would be wise to keep the Auto Select Source box checked (Render Tab), and you can avoid switching between Whole File, Selection etc.
YES…I do have it setup the way you have it “pictured”
I just tried to render again. But this time I used the “render” button in the “ribbon” and it worked. Something in my WL13.0.20 is messed up. I have three projects in house and really don’t need the problems with WL13. 
This is so strange!In my system the editing window doesn’t close, no “other” window opens and the progress bar is on the bottom, right besides the Transport commands.
My Render In Place is completely different.
Go figure.
Could it be that different Workspace settings produce such differences?
Weird.
A demo i’ve made with a different plugin (a Limiter, not FabFilter) only so that the resulting rendering would be visible.
Does your “Render-In-Place” have any similarities with this?
Yes, but when you click on Render in Master Section, a new window is opened. Ideally this should be a float window without the File, Import, etc. etc.
As you can see from the gif image i’ve shared, there’s no “other” window for Render-In-Place.
And “Render” is one thing, “Render.In.Place” is another thing.
The OP was trying to render in place by clicking on the Render Button and not the sub menu as you show in your gif.
No, I am not doing any real time rendering. Thanks for the reply.
Thanks for all the replies. Right now I can render from the “ribbon” rendering section and that works for me. I always used the “render” button in WL12’s master section and never had a problem with it.
No problem either.
I know, it’s even worse when a problem can’t be replicated because it’s no help at all but i’m here only because i wanted to help @Thomas_W_Bethel .
Sorry, i can’t replicate the problem.
__________
And here’s the same process but now with a FabFilter plugin.
As i said earlier i only have two FabFilter plugs (Pro-G and Pro-DS) so i’m doing the best i can. I’ve instantiated one single plugin in the Master section (FabFilter Pro-DS) made some exaggerated settings so that the resulting render could be seen instead of heard (besides, this recording doesn’t need any deessing so, bear with me please) and applied “Render In Place” following that longer method with the extra window, instead of the simple and straightforward ALT+A.
Here’s the result: it works again.
