They’re pretty good about getting back although sometimes there are lapses of a few weeks between emails. Maybe PG can offer some info on your particular crash when pressing play, but it would also be worth emailing FabFilter support. Folding and unfolding the plugin GUI, or moving to another plugin and back fixes the stretched GUI.įabFilter says they reported the Wavelab bug they found to the Wavelab developer but haven’t heard back about it. Turning off graphics acceleration solves the problem but of course, then the graphics don’t look as smooth and the GUI is one of the highlights of Pro-L and many other FabFilter plugins. This makes it hard to actually adjust parameters because the buttons are not where they should be. The problem is that the GUI can become stretched out irregularly horizontally when it shares a plugin chain window with other shaped plugins. Pro-Q 2 and Pro-MB don’t have the graphics issue anymore, but Pro-L and Saturn still do as they haven’t been updated in awhile.
There are also some graphics bugs that FabFilter claims is a Wavelab bug but they have been implementing workarounds on their end for now.
Something about the presets seem to trigger the rendering crash. just loading Pro-Q 2 and dialing something in from it’s default state. I often felt my rendering crashes were related to recalling presets and tweaking vs. Usually after this happened one time it wouldn’t happen again in a given montage. Especially if the VST3 preset had a CPU heavy preset like Linear Phase - High, then the audio would be very jittery and distorted until I stopped the transport and restarted it. The only playback related issue I’ve seen with FabFilter is if I start a new montage, add some audio files, play the transport, drop Pro-Q 2 on a clip insert and recall a VST3 preset. It still happens to this day but I try to work around it and avoid it. I couldn’t pin the crash on FabFilter or UAD but something was certainly causing the crash about 70% of the time. If I moved the UAD to the track insert, the crash wouldn’t happen. Recalling VST3 presets and/or WL plugin chain settings seemed to induce the problem fairly easy. It was a very bizarre crash because it was only re-produceable if I had Pro-Q 2 VST3 on an audio clip, a UAD plugin in the first slot on the montage master, and then FabFilter Pro-L VST3 after that. My FabFilter crashes always happened during renders of DDP files or rendering WAVs of each CD track from a montage. I’ve never had Wavelab crash simply from pressing play with Pro-Q2 inserted. I was using VST2 Pro-L for a bit to troubleshoot a different crashing problem earlier this year. I pretty much only use VST3 FabFilter in WL 8.5.30. In my screen shot of the menu, notice that the Sonnox and UAD plugins don’t have the /// next to them because they do not offer VST3 plugins yet. no banks in the preset section is the biggest clue for me. I’ll have find it but generally speaking, the banks vs. That being said…I can’t remember what plugin in is, but I am pretty sure I saw a case where a VST2 plugin had a VST3 style menu or maybe it was the opposite. VST2 has “banks” where VST3 has what I call more of a normal preset menu. The way I can tell is that the preset menus for VST2 and VST3 are different.
Wavelab 8.5 no audio in windows 10 2019 how to#
I’m guessing you may already have known that and just meant how to tell after it’s loaded… / (kind of like the Adidas logo), it means that it’s a VST3 plugin. It’s kind of subtle (to me anyway) but you’ll notice in plugin menus that if you see 3 slashes by the name like this: Is this something that could be fixed for the FabFilter VST2 on clips, or something to report to FabFilter if it’s on their end?Īlso, after finding this, there is one thing I would like to ask: Is there is a way to tell which version of the plugin (VST2 or VST3) you’re using once the plugin is loaded in the program? I couldn’t find any indication of path or filename for the plugins once loaded in Wavelab, and I couldn’t see any indication on the plugin itself. I didn’t try them as Track or Montage Master plugins, so I don’t know what happens when they’re used there. The FabFilter VST2 seem to work OK in the Master Section but not as clip plugins (at least not here). The VST3 seem to have no problem at all as clip plugins. So I went back and loaded the FabFilter VST3 versions as clip plugins, and those didn’t crash. Then I tried the FabFilter Multiband as a clip plugin, and got the same crash.īut it turns out I had unintentionally loaded the FabFilter VST2 version plugins. I went to play the clip, and it crashed, with a cascade of “a serious error has occurred inside the plugin…” messages. I opened an audio file in a montage and added FabFilter EQ as a clip plugin. I just got the same problem today while trying out Wavelab 8.5.30 for the first time.
0 kommentar(er)
