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

[zzz00m]

True, the "Help" menu has links to the folders, but it's still up to the user to complete the plugin update process manually. The Windows Store installer can not do it for you.

The point is that it's not obvious that you are still running an outdated VST3 plugin after the app updates. You need to manually check the "about" page in the plugin.

[zzz00m]

@impete

The MIDI Monitor in Studio One only works for external MIDI devices so I used this free monitor... https://www.kvraudio.com/product/midi_monitor_by_rs_met

This indicates that CC data is getting through to the instrument (which is probably why the MIDI track meter shows activity with the orange bar) but I don't see any note on/off which is probably why there is no sound. When I repeat this with Scaler 2 as the MIDI note provider I see note on/off messages on MIDI monitor and hear notes.

Maybe Studio One is filtering out the overlapping note on/off messages (similar to Cubase)?

Hi! I think I might have answered this by email?

My best guess is that this would be caused if you had multiple-cells, both feeding the same MIDI channel; that you were then delivering as a "merged stream" of MIDI events that then conflicted with each other.

Best wishes,

Pete

When I tried the MIDI Monitor in Studio One, all I got was this every time I hit play in the DAW. Regardless of what MIDI channel I had set in Wotja (example: ch 5), this monitor data was for Channel 1 only, so I would suspect that the DAW is inserting this data, but not passing any note data from the plugin:

Controller, Channel: 1, Number: 123 (All Notes Off), Value: 0
Controller, Channel: 1, Number: 121 (All Controllers Off), Value: 0

[impete]

True, the "Help" menu has links to the folders, but it's still up to the user to complete the plugin update process manually. The Windows Store installer can not do it for you.

The point is that it's not obvious that you are still running an outdated VST3 plugin after the app updates. You need to manually check the "about" page in the plugin.

My honest explanation for this is that I've been unable to figure-out how to make the installer put the plug-in file in the correct folder. I've asked Microsoft several times for pointers - but no response.

Best wishes,

Pete

[tatanka]

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

Transport bar still dont work .

[ZincT]

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.

The fixes in the current version (22.0.6) are mostly about improved plugin scanning and the dialog box no longer being hidden behind the app.

You can see the details of the changes in the MS Store "What's new in this version".

[tatanka]

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.

The fixes in the current version (22.0.6) are mostly about improved plugin scanning and the dialog box no longer being hidden behind the app.

You can see the details of the changes in the MS Store "What's new in this version".

Thanks, seems I mixed this up. Then back to the plugin-scanning and filling the blacklist

[zzz00m]

True, the "Help" menu has links to the folders, but it's still up to the user to complete the plugin update process manually. The Windows Store installer can not do it for you.

The point is that it's not obvious that you are still running an outdated VST3 plugin after the app updates. You need to manually check the "about" page in the plugin.

My honest explanation for this is that I've been unable to figure-out how to make the installer put the plug-in file in the correct folder. I've asked Microsoft several times for pointers - but no response.

Best wishes,

Pete

No worries, I figured that it was most likely a limitation with Microsoft Store.

For a possible workaround suggestion: maybe on Wotja startup, it checks to see if a new update is present since the last run, and then asks the user if they would like the VST3 to be updated. If the reply is "Y", then just use an automatic script to copy the VST3 file to the proper destination... or at least provide a tip that it need to be handled manually.

[zzz00m]

Ableton Live Suite 11.0.12: No transport sync (from host)
Tracktion Waveform Pro 11.5.18: No DAW transport sync (from host)

These are both fixed in the next Wotja 22 update - they shared the same issue!

Best wishes, Pete

Fantastic news!

So now I think the only thing I am still waiting for is the MIDI routing in Waveform.

I took another run at this issue using a different plugin to generate MIDI in Waveform, as a way to identify what Waveform can do.

I setup a Reason Rack plugin on track 1 with two Pattern Sequencers each patched into a MIDI Out module.
Pattern Sequencer #1 to MIDI Out ch #1.
Pattern Sequencer #2 to MIDI Out ch #2.

Then I monitored with MIDI Monitor with both pattern sequencers running.

The good news is that Waveform handled the MIDI channels exactly as sent. If data is sent on ch #1, receive from ch #1 works on another track. If data is sent on ch #2, then receive from ch #2 works as you would expect. However there is no apparent way to manipulate these channel numbers within Waveform itself. It is apparently fully dependent on the plugin sending the MIDI data.

On a related note, the same test run in Ableton Live and Studio One resulted in all sent MIDI data ending up on channel #1, regardless of the source plugin setting. In other words, MIDI data from a track sending on ch #2, is merged into ch #1 at the receiving end.

[JamminFool]

funny, as i did the exact same test and documented the results a few posts back. great minds think alike!

i posted over on the Tracktion forum to see if any users know of a way to get the route by channel going. there was a response indicating that there may be a way using the racks feature in waveform, but i have not had the time to explore it yet.

i'll report here if i discover anything.

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

[zzz00m]

Ableton Live Suite 11.0.12: No transport sync (from host)
Tracktion Waveform Pro 11.5.18: No DAW transport sync (from host)

These are both fixed in the next Wotja 22 update - they shared the same issue!

Best wishes, Pete

Fantastic news!

So now I think the only thing I am still waiting for is the MIDI routing in Waveform.

Heh! I've just been investigating MIDI routing in Ableton - and simply can't see how to get it working *at all*. Very frustrating!

Pete

I just replied to @JamminFool after running another test for this. In Ableton Live, all internal plugin sent MIDI appears to end up on channel #1 at the receiving end.

[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.

[Musical Gym]

Just a reminder for Windows users that you will probably still need to manually move the updated 22.0.6 VST3 plugin to your normal VST3 folder, "C:\Program Files\Common Files\VST3".

I just checked the running VST3 plugin version after the update for the application to 22.0.6, and it turned out that I was still running the initial plugin release 22.0.0.

The new VST3 plugin version was located here at "C:\Program Files\WindowsApps\Intermorphic.WotjaPro22_22.0.6.0_x64", which is in the Windows Store apps path. I just copied it over to my normal VST3 folder to complete the update.

Thanks for reminder; is this able to be "fixed" or do we need to do it this way in perpetuity? This could be a problem for Windows users who don't know how to take ownership and set permissions on folders.

[zzz00m]

Just a reminder for Windows users that you will probably still need to manually move the updated 22.0.6 VST3 plugin to your normal VST3 folder, "C:\Program Files\Common Files\VST3".

I just checked the running VST3 plugin version after the update for the application to 22.0.6, and it turned out that I was still running the initial plugin release 22.0.0.

The new VST3 plugin version was located here at "C:\Program Files\WindowsApps\Intermorphic.WotjaPro22_22.0.6.0_x64", which is in the Windows Store apps path. I just copied it over to my normal VST3 folder to complete the update.

Thanks for reminder; is this able to be "fixed" or do we need to do it this way in perpetuity? This could be a problem for Windows users who don't know how to take ownership and set permissions on folders.

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.

[Musical Gym]

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

[JamminFool]

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).

at least not in a straight-forward way. but like i said, i posted at the tracktion forum, and someone suggested that i investigate the "rack" feature to see if i could further route midi channels on to unique tracks.