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

[impete]

I know you are still working on all the bugs but please for the love of god.......more tutorials as soon as you can please!!! I am having a blast with what I can figure out so far but I am nowhere near as technical as all of you other Wojta users.
Thanks!!!!!!

Hi Laqua,

Many thanks for your kind words - and do please leave a review if you can

Tim is very, very keen on creating tutorials, but they take a long time to craft (as we tie then in with a lot of interactive visuals). If you have any specific requests, I'd suggest you send them in via our website contact page, as Tim is bound not to lose them that way!

There are a lot of Wotja users on here now, and - thank you all- there is a lot of love for Wotja out there, so I'm guessing if you have specific questions you should just ask away here and see what response you get!

Best wishes, Pete

[zzz00m]

I can confirm this does indeed work now with both:

>>> FIXED (Windows): Plug-in Transport bar control from Ableton Live, Tracktion Waveform Pro

Great work Pete!

[ZincT]

I have been using the spreadsheet below to track any problems I've been having with the Wotja plugin in various DAWs or DAW like programs. I shared it with Pete who suggested others might find it useful and asked if I would post it here.
So here it is.

LATEST RESULTS ARE HERE --> viewtopic.php?f=1&t=575707&start=529

After a number of updates (thanks @impete) the only remaining issue on the grid is the Studio One Pro 5 MIDI routing issue - MIDI seems to get routed to an instrument track (you can see activity on the track meter) but no instrument sound is heard. I have raised a support ticket with Presonus asking for someone who would be able to discuss the issue with Pete.

[Musical Gym]

Do we get notified when there's an update?
If not, can you keep the latest version number in thread title?

[zzz00m]

After a number of updates (thanks @impete) the only remaining issue on the grid is the Studio One Pro 5 MIDI routing issue - MIDI seems to get routed to an instrument track (you can see activity on the track meter) but no instrument sound is heard. I have raised a support ticket with Presonus asking for someone who would be able to discuss the issue with Pete.

@ZincT

Thanks for raising this issue with PreSonus! There also seems to be a performance hit with Studio One using high CPU on a single core as well, that may have something to do with the GUI lag I have also observed, with the transport apparently frozen and slow to close with the Wotja window open.

So Studio One and Tracktion Waveform are apparently the only DAWs with known Wotja MIDI routing issues. @impete has contacted Tracktion Support, so the ball is hopefully rolling towards a solution for both DAWs.

[JamminFool]

hi pete,

i have a reproducible crash in 22.0.9 stand-alone:

1) start with empty mix
2) add Generator: Sequence-Euclidean to cell 1
3) add Generator: Repeater to cell 1
4) drag connection from Repeater to Sequence-Euclidean
5) start playback (if not already playing)
6) wait for it. (you may need to stop and start playback once)

admittedly, step (4) may not make sense (i really don't know) but is the result of experimenting with "i wonder what will happen" type of approach, which wotja inspires

[JamminFool]

hi pete,

i found a behavior involving double-clicking which you may want to prevent:

1) open an empty mix
2) add a Generator: Ambient (for example)
3) in the Generator Editor Panel, select Patch
4) double-click on the name of one of the patches shown (must double-click on the text of the name to clearly demonstrate)
5) observe that the second click of the double click has actually selected the cell which is under the text of the patch name.

it seems that double-click should be treated as single click while selecting patch names to prevent the second click from potentially editing the main screen.

[impete]

hi pete,

i found a behavior involving double-clicking which you may want to prevent:

1) open an empty mix
2) add a Generator: Ambient (for example)
3) in the Generator Editor Panel, select Patch
4) double-click on the name of one of the patches shown (must double-click on the text of the name to clearly demonstrate)
5) observe that the second click of the double click has actually selected the cell which is under the text of the patch name.

it seems that double-click should be treated as single click while selecting patch names to prevent the second click from potentially editing the main screen.

Many thanks - I've logged this for investigation!

Best wishes, Pete

[impete]

hi pete,

i have a reproducible crash in 22.0.9 stand-alone:

1) start with empty mix
2) add Generator: Sequence-Euclidean to cell 1
3) add Generator: Repeater to cell 1
4) drag connection from Repeater to Sequence-Euclidean
5) start playback (if not already playing)
6) wait for it. (you may need to stop and start playback once)

admittedly, step (4) may not make sense (i really don't know) but is the result of experimenting with "i wonder what will happen" type of approach, which wotja inspires

Many thanks - I've logged this one as well!

Best wishes, Pete

[impete]

Thanks for raising this issue with PreSonus! There also seems to be a performance hit with Studio One using high CPU on a single core as well, that may have something to do with the GUI lag I have also observed, with the transport apparently frozen and slow to close with the Wotja window open.

I'm optimistic that 22.0.10 will resolve your performance problems with Studio One. We're just preparing this for app store reviews. Fingers crossed!

So Studio One and Tracktion Waveform are apparently the only DAWs with known Wotja MIDI routing issues. @impete has contacted Tracktion Support, so the ball is hopefully rolling towards a solution for both DAWs.

I heard back from Tracktion Support, and told them what they need to do in order to reproduce the issue. So, that is progress!

Pete

[impete]

Do we get notified when there's an update?
If not, can you keep the latest version number in thread title?

Hi!

Here is our Windows Store FAQ entry, explaining how you get updates etc.

https://intermorphic.com/help/#windows-app-update

NB: if you update the app, but primarily use the VST3: do please remember to run the updated app at least once, so you can get the app to update your VST3...!

If you keep an eye on https://intermorphic.com - and why wouldn't you, there is a ton of great stuff to read there - you'll also see the latest version displayed in the top right.

And, of course, we'll post update info here.

I hope that all helps!

Best wishes, Pete

[impete]

I can confirm this does indeed work now with both:

>>> FIXED (Windows): Plug-in Transport bar control from Ableton Live, Tracktion Waveform Pro

Great work Pete!

Cheers!

Pete

[ZincT]

After a number of updates (thanks @impete) the only remaining issue on the grid is the Studio One Pro 5 MIDI routing issue - MIDI seems to get routed to an instrument track (you can see activity on the track meter) but no instrument sound is heard. I have raised a support ticket with Presonus asking for someone who would be able to discuss the issue with Pete.

@ZincT

Thanks for raising this issue with PreSonus! There also seems to be a performance hit with Studio One using high CPU on a single core as well, that may have something to do with the GUI lag I have also observed, with the transport apparently frozen and slow to close with the Wotja window open.

So Studio One and Tracktion Waveform are apparently the only DAWs with known Wotja MIDI routing issues. @impete has contacted Tracktion Support, so the ball is hopefully rolling towards a solution for both DAWs.

@zzz00m

I thought about posting in the Presonus forums but I just don't find it as good as the Cakewalk forums for such things.

I think you are correct about the GUI lag; I have been testing the Wotja beta 22.0.10 and, as well as fixing the Cakewalk glitching issues, it seems to have also made a marked improvement in other DAWs including Studio One which now is as smooth as butter with the Wotja UI open or closed. I'm also not seeing any CPU spikes with the beta.

[impete]

I have been using the spreadsheet below to track any problems I've been having with the Wotja plugin in various DAWs or DAW like programs. I shared it with Pete who suggested others might find it useful and asked if I would post it here.
So here it is.

Thank you *very* much for this - and all your help (and the rest of you KVR-er's on this thread!) in helping us to polish-up the Wotja VST3 in double-quick time.

A small company is nothing without an enthusiastic and supportive user base.

In the normal course of things, long-standing Intermorphic watchers will know that we release Wotja updates quite often, as we fix issues and add new features - but we have *really* pushed out a lot in the past couple of weeks!

Best wishes to all,

Pete

[impete]

don't worry, you are not alone. there is a lot to learn here!

Wotja is very deep and quite open-ended. Just experiment at your own pace!

We have many long-standing customers who've been using with our software since the early days of Koan - so that is 30 or so years of fun creating and experimenting. Which is a nice thing to ponder

Pete