Wotja 22 VST3 - MIDI events

[impete]

Hi!

Pete here, developer of Wotja 22 - just launched!

I'm not seeing any MIDI data passed-out from Wotja 22 in Tracktion.

NB: configuration very simple:
- one track, with Wotja VST3 playing
- that is followed by an instance of your built-in MIDI Monitor.

I've also tried putting the MIDI Monitor in a separate track - nothing picked-up there either.

For the avoidance of doubt, I have MIDI data picked-up from the output of Wotja 22 in all the other Windows DAWs I've tested with, including Reaper and Cakewalk; according to my customers, the sticking point is Tracktion!

I hope somebody can point-out to me what I'm doing wrong!

Best wishes, Pete

[impete]

Anybody with any suggestions?!

Pete

[Kott]

Hi,
I'd like to check this but can't see any downloads, only links to the Windows/Apple stores.

[impete]

Hi,
I'd like to check this but can't see any downloads, only links to the Windows/Apple stores.

Hi - thanks for getting in touch!

Yes, that's right! All our apps / plug-ins are only available in the "official" app stores (iOS, macOS, Windows, Google, Amazon).

Simply download the Free version of Wotja 22 from the Windows store.

From there, simply use the Help menu item in the app, to Install / Copy the VST3 that comes with the app.

And then - give it a go with Tracktion!

Best wishes,

Pete

[jabe]

I'm trying this and getting the same as you.

The track with Wotja 22 on it is putting out audio,which I can stop it doing. I can send the audio to other tracks but I can't find any MIDI being sent from it.

It looks like the solution might be to wrap the plug-in in a rack so that the MIDI and audio outputs can be treated separately.

[zzz00m]

Yet other plugins send MIDI to another track just fine in Waveform, without needing a rack.

And the Wotja VST3 sends MIDI in other DAWs...

But even if you put a Traction MIDI monitor plugin in line with the Wotja output, you will not see any MIDI coming out.

[Steve Bolivar]

Does Plugval show any errors? I hope this can get fixed. Really interested in Wotja 22 Pro.

[JamminFool]

Does Plugval show any errors? I hope this can get fixed. Really interested in Wotja 22 Pro.

All Tests Passed. Output below:
*********************

pluginval v0.3.0 - JUCE v6.1.0
Started validating: C:\Program Files\Common Files\VST3\Wotja22.vst3
Random seed: 0x2d24345
Validation started: 16 Jan 2022 5:51:19pm

Strictness level: 5
-----------------------------------------------------------------
Starting test: pluginval / Scan for known types: C:\Program Files\Common Files\VST3\Wotja22.vst3...
Num types found: 1

Testing plugin: VST3-Wotja 22-1f789d03-8a1804c2
Intermorphic: Wotja 22 v22.0.6
All tests completed successfully
-----------------------------------------------------------------
Starting test: pluginval / Open plugin (cold)...

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

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

Plugin name: Wotja 22
Alternative names: Wotja 22
SupportsDoublePrecision: no
Reported latency: 0
Reported taillength: 0

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

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

Time taken to open editor (cold): 570 ms
Time taken to open editor (warm): 385 ms

Time taken to run test: 1 sec
All tests completed successfully
-----------------------------------------------------------------
Starting test: pluginval / Open editor whilst processing...

Time taken to run test: 680 ms
All tests completed successfully
-----------------------------------------------------------------
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: 2 ms
All tests completed successfully
-----------------------------------------------------------------
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: 2 ms
All tests completed successfully
-----------------------------------------------------------------
Starting test: pluginval / Plugin state...

Time taken to run test: 0
All tests completed successfully
-----------------------------------------------------------------
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: 2 ms
All tests completed successfully
-----------------------------------------------------------------
Starting test: pluginval / Editor Automation...

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

Time taken to run test: 0
All tests completed successfully
-----------------------------------------------------------------
Starting test: pluginval / Basic bus...
All tests completed successfully
-----------------------------------------------------------------
Starting test: pluginval / Listing available buses...
Inputs:
Named layouts: None
Discrete layouts: None
Outputs:
Named layouts: 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...
All tests completed successfully
-----------------------------------------------------------------
Starting test: pluginval / Disabling non-main busses...
All tests completed successfully
-----------------------------------------------------------------
Starting test: pluginval / Restoring default layout...
Main bus num input channels: 0
Main bus num output channels: 2

Time taken to run test: 1 ms

Time taken to run all tests: 4 secs
All tests completed successfully

Finished validating: C:\Program Files\Common Files\VST3\Wotja22.vst3
ALL TESTS PASSED

[JamminFool]

It looks like the solution might be to wrap the plug-in in a rack so that the MIDI and audio outputs can be treated separately.

I tried this and no luck. The MIDI from Wotja does not get to Waveform.

The developer is hoping to get some help from the Tracktion team.

[jabe]

Yet other plugins send MIDI to another track just fine in Waveform, without needing a rack.

And the Wotja VST3 sends MIDI in other DAWs...

But even if you put a Traction MIDI monitor plugin in line with the Wotja output, you will not see any MIDI coming out.

If the track output is both audio and MIDI there has to be a way to separate them.

[zzz00m]

Yet other plugins send MIDI to another track just fine in Waveform, without needing a rack.

And the Wotja VST3 sends MIDI in other DAWs...

But even if you put a Traction MIDI monitor plugin in line with the Wotja output, you will not see any MIDI coming out.

If the track output is both audio and MIDI there has to be a way to separate them.

If you turn off the audio output in Wotja, Tracktion still does not see any MIDI output from the plugin.

[Kott]

It could be a JUCE VST3 Host/Client MIDI issue.
I loaded Wotja in BespokeSynth (it's JUCE based too) and see in MIDI debug weird time offsets, the first row:

Normal flow from build-in sequencer:

noteseq.png

Flow from Wotja, notes start time is 5000 above:

wotja.png

[impete]

Hi folks!

What puzzles me, is that it works perfectly in Cakewalk and Reaper (so far as I can tell, anyhow!)

Best wishes, Pete

[JamminFool]

Hi folks!

What puzzles me, is that it works perfectly in Cakewalk and Reaper (so far as I can tell, anyhow!)

Best wishes, Pete

and Ableton Live (as far as the MIDI output being seen).

[impete]

Hi again folks: for those wondering:

All you have to do to reproduce this is:
- download Wotja 22 Free from the Microsoft app store (or use the Pro version, of course!)
- run the Wotja 22 Free app - you’ll be prompted to install/copy the VST3 (you can also find Help menu items to show you the file, so you can copy yourself, if you want)
- run Tracktion
- scan for Wotja 22 (Free or Pro) VST3
- add Wotja to a Track
- press the “+” button to create a new automatic mix
- start Tracktion playing - should sound good!
- the problem should then, I hope, be easy for anybody to reproduce!

Best wishes, Pete