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

[ZincT]

I had to take/change ownership to get into WindowsApps.

I found that if I tried to access the WinodwsApps folder manually through Explorer it also required me to change permissions, but if I access it through the Wotja Help menu item "Show the Wotja VST3 plugin" no permission changes are needed and you can then copy the plugin to the correct folder.

[Musical Gym]

^^Thanks, I forgot that's how I initially did it. This last time I followed the "path" shown in a prior post which caused Windows to give me the alert.

[impete]

Seems the fix for transport bar problems in some daw is not the one for Mixcraft 9 Pro.

Transport bar still dont work .

I think Pete said the transport fixes will be in the next release although he didn't specifically mention Mixcraft but I guess the same fix might work.

I don't have Mixcraft, but having verified the fix with Ableton Live and Tracktion, I have high confidence the fix will work there too!

Best wishes, Pete

[impete]

The dev is aware, and it seems to be a Windows Store app limitation at the moment. I didn't run into any ownership/permissions issue just copying the .VST3 file into "C:\Program Files\Common Files\VST3". I am running Windows 10 Pro as a standard user with Admin privileges.

The issue of permissions - not something I think I can work around.

I like the idea of the app (if you run it!) auto-copying an update to the VST Plug-ins folder; but Windows permissions might well prevent that. It is a pain for sure, but at least there is a consistent work-around.

Best wishes, Pete

[Musical Gym]

^^Getting to it from the Help menu is easy enough. It may need emphasizing for new users.

[JamminFool]

Here is a Waveform Rack which allows me to split the MIDI by Channel and route it to two different Tracks. It uses Reason Rack with two Players generating MIDI, one on MIDI Ch. 1 and the other on MIDI Ch. 2.

The key is using the MIDI Patchbay plugin to split the MIDI output from Reason (or eventually Wotja), and send it to separate plugins all inside the Waveform Rack.

Once Wotja is fixed to send MIDI data in Waveform, it can replace the Reason Rack to get the desired result.
*
*

Waveform MIDI Channel Routing Rack.jpg

*
*
There may be better ways to do this, and I am still exploring, but meanwhile this serves a proof of concept that Waveform can be a good match for the Wotja VST3.

EDIT1: first improvement is to move the MIDI generator plugin out of the Waveform Rack and place it on it's own Track. Then use "Route MIDI to..." send it to a Track containing the Waveform Rack:
*
*

Waveform MIDI Channel Routing Rack Improved.jpg

*

this makes it easier to access the MIDI Generator plugin (Reason Rack, Wotja, etc.).

[impete]

The dev is aware, and it seems to be a Windows Store app limitation at the moment. I didn't run into any ownership/permissions issue just copying the .VST3 file into "C:\Program Files\Common Files\VST3". I am running Windows 10 Pro as a standard user with Admin privileges.

I'm currently experimenting to see if it is possible to improve on this.

Pete

[zzz00m]

otherwise, i know of some feature requests for the waveform and live teams...

Actually, the Waveform MIDI routing should work as is. At least it does with Reason Rack sending data to channel #2 on another track.

yes, if you are sending all midi channels to the same track. but there is no way to send midi channel 1 from track 1 to track 2 and midi channel 2 from track 1 to track 3, etc. (which is the ultimate goal).

I'm not saying that Tracktion can "route" them that way, just saying that if the plugin used on track #1 can send out data for MIDI ch 2, track 2 or track 3 will "see" this data on MIDI ch 2. Data stays on the channel that the first plugin sends it out as.

Therefore Tracktion doesn't force everything to MIDI ch 1 as Ableton does. Tracktion leaves them be as they are generated by the plugin on track 1.

For proof, just set up a Reason Rack, or anything that can send out exclusively on a select MIDI ch. Set this for ch 2. Then set an instrument on another track (for example Kontakt or any multi-timbral synth) that has capability to only receive a select MIDI channel. Set that for MIDI ch2. Use Tracktion to set receive MIDI from track 1. It will only play MIDI ch 2 data. The data does not get transformed to ch 1.

[JamminFool]

i guess you haven't been reading my latest posts, in which i describe all of this in detail also.

in fact, two posts above yours, i describe a method to route by MIDI channel in Tracktion Waveform (i had previously thought this was not possible).

but yeah, i am aware of the limitation in Live, and have already submitted a feature request for MIDI channel routing over at the Ableton website.

@impete:
So, just waiting for Wotja to fix the MIDI output in Waveform, and i'm ready to buy!

[impete]

@impete:
So, just waiting for Wotja to fix the MIDI output in Waveform, and i'm ready to buy!

Cool However, I've not yet been able to figure-out why I can't route MIDI from Wotja in Tracktion Waveform.

It is kind of weird, in that it works (AFAIK) for every other Windows host (noting the restrictions in Ableton), so TBH it *does* have the feel to me of being in a bug in Tracktion Waveform.

Hopefully we'll figure it out soon enough!

Pete

[zzz00m]

i guess you haven't been reading my latest posts, in which i describe all of this in detail also.

in fact, two posts above yours, i describe a method to route by MIDI channel in Tracktion Waveform (i had previously thought this was not possible).

Yes, I read that and it should work, buy IMO don't think it is necessary to do it that way.

[JamminFool]

i guess you haven't been reading my latest posts, in which i describe all of this in detail also.

in fact, two posts above yours, i describe a method to route by MIDI channel in Tracktion Waveform (i had previously thought this was not possible).

Yes, I read that and it should work, buy IMO don't think it is necessary to do it that way.

it is if you want to route by MIDI channel.

[JamminFool]

@impete:
So, just waiting for Wotja to fix the MIDI output in Waveform, and i'm ready to buy!

Cool However, I've not yet been able to figure-out why I can't route MIDI from Wotja in Tracktion Waveform.

It is kind of weird, in that it works (AFAIK) for every other Windows host (noting the restrictions in Ableton), so TBH it *does* have the feel to me of being in a bug in Tracktion Waveform.

Hopefully we'll figure it out soon enough!

Pete

but it works in Waveform using other plugins. Just not in Wotja.

[zzz00m]

@impete:
So, just waiting for Wotja to fix the MIDI output in Waveform, and i'm ready to buy!

Cool However, I've not yet been able to figure-out why I can't route MIDI from Wotja in Tracktion Waveform.

It is kind of weird, in that it works (AFAIK) for every other Windows host (noting the restrictions in Ableton), so TBH it *does* have the feel to me of being in a bug in Tracktion Waveform.

Hopefully we'll figure it out soon enough!

Pete

Fyi, Tracktion was originally written by Julian “Jules” Storer, the primary architect of JUCE (Jules’ Universal C++ Extensions).

Tracktion Waveform is JUCE based, and was renamed to Waveform in version 8.

Hope you can get things sorted with Waveform or any JUCE bugs... the Tracktion engine open source is available on GitHub. https://github.com/Tracktion/tracktion_engine/

https://www.tracktion.com/develop/tracktion-engine

[zzz00m]

i guess you haven't been reading my latest posts, in which i describe all of this in detail also.

in fact, two posts above yours, i describe a method to route by MIDI channel in Tracktion Waveform (i had previously thought this was not possible).

Yes, I read that and it should work, buy IMO don't think it is necessary to do it that way.

it is if you want to route by MIDI channel.

Well I was able to do that without a rack.