Waveform Problem Plugins
-
- KVRer
- 11 posts since 7 Apr, 2019
MTPowerDrumKit is acting up with anything else that 11.5.2. The mixer portion of the plugin is unusable now. The drop down menu to chose the out channel is either not drawing up correctly and unresponsive to the mouse click on the channel# or as of 11.5.17 it pops and retracts by itself.
Reinstalled the plugin - same issue
Waveform 11.5.2 - works properly with the plugin
Waveform 11.5.9 - popup menu shows but is missing parts (drawing issues) and unresponsive
Waveform 11.5.17 - popup menu shows for a split second and retracts.
OS: Windows 10 20H2
HP Z600 with 48Gb RAM
X5670 Xeon CPUs
Reinstalled the plugin - same issue
Waveform 11.5.2 - works properly with the plugin
Waveform 11.5.9 - popup menu shows but is missing parts (drawing issues) and unresponsive
Waveform 11.5.17 - popup menu shows for a split second and retracts.
OS: Windows 10 20H2
HP Z600 with 48Gb RAM
X5670 Xeon CPUs
-
Peter Widdicombe Peter Widdicombe https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=336849
- KVRian
- 1205 posts since 29 Aug, 2014
VSTSynthFont64 hangs waveform completely if VST sandboxing is enabled; and appears to work normally if sandboxing disabled. Dreaded "Waveform is not responding" as soon as it is dragged into the VST slot end of a track.
Windows 10; Waveform 11.5.16.
Windows 10; Waveform 11.5.16.
Waveform 13; Win10 desktop/8 Gig; Win11 Laptop; MPK261; VFX+disfunctional ESQ-1
-
- KVRer
- 11 posts since 7 Apr, 2019
OK! the guys @ Manda are simply awesome. They replied within 30 min with a proper solution. That solution fixed my Izotope plugins as well. Simply enable/disable DPI aware feature on each plugin that has display/drawing issues and VOILA! fixed!basti78 wrote: Sat May 29, 2021 1:38 am MTPowerDrumKit is acting up with anything else that 11.5.2. The mixer portion of the plugin is unusable now. The drop down menu to chose the out channel is either not drawing up correctly and unresponsive to the mouse click on the channel# or as of 11.5.17 it pops and retracts by itself.
Reinstalled the plugin - same issue
Waveform 11.5.2 - works properly with the plugin
Waveform 11.5.9 - popup menu shows but is missing parts (drawing issues) and unresponsive
Waveform 11.5.17 - popup menu shows for a split second and retracts.
OS: Windows 10 20H2
HP Z600 with 48Gb RAM
X5670 Xeon CPUs
-
unholyeyebrows unholyeyebrows https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=495794
- KVRist
- 182 posts since 14 Feb, 2021
I'm getting plugin sandbox crashes with Arturia VST3 plugins. Their Pre 1973 plugin reliably causes this, but combinations of other VST3s from their V Collection 7 and FX Collection 2 can trigger the issue. Very easy to duplicate. Reaper and Bitwig seem to handle these fine.
I am running Waveform Pro 11.5.17 on Windows. Is anyone else experiencing the same problems?
I am running Waveform Pro 11.5.17 on Windows. Is anyone else experiencing the same problems?
Ryzen 5 8600G, 32GB DDR5, 4K, Ubuntu 26.04, Waveform Pro 13.5, Reaper 7, Ardour 9.
- KVRAF
- 4886 posts since 3 Jan, 2003 from Vancouver
Do they cause crashes when they're not sandboxed? The only reason to sandbox plugins is to avoid crashes of Waveform. If they're not crashing Waveform, sandboxing them is just adding another layer of complexity. I've noticed some plugins only have issues when they're sandboxed.unholyeyebrows wrote: Thu Jun 10, 2021 8:33 am I'm getting plugin sandbox crashes with Arturia VST3 plugins. Their Pre 1973 plugin reliably causes this, but combinations of other VST3s from their V Collection 7 and FX Collection 2 can trigger the issue. Very easy to duplicate. Reaper and Bitwig seem to handle these fine.
I am running Waveform Pro 11.5.17 on Windows. Is anyone else experiencing the same problems?
Surely there must be consensus by now...
-
unholyeyebrows unholyeyebrows https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=495794
- KVRist
- 182 posts since 14 Feb, 2021
With sandboxing disabled the audio engine crashes and Waveform requires a restart to recover.pough wrote: Thu Jun 10, 2021 5:23 pmDo they cause crashes when they're not sandboxed? The only reason to sandbox plugins is to avoid crashes of Waveform. If they're not crashing Waveform, sandboxing them is just adding another layer of complexity. I've noticed some plugins only have issues when they're sandboxed.unholyeyebrows wrote: Thu Jun 10, 2021 8:33 am I'm getting plugin sandbox crashes with Arturia VST3 plugins. Their Pre 1973 plugin reliably causes this, but combinations of other VST3s from their V Collection 7 and FX Collection 2 can trigger the issue. Very easy to duplicate. Reaper and Bitwig seem to handle these fine.
I am running Waveform Pro 11.5.17 on Windows. Is anyone else experiencing the same problems?
Ryzen 5 8600G, 32GB DDR5, 4K, Ubuntu 26.04, Waveform Pro 13.5, Reaper 7, Ardour 9.
- KVRian
- 973 posts since 24 Oct, 2006
FWIW, I just wanted to mention that, as of my upgrade to Waves 12, I am having no more crashes with Waves products and Waveform 11.5 (YAY!). I'm not sure what was changed, but the issues have disappeared.
I wish I could I could narrow down why this changed, but cannot; as Waves kept the suspected reasons for the crashes somewhat "close to the chest", they have played the solutions to the issue similarly.
Remind me never to play poker with Waves' support group.
Still, I'm grateful.
I wish I could I could narrow down why this changed, but cannot; as Waves kept the suspected reasons for the crashes somewhat "close to the chest", they have played the solutions to the issue similarly.
Remind me never to play poker with Waves' support group.
Still, I'm grateful.
“Madness, as you know, is like gravity: all it takes is a little push.”
- KVRer
- 6 posts since 23 Aug, 2006
Sforzando doesn't remember settings in Waveform Free 11.5.17 (in GarageBand, for example, it does). Not a big problem when using Sforzando on only one or two tracks but having to reload, say, an entire drum kit gets to be...tedious.
-
Danilo Villanova Danilo Villanova https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=418331
- KVRian
- 1196 posts since 30 Apr, 2018
Are you running it sandoxed? I saw on a vide that it needed to be sandboxed in Waveform.
- KVRAF
- 4886 posts since 3 Jan, 2003 from Vancouver
I'm running 11.5.17 Pro on Windows and I'm not having that problem. I loaded the VST2 and the VST3 versions of sforzando into an edit and they re-load with the instruments just fine.
sforzando 1.969
Instruments: Soft Drums (from Pianobook) and Cassette Vibraphone (by ThePhonoLoop)
I tested with sforzando sandboxed and not-sandboxed.
Surely there must be consensus by now...
-
- KVRer
- 11 posts since 3 Aug, 2015 from Melbourne, Australia
I have recently upgraded to 11.5.18 and the Arturia FX plugins are loading but the GUI is not right.
Anytime this happened in the past, with prevoius upgrades, I would just delete and re-install the plugins and the issue would be solved. Today I have re-installed a few times, toggled DPI Awareness, etc. with no joy.
Everytime that I re-open the plugins I have to "resize the window" in the actual Arturia plugin menu for it to display correctly. Does anyone have an answer or a fix?
Anytime this happened in the past, with prevoius upgrades, I would just delete and re-install the plugins and the issue would be solved. Today I have re-installed a few times, toggled DPI Awareness, etc. with no joy.
Everytime that I re-open the plugins I have to "resize the window" in the actual Arturia plugin menu for it to display correctly. Does anyone have an answer or a fix?
-
- KVRist
- 52 posts since 6 Mar, 2010
Now that you mention this, I was getting the same with melodyne. For now, going back to .17 seems like the way to go.BigSkyAudio wrote: Mon Aug 16, 2021 8:03 am Everytime that I re-open the plugins I have to "resize the window" in the actual Arturia plugin menu for it to display correctly. Does anyone have an answer or a fix?
-
- KVRer
- 11 posts since 3 Aug, 2015 from Melbourne, Australia
I have never had to roll back before but will try it now and let you know how it goes.
