Wotja 24 - arriving on January 1st 2024

[imtim]

Hi folks

Sorry for the being slow to answer, but we are right in the middle of working on the next update!

Cells are self-contained "pieces" so to speak, and so there is no concept of notes sustaining across to the next Cell. When play moves to the next Cell then all composing in the previous Cell stops.

If Cells have different volume levels then it is probably easiest to deal with that by using an Amplifier in the Cell FX slot (see: https://wotja.com/guide/#mix-music-fx-cell).

We do *hope* that at some point in the future we might be able to add some kind of user configurable Cell fade in/fade out (and if we are very very lucky, maybe even a way to cross-mix Cells), but for a number of reasons it is very non-trivial so not something likely to happen any time soon.

Tip: A way to get some notes going across Cells is to have a Cell in one Track that keeps playing whilst Cells in other Tracks sequence. I know it is not the same as was asked, but I hope it might help!

Best wishes

Tim

[PhilF]

I've got a proper noob question about Wotja 24 - I've only just started using it, really interesting so far.

My question is about Flows - so, I can edit some of the parameters of each Flow and this is pretty straightforward. I'm hoping I've got this right but each Flow tends to spit out MIDI on two MIDI channels (I think Environments may give you more?). Is there an easy way to go to, for example, Piano or Drone and ask it to send MIDI to more than two MIDI channels - and not just duplicate MIDI but a different part of the composition?

Thank you

[impete]

I've got a proper noob question about Wotja 24 - I've only just started using it, really interesting so far.

My question is about Flows - so, I can edit some of the parameters of each Flow and this is pretty straightforward. I'm hoping I've got this right but each Flow tends to spit out MIDI on two MIDI channels (I think Environments may give you more?). Is there an easy way to go to, for example, Piano or Drone and ask it to send MIDI to more than two MIDI channels - and not just duplicate MIDI but a different part of the composition?

Thank you

Hi! Sorry for the delay in responding, we've been focused on getting the new Wotja update ready.

The templates used by the Flow (strictly, we're now calling these Schemas from the 24.1.1 update!) are dictated by the underlying templates, in terms of how they're configured to map their Generators to different MIDI Channels.

So, you could relatively easily create/modify your own Templates, with MIDI channel mapping that suited your needs; and create your own Schema (Flow) to use only those Templates for which you'd configured the MIDI in the way you wanted.

Hoping that helps!

Best wishes, Pete

[impete]

Hi folks,

Wotja 24.1.1 is released. It is a major update!

Amongst other things, it has an API that allows 3rd party apps (including games) to play Generative Audio in the background via the Wotja app.

Info here: https://wotja.com/releases/#w24-1-1

Best wishes,

Pete

[imtim]

Hi Folks,

Wotja 24.2.0 is released. It is a major update!

Full Info here: https://wotja.com/releases/#w24-2-0

Best wishes,

Tim

[imtim]

Hi Folks,

Wotja 24.3.0 is released.

Full Info here: https://wotja.com/releases/#w24-3-0

Best wishes,

Tim

[imtim]

Hi Folks,

Wotja 24.3.2 is released.

Full Info here: https://wotja.com/releases/#w24-3-2

Best wishes,

Tim

[iNNeRNoiZe]

Hi,

Wotja (Pro) crashes while "scan plugins" on my M2 Max Sonoma ARM MBP. Tried to uninstall and reinstall Wotja multiple times.

Where do we go from here?

Edit: another problem, after reopening the AUv3 Plugin in Live 12, plugin window is empty.

[impete]

Hi, and thanks for getting in touch.

Hi,

Wotja (Pro) crashes while "scan plugins" on my M2 Max Sonoma ARM MBP. Tried to uninstall and reinstall Wotja multiple times.

Where do we go from here?

We have automated crash reporting enabled; so provided you've configured your Mac to send crash reports, we should see such crash reports.

That said, I've seen no crash reports along this line for macOS. Can you please double-check your crash reporting settings, and then try again? Thanks in advance.

Edit: another problem, after reopening the AUv3 Plugin in Live 12, plugin window is empty.

I presume that issue is when you were using Live 12 on macOS. We do our AUv3 testing under macOS using Logic Pro - and have had no issues reported with it. Our primary Mac development / test machines are M1 Mac Book Pro devices.

Live 12 should certainly support AUv3.

I've just checked here: https://help.ableton.com/hc/en-us/artic ... s-on-macOS
... Ableton don't provide much information on where to look.

I'd strongly suggest you contact Ableton directly about this issue. There are no dependencies from Wotja AUv3 on any 3rd party libraries.

Can you please let us know which version of macOS you're using?

Best wishes, Pete

[iNNeRNoiZe]

Send Wotja/Sonoma crash report per PM.

[impete]

Send Wotja/Sonoma crash report per PM.

Thank you very much for that!

It was definitely a crash when scanning plug-ins, as you reported.

It is hard to tell which audio unit caused the crash, but the only one that jumps-out to me is one by iZotope? Seems to be called something like RX Monitor?

/Library/Audio/Plug-Ins/Components/iZRX10MonitorAUHook.component

This isn't a plug-in I know anything about, but have found an interesting reference here which might give some pointers. It is a rather long thread describing issues with completing plug-in scanning with iZotope plug-ins.

https://www.logicprohelp.com/forums/top ... alidation/

If you have a way to safely and temporarily remove the plug-in, it would be interesting to know if that allows your plug-in scanning to complete.

Hoping this is of some help,

Best wishes, Pete

[iNNeRNoiZe]

I have installed 1000+ Plugins. After uninstall iZotope RX, plugin scanner crashes at the next plugin.
Feature request: Please put plugins that have crashed in the past automatically on a blacklist so that they are not rescanned at the next start. Otherwise the total-crash will be repeated with every new start of Wotja.

[impete]

I have installed 1000+ Plugins. After uninstall iZotope RX, plugin scanner crashes at the next plugin.
Feature request: Please put plugins that have crashed in the past automatically on a blacklist so that they are not rescanned at the next start. Otherwise the total-crash will be repeated with every new start of Wotja.

Hi!

Thank you for the suggestion, we'll certainly consider it for the next update.

With best wishes, Pete

[impete]

Hi again!

I've finally figured out a fix for the Izotope plug-in, and Wotja will no longer crash when it is found (after that initial scan where Izotope crashes Wotja...).

The fix is in Wotja 24.3.4, which should appear in just a few days.

Many thanks for reporting the issue!

Best wishes, Pete

[impete]

I have installed 1000+ Plugins. After uninstall iZotope RX, plugin scanner crashes at the next plugin.
Feature request: Please put plugins that have crashed in the past automatically on a blacklist so that they are not rescanned at the next start. Otherwise the total-crash will be repeated with every new start of Wotja.

Hi!

Thank you for the suggestion, we'll certainly consider it for the next update.

With best wishes, Pete

This is now implemented in Wotja 24.3.5 for macOS - coming very soon.

NEW: macOS: a new plug-in scanner that is much more resilient, and should cope with plug-ins that otherwise used to crash when scanned.

NEW: Plug-in scanner action menu: "Export Blocked Plug-ins list" Menu item to export "blocked files" list to clipboard

NB: a plug-in that fails to scan after this update, might sometimes result in an alert window that you have to Cmd-Tab to, which says "One of the files this plug-in needs cannot be found, please reinstall or contact technical support for assistance." This alert is generated by macOS, not us. It is not unique to the Wotja plug-in scanner; we've seen all sorts of reports of this with other hosting apps. If this happens for you, please get in touch to tell us the name of the offending plug-in (this will be displayed in the title bar of the scanning window), and email us your exported "blocked files" list once the scan completes. Thanks!

Best wishes, Pete