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

[vastdynamics]

Thank you. This is why I am wondering: Vaporizer2 also passes all tests in Steinberg‘s VST3 plugin test host and Apple’s auval as AU without a single error.
We will find out!

[Vitaly]

Hey VAST Dynamics, thank you so much for implementing microtuning!!!

[vastdynamics]

Hey VAST Dynamics, thank you so much for implementing microtuning!!!

You are welcome
Let me know if it is useful.

[DaveClark]

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.

Thanks for the hint about the Tracktion validate option. I'm not very familiar at all with Tracktion.

You normally would not have this "vst3 validator" installed as a user, but as a VST3 developer you would. It comes with VST3 SDK. It does a lot of things similar to what that Tracktion validate output showed, and it's executed whenever you compile a VST3. It's really nothing for you to worry about, and vastdynamics (Tobias) told us that the VST3 passes all Validator's tests anyway.

I ran Tracktion Validate File on several other instruments and found something interesting: Most instruments have a lot of layouts, but always seem to have Mono in addition to Stereo. Vaporizer 2 has only Stereo. This might be a problem for some DAWs. I'll have to admit that Kontakt player has zero inputs, so inputs may not be a problem (2 or 0 or many), but no mono output may be a problem.

[FrogsInPants]

Correct me if I'm wrong, but there doesn't seem to be any way to accurately keytrack a filter. The filter's cutoff responds to modulation linearly in frequency, so I would have to approximate an exponential response by adjusting the modulator's curve, but I'm only able to achieve a very rough approximation of an exponential. Or is there some way to modulate by semitones that I simply haven't been able to find?

[Atlatnesiti]

Downloaded and tested under Logic Pro, Cubase 13 Pro, Live 11 Suite and Reason 12.
Happy to inform that all apps mentioned above DON'T produce errors with VST3 or AU and Vaporizer ver.3.40 plugin works as intended
BTW; Mac mini PRO 12 core, 32GB Ram and 1TB SSD

[gentleclockdivider]

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

This keyboard focus issue occurs with certain plugins that use the juce framework.
Tal,sampler had it , but is now fixed , 99%. sure this is the same issue

[stoniegreen]

The latest update fixed the arp sync distortion issue in Akai MPC Beats/Software. Thanks so much for that.

[vastdynamics]

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.

Thanks for the hint about the Tracktion validate option. I'm not very familiar at all with Tracktion.

You normally would not have this "vst3 validator" installed as a user, but as a VST3 developer you would. It comes with VST3 SDK. It does a lot of things similar to what that Tracktion validate output showed, and it's executed whenever you compile a VST3. It's really nothing for you to worry about, and vastdynamics (Tobias) told us that the VST3 passes all Validator's tests anyway.

I ran Tracktion Validate File on several other instruments and found something interesting: Most instruments have a lot of layouts, but always seem to have Mono in addition to Stereo. Vaporizer 2 has only Stereo. This might be a problem for some DAWs. I'll have to admit that Kontakt player has zero inputs, so inputs may not be a problem (2 or 0 or many), but no mono output may be a problem.

Thank you for the hint. Adding an optional mono layout would be very easy.

[vastdynamics]

The latest update fixed the arp sync distortion issue in Akai MPC Beats/Software. Thanks so much for that.

Cool. Thank you. Bye the way. And of course it is anyhow expected like that: the ARP is now sample accurate in its timing when synchronized with the DAW. You should try that out. It is fun to have e.g. baselines with three steps synched to quarter notes.

[vastdynamics]

Downloaded and tested under Logic Pro, Cubase 13 Pro, Live 11 Suite and Reason 12.
Happy to inform that all apps mentioned above DON'T produce errors with VST3 or AU and Vaporizer ver.3.40 plugin works as intended
BTW; Mac mini PRO 12 core, 32GB Ram and 1TB SSD

Thank you! And we will make all DAWs work!

[andreasg]

I can not use it on my MacBook m1, i have an error message, that the plugin is not compatible with my Mac

[vastdynamics]

I can not use it on my MacBook m1, i have an error message, that the plugin is not compatible with my Mac

Where does the error message occur? In the installer? That would be strange. In 3.4.0 I removed all platform checks. You are sure it is 3.4.0?

[andreasg]

i've downloaded the last version this morning. the error message was in ableton 12 with the au version..
i cant test it now with the vst version because i've deinstalled the plugin now

[neki]

Thanks for the hint about the Tracktion validate option. I'm not very familiar at all with Tracktion.

You normally would not have this "vst3 validator" installed as a user, but as a VST3 developer you would. It comes with VST3 SDK. It does a lot of things similar to what that Tracktion validate output showed, and it's executed whenever you compile a VST3. It's really nothing for you to worry about, and vastdynamics (Tobias) told us that the VST3 passes all Validator's tests anyway.

I ran Tracktion Validate File on several other instruments and found something interesting: Most instruments have a lot of layouts, but always seem to have Mono in addition to Stereo. Vaporizer 2 has only Stereo. This might be a problem for some DAWs. I'll have to admit that Kontakt player has zero inputs, so inputs may not be a problem (2 or 0 or many), but no mono output may be a problem.

Thanks for information regarding "vst3 validator", I'm not familiar with VST development at all

I tried to get similar detailed scan info in Reason 12 plugin manager, but with no success. There are no additional options like in Tracktion Waveform, and I cannot find any kind of scan log.
Here's picture showing that VST3 version is not recognized:

Reason 12v.JPG