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

VST, AU, AAX, CLAP, etc. Plugin Virtual Instruments Discussion
Locked New Topic
RELATED
PRODUCTS
Wotja 22 Pro Wotja: Live Generative Music

Post

impete wrote: Wed Jan 05, 2022 4:42 pm
mcbpete wrote: Wed Jan 05, 2022 4:40 pm Hi Impete - Is there a way of getting Wotja to not autoscan my VSTi3s on launch? It seems to hit issues just after it hits waves plugins, though I only really intend to use it for generating midi notes so am happy for it to not use any of my vsts...
Hi!

Yes, this is changed in the next build, which I'm just finalising!

IMPROVED: Host Plug-in scanning:

Documents screen: rather than automatically starting a plug-in scan:
if you've not yet done a plug-in scan, you're prompted to do so
Title: "Scan for Hosted Plug-ins?"
Message: "You have not yet scanned for Hosted Plug-ins. Would you like to do this now?\n\nYou can scan at any time, by going to the Plug-ins screen, and press the top-left button to re-scan\n\nIf the plug-in scan closes Wotja, simply re-start Wotja; any failed plug-ins are listed in the Action menu on the Plug-ins screen."
Buttons: "Start Scan Now", "Ask Me Again Later", "Don't ask me again”

Plug-ins screen (tab): when top-left button pressed, we now display an alert before kicking-off the scan
Title: "Scan for Hosted Plug-ins?"
Message: "If the plug-in scan closes Wotja, simply re-start Wotja; any failed plug-ins are listed in the Action menu on this screen.";
Buttons: "Start Scan Now", “Cancel"

Plug-ins screen (tab): if you have failed plug-ins, you see two menu items at top of menu:
"Show Failed Plug-ins: 1 failed" (or whatever the number is)
shows alert "The following plug-ins have failed while scanning:"
"Reset Failed Plug-ins, and Re-scan"
... these aren't show if there are no failed plug-ins
Verified on Windows with my home-made VST3 failing plug-in :)
@impete

This updated scanning sounds great! I was going to suggest at least a scan log to see which plugin the scan stopped on. But this is better! The scanner info line in the current version sometimes lags and does not always update the actual plugin being scanned in real-time.
Windows 10 and too many plugins

Post

UncleAge wrote: Wed Jan 05, 2022 5:19 pm
JamminFool wrote: Wed Jan 05, 2022 5:04 pmThank you for spending your time confirming this for me. Bummer, since this is exactly what I want to do with the Wotja VST3.
I asked for this in Live many years ago. I didn't see it come down the pike so I switched to Bitwig. And yes, Reaper can do this natively as well.

However, to get you going I am pretty sure a midi loop-back app like LoopBe can take care of this for you. Use LoopBe as your output on the Wotja track and input on any tracks that you want to work with. If I remember correctly each of the midi channels will be available to pick from. All you have to do really is assign each generator to a separate midi channel in Wotja. And if memory serves me correct LoopBe is free. I have no idea if this will work in your OS.
thank you. i will look into this. :hug:

Post

impete wrote: Wed Jan 05, 2022 5:50 pm Once Wotja 22.0.6 is pushed out, I'll get back to looking at issues reported around the Wotja VST3, as well as various VST3 hosting niggles.

Never a shortage of things to do :)

Pete
thanks for your attention to this thread. i really appreciate what you are doing!

Post

impete wrote: Wed Jan 05, 2022 5:50 pm Once Wotja 22.0.6 is pushed out, I'll get back to looking at issues reported around the Wotja VST3, as well as various VST3 hosting niggles.

Never a shortage of things to do :)

Pete
My interest is mostly for using Wotja as a DAW plugin. But I was playing around with the standalone version and thought I might try out an FX plugin.

I do like the way that the internal Wotja plugin browser is organized.

Running a mix through the IK T-RackS Leslie was interesting... :D
Windows 10 and too many plugins

Post

zzz00m wrote: Wed Jan 05, 2022 5:52 pm This updated scanning sounds great! I was going to suggest at least a scan log to see which plugin the scan stopped on. But this is better! The scanner info line in the current version sometimes lags and does not always update the actual plugin being scanned in real-time.
Thanks! I think it'll solve a lot of problems, but am always going to be open to ways to improve it.

Best wishes, Pete

Post

JamminFool wrote: Wed Jan 05, 2022 5:56 pm thanks for your attention to this thread. i really appreciate what you are doing!
No problem. We're very grateful for all the support we're getting here! :)

Best wishes, Pete

Post

zzz00m wrote: Wed Jan 05, 2022 6:00 pm I do like the way that the internal Wotja plugin browser is organized.
Thank you! I thought about it very carefully. It took me a long time to formulate out in my mind, thinking it all through; before writing the spec and then coding.

Pete

Post

Sorry if this is an obvious thing I am overlooking but i looked both here and in the online manual without any luck. I purchased Pro yesterday and installed it from the MS Store on Win 10. Stand alone works and I can see all of the VST3 plug-ins I have. I have not tested them all but the one I did test and it worked was Dawsome Abyss.
My DAW = BitWig 4.08 and I do not see the Wotja plugin anywhere. Since it installed via the MS Store I am not sure where to tell BitWig to look for it to try and re-scan. If it is in the C:\Program Files\Common Files\VST3 i have that folder already added and I have no issues with any other VST3s in there. I also looked in the list of plugin with errors and it is not in there either.
Is anyone able to help? Thanks in advance!

Post

@Laqua:

you need to manually move it to the VST3 folder. if you look in the Help menu of Wotja, there will be two entries:

one will take you to the install folder where the VST3 version is placed. Go there and copy the dll.

the other entry in the Help menu will take you to the default VST3 folder on Windows. Paste the dll there.

After that, your DAW should pick it up when it rescans.

Post

Thanks Jammin! I will give that a try. I saw the Documents folder where the saves go but I must have missed the folder in the Help menu with the DLL. I knew I must have missed something obvious!

Post

@JamminFool
I have now installed Reason and tested the Reason Rack in standalone Wotja and it's not working here either. Whatever instruments I select in the rack are not played by Wotja.

Post

ZincT wrote: Wed Jan 05, 2022 7:57 pm @JamminFool
I have now installed Reason and tested the Reason Rack in standalone Wotja and it's not working here either. Whatever instruments I select in the rack are not played by Wotja.
yup, thanks for confirming! :tu:

Post

Are some of the chord structures, motifs, etc. inside Wotja pre-written/determined?
Can Wotja's "samples" be played by an external controller without Wotja generating anything extra (played as one-shots)?

Post

I must admit the VST3 version is also still a bit rough. It sometimes completely crashes and even reloading the plugin won't work, I have to restart Bitwig. Sometimes it works nicely, but it's not very stable. Hope after the scanning is sorted, we will see some stability fixes. Still lovely plugin though.

Post

Musical Gym wrote: Wed Jan 05, 2022 8:10 pm
Can Wotja's "samples" be played by an external controller without Wotja generating anything extra (played as one-shots)?
I have been trying to figure that out also. It seems the Listener+Follower Generator is the starting point for this, but I'm not entirely sure about how well it will work. There seems to be some latency when i tried it. It also requires a note off before the next note on is played. So I think I may be missing what it's real intended purpose is.

Locked

Return to “Instruments”