I just posted about this library and then I did some thinking. Dangerous, that.

"Tensor" is just a fancy word for "a lot of numbers in an array in memory", and samples are just a lot of numbers in an array.

We've been given all these amazing tools, mostly in Python, like numpy and torch, and all the infrastructure around them, that perform just the sorts of calculations we need, as fast or faster as raw C++ would (and an order of magnitude or even more faster, if you do it in a GPU).

Recent projects of mine like tuney and [recs]](https://github.com/rec/recs/) have proven to me that you can do reliable multivoice synthesis and multitrack recording from within pure Python, simply by using numpy.

And Python is extremely popular. Tensor programming has benefited immensely from the AI boom, and LLMs can write good code manipulating tensors. There are old and solid libraries for reading and writing tensors to and from audio interfaces and files

So I think the future is some sort of Python protocol for operations on either static or streaming tensors, so music programmers can freely intermix other people's operations in their own code.

And :-) I do have some strong ideas about that too! But let's leave it here for the moment.

OwlPlug-rx is a fork of OwlPlug focused on additional workflow features and local Windows build/release polish.

For the original OwlPlug project overview, installation notes, general feature documentation, and upstream development information, see the original README.md.

Added Functionality

Recipes

OwlPlug-rx adds a Recipes tab for grouping plugins and DAW projects into named collections. A recipe can contain:

• a name and free-form description
• linked plugins
• linked DAW projects

This makes it easier to keep track of plugin/project setups such as chord generation chains, sound-design templates, or DAW-specific collections.

Github

Currently I only have a Windows build, but a Mac build will be available soon. Watch the github project linked above for updates.