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

[impete]

Just trying to get all my ducks in a row in advance of next week!

22.0.11 is what - for me - solved the problem of routing MIDI in Tracktion Waveform Pro; and I verified this at the time with Waveform, Cakewalk, Reaper (NB the latter two were also fine with previous builds).

However: from what I understand, some of you report that 22.0.11 actually caused a regression with at least some DAWs in terms of MIDI connectivity.

So, I'd be grateful if anybody with problems with routing of MIDI from the Wotja VST3 in the current build (22.1.0) could let me know:
- what DAWs you're having problems with (and a rough headline summary of the problem(s))
- what DAWs you *don't* have problems with (this is also very important to know!)
- at what Wotja version you're (fairly!) certain any problems got resolved and/or fixed.

hi pete,

i have already fully documented my issue in Waveform in this thread, so i'm pretty sure you know about that.

but i also have an the issue in Loomer Architect. it is still in beta, so i hesitated to mention it here before, but I mention it now because it fails to pass any MIDI from Wotja to another VST at all, whether between tracks, or when the VST directly follows Wotja in the same track (which works with all other MIDI generating VSTs I tested in Architect).

the interesting thing to note here is that Loomer Architect also uses JUCE. Just like Waveform.

so more evidence that JUCE may be stripping badly formed MIDI messages.

Thanks for that info!

Right now, I think the JUCE issue is a documentation ambiguity, rather than a bug. In other words, it's going to be a bug on *my* side rather than a JUCE code bug.

Anyhow: I'm just about to verify my changes still work on iOS etc. before testing on Windows.

If you're happy to try a Beta for Windows, then do please get in touch as noted above!

Pete

[JamminFool]

you are welcome.

[zzz00m]

So, I'd be grateful if anybody with problems with routing of MIDI from the Wotja VST3 in the current build (22.1.0) could let me know:
- what DAWs you're having problems with (and a rough headline summary of the problem(s))
- what DAWs you *don't* have problems with (this is also very important to know!)
- at what Wotja version you're (fairly!) certain any problems got resolved and/or fixed.

Thanks in advance for any/all feedback!

Best wishes, Pete

@impete

Wotja VST3 22.1.0 results in my DAWs:

Ableton Live 11.0.12: Yes (MIDI ch 1 routing only - DAW limitation)
Reaper 6.46: Yes
Cakewalk 2021.12: No (works until CPU overload causes audio engine dropout)
Studio One Pro 5.5: No (works until CPU overload causes audio engine dropout)
Waveform 11.5.18: No (works *experimental engine only* until CPU overload causes audio engine dropout)

Hope this helps!

Note: the DAWs in the "No" category above are routing MIDI, but the one problem that they all have in in common is that one CPU core ALWAYS increases CPU usage from normal to 100% over a short time period as the DAW transport is playing. I have used Windows Sysinternals 'Process Explorer' to analyze the DAW process as it is running, and it seems that one active thread is causing the CPU spike (actual problem thread varies by DAW).

I suspect that this CPU issue may not affect all computer configurations. I discussed this with another user that has a different brand of hardware audio interface and ASIO driver, and they were not seeing this problem.

[andreasg]

sorry for my question, but i cannot find the auv3 plugin in my Ableton 11 and not in my logic pro,
and in the /Library/Audio/Plug-Ins/Components is no Wotja.component.
perhaps someone can help me

[impete]

sorry for my question, but i cannot find the auv3 plugin in my Ableton 11 and not in my logic pro,
and in the /Library/Audio/Plug-Ins/Components is no Wotja.component.
perhaps someone can help me

Hi!

Alas, Ableton does not support Apple’s AUv3 format plug-ins - at least, so far as I’m aware. Though you’d have thought they would do by this point!

To answer your other question, AUv3 plug-ins are delivered as extensions embedded within their associated app, so they’re not installed separately in the “old place” used by AU 2 format plug-ins.

Best wishes, Pete

[syncline]

"So, I'd be grateful if anybody with problems with routing of MIDI from the Wotja VST3 in the current build (22.1.0) could let me know:
- what DAWs you're having problems with (and a rough headline summary of the problem(s))
- what DAWs you *don't* have problems with (this is also very important to know!)
- at what Wotja version you're (fairly!) certain any problems got resolved and/or fixed."

I use FL Studio (version 20.9). There are a couple of issues with the VST3 plugin. As far as I can tell, MIDI is not being received by the DAW at all. If I load Wotja (latest version) into Patcher, the Wotja MIDI port shows no activity while Wotja is running. I can see/hear audio coming from the Wotja plugin, but no MIDI. MIDI is also broken if Wotja is loaded directly as a VST3 plugin.
It is not clear whether the issue stems from Wotja itself or from something wrong with how FL Studio handles MIDI with VST3 instruments.
I'd be happy to test workarounds or Beta versions of Wotja if it would help you find the source of the problem.

[dopet]

I just tried the latest VST3 version (22.1.0) again in Studio One 5 (latest update, Win 10) and the midi routing between tracks (midi out from Wotja VST3 to another track) still does not trigger any sounds in the other track. The midi activity monitor lights up on the receiving track (as it did in earlier versions), but no sound is generated.

Using Wotja standalone and piping midi into Studio One thru LoopMidi does work as expected.

[ZincT]

I just tried the latest VST3 version (22.1.0) again in Studio One 5 (latest update, Win 10) and the midi routing between tracks (midi out from Wotja VST3 to another track) still does not trigger any sounds in the other track. The midi activity monitor lights up on the receiving track (as it did in earlier versions), but no sound is generated.

Using Wotja standalone and piping midi into Studio One thru LoopMidi does work as expected.

@dopet That's weird, the plugin works fine here (also latest Wotja and latest S1 Pro).
Here's a video I made to show how to use multi-timbral instruments with Wotja in Studio One which might help? If not I can always do a step by step video starting with a blank project if that would help?

I guess the key thing is to make sure that the instrument track MIDI input is set to the correct Wotja MIDI channel output.

[ZincT]

@dopet

Ok here's a video starting from a blank project in Studio One Pro 5. Hope it helps.

[DarkStar]

@impete
Maybe a silly question, but why go for a wotja VST3 plug-in rather than VST2 (as you had all those years ago for noatikl)? And VST2 hosting?

[impete]

@impete
Maybe a silly question, but why go for a wotja VST3 plug-in rather than VST2 (as you had all those years ago for noatikl)? And VST2 hosting?

That is down to our reading of the latest Steinberg VST SDK license!

Best wishes,

Pete

[DarkStar]

Hmmm .... Understood (I was asking as, from a skim through this thread, the VST3 edition seems to have some MIDI problems).

[dopet]

@dopet

Ok here's a video starting from a blank project in Studio One Pro 5. Hope it helps.

Appreciate it! I’ve got all the generative tools and they all route midi and work as you would expect. This one does have me scratching my head a bit?? .

I’ll try to carve out soMe time later to watch.

[impete]

Hi!,

Here are some notes on Routing in Tracktion - I hope somebody finds them useful!

Set up a Track with a new (empty) Plugin Rack.

Open the Plugin Rack.

We'll now set-up a Rack that looks like this:



Add one instance of Wotja 22 Pro

Add two MIDI Patch Bay instances (the ones showing two crossed lines).

Add two MIDI Monitors instances.

Add two separate Instrument plug-in instances (I’ve chosen a Piano and a Bass Guitar in my test case).

Drag the MIDI Output from Wotja to the MIDI Inputs of the two Patch Bays.

Drag the MIDI outputs of the two Patch Banks to their respective MIDI Monitor MIDI Inputs.

Drag the MIDI Outputs of the two MIDI Monitors to the their respective Instrument MIDI Inputs.

Drag the left/right audio outputs of the two Instruments, to the Left and Right audio outputs of the Plug-in Rack.

In my test, my Wotja Mix has generators feeding two MIDI Tracks (1 and 2).

So: the top line responds to MIDI Channel 1, the bottom line responds to MIDI Channel 2.

Modify the top MIDI Patch Bank to Block MIDI Channel 2 (so it only gets channel 1 in this case).

Modify the bottom MIDI Patch Bank to Block MIDI Channel 1 (so it only gets channel 2 in this case).

Started it playing - it works as expected.

This is easily proved by looking at the info in the two MIDI Monitors (which are useful, but optional).

Pete

[JamminFool]

yes, but that is only for the case when you want to send each channel to a unique VST. i have demonstrated this several times already.

the problem is:

it should also work for the case of sending all data directly (no Rack required) from Wotja to a multitimbral instrument like Kontakt. in this case, all the data sent from Wotja ends up on channel 1. as i have posted multiple times, please see my example on page 43 of this thread.

it should also work regardless of whether the Experimental Engine is on or off.