Parameter recorder for multislider - non real time rendering


    Oct 26 2020 | 10:59 pm
    Hello,
    the parameter recorder from "Best practices in Jitter part 2 Recording" https://cycling74.com/tutorials/best-practices-in-jitter-part-2-recording-1 seems to truncate parameters that are lists to a single value e.g. if you use [multislider] it will record only the first slider value. As far as I understand the recorder patch this is due to the use of [t b f] and [setcell1d] in the set-row sub patcher. What would be the recommended way to adapt the patch for use with [multislider] meaning arbitrary list lengths?
    set-row sub patcher
    set-row sub patcher
    PARAMETER-RECORDER: environment of jit.matrixset that stores the parameters
    PARAMETER-RECORDER: environment of jit.matrixset that stores the parameters
    PARAMETER-PLAYBACK: environment of jit.matrixset for playback.
    PARAMETER-PLAYBACK: environment of jit.matrixset for playback.

    • Oct 27 2020 | 9:40 am
      -----
    • Oct 27 2020 | 6:32 pm
      The problem with the patch is that it is designed to store float values in a jit.matrixset by setcell1d messages. And also the playback is based on reading from jit.matrixset cells. This means in my opinion lists must be serialized somehow e.g. by [iter]. And the serialised list values have to be fed to different indices in the jit.matrixset. I have coarse idea how to accomplish that, but perhaps the creators of the patch can comment on the topic? Maybe there are better ways? Or one can point to some pitfalls ;-) like the zl.rev in the playback sub patcher?
      Edit: [mtr] seems to be the best alternative to the PARAMETER RECORDER patch. It can record up to 128 tracks and a track can store a list.