@arseniy Maybe this will give you some ideas (I see that I left the knob part out, but you can probably figure that out)
tableToSliders.pd

I guess the key idea here is to set each slider's receive symbol to something that you can iterate on since you can already iterate on array values.

@arseniy How are you storing the dozen numerical values?

In Pd, if you implement a fade using [line~] into [*~], you get one that is linear in amplitude, which sounds like it starts out slowly and speeds up very quickly. If you put [dbtorms~] inbetween and adjust [line~]'s args, it sounds more like a constant fade and you could say it was "linear in dB" or a constant dB/sec fade. There's nothing exactly like that in either REAPER or Soundforge--their audio-tapered curves still speed up as they get softer. Automating the track fader in REAPER shows something similar. In the following snapshot, the automation line on the bottom track is controlling the track fader, and the vertical red marker lines mark the points where the signal drops another 6dB from the previous marker. See how the markers get closer and closer as the fade progresses? That means the fade is speeding up in terms of dB/s, despite being controlled by a straight line between two points.

Assuming that REAPER and SoundForge cater to the way the vast majority of people hear/use fades, the constant dB/sec fade must not be considered useful in most cases. If I'm right, why would that be?

@arseniy This happens to me when using Chrome--Edge works fine.

@Yar That sounds similar to the Pd help example I04.noisegate

@porres Here's a comparison with cyclone/urn. Both are generating 4 element permutations, but urn sometimes generates a permutation that starts with the same number that the previous permutation ended with. Setting shuffle's 3rd arg to 0.25 guarantees that won't happen with 4+ element permutations.
motex shuffle explanation.pd

I've always liked motex/shuffle because it allows you to specify how soon a repetition can occur when you generate a new permutation. See the third argument:

@mrsean I wasn't really suggesting you use it. I was thinking of posting my own solution to your problem (which uses both expr and expr~) but when I looked more closely I realized that it's almost the same as yours except all in audio domain.

@mrsean Is [expr] and [expr~] available in the heavy compiler?

@raynovich Did you try increasing the delay in your audio interface settings? On one of my patches that fixes the drop out after I create and destroy the gem window once.