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

[impete]

Updated to 22.06 on Windows 10 but VST3 scanning hasn't improved for me. It seems to fail rather arbitrarily: I've tried removing VSTs that cause Wotja to exit but then it fails on VSTs that seemed to previously be OK.

Running 22.0.6 on Windows 10 and cannot get the VST3 scan to complete. No clue given as to which plugin is causing this. The only VST3 plugins present were here when 22.0.4 last scanned them successfully.

We really need a scan log output file showing line by line the plugin names as they are scanned. That way it would be much simpler to identify the failed plugin.

Hi!

I have plans to improve this once we've got 22.0.9 out the door. Probably 1 or 2 weeks of solid work, but it should make scanning much more solid and understandable.

Watch this space, as they say!

Best wishes, Pete

[zzz00m]

Running 22.0.6 on Windows 10 and cannot get the VST3 scan to complete. No clue given as to which plugin is causing this. The only VST3 plugins present were here when 22.0.4 last scanned them successfully.

We really need a scan log output file showing line by line the plugin names as they are scanned. That way it would be much simpler to identify the failed plugin.

Hi!

I have plans to improve this once we've got 22.0.9 out the door. Probably 1 or 2 weeks of solid work, but it should make scanning much more solid and understandable.

Watch this space, as they say!

Best wishes, Pete

Thanks Pete!!!

[impete]

Thanks Pete!!!

Lets hope I manage to improve things

Pete

[impete]

Running 22.0.6 on Windows 10 and cannot get the VST3 scan to complete. No clue given as to which plugin is causing this. The only VST3 plugins present were here when 22.0.4 last scanned them successfully.

I've just checked back on our automated crash reports (thank goodness we have them!), and I'm seeing quite a few crashes in (only) the following two/three VST3 files:

TR5 Sunset Sound Studio Reverb.vst3
Union.vst3
EDIT: Schoeps Double MS.vst3 after KVR feedback!

And I think that is about it.

If any of you are experiencing problems with the above, I'd ask you consider contacting the developers and asking to check.

Best wishes, Pete

[tatanka]

Just now came to try out the "new" scan in 22.06 win 10 but for me nothing changed. Wotja crashes, I dont see any "action menue" or "black list", it simply crashes like before

[omphalocentric]

I've just checked back on our automated crash reports (thank goodness we have them!), and I'm seeing quite a few crashes in (only) the following two VST3 files:

TR5 Sunset Sound Studio Reverb.vst3
Union.vst3

And I think that is about it.

If any of you are experiencing problems with the above, I'd ask you consider contacting the developers and asking to check.

Best wishes, Pete

I tried removing the TR5 SSSR vst3 but the scan still failed for me.

After much trial and error, I discovered the culprit on my system:
Schoeps Double MS.vst3

This was a freebie from Plugin Alliance, so nothing important. The scan completes succesfully now!

[wasi]

Why can't I select ASIO devices/drivers in the (windows) standalone app? This would be really helpful as it would allow routing through Jack.

Hi!

Thanks for asking. I've downloaded the SDK from Steinberg, to take a look see if it is feasible to add support at some point!

With best wishes, Pete

Thanks, it's a bit deal, latency is terrible otherwise and even if this is ambient stuff it matters at some point.

[impete]

I tried removing the TR5 SSSR vst3 but the scan still failed for me.

After much trial and error, I discovered the culprit on my system:
Schoeps Double MS.vst3

This was a freebie from Plugin Alliance, so nothing important. The scan completes succesfully now!

Thank you *very* much for letting us know!

Best wishes, Pete

[impete]

Just now came to try out the "new" scan in 22.06 win 10 but for me nothing changed. Wotja crashes, I dont see any "action menue" or "black list", it simply crashes like before

Hi! We've been building-up a list of 3rd party VST3 plug-ins that can crash on scan, I think this is the current list to check for:

[EDIT - just updated after feedback, thank you!!]

AmpliTube 4.vst3
ANIMATE.vst3
Auto-Tune EFX.vst3
Harmony Engine 4x.vst3
Union.vst3 - note this works for some users
Schoeps Double MS.vst3
Simple Concept.vst3
TR5 Sunset Sound Studio Reverb.vst3 - note that 5.8.0 is said to be OK, so make sure you're updated!
WaveShell1-VST3 10.0_x64.vst3
WaveShell1-VST3 12.6_x64.vst3
WaveShell1-VST3 12.7_x64.vst3
WaveShell1-VST3 13.0_x64.vst3
WaveShell1-VST3 13.1_x64.vst3
WaveShell2-VST3 13.0_x64.vst3
WaveShell3-VST3 10.0_x64.vst3
WaveShell4-VST3 10.0_x64.vst3
WaveShell5-VST3 10.0_x64.vst3

NB: if anybody else can add to this list, do please share the info here!

I hope this information helps.

I'm going to spend the next week or two working further on our plug-in scanning process for Windows, to help deal with these sorts of issues. Wish me luck!

Best wishes, Pete

[impete]

Hi all,

Just to let you know that we're soon going to submit Wotja 22 version 22.0.9 for review. I'd hope this will be available for download in a few days, subject to the usual app store review processes.

The provisional release notes for the Windows version are as follows:

Wotja 22.0.9 Windows release notes (since 22.0.6)

FIXED: VST3: was unable to run at 48000 (but was OK at 44100) in certain plug-in hosts

FIXED: VST3: Transport bar control from Ableton Live and Tracktion Waveform Pro

FIXED: App and VST3: alerts can appear behind the app/plug-in Window

IMPROVED: VST3: Settings screen: replace "Output Device" (which showed an empty pop-up) with
a simple label, displaying text like this (localized):
"VST3 Plug-in: 48000 Hz"

IMPROVED: App: Added Help Menu item to "Install Wotja VST3"
- this is mainly for "first install" or if the auto-update failed
- we keep the other items to make it possible for the user to do easily via Explorer,
as an alternative approach.

FIXED: VST3: issue that required the Wotja plug-in UI to be displayed before the DAW transport
control worked.
- verified with Reaper, Cakewalk, Logic Pro

IMPROVED: App: can now auto-copy the VST3, if not yet done, at start-up
- Prompts user whenever they start the app, if the VST3 has not yet been copied

IMPROVED: App: if the VST3 version available to install is more recent that the
installed VST3 version, then on app start-up prompt the user the copy the updated VST3

TIP: Wotja VST3 Plug-in not scanning from your favourite DAW?
- Solution: install the latest Microsoft C++ Redistributable from here:
https://aka.ms/vs/17/release/vc_redist.x64.exe
- read more here: https://docs.microsoft.com/en-us/cpp/wi ... w=msvc-170

Best wishes, Pete

[tatanka]

Just now came to try out the "new" scan in 22.06 win 10 but for me nothing changed. Wotja crashes, I dont see any "action menue" or "black list", it simply crashes like before

Hi! We've been building-up a list of 3rd party VST3 plug-ins that can crash on scan, I think this is the current list to check for:

[EDIT - just updated after feedback, thank you!!]

AmpliTube 4.vst3
ANIMATE.vst3
Auto-Tune EFX.vst3
Harmony Engine 4x.vst3
Union.vst3 - note this works for some users
Schoeps Double MS.vst3
TR5 Sunset Sound Studio Reverb.vst3 - note that 5.8.0 is said to be OK, so make sure you're updated!
WaveShell1-VST3 10.0_x64.vst3
WaveShell1-VST3 12.6_x64.vst3
WaveShell1-VST3 12.7_x64.vst3
WaveShell1-VST3 13.0_x64.vst3
WaveShell1-VST3 13.1_x64.vst3
WaveShell2-VST3 13.0_x64.vst3
WaveShell3-VST3 10.0_x64.vst3
WaveShell4-VST3 10.0_x64.vst3
WaveShell5-VST3 10.0_x64.vst3

NB: if anybody else can add to this list, do please share the info here!

I hope this information helps.

I'm going to spend the next week or two working further on our plug-in scanning process for Windows, to help deal with these sorts of issues. Wish me luck!

Best wishes, Pete

- updated TR Sunset studio
- deleted Amplitube 4
- isolated/cut Union to another folder

Result: still crashes, this is use-/endless without a logfile saying WHICH plugin exactly causes the crash. Especially as while it crashes all working plugins which passed the scan are lost again. Really no use for scanning with this version, hoping the next one will have a (working) logfile.....

[impete]

Result: still crashes, this is use-/endless without a logfile saying WHICH plugin exactly causes the crash. Especially as while it crashes all working plugins which passed the scan are lost again. Really no use for scanning with this version, hoping the next one will have a (working) logfile.....

Hi! Thanks for letting me know.

Wotja 22.0.9 is focused mainly (but not entirely) on issues with the Wotja VST3; which is going to be much more "solid" in that update.

I plan to look at making VST3 scanning (from the app) more solid from tomorrow. I currently anticipate it will take me 1 to 2 weeks to rework things...

With best wishes,

Pete

[DarkStar]

However, I cannot find the VST3 version of Wotja in my Wotja directory in my Documents folder. I tried re-installing from the Microsoft Store, but no joy - no Wotja.vst3 file anywhere. Perhaps I missed something or need to install/download it separately? Any help or suggestions would be much appreciated.

The Wotja vst3 file is hidden away in Program Files > WindowsApps. Just launch Wotja standalone and browse Help>Show the Wotja VST3 Plug-in. It will open up the file location in Explorer and you can then copy and paste it to the VST3 folder (also has a shortcut under the Help menu)

Thank you very much for that!!

We're working hard to try to improve this for new users, in the next update that is taking quite a long time to test!

With very best wishes, Pete

Doesn't Windows 10 /11 insist on Apps being installed into the WindowApps folder? So that they can be protected from undesirables?

And wouldn't that mean that a DAW has to scan the WindowsApps folder for plug-ins? Unless it is extracted as Pete described above.

[impete]

Doesn't Windows 10 /11 insist on Apps being installed into the WindowApps folder? So that they can be protected from undesirables?

For whatever reason, Windows Store apps are installed into hard-to-find folders on the disk.

I presume this is related to some sort of sandboxing; I don't really know however to be honest!

But it does mean that it isn't practical (AFAIK, anyhow) to configure DAWs to scan for VST3 installed alongside the apps from the store.

And wouldn't that mean that a DAW has to scan the WindowsApps folder for plug-ins? Unless it is extracted as Pete described above.

We've modified the 22.0.9 app to auto-detect if you've yet (first) copied the VST3; and you're give the option to do this from the app.

Similarly, if you've already got (say) 22.0.8 copied, the app will check for this at start-up, and give you the option to copy the 22.0.9 across to the standard VST3 folder.

So the bottom line is - that should make the VST3 much easier to (first) configure and (then) keep up-to-date

Best wishes, Pete

[DarkStar]

Thank you Pete, it sounds like you are taking care of Microsoft's attempts to control us all

I presume that pasting the VST3 into a sub-folder will be OK, e.g. C:\Program Files\Common Files\VST3\Intermorphic\