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

[impete]

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

Hi! This is, I think, possible in theory; but looks very complicated to achieve in practice.

So, "Never say Never" but I can't quite imagine how I'd achieve this!

Best wishes, Pete

[JamminFool]

i understand. maybe some day then.

[impete]

i understand. maybe some day then.

Always live in hope

It has taken us years to add Plug-in Hosting, and VST3 support. Just required the right combination of circumstances to come together. Glad we got there in the end, to say the least

Pete

[El°HYM]

@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

Thanks for the update, Pete!

Will add my Windows vst - list in a few, too.

[zzz00m]

i understand. maybe some day then.

Always live in hope

It has taken us years to add Plug-in Hosting, and VST3 support. Just required the right combination of circumstances to come together. Glad we got there in the end, to say the least

Pete

If you are using a DAW setup to route the Wotja MIDI mix split over separate MIDI channels to various VST instruments on individual DAW tracks, you can simply mix those audio output channels from the instrument tracks in the DAW console.

Or am I missing something here?

Of course the suggestion would obviously make sense if you were only using the Wotja internal sound generators, as that is all mixed together and sent to one stereo audio pair in the DAW as it currently works.

[impete]

i understand. maybe some day then.

Always live in hope

It has taken us years to add Plug-in Hosting, and VST3 support. Just required the right combination of circumstances to come together. Glad we got there in the end, to say the least

Pete

If you are using a DAW setup to route the Wotja MIDI mix split over separate MIDI channels to various VST instruments on individual DAW tracks, you can simply mix those audio output channels from the instrument tracks in the DAW console.

Or am I missing something here?

Of course the suggestion would obviously make sense if you were only using the Wotja internal sound generators, as that is all mixed together and sent to one stereo audio pair in the DAW as it currently works.

Hi! The problem is that to route Track data from within Wotja to separate outputs (aka buses, I think) in the plug-in; I'd somehow have to configure the VST3 / AUv3 to present a multi-output option - one bus per Wotja track [audio and MIDI] (in addition to the "Omni" output from Wotja (our current 2-channel stereo output).

The sticking point here is that when I looked at it last year, the documentation in this area for JUCE was as clear as mud to me - I simply couldn't get my head around how to implement it!

Hopefully I'll be able to dig into it at some point, and make sense of the documentation...

Best wishes, Pete

[zzz00m]

If you are using a DAW setup to route the Wotja MIDI mix split over separate MIDI channels to various VST instruments on individual DAW tracks, you can simply mix those audio output channels from the instrument tracks in the DAW console.

Or am I missing something here?

Of course the suggestion would obviously make sense if you were only using the Wotja internal sound generators, as that is all mixed together and sent to one stereo audio pair in the DAW as it currently works.

Hi! The problem is that to route Track data from within Wotja to separate outputs (aka buses, I think) in the plug-in; I'd somehow have to configure the VST3 / AUv3 to present a multi-output option - one bus per Wotja track [audio and MIDI] (in addition to the "Omni" output from Wotja (our current 2-channel stereo output).

The sticking point here is that when I looked at it last year, the documentation in this area for JUCE was as clear as mud to me - I simply couldn't get my head around how to implement it!

Hopefully I'll be able to dig into it at some point, and make sense of the documentation...

Best wishes, Pete

I understand, which is why I suggested that a good alternate method would be to mix audio in the DAW's mixer, assuming one was sending the Wotja MIDI out to multiple virtual instrument plugins hosted in the DAW. Each virtual instrument could then have an audio output channel (L/R) present in the DAW mixer representing the track that they were using.

So in this scenario, Wotja would just be a MIDI generator. No need to implement multi-audio outputs from Wotja!

[zzz00m]

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.

I finally confirmed that the multi-MIDI channel output from Wotja works in Reaper! Yay! Just set the desired MIDI channels in Wotja, and then select the channels in Reaper in the routing widget for the respective instrument tracks.

So mark Reaper and Cakewalk as a success for the Wotja VST3 MIDI routing and transport sync!

Studio One works for transport sync only. Studio One and Live don't appear to have the same internal ability to route MIDI as Cakewalk and Reaper do.

I'm with you on the move to Studio One as my primary DAW, but I keep finding excuses to drop back to Cakewalk, which I know much better. I am also trying to dig into Ableton Live, as it's unique workflow and resources seem to excel at ambient and experimental music.

I have hope that the Live transport sync issue will be resolved soon. That would also leave Studio One and Live as good options for the Wotja VST3 plugin, but still with the necessity to use a virtual MIDI loopback adapter for MIDI output to the DAW instrument tracks. IMO, it doesn't appear that MIDI routing can be fixed from the Wotja plugin side. DAW issue...

[Musical Gym]

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!

How do I get the update from Microsoft?

[JamminFool]

Of course the suggestion would obviously make sense if you were only using the Wotja internal sound generators, as that is all mixed together and sent to one stereo audio pair in the DAW as it currently works.

exactly.

[impete]

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!

How do I get the update from Microsoft?

Hi!

This should just happen automatically, in general.

However, we've got a FAQ entry on this, just to make things crystal clear:

https://intermorphic.com/help/#windows-app-update

NB: the Apple updates for 22.0.6 are now live, but Microsoft are still certifying the 22.0.6 updates for Windows!

With best wishes, Pete

[impete]

@impete

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

I've asked Ableton for a Live NFR, to help us investigate. Hopefully they'll get back with a positive response!

Best wishes, Pete

[JamminFool]

[impete]

Folks, there is a lot of info in this thread that has been building-up! I hope to review the *entire* thread in the coming days, to make sure I've captured anything.

One thing I need to start with, is figuring-out the definitive solutions for MIDI Routing from the VST3 in the various plug-in hosts / DAWs for Windows (Cakewalk, Reaper etc.)...

[impete]

I finally confirmed that the multi-MIDI channel output from Wotja works in Reaper! Yay! Just set the desired MIDI channels in Wotja, and then select the channels in Reaper in the routing widget for the respective instrument tracks.

Hi! I'm just trying to figure-out how to document this!

Starting with an empty project.

Add the first track (Track 1).
I set Wotja VST3 in Track 1.

Add a new track (Track 2).
Clicking Route in Track 2, then click "Add new receive..." and add a receive from Track 1. Specifically set the "MIDI:" drop-down to be MIDI channel 1.

I can repeat this as required to have different tracks get driven by different MIDI channels from Wotja.

Alternatively, if I have lots of tracks already set-up, I can select my Wotja Track, click "Route" and then "Add new send..." and set "MIDI:" to whatever I want.

Is that about right?!

Pete