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

[JamminFool]

@impete

i'm really hoping that the transport and tempo sync are fixed for Live 11 in the next drop of Wotja.

at this point i'm fairly sure i will be picking this up soon, i just want to make sure i have a good use case for it with my current setup. I really wish i could use all the midi channels output by wotja in Live 11 (without an external tool), but i still think this thing is worth having even without that.

[ZincT]

@JamminFool @zzz00m

Out of curiosity I installed Ableton Live 11 Lite and can confirm the non working transport/tempo sync. I tried various sync options from the preferences menu all to no avail.

@impete
I investigated the Omnisphere crash a bit more in standalone Wotja and found that it always crashes, however if you load PlugInGuru Unify (which works OK) and then load Omnisphere as a plugin in that it works fine. Not ideal but a workaround for now. It also works with other plugins hosts like DDMF Metaplugin and Kushview Element (the cheapest option).

One issue I am having which I see mentioned by others is the routing of MIDI both in standalone and plugin. For example, if I have a wotja track playing a drone on midi ch 1 and another track playing a generator on ch 2 then making sure that only the drone goes to one plugin and the generator goes to another plugin seems a bit tricky. It sounds like all channels are going to all plugins on ch 1. I have tried changing the midi channel on each track and also using the plugin screen channnel/track selector without any luck. Any suggestions? Thanks

[ZincT]

I also just found that you can get the Reason Rack working using the same solution as Omnisphere i.e. a plugin host like Kushview Element, DDMF Metaplugin or PG Unify.

[impete]

@impete

i'm really hoping that the transport and tempo sync are fixed for Live 11 in the next drop of Wotja.

Hi! 22.0.6 has (just) now been uploaded to the App Stores for review. There are a lot of fixes / changes in here, mainly related to plug-in scanning - as you'd probably expect!

I'll now start looking at "any other issues". Interestingly, most issues seem to be on Windows / VST3 - things seem much more 'predictable' with macOS / AUv3. I really don't know why this is; Wotja uses JUCE for plug-in handling at its core, and JUCE is really pretty good at plug-in handling; though I've found a few issues recently on the AUv3 side that needed fixing / tweaking.

Best wishes, Pete

[JamminFool]

...or you just have some good testers working in Windows right now.

(and thanks for the hard work addressing the issues...)

[impete]

...or you just have some good testers working in Windows right now.

I've had so many offers of help. You know who you are, Beta testers

(and thanks for the hard work addressing the issues...)

My pleasure. I must say that the community support for us (and Wotja users) both here (and on the AudioBus forum) has been simply fantastic.

Best wishes, Pete

[impete]

As always, if anybody has any specific issues that they'd like looked at, please simply let us know, and we'll factor them into our plans!

Best wishes, Pete

[experimental.crow]

does 'wotja' contain something akin to the ' midi file cooker ' that was
offered in your ' noatikl ' app ?..

if not , it should ...

[JamminFool]

in the standalone, i am trying to send one of the tracks in the example "V22 Play Me!" mix to a VST3:

however, when i add a VST3 synth to FX Chain 1 and change it from "Wotja: All Tracks" to "Track 1", it silences all other tracks in the mix. This seems like a bug. I want to use both the internal existing sounds on all the other tracks and only replace the sound on one of the tracks with my VST3.

if i switch each of the silent tracks to also use a VST3, they begin to make sound again.

so it seems like I can either use all VST3 for sound, or all internal, but not mix them together.

is this intended, or a bug? if intended, then I am limited to 6 tracks for any mix when i want to use VST3 instruments, which seems wrong.

[JamminFool]

also: i would love to see a multi-out version of the VST3 to allow for mixing in the DAW.

[zzz00m]

@impete

i'm really hoping that the transport and tempo sync are fixed for Live 11 in the next drop of Wotja.

That's truly a strange one. Other plugins which I have that have internal pattern playback, such as EZbass and Addictive Drums, always start playing in Live when the Live transport "play" button is pressed. With full tempo sync as well. The EZbass plugin that I tested with is the VST3 version, so that is a demonstration that Live 11 is sending transport and tempo info to a VST3 plugin.

One note with these other plugins, is that the host sync can be enabled/disabled in the plugins. If enabled, it always works!

[zzz00m]

@ZincT

One issue I am having which I see mentioned by others is the routing of MIDI both in standalone and plugin. For example, if I have a wotja track playing a drone on midi ch 1 and another track playing a generator on ch 2 then making sure that only the drone goes to one plugin and the generator goes to another plugin seems a bit tricky. It sounds like all channels are going to all plugins on ch 1. I have tried changing the midi channel on each track and also using the plugin screen channnel/track selector without any luck. Any suggestions? Thanks

I got this working in Cakewalk, but not in Live. Seems to be a limitation within Live's routing system. But a virtual MIDI loopback cable such as LoopBe1 was suggested as an external workaround.

I would like to at least see the transport sync working in Live. Live offers a good environment for experimental music, and Wotja seems like a great inspirational match for that!

[ZincT]

@ZincT

One issue I am having which I see mentioned by others is the routing of MIDI both in standalone and plugin. For example, if I have a wotja track playing a drone on midi ch 1 and another track playing a generator on ch 2 then making sure that only the drone goes to one plugin and the generator goes to another plugin seems a bit tricky. It sounds like all channels are going to all plugins on ch 1. I have tried changing the midi channel on each track and also using the plugin screen channnel/track selector without any luck. Any suggestions? Thanks

I got this working in Cakewalk, but not in Live. Seems to be a limitation within Live's routing system. But a virtual MIDI loopback cable such as LoopBe1 was suggested as an external workaround.

I would like to at least see the transport sync working in Live. Live offers a good environment for experimental music, and Wotja seems like a great inspirational match for that!

Good point @zzz00m, I must try it again in Cakewalk which I know probably better than any of the other DAWs (although I'm trying to move to Studio One, but keep getting drawn back .

I have also been doing quite a bit of testing in standalone Wotja when my primary use of Wotja was really intended to be the plugin. I would prefer to avoid using external solutions like LoopBe1, if possible, so I guess I will stick with Cakewalk for now. Ableton has a huge following so the transport issues will surely receive attention, and I would also like to see Studio One MIDI routing addressed if that's possible without external workarounds.

[impete]

in the standalone, i am trying to send one of the tracks in the example "V22 Play Me!" mix to a VST3:

however, when i add a VST3 synth to FX Chain 1 and change it from "Wotja: All Tracks" to "Track 1", it silences all other tracks in the mix. This seems like a bug. I want to use both the internal existing sounds on all the other tracks and only replace the sound on one of the tracks with my VST3.

if i switch each of the silent tracks to also use a VST3, they begin to make sound again.

so it seems like I can either use all VST3 for sound, or all internal, but not mix them together.

is this intended, or a bug? if intended, then I am limited to 6 tracks for any mix when i want to use VST3 instruments, which seems wrong.

I now understand this better: and have explained later in the thread!

Pete

[impete]

does 'wotja' contain something akin to the ' midi file cooker ' that was
offered in your ' noatikl ' app ?..

if not , it should ...

Hi! Yes, absolutely.

Open a mix, and look at the bottom right for the "Record" tab button. Click this button.

You'll then be in the Mix Recording view, where you can make MIDI and/or WAV recordings (not both at the same time, however!) of the current mix.

Best wishes, Pete