minor gripe about jit.movie rate

    Jul 12 2016 | 10:23 pm
    The reference for the 'stop' message to jit.movie reads:
    "Stops movie playback. rate is unaffected)."
    This is quite reasonable, and it would also be reasonable the other way round - that is, sending a 'rate' message shouldn't start or stop movie playback.
    Unfortunately, when jit.movie receives a 'rate' message (different from its current rate), the movie starts playing. And since I have a float controlled by a pattrstorage setting the movie rate , every time I go to a new preset with a different rate, the movie starts playing automatically. The @autostart 0 attribute thus becomes ineffective.
    Since I can't see any advantage to having a rate message start movie playback, I would consider this a bug. Not a big bug, but still irritating, maybe comparable to a flea.

    • Jul 14 2016 | 5:29 pm
      unfortunately this is the way it's always been and will always be. i would recommend decoupling your rate pattr object from the rate attribute, and bang out the stored value whenever the object is triggered to start (or simply use the rate value to start playback).