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

[JamminFool]

ok, i guess that will work, but why should this be necessary? it seems like everything was working, and i just switch one track to use a different output, and that forces everything else to be re-routed by the user? maybe it makes sense given the way the code is organized, but not from the perspective of what a user might expect.

no big deal, but definitely counter-intuitive.

Well, I take your point!

Background to this: we decided after playing with original prototypes, that it if people were going to use hosted instruments, then from that point they *generally by default* wouldn't want to hear the Wotja Audio Engine output mixed-in as well.

The approach we have *does* allow the Wotja output to be mixed together with Instrument chains; and that can be filtered by Wotja Track(s) as well.

Just one of those design compromises!

We're going to document all this in the near future - just so much to do!

Pete

you are probably correct in this assumption.

[JamminFool]

as almost all other VSTs are displaying properly

there are other VST3 plugs which I reported with UI issues: Roland Cloud, and NI Massive X, for example. i guess i'm hoping a fix for one may be a fix for the others, as well?

[impete]

as almost all other VSTs are displaying properly

there are other VST3 plugs which I reported with UI issues: Roland Cloud, and NI Massive X, for example. i guess i'm hoping a fix for one may be a fix for the others, as well?

I'd guess so. There is probably a common JUCE bug behind these.

We keep up-to-date with JUCE releases, so I'd like to think that this will just "start working" due to ongoing maintenance by the JUCE team.

Pete

[ZincT]

Folks - I've just finished reviewing all comments in this thread. Was a mammoth task

Summary of outstanding issues with the Windows the VST3:

{snip}
If I'm missing anything, or have made any mistakes in the above, do please let me know!

Best wishes to all, Pete

Hi Pete,

Other issues which I have raised:

• You can route MIDI from the Wotja plugin to an instrument but there's no sound from the instrument in Studio One and Cubase.

• Wotja plugin crashes when trying to use Omnisphere (you have captured the workaround)

[impete]

• You can route MIDI from the Wotja plugin to an instrument but there's no sound from the instrument in Studio One and Cubase.

That is a weird one, to be sure. To be clear, that is about routing within the DAW itself?

Does the generic LoopBE work-around solve this?

https://intermorphic.com/help/#plugins-vst-midi-routing

Best wishes,

Pete

[ZincT]

• You can route MIDI from the Wotja plugin to an instrument but there's no sound from the instrument in Studio One and Cubase.

That is a weird one, to be sure. To be clear, that is about routing within the DAW itself?

Does the generic LoopBE work-around solve this?

https://intermorphic.com/help/#plugins-vst-midi-routing

Best wishes,

Pete

Yes routing within the DAW. When I try the same method with other MIDI generators in those DAWs such as Scaler 2 or InstaComposer they work fine.

I will try the LoopBE workaround but I found in the past that I tended not use MIDI generators e.g. AutoTheory Pro (now ChordPrism), that needed an external tool setup, which is why the Wotja plugin appeals to me.

[ZincT]

Folks - I've just finished reviewing all comments in this thread. Was a mammoth task

Summary of outstanding issues with the Windows the VST3:

If I'm missing anything, or have made any mistakes in the above, do please let me know!

Best wishes to all, Pete

I just found that NI Super 8 also does not show a full GUI (only a small upper left corner of the full plug).

[impete]

• You can route MIDI from the Wotja plugin to an instrument but there's no sound from the instrument in Studio One and Cubase.

That is a weird one, to be sure. To be clear, that is about routing within the DAW itself?

Does the generic LoopBE work-around solve this?

https://intermorphic.com/help/#plugins-vst-midi-routing

Best wishes,

Pete

Yes routing within the DAW. When I try the same method with other MIDI generators in those DAWs such as Scaler 2 or InstaComposer they work fine.

I will try the LoopBE workaround but I found in the past that I tended not use MIDI generators e.g. AutoTheory Pro (now ChordPrism), that needed an external tool setup, which is why the Wotja plugin appeals to me.

Is the routing issue one a generic one within the MIDI routing capabilities of Studio One and Cubase, or is it specific to the Wotja VST3 in these DAWs?

I've also seen on this thread that Live has limitations when it comes to MIDI routing... which surprised me!

Best wishes, Pete

[ZincT]

• You can route MIDI from the Wotja plugin to an instrument but there's no sound from the instrument in Studio One and Cubase.

That is a weird one, to be sure. To be clear, that is about routing within the DAW itself?

Does the generic LoopBE work-around solve this?

https://intermorphic.com/help/#plugins-vst-midi-routing

Best wishes,

Pete

Yes routing within the DAW. When I try the same method with other MIDI generators in those DAWs such as Scaler 2 or InstaComposer they work fine.

I will try the LoopBE workaround but I found in the past that I tended not use MIDI generators e.g. AutoTheory Pro (now ChordPrism), that needed an external tool setup, which is why the Wotja plugin appeals to me.

Is the routing issue one a generic one within the MIDI routing capabilities of Studio One and Cubase, or is it specific to the Wotja VST3 in these DAWs?

I've also seen on this thread that Live has limitations when it comes to MIDI routing... which surprised me!

Best wishes, Pete

I have only found it to be an issue with Wotja in these DAWs. That's not to say that there aren't other plugins which I don't own that have a similar issue in these DAWs.

[ZincT]

Folks - I've just finished reviewing all comments in this thread. Was a mammoth task

Work-around: "you can get the Reason Rack working using the same solution as Omnisphere i.e. a plugin host like Kushview Element, DDMF Metaplugin or PG Unify."[/list]

If I'm missing anything, or have made any mistakes in the above, do please let me know!

Best wishes to all, Pete

By the way, the cheapest workaround option is Kushview Element which can be purchased for $2 here --> https://kushview.net/shop/software/

I'm hoping to make a video of how to use it.

[impete]

Folks - I've just finished reviewing all comments in this thread. Was a mammoth task

Work-around: "you can get the Reason Rack working using the same solution as Omnisphere i.e. a plugin host like Kushview Element, DDMF Metaplugin or PG Unify."[/list]

If I'm missing anything, or have made any mistakes in the above, do please let me know!

Best wishes to all, Pete

By the way, the cheapest workaround option is Kushview Element which can be purchased for $2 here --> https://kushview.net/shop/software/

I'm hoping to make a video of how to use it.

Oooh - I've never heard of that

Pete

[JamminFool]

Folks - I've just finished reviewing all comments in this thread. Was a mammoth task

Work-around: "you can get the Reason Rack working using the same solution as Omnisphere i.e. a plugin host like Kushview Element, DDMF Metaplugin or PG Unify."[/list]

If I'm missing anything, or have made any mistakes in the above, do please let me know!

Best wishes to all, Pete

By the way, the cheapest workaround option is Kushview Element which can be purchased for $2 here --> https://kushview.net/shop/software/

I'm hoping to make a video of how to use it.

Oooh - I've never heard of that

Pete

but surely the Reason Rack should work in Wotja without needing a sub-host.

[Umcorps]

Is the "Macro Osc" based on Braids?

If it helps at all there is a video here that looks in more detail at the Macro oscillator and how it is implemented in Wotja.

[UncleAge]

I've also seen on this thread that Live has limitations when it comes to MIDI routing... which surprised me!

Best wishes, Pete

Always been that way in Live for any plugin that can output multiple midi channels (Kontakt, Microtonic, etc.). I don't think Ableton sees it as an issue. Or if they do there isn't an easy fix in their system. It is THE reason I switched to Bitwig Studio. I use multi-channel-midi out plugins a lot so I had to switch. And it should be noted I haven't had any showstopper issues with the VST version of Wotja in Bitwig. It just works.

As always, ymmv...

[zzz00m]

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

Yes, that is mostly the way I tested it in Reaper, except for that last part. Never touched the Reaper track #1 "route" for Wotja. Just the track #2 "route > new receive track # > MIDI ch#".