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

[zzz00m]

the good news is that i have purchased WotjaPro 22 because i think it is a really cool program.

Great news!!!

It's an amazing program, and glad to have it also!

[ZincT]

@impete and @zzz00m

I finally figured out how to use multi channel MIDI out of the Wotja plugin in Studio One routing the MIDI to a single instance of a multi-timbral instrument like Kontakt or Miroslav Philharmonic.

There's a little arrow above the instrument UI for multi-timbral instruments which allows you to route each MIDI channel to each layer in the instrument.

Here's a video demoing the functionality...

[zzz00m]

@impete and @zzz00m

I finally figured out how to use multi channel MIDI out of the Wotja plugin in Studio One routing the MIDI to a single instance of a multi-timbral instrument like Kontakt or Miroslav Philharmonic.

There's a little arrow above the instrument UI for multi-timbral instruments which allows you to route each MIDI channel to each layer in the instrument.

Here's a video demoing the functionality...

@ZincT

Wow! Very kewl!!!

I looked all over for a clue to something like that. PreSonus could not have hidden that item in a less intuitive place, LOL!!! How the heck did you locate it?

Well done!

[ZincT]

@impete and @zzz00m

I finally figured out how to use multi channel MIDI out of the Wotja plugin in Studio One routing the MIDI to a single instance of a multi-timbral instrument like Kontakt or Miroslav Philharmonic.

There's a little arrow above the instrument UI for multi-timbral instruments which allows you to route each MIDI channel to each layer in the instrument.

Here's a video demoing the functionality...

@ZincT

Wow! Very kewl!!!

I looked all over for a clue to something like that. PreSonus could not have hidden that item in a less intuitive place, LOL!!! How the heck did you locate it?

Well done!

@zzz00m Cheers

I find that a lot with Studio One; things hidden in plain sight! Anyway, I decided to post a question on the Presonus Forum but, just before I posted, did a search there for "MIDI routing multi timbral instrument" or something like that. It uncovered a few posts with the solution including this one...

https://forums.presonus.com/viewtopic.p ... al#p273950

I also quickly tried it with Kontakt in the following config...

• Amadeus full symphony ch1, Alicias keys ch2, Ethereal Earth (Synthy Out of Breath) ch3 and Cinematic Keys (Key Maker) ch4.

• Wotja tk1 Ambient, Tk 2 Gen + Foll, Tk 3 List + Foll, Tk 4 Euc Seq.

Wow! Sounded amazing!

Incidentally, Cubase works slightly differently but a similar idea. Having created an instrument track, you select the instrument track and then add as many MIDI tracks as you have output tracks from Wotja. Each of these MIDI tracks will be routed to the instrument on sequential MIDI channels and you just have to set their input to Wotja.

[JamminFool]

@pete,
There are some minor problems with FX Presets:

1) The Preset name display and drop down list for Reverb 1 Presets do not update. It always shows "User-defined". The selected Preset is loaded, but the display does not reflect the new name.

2) Also, Reverb 2XL and Equaliser uses the name "Custom" while Reverb 1 and Chorus use "User-defined".

3) After you select a Preset in FX section, if you click back on the icon for the FX (in the graph), it changes the Preset name from the selected Preset to "Custom", or "User-defined" instead of retaining the selected name.

[JamminFool]

what does "Embed Host Plug-in UIs" in General Settings do? it's not documented.

EDIT: figured it out. seems like it should be called "Embed Hosted Plug-in UIs".

[JamminFool]

@pete:

i have been testing the Embed Host plug-in UIs setting:

1) if you embed a plugin UI, and then navigate straight to the Music page (or any of the other main pages), you will have the plugin UI pasted on top like this:
*

Embedded Plug UI screen corruption 1.jpg

*

i assume this this is not intended (but rather only on the Hosted Plug-in page), as it makes the other pages un-useable while the setting is in effect.

2) if you play around long enough with the feature (if i recall, i exited the embedded plug page first, returning to the Hosted Plug-in page, then tried to re-open the plugin UI) it can then corrupt the UI further by showing a remnant of a previous piece of the Wotja UI instead of the plugin UI, like this:
*

Embedded Plug UI screen corruption 2.jpg

*
3) note: the above example also intentionally shows a plug-in (Roland Cloud D-50) which already has a problem with it's window being drawn properly in Wotja. but i was able to reproduce (1) and (2) above with other plugins also.

4) it would be great if on the Hosted Plug-in page, the Embedded Plug-in UI's did not obscure the row which provides quick access to the Plug-in chains (labeled #1, #2...., Master) so that you would not have to dismiss one plug-in in order to view another. you could just switch between them with 1-click (however, i guess that won't handle the case of FX plug-ins in the chain....hmmmm)

[JamminFool]

Hi Pete,
I find it very counter-intuitive to use Loop/Unloop to trigger a cell in a row which uses the One-Shot mode (Zap icon).

It makes sense for the Loop mode (obviously), but re-using this button is confusing in One-shot mode, which is by definition not a loop.

Worse, to use it as a trigger means that the first time you want to trigger it, you turn Loop on. The next time you want to trigger it, you turn Loop off. Then on, then off, etc...

May I suggest that the Cell Action menu and the Cell Properties panel switch to showing "Trigger cell" when in One-Shot cell sequencing mode. Then it should be automatically reset to off when the cell is finished playing.

Alternatively, you could use "Trigger cell" for both One-shot and Loop mode, since the cell sequencing icon already makes it clear that it will either trigger a one-shot or a loop. Again it would automatically reset to off in One-shot mode when the cell finishes playing, or wait for the user to toggle it off to end looping in Loop mode.

[zzz00m]

Hey, a request please!

If anyone else here is running a Focusrite USB audio interface with Wotja, kindly PM me if you don't mind sharing notes.

I ran into an audio output issue here using the VST3 plugin, but it is not happening to another Wotja user I contacted who is using a different brand of audio interface. I have already ruled everything else out, and have narrowed it down to the Focusrite USB audio driver installed here.

I would just like to see if it's something common to the Focusrite driver, or just to me!

Thanks!

[JamminFool]

@zzz00m

Here is an screen grab that I made to show a simple arrangement with Waveform 11 Pro and Wotja 22.0.10 Pro. This is with the Waveform Experimental Engine switched "off".

in this post, you showed an example of Wotja 22.0.10 sending MIDI to a multitimbral VST and showed a MIDI Monitor to verify that the VST was receving MIDI data on all channels being sent.

However, using the above example, I could not get Waveform 11 Pro and the new Wotja 22.0.11 Pro to play more than a few notes before the MIDI stopped being routed. I tried it with the Experimental Engine both off & on.

in this post, you agreed with me that something was broken in the Wotja 22.0.11 release and that it no longer worked.

That wasn't my experience in Waveform 11 Pro when I sent Wotja 22 Pro MIDI directly to a multi-timbral instrument plugin on another track. All channels sent were received at the instrument. No racks used.

But this only worked with the Waveform experimental engine disabled.

Can you please verify once more that this is working for you in Wotja Pro 22.1.0? I would really appreciate it since I think I may be going crazy.

You originally had agreed that the 22.0.11 had broken it after being fixed in 22.0.10 (if you recall, we had cross-posted on page 40 of this thread) but when I reported that recently here in this thread, you posted that you had it working.

Currently I can not get it to work even though the Experimental Engine is off in Waveform Pro.

[impete]

what does "Embed Host Plug-in UIs" in General Settings do? it's not documented.

EDIT: figured it out. seems like it should be called "Embed Hosted Plug-in UIs".

Hi! I'll run your suggestion past Tim, and see what we think

Many thanks, Pete

[impete]

i have been testing the Embed Host plug-in UIs setting:

Hi! And: many thanks for your detailed feedback, it is really appreciated.

The background to this is what we found, from experimentation last year:

- displaying AUv3 in hosted Window or embedded in Wotja always works fine. We default to the latter, as we think it looks better in most cases.

- displaying VST3 in hosted Window generally works fine (some plug-ins still have issues), but embedded in Wotja rarely seems to work as we'd want. I simply couldn't figure-out why, but that is the reason why for Windows, we default to the hosted Windows case, but allow the embedded case for experimentation as an alternative (I've not yet given up on it!)

So, that explains what you're seeing, really.

As a result, for Windows I'll look to change in the future to say something along the lines that the that Embedded mode is "experimental" ...

Best wishes, Pete

[impete]

Hi Pete,
I find it very counter-intuitive to use Loop/Unloop to trigger a cell in a row which uses the One-Shot mode (Zap icon).

It makes sense for the Loop mode (obviously), but re-using this button is confusing in One-shot mode, which is by definition not a loop.

Worse, to use it as a trigger means that the first time you want to trigger it, you turn Loop on. The next time you want to trigger it, you turn Loop off. Then on, then off, etc...

May I suggest that the Cell Action menu and the Cell Properties panel switch to showing "Trigger cell" when in One-Shot cell sequencing mode. Then it should be automatically reset to off when the cell is finished playing.

Alternatively, you could use "Trigger cell" for both One-shot and Loop mode, since the cell sequencing icon already makes it clear that it will either trigger a one-shot or a loop. Again it would automatically reset to off in One-shot mode when the cell finishes playing, or wait for the user to toggle it off to end looping in Loop mode.

Hi! Many thanks for this suggestion. We're hoping to look again at cell looping in a new context quite soon (Tim keeps pushing, but I'm really busy right now tidying-up a some old code); so, I've logged your idea in full, and will look at it as soon as we get to look at cell looping!

Best wishes, Pete

[impete]

@pete,
There are some minor problems with FX Presets:

1) The Preset name display and drop down list for Reverb 1 Presets do not update. It always shows "User-defined". The selected Preset is loaded, but the display does not reflect the new name.

2) Also, Reverb 2XL and Equaliser uses the name "Custom" while Reverb 1 and Chorus use "User-defined".

3) After you select a Preset in FX section, if you click back on the icon for the FX (in the graph), it changes the Preset name from the selected Preset to "Custom", or "User-defined" instead of retaining the selected name.

Hi! This, believe it or not, is ~12 year old UI code logic (!) that's been bugging me probably for 10 years - there always seems to be something more critical to do however (that is what we get with half a million lines of code and just one developer!). Anyhow, I've just now added your notes to the issue tracker item.

Best wishes, Pete

[JamminFool]

i have been testing the Embed Host plug-in UIs setting:

Hi! And: many thanks for your detailed feedback, it is really appreciated.

The background to this is what we found, from experimentation last year:

- displaying AUv3 in hosted Window or embedded in Wotja always works fine. We default to the latter, as we think it looks better in most cases.

- displaying VST3 in hosted Window generally works fine (some plug-ins still have issues), but embedded in Wotja rarely seems to work as we'd want. I simply couldn't figure-out why, but that is the reason why for Windows, we default to the hosted Windows case, but allow the embedded case for experimentation as an alternative (I've not yet given up on it!)

So, that explains what you're seeing, really.

As a result, for Windows I'll look to change in the future to say something along the lines that the that Embedded mode is "experimental" ...

Best wishes, Pete

but are the embedded plug UIs supposed to display themselves when the user switches back to the Music tab, or Display tab, or Text tab, for example? that seems like a bug that needs to be fixed.