I’m still not convinced about your assertions on the difference, though I must admit that I hadn’t considered the difference in size between wavetables and samples. I was not expecting (because I’m not demanding anything) a version 2 of the hardware with a bigger memory to accomodate samples. All I was speculating about was, given the hardware constraints, what’s possible, and really what’s the conceptual difference between user-loaded wavetable and user-loaded samples
The UI/UX would have to change for both.
To get a user wavetable into the existing SY CHORD might, for all we know, mean a radical re-write of the algorithm. Might even turn out to me more work than a simple sample player.
I’m also thinking it’s unlikely (and I’m not going to cry about it) but more from the point of view that if they DID implement a sample player machine (of the level of M:S or even less), there then would be a cascade of requests for recording, slicing, stereo, pitch shift without tempo change, “how can you release something this limited in 2023” etc, etc, ad nauseam.