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

[zzz00m]

Hi!

That is incredibly helpful feedback.

Can I please ask you to clarify what you mean by "No transport sync"?

Sorry if that is a dumb question , but I *presume* it is that the Wotja internal stop/start button don't control the *host* transport bar. Of course, I might be missing the point entirely, hence my asking!!

Wotja slaves to the *host* transport bar - the wotja internal start/stop buttons only stop/start wotja internally within the context of the DAW's master transport control. We might yet remove Wotja's internal play/stop buttons in the Plug-in versions of Wotja, to remove any ambiguity / confusion here!

Best wishes, Pete

Understood. I will try to clarify. I was NOT attempting to start/stop from Wotja. By "No transport sync" I meant that Wotja does not follow or respond to host transport start/stop or the host tempo sync.

And an update to my original post: I finally got the host sync to work in Reaper, Cakewalk , and Studio One. The latest as of 1/07/2022:

Have tested Wotja 22 Pro VST3 on Windows 10 Pro 21H2, with these DAWs:

Ableton Live Suite 11.0.12: No transport sync (from host), MIDI routing to another track/instrument is OK.
Cakewalk by BandLab 2021.12: DAW transport sync OK (from host), MIDI routing to another track/instrument is OK.
Reaper 6.43: DAW transport sync OK (from host), MIDI routing to another track/instrument is OK.
Studio One 5 Pro 5.4.1: DAW transport sync here OK (from host) But no MIDI channel routing to another track/instrument. MIDI routing is simple in this DAW. If an instrument supports MIDI output, it is available as a MIDI input selection for any other instrument track. But all channels (omni) are sent. No apparent way to filter them by channel in this DAW.
Tracktion Waveform Pro 11.5.18: No DAW transport sync (from host), no MIDI routing to another track/instrument (Note: I really don't use this DAW much anymore, so it's not a priority for me, but there may be other users that notice this).

[JamminFool]

Tracktion Waveform Pro 11.5.18: No DAW transport sync (from host), no MIDI routing to another track/instrument (Note: I really don't use this DAW much anymore, so it's not a priority for me, but there may be other users that notice this).

@impete, @zzz00m:

actually, Waveform DOES support MIDI routing to another track:

click on the MIDI input item in the Track input field and you will find "Route MIDI from Track..." in the menu.

it works great with Reason Rack. for example, i tested it by sending the MIDI output from a Reason Player to another track in my project.

UNFORTUNATELY: it doesn't work with Wotja 22 VST3.

this would appear to be a bug with Wotja.

it is also true that Wotja does not sync tempo or transport to Waveform.

since I am already left high and dry with Live not supporting multi-channel MIDI routing, I was really hoping to be able to do this in Waveform. since it IS supported in the DAW, i am now hoping that Wotja can be fixed to address this.

[ValliSoftware]

Now Wotja 22 Pro is hanging when validating on starting Logic Pro X 10.7.2 Arm, no Rosetta 2 installed,

Scanning in Logic Pro X.png

I have to abort to continue.

[zzz00m]

Tracktion Waveform Pro 11.5.18: No DAW transport sync (from host), no MIDI routing to another track/instrument (Note: I really don't use this DAW much anymore, so it's not a priority for me, but there may be other users that notice this).

@impete, @zzz00m:

actually, Waveform DOES support MIDI routing to another track:

click on the MIDI input item in the Track input field and you will find "Route MIDI from Track..." in the menu.

it works great with Reason Rack. for example, i tested it by sending the MIDI output from a Reason Player to another track in my project.

UNFORTUNATELY: it doesn't work with Wotja 22 VST3.

You are correct. The context of my Waveform statement, if not originally clear, was in terms of routing MIDI for Wotja VST3 only, not globally.

[JamminFool]

Tracktion Waveform Pro 11.5.18: No DAW transport sync (from host), no MIDI routing to another track/instrument (Note: I really don't use this DAW much anymore, so it's not a priority for me, but there may be other users that notice this).

@impete, @zzz00m:

actually, Waveform DOES support MIDI routing to another track:

click on the MIDI input item in the Track input field and you will find "Route MIDI from Track..." in the menu.

it works great with Reason Rack. for example, i tested it by sending the MIDI output from a Reason Player to another track in my project.

UNFORTUNATELY: it doesn't work with Wotja 22 VST3.

You are correct. The context of my Waveform statement, if not originally clear, was in terms of routing MIDI for Wotja VST3 only, not globally.

my bad, i misread your message. thanks for clarifying.

[rollasoc]

Oh how I dislike using the Microsoft store...

Thought I would get this having skipped 21.

Boot it up, starts to scan, locks up and then isn't running anymore.

Gonna be a long weekend....

[Banquet]

I'm finding Wotja very intriguing and must congratulate the devs for creating this. Some part of the interface seem very well thought out, and other parts are leaving me a little lost. I have some questions - I've had a look at the manual and searched YouTube for tutorials, but still not sure on some fairly basic things.

1/ When I create my own empty mix, even when I shut off the sounds, something still keeps playing. I have found out how to send the generators our to my hardware, which is great, but Wotja keeps playing even with a midi track selected with the sound sources deleted... how do I get Wotja to not play anything on the midi channels I'm routing to hardware (or to a plugin)?

2/ When I click on a generator button, I can edit it on the right of the screen. On that screen, just under 'pitch range' there's a 'Patch' selector, which has a name nothing like the sound source (it's often a piano). If you click on it, you can select lots of different instrument names, but doing so doesn't seem to change the sound source, or anything else that I can notice. What does this do?

It would be great if the devs (or anyone else) could do some really in-depth video tutorials.

[dopet]

Hi All,

Just sprung for the Pro version. I am here to confirm all the issues others have with Studio One 5. All graphics freezing when Wotja GUI is open, slow/sluggish to close GUI, and the BIG ONE ---- midi out from Wotja does not trigger the synths when routed to other midi tracks inside Studio One.

All other plugins that generate midi data work as expected.

[zzz00m]

After a few days of wrangling this thing, I decided to just let it do it's thing. Started a flow playing...

It's Friday evening, so just poured a glass of my favorite extra pale ale, and sitting here listening to the flow. And breathing...

I will dig deeper into it next week! Cheers!

[omphalocentric]

The version on the Windows app store is still at 22.02, so I'm having VST scanning failures.

Using it as a VST3 in Reaper, I found that that 48 kHz sample rate did not work: no apparent transport sync or MIDI to synths. Changing to 44.1 kHz and restarting Reaper got things working.

System specs:
Windows 10 (21H1)
Reaper 6.43
Motu Ultralite Mk4 ASIO

[zzz00m]

The version on the Windows app store is still at 22.02

That's what I see as well. The new version is apparently still under review by Microsoft.

[UncleAge]

1/ When I create my own empty mix, even when I shut off the sounds, something still keeps playing. I have found out how to send the generators our to my hardware, which is great, but Wotja keeps playing even with a midi track selected with the sound sources deleted... how do I get Wotja to not play anything on the midi channels I'm routing to hardware (or to a plugin)?

1. If you want to eliminate Wotja from using it's own sounds you can;
a. Click on the gear in the upper right-hand side, which takes you to settings. Go to the Audio MIDI+ tab.
b. Take the volume slider all the way down, or...
c. Uncheck the box for WAE For Sounds & FX and Hosted Plugins

2. You could go the the Mixer page along the top and reduce the volume on the cells you don't want to hear.

I asked about this earlier in the thread. I think Pete is putting out the big fires first but I am pretty sure the answer from the developer will come around.

Hope this helps.

[Musical Gym]

^thanks Uncle

[UncleAge]

@impete
I just came across the the sequence, loop, one shot functionality at the cell level. This led immediately to me looking for a few script examples that allow me to trigger cells via whatever. My Q is can I trigger one cell based on the outcome from another cell. For instance, let's say Cell 1 was playing an ambient generator and it occasionally hits a "C" note. Can script detect that and then trigger a different cell, Cell 2, to play?

I can see examples for external "CC" or MIDI note-in but was wondering about internal triggers

[Banquet]

1/ When I create my own empty mix, even when I shut off the sounds, something still keeps playing. I have found out how to send the generators our to my hardware, which is great, but Wotja keeps playing even with a midi track selected with the sound sources deleted... how do I get Wotja to not play anything on the midi channels I'm routing to hardware (or to a plugin)?

1. If you want to eliminate Wotja from using it's own sounds you can;
a. Click on the gear in the upper right-hand side, which takes you to settings. Go to the Audio MIDI+ tab.
b. Take the volume slider all the way down, or...
c. Uncheck the box for WAE For Sounds & FX and Hosted Plugins

2. You could go the the Mixer page along the top and reduce the volume on the cells you don't want to hear.

I asked about this earlier in the thread. I think Pete is putting out the big fires first but I am pretty sure the answer from the developer will come around.

Hope this helps.

Thanks. I found when you delete a synth/sound generator it seems to get replaced by a default piano sound, which is really annoying. You're right though, it can be turned down at the 'amp' level which is good to know.