hi @wiggin2250 ! thanks for taking the time to spell out what you’re after.
yes, it does get quite a bit more complex if dealing with multiple sample fx chains (especially since you can route a samplefx chain to another chain.. and to another chain… and so on) - actually, what i was thinking of, was to do it in the simplest possible way, i.e. have a user-defined chain that is on the track itself, and using the track to trigger all the slices or individual samples, and play them through the TrackDSP fx, recording them, and cutting the silences out.
but of course, an ideal solution would be to be able to first spread an instrument into multiple slices, then slam them all into separate sample fx chains, then process them, and kick out a PTI that has the processing audio on them, per each slice. that can definitely be done, but it will be somewhat more complex. i’ll attempt to do both, since both are worth doing, but first i gotta build the Preset++system fully so that it allows for this. it’s a longer process, but i think it’ll be very useful - since it’ll allow for the user to turn a Track DSP Chain into a preset they can use to render samples through, and then use a different bunch of slots per each FXRender. then after that it’s pretty easy to do a method of taking a break, and letting the user set a user-defined preset for each of the slices and out comes the PTI.
so i’ll have a think about it this week, about the easiest “next step” to advance this, as all of this is definitely on my todo-list. i’ve got a 5 hour bus-ride to take on saturday and another on sunday (going to an ambient festival to play a live sampling ambient drone gig with unplugged cables) - so there’ll be time to think about how to advance this.
so, consider it all on my todo-list, just need to work the “preset preparation + storing + rendering with” workflow out first, then i can start applying it to PTI export.