Help testing my first module: Memory Pad

Development
6

Hmmm, I just tried it again and at first it did not remember the path, but then on the 2nd try it did… now I can’t get it to fail. So not really sure why it didn’t work at first, if I had realised I should have checked the autosave patch.json

I can see this in there now so looks like your module is working fine

      "data": {
        "RECORDED_X_PATH_KEY": [
          0.48074448108673096,
          0.48074448108673096,
          0.48074448108673096,
          0.48074448108673096,
          ...

edit: I notice in my autosave patch.json that PPW saves 2048 rows of values in there, like so:

        "fram_data": [
          -1590029344,
          0,
          200,
          251658496,
          251723875,
          65635,
          0,
          704668431,
          25359,
          838886159,
          25359,
          1677746959,
          25359,
          -285187313,
          25359,
          -285187313,
          1677746959,
          25359,
          25359,
          16802575,
          25359,
          6491904,
etc...

A while back I asked about the amount of data that is acceptable to store in the json file:

I believe this is due to the latency of writing more than 100kb to a file between frames, but that might not be accurate, anyway, I thought this was interesting…

Your module didn’t save anywhere near 100kb of data for the path, but is there a max length to the recording?

2nd edit: that makes me wonder, would it be possible to create some preset paths that the module could load? That might be fun, if you could load a preset of a circle, or other predefined paths that would be difficult to accurately draw in by hand (or mouse in my case :wink: )

3rd edit: just had another idea: might be cool if in the right click menu there were options to do some transformations on the path, like flip it vertically, or mirror the left side to the right side, maybe even a quantise options or something like that?

1 Like