In the discussion about buffers vs channels in the thread about
fluid.bufhpss~, I tangentially suggested a way to visualize and interact with all the permutations of
fluid.buftransients~ to get the ideal “three way” split.
My, not fully fleshed out, idea is that there would be some kind of abstraction/bpatcher that would let you load an audio file, and then behind the scenes it would work out all the
sines / etc… permutations so you would end up with a (visual) matrix of options.
You could then click on each component (
jsui?) to hear it back as well as selecting it (or maybe a separate tickbox or something to “select” it). When you have selected a specific layer, it then greys out the remaining options which do not null-sum with your chosen thing.
Obviously more details to hash out, but that would be an infinitely better way to explore/audition the choices than manually making signal paths, buffers, and playback objects to (slowly) test every thing.