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

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

Well I was able to do that without a rack.

please show me how. this is the only way that I have been able to make it work.

[impete]

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

I've actually met Jules a few times over the years - a lovely chap - and *very* clever.

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

Aha - interesting!

Best wishes, 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.

it is if you want to route by MIDI channel.

Well I was able to do that without a rack.

please show me how. this is the only way that I have been able to make it work.

I think that we are really taking about 2 different things here. Your method is correct if you wish to "route" the MIDI channels with Tracktion.

What I am suggesting is that channel routing by Tracktion is not necessary, unless you wanted to be able to "re-route" the MIDI channel.

But apparently the source MIDI channel # remains intact from the source instrument to the destination track. So if you send from track 1 via MIDI channel 2, any track can receive from track 1 as MIDI channel 2. This is assuming the instrument on track 1 is set up to send on multi MIDI channels.

[zzz00m]

I've actually met Jules a few times over the years - a lovely chap - and *very* clever.

Speaking of clever, Tracktion Waveform is cross platform for Win/Mac/Linux. It even runs on the Raspberry Pi using Linux on ARM-compatible hardware.

[impete]

Speaking of clever, Tracktion Waveform is cross platform for Win/Mac/Linux. It even runs on the Raspberry Pi using Linux on ARM-compatible hardware.

Wotja currently uses JUCE, so could potentially run on Linux quite easily. However, there doesn't seem to be any meaningful market for Linux apps at the moment.

Best wishes, Pete

[impete]

Speaking of clever, Tracktion Waveform is cross platform for Win/Mac/Linux. It even runs on the Raspberry Pi using Linux on ARM-compatible hardware.

Wotja currently uses JUCE, so could potentially run on Linux quite easily. However, there doesn't seem to be any meaningful market for Linux apps at the moment.

Best wishes, Pete

As an interesting bit of history, the precursor to Wotja (miniMIXA) also ran on Windows Mobile and Symbian! I used to use my own JUCE-equivalent cross-platform user interface framework (that I wrote and maintained myself) for macOS, Windows, iOS and Android; but have replaced that layer in the past few years with JUCE, leaving me better able to focus on the core technologies in Wotja (which is available for all of iOS, macOS, Windows and Android).

Best wishes, Pete

[JamminFool]

What I am suggesting is that channel routing by Tracktion is not necessary, unless you wanted to be able to "re-route" the MIDI channel.

yes, but unless you use a rack in Waveform, you can only send the MIDI from a track to one other track. thus the receiving track has to use an instrument that can play different sounds on different channels. which is fine, but limiting.

the rack solution allows you to send the midi by channel to different instruments on different tracks.

which is the real power of the Wotja VSTi.

[impete]

The Wotja 22.0.7 build has now been shared with Beta Testers!

Wotja 22.0.7

FIXED: Plug-in: was unable to run at 48000 (but was OK at 44100) in certain plug-in hosts

FIXED: Windows Plug-in: Transport bar control from Ableton Live, Tracktion Waveform Pro and Mixcraft

FIXED: Windows App and VST3: alerts can appear behind the app/plug-in Window

IMPROVED: Plug-in: Settings screen: replace "Output Device" (which showed an empty pop-up) with
a simple label, displaying text like this (localized):
"AUv3 Plug-in: 48000 Hz"
"VST3 Plug-in: 48000 Hz"

IMPROVED: Windows App: if the VST3 version available to install is more recent that the
installed VST3 version, then on *app* start-up install the update to Windows VST3 automatically
- note that nothing happens for this at start-up, if user has not yet installed the plug-in

IMPROVED: Windows App: Added Help Menu item to "Install Wotja VST3"

[impete]

NB if "Install Wotja VST3" fails, this is probably because you forgot to run Wotja in Administrator mode. The app will tell you this. Just restart in Administrator mode, and you're good to go!

Pete

[JamminFool]

- note that nothing happens for this at start-up, if user has not yet installed the plug-in

wouldn't this make sense, since it would catch the first time install, ie. if the there is a older version, or there is no version, already installed, then move the new one to the VST3 folder.

or am i not understanding what this means?

[impete]

wouldn't this make sense, since it would catch the first time install, ie. if the there is a older version, or there is no version, already installed, then move the new one to the VST3 folder.

or am i not understanding what this means?

Thanks for asking!

This will work "as expected" for users of the old version - it'll prompt if you want to install the updated VST3. Depending on your account, you might need to do this having restarted Wotja in Administrator mode. Or, of course you can simply copy the file across manually using Explorer.

What we're not doing at this present time is to automatically "install" the plug-in for new users; as in general we don't like the idea of apps installing stuff within a system without the user being in full control.

Hoping that explains things, Pete

[impete]

Good news - Mixcraft transport is now sync'ing with the Wotja plugin (in the Wotja 22.0.7 build, not yet released...)

Pete

[JamminFool]

@impete,

cool. i appreciate the idea of not installing stuff within a system without the user being in control. but it also seems like it would take care of the case of the newbie just expecting it to work after the first time install. they are, afterall, the most likely to be confused.

either way is fine with me, since i now know how it works.

[impete]

@impete,

cool. i appreciate the idea of not installing stuff within a system without the user being in control. but it also seems like it would take care of the case of the newbie just expecting it to work after the first time install. they are, afterall, the most likely to be confused.

either way is fine with me, since i now know how it works.

I've just figured-out a sensible way to do this - can't believe I didn't think about it! It'll be in the version that comes after 21.0.7, however...!

Best wishes, Pete

[zzz00m]

What I am suggesting is that channel routing by Tracktion is not necessary, unless you wanted to be able to "re-route" the MIDI channel.

yes, but unless you use a rack in Waveform, you can only send the MIDI from a track to one other track. thus the receiving track has to use an instrument that can play different sounds on different channels. which is fine, but limiting.

the rack solution allows you to send the midi by channel to different instruments on different tracks.

Ah, yes. I was also assuming that we could use the virtual MIDI inputs for each additional track, but virtual inputs only recognize external hardware, not internal tracks. So if you need more than one secondary track, then racks would be the correct solution.