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

[impete]

How do you get Wotja to rescan plugins? Wotja was crashing during plugin scanning so I temporarily renamed the VST3 folder so that Wotja would load. I then renamed the vst3 folder back to the original name but Wotja does not want to scan the folder anymore. Also is there a way to tell with VST is crashing Wotja?

Hi! In the current version, there is a "Rescan" button in the top of the Plug-in Browser window.

Best wishes, Pete

[impete]

I decided to uni-install Wotja 22 PRo. I had no business being an early adaptor.
I have no idea if it was properly un-installed.
Unfortunately Revo could not see that Wotja was installed so could not use Revo to un-install it.

Hi! Thanks for your feedback. We've been caught-out when scanning some of the (many!) VST3 plug-ins there are out there; many more than we've been able to test for in our development and testing phases.

On the iOS/macOS side, where we use AUv3, we had very few problems - just 3 plug-ins I think that caused problems.

Anyhow: we're looking to rework the way we handle VST3 scanning, to accommodate this; we'll probably take a couple of weeks to find a nice solution.

Best wishes, Pete

[impete]

My first impressions on win 10:

- IF it will (hopefully....) work SOMEDAY, yes, it is THE generative SOLUTION to Ambient composing....

Hi, and many thanks for your feedback.

- It is SO far away from working (VST3 plugins IN Wotja, VST3 IN any daw) properly in win 10 I wonder if this all could be fixed in the 22 version to at least work SOMEWAY but I really EXPECT it. There could NOT be a (payed) 23 version without all this issues fixed on the VST3 version....

As noted elsewhere in this thread, we've been caught-out when scanning some of the (many!) VST3 plug-ins there are out there; many more than we've been able to test for in our development and testing phases.

On the iOS/macOS side, where we use AUv3, we had very few problems - just 3 plug-ins I think that caused problems.

Anyhow: we're looking to rework the way we handle VST3 scanning, to accommodate this; we'll probably take a couple of weeks to find a nice solution. When we have, we'll push the update to the Store as normal!

- for me apart from the scanning issues (that need a whold new workflow for the scanning process) there are lots of problems to be fixed I cant even figure out where they might be (for example kontakt gui does not react as it should in anyway, no matter if Wotja is playing or not, you could simply change anything on the gui)

- crashes.......

- the cpu load is incomprehensible high (one of the few VST3 working at all so far in Wotja22 is Unify but in my environment I could load TEN Unify versions with the same content in ANY daw where ONE version of Unify inside Wotja gets me a cpu overload and crash.....

Wotja does a *lot* of stuff. Not only does it have its own internal modular synth and FX, it is also now hosting. So, if you add those two together - it *can* end-up doing a lot of work. But that said, we do monitor periodically for performance hot-spots, and if we find them, we look to fix them.

- vst3 version INSIDE daw does not work at all (tried it on Mixcraft Pro 9). Nothing more to be said: NOT at all....

I think that, to be fair, being a Host app is tricky. Not only for Wotja (!), but no doubt other more general purpose DAWs. I've personally tested Wotja VST3 with Cakewalk, Reaper.

- I cant even imagine how much work must have gone into this to even got it this far.

30 years and counting. But - the Hosting side has been in development (by just 1 person - me!) since last March. It is very stable *but* we've seen the problems with scanning some VST3s at launch, as you've noted. Please bear with us while we address this!

- The general idea is INCREDIBLE. Or: if it works, this IS IT

Totally torn between the feeling of betatesting a (bad) alpha with trying workarounds definitely NOT in the users responsibility and a genious lookout into a bright future.....

To be fair - I would't describe this as (bad) alpha. Wotja 22 is very solid software, that has been caught-out at (soft) launch by a very tough environment of hundreds (thousands?) of VST3 plug-ins that show a very wide range of behaviours, some of which are catching-out our plug-in scanning. I doff my cap to the plug-in hosting apps / DAWs that have gone before Wotja, it is a real challenge to do - let alone for a single-developer company / product like Intermorphic / Wotja

Best wishes, Pete

[ZincT]

Some initial reports on the VST3 plugin in Cakewalk (Windows 10, Wotja lite) with Play Me 22:

- CPU usage seems ok; starts at around 10% and then drops to 2-3 % after a while. Load seems to be shared among a number of threads (on the standalone it all seems to be on the first thread). (Ryzen 7 5800X)

- Zero crashes so far

- Initially I had some odd interaction with the Cakewalk UI causing flickering and apparent lock up which then disappeared and all was ok

- Tried with a number of Kontakt instruments which was a lot of fun!

I also quickly tried loading it in Unify as an instrument layer. I added a MIDI latch for Wotja in Unify to start/stop it and then jammed over the top. Excellent fun and I lost track of time

Based on my experience so far and the "potential" I will buy.

[Musical Gym]

Anyone have a link for getting midi out of it?

[tatanka]

Some initial reports on the VST3 plugin in Cakewalk (Windows 10, Wotja lite) with Play Me 22:

- CPU usage seems ok; starts at around 10% and then drops to 2-3 % after a while. Load seems to be shared among a number of threads (on the standalone it all seems to be on the first thread). (Ryzen 7 5800X)

- Zero crashes so far

- Initially I had some odd interaction with the Cakewalk UI causing flickering and apparent lock up which then disappeared and all was ok

- Tried with a number of Kontakt instruments which was a lot of fun!

I also quickly tried loading it in Unify as an instrument layer. I added a MIDI latch for Wotja in Unify to start/stop it and then jammed over the top. Excellent fun and I lost track of time

Based on my experience so far and the "potential" I will buy.

Dont you have "freezing gui" (dont know how to describe better) problems in Kontakt/Unify ? Was in the standalone version I have to admit but initially it works, then when I try to reopen the instrument and change something the GUI in Kontakt was like a screenshot, nothing could be turned, adjusted, whatever.

Maybe if it works in Cakewalk have to go back to my first DAW . In Mixcraft 9 Pro it simply dont work at all .

Would be really glad to hear some more daw experiences on win 10 especially where it works without any problems.

[wasi]

It works fine here on Win11, plugin scan went through without a hitch (other hosts have been pickier).

However, opening a plugin takes a very long time and it is advisable to pause Wotja when switching presets.

Also, should the VST3 version output midi notes to the daw (or anywhere)? It doesn't seem to.

[ZincT]

Dont you have "freezing gui" (dont know how to describe better) problems in Kontakt/Unify ? Was in the standalone version I have to admit but initially it works, then when I try to reopen the instrument and change something the GUI in Kontakt was like a screenshot, nothing could be turned, adjusted, whatever.

Maybe if it works in Cakewalk have to go back to my first DAW . In Mixcraft 9 Pro it simply dont work at all .

Would be really glad to hear some more daw experiences on win 10 especially where it works without any problems.

I'm not using the standalone version until the ability to turn off the plugin scanner or exclude certain plugins is added. I did the CPU test on standalone by renaming my VST3 folder; something which I don't plan to do permanently!

For the plugin we maybe talking about the same issue - I described it as flickering and apparent UI lockup which then cleared.

In Unify I was using one of the Unify Factory patches with a Wotja layer added, not Kontakt. I have just tried adding Kontakt to Unify with Wotja on another layer and Kontakt UI seemed ok although I couldn't figure out how to route the MIDI from Wotja to Kontakt. I also tried it by adding Wotja to a Combobox MIDI effect on the same layer as Kontakt and still got nothing out. UPDATE: Ok I got it working by having Wotja and Kontakt in the same ComboBox on a layer with routing within Combobox.

I was able to route the MIDI from Wotja to Kontakt in Cakewalk.

I think it's early days for Wotja 22 and I'm not an expert with it by any means.

@impete I am happy to help debug/test any issues if it would help.

[tatanka]

Thanks for the info

[Musical Gym]

I was able to route the MIDI from Wotja to Kontakt in Cakewalk.

I would like to know how you did this.

[wasi]

I was able to route the MIDI from Wotja to Kontakt in Cakewalk.

I would like to know how you did this.

Here's what I did in Bitwig/Live:

Wotja on track 1, Instrument on track 2, track 2 midi input has Wotja selected, in Live I had to additionally select "Wotja" again in the pre/post droptown.

I can't get channels to work though, it seems like all midi output is on channel one?

[Erisian]

Is the Windows version absolutely only Win10, or is there a chance it might work on earlier versions?

[ZincT]

I was able to route the MIDI from Wotja to Kontakt in Cakewalk.

I would like to know how you did this.

- Drag a Wotja instrument onto a blank track area to create a Wotja instrument track
- Load Play Me 22 into Wotja
- Drag a Kontakt instrument onto a blank area to create a Kontakt instrument track (& enable note echo)
- Load an instrument into Kontakt (I used Alicia's Keys)

Hit play on the Cakewalk transport and anything from Wotja Midi Ch 1 will be sent to Kontakt Ch 1.
Some of the notes are Conga/Tamburine and others are Tampura drone and lead so might not make sense depending on what instrument you choose in Kontakt. You could also change the MIDI channel in Wotja for each instrument. I'll see if there's a better demo for playing external instruments via MIDI.

I am seeing that UI glitch quite often now in Cakewalk and of course keep hitting the Lite timeout. UPDATE: Actually it's worse with Kontakt loaded; almost unusable I'd say. Tried something simpler than Kontakt (Cherry DCO-106) and had the same problems. It's like Wotja's taking priority over Cakewalk/other instruments even though the CPU load seems ok when this happens.

[wasi]

OK multichannel midi works fine, I didn't see Bitwig has a per track channel select and default is "All-->1", so obviously everything came in on #1...

[impete]

@impete I am happy to help debug/test any issues if it would help.

That is extremely kind of you. I'll do my best to keep the thread posted with developments!

Best wishes, Pete