1.8.1

Fixes issues with string splitting which causes fftsettiings to be heinously precise.

1.7.0

Updates the noveltyslice algorithm to use the newly named -algorithm instead of -feature. This has no effect on how the slicer works, but ensures that it will actually be configurable with newer versions of the CLI.

1.6.2

Various fixes

1.6.0

This is a non-alpha version of ReaCoMa.

I improved version checking, which now is less necessary given the stability of the toolbox.

I also now check for the new architectures added to ReaCoMa, which include macOS-arm64, when you call get the operating system code from the ReaScript API.

1.5.4a

Made it so that it doesn't freak out on WAV/AIFF/AIF

1.5.3.a

Fixed a bug in an or statement that was incorrectly structured. Testing of operating system strings works properly now!

Thanks for catching this one Natasha!

https://discourse.flucoma.org/t/reaper-script-path-error-v2/666/2

1.5.2a

Thanks to Jacob Hart for finding a bug where paths where not correctly resolved for 32 bit clients when looking for the executables. This is now fixed.

1.5.1a

Add config.lua option to bypass version checking on the command line tools. This is useful for development but also for those who are adventurous and building their own copies of the CLI stuff.

Thanks for making a quasi request Kylee.

1.5.0a

1.5.0a

This release brings several features and bug fixes.

Bug Fixes:

'iterations' is now correctly passed to the command line calls. Previously it was only using the default

Features:

config.lua now holds special variables used for configuring ReaCoMa behaviour. You can set the location of outputs generated by ReaCoMa with three options.

1. "source" this is the default behaviour. The location of new files is in the same folder as the source.
2. "media" The location of new files will be in the REAPER Media folder
3. "/custom/path" This will put files in a custom location.

---

Warnings about file types

You will be warned if you try to process anything except wav or aiff files.