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

[ZincT]

I have been testing beta 11 and the good news is that Studio One now works when routing MIDI from the Wotja plugin to a virtual instrument on another track. Maybe the fixes for Tracktion also helped with Studio One but either way stellar work Pete

I have also included results for Tracktion Waveform 11.

Here's the updated spreadsheet for beta 11.

[impete]

I have been testing beta 11 and the good news is that Studio One now works when routing MIDI from the Wotja plugin to a virtual instrument on another track. Maybe the fixes for Tracktion also helped with Studio One but either way stellar work Pete

Wow - that is incredibly helpful, and very generous of your time to compile the spreadsheet!

Many thanks again,

Pete

[ZincT]

I have been testing beta 11 and the good news is that Studio One now works when routing MIDI from the Wotja plugin to a virtual instrument on another track. Maybe the fixes for Tracktion also helped with Studio One but either way stellar work Pete

Wow - that is incredibly helpful, and very generous of your time to compile the spreadsheet!

Many thanks again,

Pete

Glad to help Pete and congrats on some great bug zapping!

[courtjestr]

I have been testing beta 11 and the good news is that Studio One now works when routing MIDI from the Wotja plugin to a virtual instrument on another track. Maybe the fixes for Tracktion also helped with Studio One but either way stellar work Pete

I have also included results for Tracktion Waveform 11.

Here's the updated spreadsheet for beta 11.

Hey ZinkT. Do you have Unify? I tried to use Wotja on a midi effect layer but it is not working. I inserted a midi monitor after Wojta on the effects layer and I can see midi messages but when I route the midi effects layer to an instrument, no midi messages reach the instrument. It does work if I insert Wotja just before an instrument on an instrument layer. I am now wondering if the Waveform fix will also fix Unify.

[ZincT]

Hey ZinkT. Do you have Unify? I tried to use Wotja on a midi effect layer but it is not working. I inserted a midi monitor after Wojta on the effects layer and I can see midi messages but when I route the midi effects layer to an instrument, no midi messages reach the instrument. It does work if I insert Wotja just before an instrument on an instrument layer. I am now wondering if the Waveform fix will also fix Unify.

@courtjestr Yes, I noticed the same thing with Unify. I will try it in beta 11 and post the results although I suspect it is the same. I have had this with other MIDI utilities in Unify so I suspect it may be something to do with how Unify works. I'll see if the dev can shed any light on it.

UPDATE: Yes it is the same with beta 11. As a check, I have just tried a number of different MIDI utilities configured as a separate MIDI layer in Unify (Scaler 2, InstaComposer, Orb Chords, ChordPotion, Kirnu Cream) and they DO seem to send MIDI correctly into instrument layers.

[courtjestr]

Hey ZinkT. Do you have Unify? I tried to use Wotja on a midi effect layer but it is not working. I inserted a midi monitor after Wojta on the effects layer and I can see midi messages but when I route the midi effects layer to an instrument, no midi messages reach the instrument. It does work if I insert Wotja just before an instrument on an instrument layer. I am now wondering if the Waveform fix will also fix Unify.

@courtjestr Yes, I noticed the same thing with Unify. I will try it in beta 11 and post the results although I suspect it is the same. I have had this with other MIDI utilities in Unify so I suspect it may be something to do with how Unify works. I'll see if the dev can shed any light on it.

UPDATE: Yes it is the same with beta 11. As a check, I have just tried a number of different MIDI utilities configured as a separate MIDI layer in Unify (Scaler 2, InstaComposer, Orb Chords, ChordPotion, Kirnu Cream) and they DO seem to send MIDI correctly into instrument layers.

Yes, I found the same thing. Skippy may be able to shed some light. He seem like a cool dude and a very responsive developer.

[ZincT]

@courtjestr Yes, I noticed the same thing with Unify. I will try it in beta 11 and post the results although I suspect it is the same. I have had this with other MIDI utilities in Unify so I suspect it may be something to do with how Unify works. I'll see if the dev can shed any light on it.

UPDATE: Yes it is the same with beta 11. As a check, I have just tried a number of different MIDI utilities configured as a separate MIDI layer in Unify (Scaler 2, InstaComposer, Orb Chords, ChordPotion, Kirnu Cream) and they DO seem to send MIDI correctly into instrument layers.

Yes, I found the same thing. Skippy may be able to shed some light. He seem like a cool dude and a very responsive developer.

The Unify dev is actually Shane Dunne and, as it happens, I am also a beta tester for Unify. So I will drop him a line and see if he has any insight on what could be causing this. Skippy is a great guy and a sound design guru. I think he had the original idea for Unify and Shane brought it to life. The two of them continue to come up with great new ideas for it. It's also a great platform for Wotja.

[courtjestr]

@courtjestr Yes, I noticed the same thing with Unify. I will try it in beta 11 and post the results although I suspect it is the same. I have had this with other MIDI utilities in Unify so I suspect it may be something to do with how Unify works. I'll see if the dev can shed any light on it.

UPDATE: Yes it is the same with beta 11. As a check, I have just tried a number of different MIDI utilities configured as a separate MIDI layer in Unify (Scaler 2, InstaComposer, Orb Chords, ChordPotion, Kirnu Cream) and they DO seem to send MIDI correctly into instrument layers.

Yes, I found the same thing. Skippy may be able to shed some light. He seem like a cool dude and a very responsive developer.

The Unify dev is actually Shane Dunne and, as it happens, I am also a beta tester for Unify. So I will drop him a line and see if he has any insight on what could be causing this.

Oh right. I should have known that. So do you do a lot of beta testing?

[ZincT]

Oh right. I should have known that. So do you do a lot of beta testing?

Not a lot, but I like to help small developers, time permitting. It just so happens that there's a Unify beta test going on at the moment so I will wait until Shane is less busy to ask about this issue.

As a temporary workaround, I'm demoing https://www.bluecataudio.com/Products/P ... Connector/ to see if it can be used to route the MIDI within Unify.

[ZincT]

DELETE duplicate

[ValliSoftware]

Does anyone know where these Wotja 22 Pro Flow documents are stored on a Mac OSX System.

Wotja 22 Pro Flow Documents.png

[courtjestr]

I found one more Wotja gotcha. If you load two instances of Wotja in the same DAW, trying to open a mix in the first instance actually opens the mix in the second instance. If you load more than two instances, the mix always opens in the last added instance, no matter which instance you use to open a mix.

[ZincT]

@ValliSoftware
I don't have the Mac version and I'm not at my PC right now, but have you tried Help Menu - - Show Wotja Data Folder? I think flows are stored as randomisation presets so .wotjarp files.

UPDATE: I'm at my PC now and I cannot find the flow files either (I know you are on Mac). So maybe wait for Pete to answer.

[courtjestr]

I was able to get Wotja to work on a Unify midi effects layer if I added midi polysher (https://www.eareckon.com/en/products/freebies.html) right after Wotja on the Midi effect layer. Unify does not like whatever Wotja is outputting, but polysher seems to make it more palatable. I inserted a midi monitor before and after polysher and I noticed two changes. The first is that polysher set the velocity of all note off messages to 0 while the velocity Wotja's note off messages are 127. The second is that polysher's time stamps seem more "normalized" while Wotjas are all over the place. I am not sure why, but polysher's time stamps are smaller than that Wotja's for the same midi messages.

[ZincT]

I found one more Wotja gotcha. If you load two instances of Wotja in the same DAW, trying to open a mix in the first instance actually opens the mix in the second instance. If you load more than two instances, the mix always opens in the last added instance, no matter which instance you use to open a mix.

Interesting, when I add a second instance of Wotja to Cakewalk it immediately pegs out at max volume on both tracks. That's without any mix playing. Which DAW were you using? I'll let Pete know.

I was able to get Wotja to work on a Unify midi effects layer if I added midi polysher (https://www.eareckon.com/en/products/freebies.html) right after Wotja on the Midi effect layer. Unify does not like whatever Wotja is outputting, but polysher seems to make it more palatable. I inserted a midi monitor before and after polysher and I noticed two changes. The first is that polysher set the velocity of all note off messages to 0 while the velocity Wotja's note off messages are 127. The second is that polysher's time stamps seem more "normalized" while Wotjas are all over the place. I am not sure why, but polysher's time stamps are smaller than that Wotja's for the same midi messages.

Good find thanks, I'll give it a go I also noticed the velocity value of 127 for note off messages from Wotja which is different to, say, Scaler 2 or InstaComposer.

UPDATE: Yes, MIDI Polysher also works here to "clean up" the MIDI when using Wotja on a separate MIDI layer. It makes a lot more sense to use Wotja like this in Unify as you can have all manner of different instruments loaded on each layer and Wotja driving each instrument layer separately from different MIDI channels. Could be the basis of a live ambient setup for example