Moviein cue bug? more a need for clarification in docs

[rodberry]

Michela and I worked on a project recently that involved playing several movie files and resetting them to play again when called. There were some occasions when the movies did not reset to the beginning and others where they did.

Michela's notes on the cue issue:

Had issues using a cleanup script to reset a moviein OP

Exactly the same sequence of commands - cue, set cuepoint, stop cueing, play - did not do this reliably

i.e. where $movie contains moviein OP name

opparm $movie cue (1)
opparm $movie cuepoint (0)
opparm $movie cue (0)
opparm $movie play (1)

Unclear from the docs whether you need to keep setting cuepoint or whether this needs only to be set once.

Also unclear whether there is any conflict setting cue and play at different time.

My understanding, reflecting in above code, is that to reset a node you have to
1) turn cue on
2) set cuepoint to where you want to cue to
3) turn cue off
4) turn play on

I seemed to get better behaviour when I set cue permanently to 1 and the cuepoint to zero but the client still reported occasional non-restarting (meaning resumed play form wherever they stopped last time) movies.

any clarifications most welcome.

rod.

[malcolm]

The key thing to remember, which isn't obvious, is that opparming a node doesn't cause it to cook. You need to cook the node when it's cue parameter is 1, and then you can change it back to 0. You can use opcook after changing the cue parmaeter, but even better is to use the opparm -p option to 'pulse' the parameter to that value, which will cook it and then return the parameter back to it's original value.