LAUNCH! VAST Dynamics - Vaporizer2 - Hybrid Wavetable Additive / Subtractive Synthesizer / Sampler / Workstation

[neki]

What I see from the screenshot is that it seems to crash when loading a preset out the 5(!) years old soundbank from Che / sonic Sirius. Is that only related to those? Then I will concentrate testing on these legacy presets.

Yes, this preset has significant name - 'The Terminator'

I thought the same as you, so I started FlStudio again and loaded VST3 version of Vaporizer2, went to preset browser direct to The Terminator preset, and nothing crashed, or froze. But, maybe this means nothing.

Thing is - I bought Vaporizer2 in 2021., and I installed some banks from Che. So maybe you're right, and concentrate testing on these legacy presets.

[Korg Supporter]

I am still having the inconsistent note issue when modulating pitch with the LFO and then removing the modulation target.

This should be fixed here now:
https://github.com/VASTDynamics/Vaporiz ... _3.4.0.zip

Thank you!

[vastdynamics]

Strange. I did a 20 Minutes "gorilla test" here in cakewalk and do not manage to crash it. If you have "instructions" on how exactly to reproduce it would be appreciated

Yes, it is strange, because I can't give you exact instructions - but I have now also managed to crash down FLStudio with VST3 version, as in this picture (Windows messages are in Croatian language, meaning - FL Studio is not responding, blah, blah):

FLStudio.JPG

So, it's all about clicking in preset browser, and being patient

But, maybe this is specific to my PC configuration and OS, who knows?
Maybe you should wait, and see if others have the same problem...

Another thing that would be helpful as a test woul be to disable the OpenGL graphics temporarily in the plugin settings (Preset>Disable Gfx = X) to see if it is related to that. This could maybe explain different systems behavior ...

[neki]

Another thing that would be helpful as a test woul be to disable the OpenGL graphics temporarily in the plugin settings (Preset>Disable Gfx = X) to see if it is related to that. This could maybe explain different systems behavior ...

I tried disabling OpenGL, but FlStudio froze again

However, no matter potential problems with legacy presets, there is still the other problem: VST3 version is not recognized as VST3 plugin on my Win 10 system by Reason 12, nor by Tracktion Waveform 12. Maybe this is Reason 12 and Waveform 12 problem, but who knows?

Thanks, anyway...

[DaveClark]

However, no matter potential problems with legacy presets, there is still the other problem: VST3 version is not recognized as VST3 plugin on my Win 10 system by Reason 12, nor by Tracktion Waveform 12. Maybe this is Reason 12 and Waveform 12 problem, but who knows?

Is there an official SHA-256 or MD5 sum available? I couldn't find one.... Might help those who find the result above.

Edit: Samplitude Pro X7 Suite does not recognize VST3 version; Tracktion 12.5.3 does not recognize VST3 version. VST3 version works in Cubase Artist 13, FL Studio 21, Cakewalk by Bandlab 2023.09 Build 075, and Mixcraft 10 Pro Studio.

Edit 2: Also works in Bitwig Studio 8-Track v. 5.0.11.

[imaginowsky]

Hey everyone.

Since I couldn't find the solution anywhere, I thought I'd request help here.
I have this strange behaviour of Vaporizer2, when it changes pitch of my typing keyboard as MIDI input (Ctrl+T) in FL Studio 21.2.1. Everytime I left-click anywhere on the GUI of Vaporizer2 and play, the synth does not register pitch the same as when I click back on the top bar of the plugin wrapper window, or highlight/select the plugin in the Channel Rack. Doing the latter two makes midi playback go back to normal. You can observe which piano notes are highlighted in Vaporizer2 and how they change as you click in and out of the plugin in FL. Both version 3.3.0 and 3.4.0 seem to have that.

Thank you in advance, best regards

[vastdynamics]

However, no matter potential problems with legacy presets, there is still the other problem: VST3 version is not recognized as VST3 plugin on my Win 10 system by Reason 12, nor by Tracktion Waveform 12. Maybe this is Reason 12 and Waveform 12 problem, but who knows?

Is there an official SHA-256 or MD5 sum available? I couldn't find one.... Might help those who find the result above.

Edit: Samplitude Pro X7 Suite does not recognize VST3 version; Tracktion 12.5.3 does not recognize VST3 version. VST3 version works in Cubase Artist 13, FL Studio 21, Cakewalk by Bandlab 2023.09 Build 075, and Mixcraft 10 Pro Studio.

If it reoccurs and you have a crashreport.log file in your /applications/Vaporizer2 or /Program Files/Vaporizer2 folder it would be great if you could paste the content to me via PM. Thank you.

[vastdynamics]

Hey everyone.

Since I couldn't find the solution anywhere, I thought I'd request help here.
I have this strange behaviour of Vaporizer2, when it changes pitch of my typing keyboard as MIDI input (Ctrl+T) in FL Studio 21.2.1. Everytime I left-click anywhere on the GUI of Vaporizer2 and play, the synth does not register pitch the same as when I click back on the top bar of the plugin wrapper window, or highlight/select the plugin in the Channel Rack. Doing the latter two makes midi playback go back to normal. You can observe which piano notes are highlighted in Vaporizer2 and how they change as you click in and out of the plugin in FL. Both version 3.3.0 and 3.4.0 seem to have that.

Thank you in advance, best regards

Hm, Vaporizer2 grabs keyboard input whenver the plugin editor is focussed. Keyboard input then goes to the MIDI keyboard in the plugin itself. Could you be more specific what goes wrong here with that?

[Parduz]

Hey everyone.

Since I couldn't find the solution anywhere, I thought I'd request help here.
I have this strange behaviour of Vaporizer2, when it changes pitch of my typing keyboard as MIDI input (Ctrl+T) in FL Studio 21.2.1. Everytime I left-click anywhere on the GUI of Vaporizer2 and play, the synth does not register pitch the same as when I click back on the top bar of the plugin wrapper window, or highlight/select the plugin in the Channel Rack. Doing the latter two makes midi playback go back to normal. You can observe which piano notes are highlighted in Vaporizer2 and how they change as you click in and out of the plugin in FL. Both version 3.3.0 and 3.4.0 seem to have that.

Thank you in advance, best regards

Hm, Vaporizer2 grabs keyboard input whenver the plugin editor is focussed. Keyboard input then goes to the MIDI keyboard in the plugin itself. Could you be more specific what goes wrong here with that?

Fl Studio captures the keyboard events to play notes when you click on the bar of the plugin window, but (tries to) let the plugin handle them when you click on the plugin interface.

Vaporizer2 handles the key ==> note played differently, also depending on the user keyboard layout.
Could be this the problem?

[Hanz Meyzer]

Wow such a nice synth! The GUI is nicely straightforward, I love that. Now also works natviely on my ARM machine.

[imaginowsky]

Hey everyone.

Since I couldn't find the solution anywhere, I thought I'd request help here.
I have this strange behaviour of Vaporizer2, when it changes pitch of my typing keyboard as MIDI input (Ctrl+T) in FL Studio 21.2.1. Everytime I left-click anywhere on the GUI of Vaporizer2 and play, the synth does not register pitch the same as when I click back on the top bar of the plugin wrapper window, or highlight/select the plugin in the Channel Rack. Doing the latter two makes midi playback go back to normal. You can observe which piano notes are highlighted in Vaporizer2 and how they change as you click in and out of the plugin in FL. Both version 3.3.0 and 3.4.0 seem to have that.

Thank you in advance, best regards

Hm, Vaporizer2 grabs keyboard input whenver the plugin editor is focussed. Keyboard input then goes to the MIDI keyboard in the plugin itself. Could you be more specific what goes wrong here with that?

Thank you for your response. To replicate the issue and observe the pitch variation, follow these steps:

1. Add Vaporizer2 to "Channel Rack" (F6).
2. Open Vaporizer2.
3. Within Vaporizer2's interface, click anywhere (button/knob or empty space) and play MIDI notes using your computer keyboard (Ctrl+T). Take note of how the internal piano roll of Vaporizer2 highlights the played notes.
4. Play the same MIDI pattern using the computer keyboard after shifting focus away from the plugin. To do this, either click on the top bar of the plugin wrapper or select Vaporizer2 in the FL's Channel Rack by clicking on the rectangular MIDI input meter. Continue playing with the computer keyboard as MIDI input as you shift focus in/out of the plugin to notice difference in pitch/sound and notes registered by Vaporizer2's internal piano roll.

For additional context, I've experimented with launching Vaporizer2 in FL Patcher or using third-party plugin wrapper like "Kushview Element" within FL. I also explored switching and locking the PC keyboard to different scales/root notes using FL's built-in scale/root lock feature (accessible by right-clicking the button activated by Ctrl+T). All results in the same pitch behaviour/change as you switch in and out of the Vaporizer2's GUI.

I hope this clarifies things

[vastdynamics]

Wow such a nice synth! The GUI is nicely straightforward, I love that. Now also works natviely on my ARM machine.

Thank you

[DaveClark]

If it reoccurs and you have a crashreport.log file in your /applications/Vaporizer2 or /Program Files/Vaporizer2 folder it would be great if you could paste the content to me via PM. Thank you.

No crashreport.log found anywhere I looked. The VST3 version isn't passing the plugin scan. The VST3 plugin isn't available in the list of plugins, but the VST2 version is.

No crashes have occurred that I recall with any host.

I thought about compiling a debug version of Vaporizer2, but don't have JUCE installed here yet. Not sure that this would help with these cases, though, because it's failing in scan, and I don't have source for hosts!

[DaveClark]

Regarding the problem described by imaginowsky:

<snip>

Continue playing with the computer keyboard as MIDI input as you shift focus in/out of the plugin to notice difference in pitch/sound and notes registered by Vaporizer2's internal piano roll.

<snip>

I've confirmed this with FL Studio. The same problem exists with Cubase Artist 13. Certain QWERTY keys are transposed, others are the same.

[neki]

If it reoccurs and you have a crashreport.log file in your /applications/Vaporizer2 or /Program Files/Vaporizer2 folder it would be great if you could paste the content to me via PM. Thank you.

No crashreport.log found anywhere I looked. The VST3 version isn't passing the plugin scan. The VST3 plugin isn't available in the list of plugins, but the VST2 version is.

No crashes have occurred that I recall with any host.

I thought about compiling a debug version of Vaporizer2, but don't have JUCE installed here yet. Not sure that this would help with these cases, though, because it's failing in scan, and I don't have source for hosts!

Infact, in Tracktion Waveform 12 there is option to validate single plugin file, and together with advanced options set via Settings->Advanced->Plugin Processing you can get some kind of scan log for that plugin.
So here is scan log for Vaporizer2 VST3:

Started validating: C:\Program Files\Common Files\VST3\VASTvaporizer2.vst3\VASTvaporizer2.vst3\Contents\x86_64-win\VASTvaporizer2.vst3
Random seed: 0x64729d2
Validation started
Strictness level: 5
-----------------------------------------------------------------
Starting tests in: pluginval / Scan for plugins located in: C:\Program Files\Common Files\VST3\VASTvaporizer2.vst3\VASTvaporizer2.vst3\Contents\x86_64-win\VASTvaporizer2.vst3...
Num plugins found: 1

Testing plugin: VST3-Vaporizer2-2b3babce-1a967cc8
VAST Dynamics: Vaporizer2 v3.4.0
Completed tests in pluginval / Scan for plugins located in: C:\Program Files\Common Files\VST3\VASTvaporizer2.vst3\VASTvaporizer2.vst3\Contents\x86_64-win\VASTvaporizer2.vst3
-----------------------------------------------------------------
Starting tests in: pluginval / Open plugin (cold)...
Completed tests in pluginval / Open plugin (cold)
-----------------------------------------------------------------
Starting tests in: pluginval / Open plugin (warm)...
Running tests 1 times
Completed tests in pluginval / Open plugin (warm)
-----------------------------------------------------------------
Starting tests in: pluginval / Plugin info...

Plugin name: Vaporizer2
Alternative names: Vaporizer2
SupportsDoublePrecision: no
Reported latency: 0
Reported taillength: 0
Completed tests in pluginval / Plugin info
-----------------------------------------------------------------
Starting tests in: pluginval / Plugin programs...
Num programs: 1247
All program names checked

Changing program
Completed tests in pluginval / Plugin programs
-----------------------------------------------------------------
Starting tests in: pluginval / Editor...
Completed tests in pluginval / Editor
-----------------------------------------------------------------
Starting tests in: pluginval / Open editor whilst processing...
Completed tests in pluginval / Open editor whilst processing
-----------------------------------------------------------------
Starting tests in: 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]
Completed tests in pluginval / Audio processing
-----------------------------------------------------------------
Starting tests in: pluginval / Plugin state...
Completed tests in pluginval / Plugin state
-----------------------------------------------------------------
Starting tests in: 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]
Completed tests in pluginval / Automation
-----------------------------------------------------------------
Starting tests in: pluginval / Editor Automation...
Completed tests in pluginval / Editor Automation
-----------------------------------------------------------------
Starting tests in: pluginval / Automatable Parameters...
Completed tests in pluginval / Automatable Parameters
-----------------------------------------------------------------
Starting tests in: pluginval / auval...
Completed tests in pluginval / auval
-----------------------------------------------------------------
Starting tests in: pluginval / vst3 validator...
INFO: Skipping vst3 validator as validator path hasn't been set
Completed tests in pluginval / vst3 validator
-----------------------------------------------------------------
Starting tests in: pluginval / Basic bus...
Completed tests in pluginval / Basic bus
-----------------------------------------------------------------
Starting tests in: pluginval / Listing available buses...
Inputs:
Named layouts: Stereo
Discrete layouts: None
Outputs:
Named layouts: Stereo
Discrete layouts: None
Main bus num input channels: 2
Main bus num output channels: 2
Completed tests in pluginval / Listing available buses
-----------------------------------------------------------------
Starting tests in: pluginval / Enabling all buses...
Completed tests in pluginval / Enabling all buses
-----------------------------------------------------------------
Starting tests in: pluginval / Disabling non-main busses...
Completed tests in pluginval / Disabling non-main busses
-----------------------------------------------------------------
Starting tests in: pluginval / Restoring default layout...
Main bus num input channels: 2
Main bus num output channels: 2
Completed tests in pluginval / Restoring default layout

To be honest, I don't see anything suspicious, except: 'INFO: Skipping vst3 validator as validator path hasn't been set' - but I don't have a clue what it means... hope this may help.