I shared an early version of this in The Party Van thread, but it's now ready for primetime (beta testing).
I give you C-C-Combine:
(this zip contains the main device, with 4 built-in corpora, and a 'Create Corpus' device, for making your own corpora)
Extra corpora to test with:
Here's a little demo video of what it looks/sounds like (this is before the main MATCH visualizer was added):
What it is is a concat synthesis Max for Live device that is a MASSIVE improvement to the Max patch with the same name that I initially shared about 5 years ago (crazy!). The core concepts are the same, so if you're interested you can have a look at the original post about it, but the current implementation is better in every conceivable way.
It has gone through a bit of testing (special thanks to @Leverkusen and @jasonw22) and iteration, and is now at a point where it's ready for a broader testing.
When it's done it will be shared openly/freely, come with a manual, tutorial videos, blog post, etc... so for now I'll just include some text instructions.
So some initial bits:
*It’s 32bit only at the moment (though it should play fine on Mac/Win). This means you will have to use it in 32bit Live and 32bit Max for Live. This will change by the time the full release is out.
*Some of the bigger corpora take a long time to load (pinwheel and all). This is normal, and just due to the file sizes involved.
*Automation and mapping should all work fine.
*The Live set should store/recall everything just fine, including externally loaded corpora.
*Everything has descriptive annotations, so you can hover over things to find out what things do (quick start guide below).
*There are lots of checks and limits built on CPU usage, but you can still drive it to really high CPU usage (at really fast/smooth settings, with lots of corpora loaded), so be aware of this.
Things to check out:
*General usability. Does it make sense? Is it confusing? etc...
*General mapping/naming. Do things work, automate, and map/behave as expected?
*Does anything crash or otherwise act funny?
*Does the corpus creation device make sense?
In general I welcome any/all comments/suggestions, from UI/interface/color, to bugs/crashes, to general workflow improvements etc…
Here is a simple ‘getting started’ guide.
*There are 4 built-in corpora that you can load via the CORPUS loading section. You can load more via the
load custom entry in the corpus select menu (either ones from the additional corpus zip or ones you've created.
*Once a corpus is loaded, the device is ‘running’. If you play audio through it, you’ll hear it resynthesized by the loaded corpus, by default.
*You can also select between the current, or all loaded, corpora using the current/all toggle. With this you can get some really interesting results by choosing what corpora you choose to load/combine.
*Most of the change in sounding results will come from the PLAY section. Play around with the
chunky toggle, and smear.
glitch have more extreme impacts on the sounds, as do the various envelopes you can apply to the grains.
More advanced bits:
*Once you are playing audio through it (at least 5 seconds worth), select the
learn input entry in the normalization section. This will match the input audio to the corpus so that you can access more of the corpus based on your input (like if you only have high pitched sounds, you can still trigger low pitched sounds in the corpus). You can then press the NORM button to enable the normalization.
*The MATCH section tunes the matching engine. You can tweak the
select knob to get more or less matching overall.
*The individual descriptor knobs in the MATCH section lets you dial in really specific querries since the underlying code will reorder based on how the knobs are set. For example, turning a descriptor knob all the way down stops searching for it, so play with these knobs to get some quirky settings (centroid and pitch turned all the way down, with loudness/noise turned up 3/4 of the way).
So yeah, have a play and let me know how you get on.