softcut is literally not designed for this sort of thing (as warned about by others here, lol) and has a bunch of other features iām not using at all. maybe explaining my current chain would help make sense of the use case iām working towards:
sound source (presently op-1/op-z/ipad) feeds into norns, which feeds into my newest big dumb splurge, elektron analog heat. this is set up as a soundcard for ableton (which still seems to allow you to use overbridge as a send effect even as it acts as a soundcard despite that not being an option in the elektron settings.)
so the use case for me is really just taking the pressure off to catch every āhappy accidentā one might find, or as noted in that other thread if youāre listening to something and think āi should sample thatā, if you were running through the script, you already did.
like if you were to notice that your local least-bad iheartradio station had changed its tagline to a platitude which, the first time you heard it, sounded awkward but positive, but as it kept repeating, over and over, without any further clarification or explanation, began to take on an weirdly dystopian tone, you could go back and grab a bunch of instances of that thing:
for this case, even when i had the buffer set to run an hour i found i was rarely if ever wanting (or indeed even remembering) to scrub more than 5-10 minutes back to grab something for ableton. and honestly the saturation options on the heat mean i can run softcut at super low sample rates and still get pleasant or at least interesting results. but i am still working with a pretty limited set of sound sources which i know are going into a DAW. so iāve kind of stumbled upon the rare use case where (to me at least) it actually makes sense to use softcut in this way.
looking at the API, possibly a more traditional version of this concept could be done with the existing tape commands (start tape on script launch, flag things to revisit in lua layer, then maybe interact with the interesting chunks via softcut?) if the tape functionally could be expanded to include commands for playing faster/slower/backwards, it would be an no brainer. but iām in absolutely no position to comment on how that would work.
