waveplayer with some adjustments - questions

[tester]

It's been some months without programming (long injury, still on rehab), so it will take some time before I gather my thoughts on what I have where, and how to mess with it... I see new faces and their creative inventions (Spogg, BobF), so it's good to see, hat Flowstone is still alive and kicking.

To not invent the wheel from scratch, I have some questions, maybe there is already something, maybe someone has it or time to play with it.

What wanders around me since some time is a multi-sample player. The core thing of it would be (multiple instances of a) wav player, that has following properties.

- Stereo samples are shorter than 5 mins, so there is no issue with length limit at 5+ mins (we spent with KG some time on that topics over a year ago).

- This is a looped playback, but looping time length is independent from sample time length, thus:

-- repeating point may be shorter than loaded sample (time) length or longer than it

-- there must be some anti-click/glitch solution if looping length is set to be shorter than sample length. I guess it could be bonded with some envelope, that adds few (1-3?) ms fadeout and the same fadein on re-invoke points (or clicks could be removed via some filter on output, but this limits freq band quality).

-- looping length is driven by a blue random generator, so that each each looping period has different length (within a specified range); if there are multiple such waveplayers, each random generator must produce different values.

- Relatively CPU efficient for live playback. I guess, there will be from 40 to 120 such units in the project.

Now the question - anyone has maybe such little thing under hand? I would be greatful. I guess the most of stuff is related to the counter that drives the waveplayer (and anti-click control?).

This simple concept has many values for variety of projects, because it adds the factor of generative unpredictability.