Waveform Problem Plugins

[Coil]

Have you tried un-sandboxing it?

yes!

[Watchful]

Other than reinstalling Wavestation to the latest version, not sure how to address this. It's working fine for me in WF11 and Win10, so I don't think it's a Waveform issue. I have heard some folks are having issues with new KLC on other DAWs, though, and reinstalling the problem plugins seems to help sometimes.

[Coil]

Thanks a lot for your answer!
i have already reinstalled the plugin with the same result.

[imstre]

Coil - you need to install microsoft visual c ++ 2005-2019 at x86-x64 version

[Coil]

Coil - you need to install microsoft visual c ++ 2005-2019 at x86-x64 version

hm, the following Korg PlugIns are running just fine with Tracktion on the same machine:

M1, MonoPoly, Polysix, MS20

also all PlugIns (including Wavestation) are running with Reaper

[Watchful]

Does its standalone version run fine? I read elsewhere that KLC install plugins in 2 locations... I want to say a Korg directory and a Steinberg one. If one doesn't work, try the other.

[gpkcaminha]

Edit: was able to fix this by enabling DPI awareness by right clicking the plugin. I had tried that before but this time I left it enabled and restarted Waveform. It kept the configuration and if I add another instance of the plugin the setting is enabled too.

Having this issue with a few plugins... Waveform 11. when I open them they use part of the window. Some of them I can resize and as soon as I do that they use the full window. But for this one (Ascension) I can't resize the screen so it gets stuck like that. It has a UI scale option inside the settings but it's super annoying having to do that all the time specially since the mouse cursor doesn't map correctly, so for example to open the "options" button I need to blindly click on the black top-right part of the window until I hit it.

Tried un-sandboxing it and also changing Waveform's Display scale. Doesn't seem to matter if the plugins are VST or VST3.

[yingfan]

all instruments of arturia v collection not respond on waveform.
no sound even click the key on window directly. on other daws they just work fine.
no clues on neither arturia nor tracktion waveform's website.
so i use reaper instead...
======
update 2020/12/18
works again after update.

[Coil]

Coil - you need to install microsoft visual c ++ 2005-2019 at x86-x64 version

i have had this installed already

[Coil]

The standalone version is running fine, also the plugin works nice with reaper on the same machine

Code: Select all

[i][quote]pluginval v0.2.9 - JUCE v6.0.1
Started validating: C:\# Audio Plugins\Korg\VstPlugins\KORG\WAVESTATION.dll
Random seed: 0x1d37c37
Validation started: 12 Dec 2020 9:04:34am

Strictness level: 5
-----------------------------------------------------------------
Starting test: pluginval / Scan for known types: C:\# Audio Plugins\Korg\VstPlugins\KORG\WAVESTATION.dll...
Num types found: 1

Testing plugin: VST-WAVESTATION-1540e426-4b4c5756
KORG: WAVESTATION v3.35.54.944
[b]All tests completed successfully[/b]
-----------------------------------------------------------------
Starting test: pluginval / Open plugin (cold)...

Time taken to open plugin (cold): 598 ms
[b]All tests completed successfully[/b]
-----------------------------------------------------------------
Starting test: pluginval / Open plugin (warm)...

Time taken to open plugin (warm): 456 ms
Running tests 1 times
[b]All tests completed successfully[/b]
-----------------------------------------------------------------
Starting test: pluginval / Plugin info...

Plugin name: WAVESTATION
Alternative names: WAVESTATION
SupportsDoublePrecision: no
Reported latency: 0
Reported taillength: 0

Time taken to run test: 0
[b]All tests completed successfully[/b]
-----------------------------------------------------------------
Starting test: pluginval / Plugin programs...
Num programs: 50
All program names checked

Changing program

Time taken to run test: 0
[b]All tests completed successfully[/b]
-----------------------------------------------------------------
Starting test: pluginval / Editor...

Time taken to open editor (cold): 225 ms
Time taken to open editor (warm): 218 ms

Time taken to run test: 449 ms
[b]All tests completed successfully[/b]
-----------------------------------------------------------------
Starting test: pluginval / Open editor whilst processing...

Time taken to run test: 221 ms
[b]All tests completed successfully[/b]
-----------------------------------------------------------------
Starting test: pluginval / Audio processing...
Testing with sample rate [44100] and block size [64]
Testing with sample rate [44100] and block size [128]
Testing with sample rate [44100] and block size [256]
Testing with sample rate [44100] and block size [512]
Testing with sample rate [44100] and block size [1024]
Testing with sample rate [48000] and block size [64]
Testing with sample rate [48000] and block size [128]
Testing with sample rate [48000] and block size [256]
Testing with sample rate [48000] and block size [512]
Testing with sample rate [48000] and block size [1024]
Testing with sample rate [96000] and block size [64]
Testing with sample rate [96000] and block size [128]
Testing with sample rate [96000] and block size [256]
Testing with sample rate [96000] and block size [512]
Testing with sample rate [96000] and block size [1024]

Time taken to run test: 18 ms
[b]All tests completed successfully[/b]
-----------------------------------------------------------------
Starting test: pluginval / Non-releasing audio processing...
Testing with sample rate [44100] and block size [64]
Testing with sample rate [44100] and block size [128]
Testing with sample rate [44100] and block size [256]
Testing with sample rate [44100] and block size [512]
Testing with sample rate [44100] and block size [1024]
Testing with sample rate [48000] and block size [64]
Testing with sample rate [48000] and block size [128]
Testing with sample rate [48000] and block size [256]
Testing with sample rate [48000] and block size [512]
Testing with sample rate [48000] and block size [1024]
Testing with sample rate [96000] and block size [64]
Testing with sample rate [96000] and block size [128]
Testing with sample rate [96000] and block size [256]
Testing with sample rate [96000] and block size [512]
Testing with sample rate [96000] and block size [1024]

Time taken to run test: 24 ms
[b]All tests completed successfully[/b]
-----------------------------------------------------------------
Starting test: pluginval / Plugin state...

Time taken to run test: 0
[b]All tests completed successfully[/b]
-----------------------------------------------------------------
Starting test: pluginval / Automation...
Testing with sample rate [44100] and block size [64] and sub-block size [32]
Testing with sample rate [44100] and block size [128] and sub-block size [32]
Testing with sample rate [44100] and block size [256] and sub-block size [32]
Testing with sample rate [44100] and block size [512] and sub-block size [32]
Testing with sample rate [44100] and block size [1024] and sub-block size [32]
Testing with sample rate [48000] and block size [64] and sub-block size [32]
Testing with sample rate [48000] and block size [128] and sub-block size [32]
Testing with sample rate [48000] and block size [256] and sub-block size [32]
Testing with sample rate [48000] and block size [512] and sub-block size [32]
Testing with sample rate [48000] and block size [1024] and sub-block size [32]
Testing with sample rate [96000] and block size [64] and sub-block size [32]
Testing with sample rate [96000] and block size [128] and sub-block size [32]
Testing with sample rate [96000] and block size [256] and sub-block size [32]
Testing with sample rate [96000] and block size [512] and sub-block size [32]
Testing with sample rate [96000] and block size [1024] and sub-block size [32]

Time taken to run test: 3 ms
[b]All tests completed successfully[/b]
-----------------------------------------------------------------
Starting test: pluginval / Editor Automation...

Time taken to run test: 1 sec
[b]All tests completed successfully[/b]
-----------------------------------------------------------------
Starting test: pluginval / Automatable Parameters...

Time taken to run test: 0
[b]All tests completed successfully[/b]
-----------------------------------------------------------------
Starting test: pluginval / Basic bus...
[b]All tests completed successfully[/b]
-----------------------------------------------------------------
Starting test: pluginval / Listing available buses...
Inputs:
	Named layouts: None
	Discrete layouts: None
Outputs:
	Named layouts: Stereo, Stereo
	Discrete layouts: None
Main bus num input channels: 0
Main bus num output channels: 2
All tests completed successfully
-----------------------------------------------------------------
Starting test: pluginval / Enabling all buses...
[b]All tests completed successfully[/b]
-----------------------------------------------------------------
Starting test: pluginval / Disabling non-main busses...
!!! WARNING: Disabling non-main buses failed
[b]All tests completed successfully[/b]
-----------------------------------------------------------------
Starting test: pluginval / Restoring default layout...
Main bus num input channels: 0
Main bus num output channels: 2

Time taken to run test: 0

Time taken to run all tests: 3 secs
[b]All tests completed successfully[/b]

Finished validating: C:\# Audio Plugins\Korg\VstPlugins\KORG\WAVESTATION.dll
ALL TESTS PASSED  :party:[/quote][/i]

ALL TESTS PASSED

WS.JPG

[pough]

Yes, the standalone version is running fine, also the plugin works nice with reaper on the same machine so this seams to be, like many times in the past, a tracktion thing.

after 7 years buying their software i don`t belive that i will give them another try in the future anymore
Just have a look how long this thread is

TSC does have the unenviable position of being relatively strict in its adherence to standards while being viewed as not worth considering by plugin vendors. The few times an issue has been the fault of TSC (like JUCE VST3 plugins not rendering properly) has been fixed. Other cases require changes from the plugin makers. Yes, even when those plugins "work fine" in other DAWs. I doubt Korg will bother to look into this issue, so if using Korg plugins is a must for you it's likely you will be better served by Reaper. Note, though, that Reaper can also have problems with plugins, just not necessarily the ones you're using. Just do a search for "plugin crash reaper" or check out the Reaper forums.

The built-in validator runs at a strictness level of 5/10. If you want to run stricter tests you can download the full validator.

https://github.com/Tracktion/pluginval/ ... tag/v0.2.9

Now... maybe it's time to see if I can track down the issues with Image-Line plugins in Waveform. I think this one is a Waveform issue because WF9 has no problems but WF11 bungs the presets on loading. Something changed.

[pough]

The latest version of Audio Damage Discord (v4.1.0a) seems to be causing very strange issues with Waveform. If I have an instance somewhere and I try to record anything, the main output of Waveform goes silent*. That's one of the strangest issues I've seen. Downgrading to v4.1.0 looks like things are normal.

* According to SPAN it's not going silent - the whole spectrum is filled. All frequencies at 100% volume.

UPDATE: Whoops! Nope, the slightly older version does the same. It seems to depend on the settings.

UPDATE 2: After lots of testing, I believe the problem is a combination of Discord4's LFOs in sync mode and Waveform recording.

1. Create new edit
2. Load Discord4
3. Turn LFO sync on
4. Arm an input and hit record

If one LFO is sync'd it will usually result in the audio output being flooded and going silent. If both LFOs are sync'd it will usually result in a crash.

Playback is fine. Recording does something weird that Discord4 does not like. These tests were also run in FL Studio and MU-LAB without any issues.

UPDATE 3: It might just be recording MIDI that causes the problem. I recorded some audio and things went fine. So what's special about recording MIDI that makes Discord4 go haywire?

BTW, Waveform PRO 11.1.0 running on Windows 10.

UPDATE 4: I finally got around to trying the beta (11.2.4) and can't get Discord4 to go buggy. So it seems like the problem will have been fixed with the next version, maybe.

[scotofil]

Apologies in advance if I am doing something wrong as this is my first attempt here; all constructive feedback would be appreciated!

I am using the free version of Waveform 11.1.0 on an x64 Win10 PC, and I am having issues with Unfiltered Audio's G8 v1.2: I am using the x64 vst3 version of the plugin and whenever I change the value of the Lookahead parameter, W11 crashes. This happens also when the plugin is sandboxed (experimental sandboxed parameters are disabled). Unfortunately there is no crash report generated at the usual location (AppData\Local\Temp\Waveform 11 Crash Logs\), and the normal log file (%AppData%\Tracktion\Waveform\Temporary\Waveform11Log.txt) does not contain anything specific either. I stripped down my use case to a single-track project containing a single 96kHz sample and only G8 is added to the track (apart from the default Volume & Pan and Level Meter Tracktion plugins). I am using ASIO and my interface (Focusrite 2nd gen Scarlett) is also at 96kHz (24bit), and the issue appears to persist regardless of my buffer size (initially I thought the problem might be related to setting the lookahead to a greater value than the buffer size, but that is apparently not the case, even if I set to e.g. 1ms W11 crashes). All pluginval tests pass. Let me know how I can help further and thanks in advance!

[Polluxmdq]

Hi all,

there is an issue with Waves InPhase. The plugin introduces a 20ms latency to be able to shift the audio back and forth, and this is correctly compensated in the track where the plugin is inserted. The thing is that it requires a sidechain input from the track you want to align against, and in the sidechain the latency is not compensated, making the plugin unusable>

[uselessdetails]

Captain Chords... (Mac). I can pop up the plugin window and it appears to display ok, but it doesn't pick up transport. Midi Madness 3 does, though, so I have to presume that the transport is available to the plugin.