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

[impete]

Problem updating from Microsoft telling me I'm not running as Administrator or that VST3 is in use. Tips?
I had to click the Buy button to initiate an update.

Hi - easy enough. That message is about updating the VST3.

Run the app as Administrator (you only need to do this after update; if you want to update the VST3). It'll then let you update the VST3.

Best wishes, Pete

The documentation for this is here:

https://intermorphic.com/help/#plugins-vst3-install

Pete

[Musical Gym]

Thanks, vst3 has a date of 1/30; is that right?

[JamminFool]

hi pete,

i am happy to report that everything now (v22.1.2) works as expected in Waveform when the Experimental Engine is ON!

but when the Experimental Engine is OFF, the MIDI all gets mapped to channel 1 as soon as you direct the midi to another track (this is the case of Wotja on track 1 and Kontakt on track 2) using the "Route MIDI from track...Track 1" input option on track 2.

the good news is that this is the exact behavior of Reason Rack in all cases described.

note it all works fine when Kontakt is on the same track as Wotja (or Reason Rack) regardless of the Experimental Engine setting.

CONCLUSION: it looks like Wotja is now fixed for all my test cases in Waveform. due to both Reason Rack and Wotja behaving the same, I am convinced the remaining issues are on the Waveform side. i had already reported the problem with Reason Rack in Waveform to the Tracktion team, and now i will update that report to include Wotja.

congratulations!

SIDE NOTE: i also quickly tested the new version of Wotja in Loomer Architect, and it now sends data, but there is a similiar pattern there regarding not all data arriving correctly when sent to another track (and it mostly works when in the same track). since Architect now behaves very much like Waveform with the Experimental Engine off and since they both use JUCE, I am guessing that the problem lies in the JUCE framework, or at least related to that. i have contacted Loomer with these details.

[Musical Gym]

Mine says 22.1.0. Do I have to go to Microsoft to update?
I guess stand-alone is still the same.

[JamminFool]

hi Musical Gym,
first you have to go to the Microsoft Store to get the update. then you have to let Wotja update the VST3 automatically (by running Wotja stand-alone as Administrator) or manually by following the short-cuts in the Help Menu of Wotja stand-alone.

[Musical Gym]

Was the stand-alone updated? When I go to Microsoft, I get a Buy button.

[JamminFool]

Was the stand-alone updated? When I go to Microsoft, I get a Buy button.

yes, both stand-alone and VST3 are updated. in the Store, click on Library (at the bottom of the left hand column). then click Get Updates button (near upper right).

[Musical Gym]

@JF Thanks for your help. Looks like vst3 was auto-updated in Common Files>VST3 without user intervention?

[JamminFool]

yes, but only if you ran as adminstrator (it should have prompted you, though).

[Musical Gym]

I got a weird prompt asking whether I wanted to update to the same version number. Maybe the prompt should say "Update VST3 to current version in Common Files>VST3 folder?"
I don't think a prompt is necessary.

[JamminFool]

hmmm, not sure exactly what happened there.

but, as long as you check the version number in the stand-alone (shown in Settings - top of page) and the VST3 shows the same number (in this case 22.1.2) then everything is OK.

[Musical Gym]

got it, thanks

[impete]

I got a weird prompt asking whether I wanted to update to the same version number. Maybe the prompt should say "Update VST3 to current version in Common Files>VST3 folder?"
I don't think a prompt is necessary.

Yeah, sorry about this. The alert text isn't displayed properly.

This is fixed in the next update (22.1.3 or later...)

Best wishes,

Pete

[impete]

congratulations!

Thank you very much JamminFool!

You've provided great feedback to us (as have many, many others on this forum - you know who you all are!) and that has allowed us to *touch wood* fix most (all?) of the big issues related to both the VST3 and Plug-in Hosting.

Happy days

That means that we can now start looking at adding more features.

Actually, that said, the next update will mainly be about a number of smaller bug fixes that I'm now catching-up with!

Best wishes to all,

Pete

[JamminFool]

congratulations!

Thank you very much JamminFool!

you are welcome.

That means that we can now start looking at adding more features.

speaking of which:
1) in the stand-alone, we badly need the mixer to apply to hosted VSTs.
2) meters in the mixer.

Actually, that said, the next update will mainly be about a number of smaller bug fixes that I'm now catching-up with!

speaking of which, this one still happens:

1) add Seq:Euc to cell.
2) add Repeater to same cell
3) connect Repeater to Seq:Euc
4) hang.