Wotja 22 - Generative Music App & Plug-in Host (Free, Pro; AUv3 / VST3)

[impete]

I've verified that the 44100/48000 Hz options (etc.) work fine on Windows with the fixed code, using Reaper / VST3 on Windows.

[impete]

Can confirm this with the VST3 - Version, any Sample Rate higher than 44.1 kHz causes Silence.

This is fixed in the next update!

Pete

[impete]

Tracktion Waveform Pro 11.5.18: No DAW transport sync (from host)...

The transport control in Tracktion is fixed in the next Wotja 22 update - it is the same issue that caused problems with Ableton Live!

Best wishes, Pete

[impete]

Ableton Live Suite 11.0.12: No transport sync (from host)
Tracktion Waveform Pro 11.5.18: No DAW transport sync (from host)

These are both fixed in the next Wotja 22 update - they shared the same issue!

Best wishes, Pete

[impete]

@impete

The MIDI Monitor in Studio One only works for external MIDI devices so I used this free monitor... https://www.kvraudio.com/product/midi_monitor_by_rs_met

This indicates that CC data is getting through to the instrument (which is probably why the MIDI track meter shows activity with the orange bar) but I don't see any note on/off which is probably why there is no sound. When I repeat this with Scaler 2 as the MIDI note provider I see note on/off messages on MIDI monitor and hear notes.

Maybe Studio One is filtering out the overlapping note on/off messages (similar to Cubase)?

Hi! I think I might have answered this by email?

My best guess is that this would be caused if you had multiple-cells, both feeding the same MIDI channel; that you were then delivering as a "merged stream" of MIDI events that then conflicted with each other.

Best wishes,

Pete

[JamminFool]

Ableton Live Suite 11.0.12: No transport sync (from host)
Tracktion Waveform Pro 11.5.18: No DAW transport sync (from host)

These are both fixed in the next Wotja 22 update - they shared the same issue!

Best wishes, Pete

Fantastic news!

So now I think the only thing I am still waiting for is the MIDI routing in Waveform.

[impete]

Ableton Live Suite 11.0.12: No transport sync (from host)
Tracktion Waveform Pro 11.5.18: No DAW transport sync (from host)

These are both fixed in the next Wotja 22 update - they shared the same issue!

Best wishes, Pete

Fantastic news!

So now I think the only thing I am still waiting for is the MIDI routing in Waveform.

Heh! I've just been investigating MIDI routing in Ableton - and simply can't see how to get it working *at all*. Very frustrating!

Pete

[ZincT]

@impete

The MIDI Monitor in Studio One only works for external MIDI devices so I used this free monitor... https://www.kvraudio.com/product/midi_monitor_by_rs_met

This indicates that CC data is getting through to the instrument (which is probably why the MIDI track meter shows activity with the orange bar) but I don't see any note on/off which is probably why there is no sound. When I repeat this with Scaler 2 as the MIDI note provider I see note on/off messages on MIDI monitor and hear notes.

Maybe Studio One is filtering out the overlapping note on/off messages (similar to Cubase)?

Hi! I think I might have answered this by email?

My best guess is that this would be caused if you had multiple-cells, both feeding the same MIDI channel; that you were then delivering as a "merged stream" of MIDI events that then conflicted with each other.

Best wishes,

Pete

Thanks Pete. Yes it looks that way. Sorry I haven't had a chance to get back to you.

[JamminFool]

Ableton Live Suite 11.0.12: No transport sync (from host)
Tracktion Waveform Pro 11.5.18: No DAW transport sync (from host)

These are both fixed in the next Wotja 22 update - they shared the same issue!

Best wishes, Pete

Fantastic news!

So now I think the only thing I am still waiting for is the MIDI routing in Waveform.

Heh! I've just been investigating MIDI routing in Ableton - and simply can't see how to get it working *at all*. Very frustrating!

Pete

there is no channel MIDI routing in Ableton. So, yes, it is extremely frustrating.

You CAN send ALL the MIDI from one track to another track. But that is less than useful for your plugin.

To do that: In the track you want to receive the MIDI, use the MIDI From: drop down to select Wotja, then select Wotja again in the drop down right below it. That is where you expect to see the individual MIDI channels, but you can only select the plugin - which means ALL the MIDI data from Wotja.


In the meantime: Waveform also supports MIDI routing. It just doesn't work with Wotja (yet). But the same problem as with Live, there is no way to set the channel that it listens to. it seems to get all the MIDI from the sending track. Again, making it somewhat useless for the purpose of sending output on various MIDI channels to separate VSTi plugs in the DAW.

For both of these cases (Ableton and Waveform), I guess you could use something like Kontakt as the receiving Track, and then send the different channels to instruments on different instruments loaded in Kontakt.

[impete]

Thanks Pete. Yes it looks that way. Sorry I haven't had a chance to get back to you.

No problem at all

Pete

[impete]

there is no channel MIDI routing in Ableton. So, yes, it is extremely frustrating.

You CAN send ALL the MIDI from one track to another track. But that is less than useful for your plugin.

To do that: In the track you want to receive the MIDI, use the MIDI From: drop down to select Wotja, then select Wotja again in the drop down right below it. That is where you expect to see the individual MIDI channels, but you can only select the plugin - which means ALL the MIDI data from Wotja.

Thanks for the clarification - matches what I found

In the meantime: Waveform DOES support MIDI channel routing. It just doesn't work with Wotja (yet).

I've been trying to figure this out, and even went to the extent of creating a "Wrapper" in Waveform Pro, containing both an instance of Wotja 22 Pro VST3, and various instruments - hooked-up the MIDI output from Wotja into the MIDI input of the instruments I tried - and couldn't get them to make any sound (though I could add-in the audio output from Wotja into the "Wrapper" output, and could at least hear that).

All I can suggest is contacting Waveform support, and asking them what is going on. It is beyond me, alas! NB: I'm completely new to Tracktion. I couldn't believe how painful it was to guess how to add a plug-in reference to track in the first place

Best wishes, Pete

[JamminFool]

@impete:

i had to edit the previous post because i am realizing that Waveform suffers the same limitation as Ableton Live with respect to CHANNEL routing (i think).

But MIDI routing itself DOES work, just not in Wotja. So this still needs to be fixed for the case of a multi-channel capable VSTi like Kontakt, or an external synth like a Roland JV1080.

add Wotja to the first track in Waveform. Add a synth on track 2. now click in the input of track 2 and select "Route MIDI from..." and choose Track 1.

You wont hear anything from Track 2, because Wotja is not sending the MIDI.

If you replace Wotja with, say, Reason Rack, and put a MIDI generator like Quad Note Generator in the Rack, then it will correctly drive the synth on Track 2.

EDIT: I really hope someone proves me wrong with respect to not having access to the MIDI channel in Waveform, but I couldn't find it.

[JamminFool]

@impete:

OK i have done some more tests:

Ableton Live 11 appears to be merging all MIDI data from all channels to MIDI channel 1 when you re-route it to another track. So even if the sending plug outputs on 2 channels (my test used channel 1 and channel 2), it all arrives on channel 1. At least that's what it looks like since Kontakt only played the instrument on channel 1 while the instrument on channel 2 remained silent. (I used Reason rack with two Players sending on channels 1 and 2)

So this is either a bug in Live or a very stupid design decision by Ableton. But it definitely is not Wotja's fault, since it behaves the same as when Reason Rack is driving the MIDI.

NOW: if I use the same setup in Waveform (ie. Reason Rack driving MIDI on channels 1 and 2 to instruments in Kontakt) both instruments play in Kontakt. So we know at least that works in Waveform.

BUT: when I replace Reason Rack in Waveform with Wotja to send the MIDI data instead, then NO instruments play in Kontakt. So, there is a bug in Wotja (which we already knew, and hopefully you can fix!)

The bad news is that Live is useless for using Wotja (or any multi-channel MIDI plug) until they fix their side.

I hope this makes sense to anyone reading it. It is difficult to describe. And hopefully someone can correct me regarding the routing of MIDI channels in Waveform, since this is where the real power of the Wotja VST3 lies.

[zzz00m]

Just a reminder for Windows users that you will probably still need to manually move the updated 22.0.6 VST3 plugin to your normal VST3 folder, "C:\Program Files\Common Files\VST3".

I just checked the running VST3 plugin version after the update for the application to 22.0.6, and it turned out that I was still running the initial plugin release 22.0.0.

The new VST3 plugin version was located here at "C:\Program Files\WindowsApps\Intermorphic.WotjaPro22_22.0.6.0_x64", which is in the Windows Store apps path. I just copied it over to my normal VST3 folder to complete the update.

[JamminFool]

Just a reminder for Windows users that you will probably still need to manually move the updated 22.0.6 VST3 plugin to your normal VST3 folder, "C:\Program Files\Common Files\VST3".

I just checked the running VST3 plugin version after the update for the application to 22.0.6, and it turned out that I was still running the initial plugin release 22.0.0.

The new VST3 plugin version was located here at "C:\Program Files\WindowsApps\Intermorphic.WotjaPro22_22.0.6.0_x64", which is in the Windows Store apps path. I just copied it over to my normal VST3 folder to complete the update.

HINT: you can make it a little easier on yourself by using the Help Menu in the stand-alone version. It includes two entries which take you directly to the relevant folders for a quick copy and paste of the dll.