ScriptPlayer icon indicating copy to clipboard operation
ScriptPlayer copied to clipboard

Playlist will start new script at wrong position.

Open RedZadow opened this issue 10 months ago • 3 comments

When advancing to a new video in the playlist the script will often start at the wrong position in the file, or not play the script at all. I believe what's happening is that Script Player (or The Handy) will play the new script from the position of the previous video. So say the video was 1m23s long the script in the new video will start playing at 1m23s.

When the script doesn't appear to be playing at all I believe this is because the previous video was longer than the current video. So let's say the first video was 5m48s long the script in the new video will start playing at 5m48s, but let's say the script was only 3m11s long, so nothing is played.

Annoyingly this doesn't seem to happen every time even with the same video files, but in Script Player v1.2.2 with Handy fw4 it seems like it happens more often.

Clicking on the seek bar will resolve the issue for the current video.

RedZadow avatar Mar 05 '25 22:03 RedZadow

Hmmm. That might be what is happening.

2120githubuser avatar Mar 07 '25 14:03 2120githubuser

Was just thinking about this, and something else I've noticed is that the handy will stop playing after skipping a gap. As in the original scenario I'm guessing the handy never receives the new timecode position for whatever reason. It's not so much that the handy stopped, but that it's playing the script through the gap where there's nothing to do. Again, clicking on the seek bar.

The other day before I posted the issue I thought maybe it was related to having gaps turned no, so I turned them off and it still happened. So the issue is more broad, but also perhaps happens with gap skipping. Something else I'll mention is that I have soft seek turned OFF. I've had other issues with that, so its been disabled for months.

Something else to make note of, skipping forward or back with left and right keys DOES NOT resolve the issue.

RedZadow avatar Mar 09 '25 05:03 RedZadow

Yep, been seeing that aswell - I hope this "solves itself" by the time FW4 is close to RC, I don't really want to fiddle too hard with SPs insides while it's still in beta.

FredTungsten avatar Mar 09 '25 10:03 FredTungsten