cuepoint appears to be triggering twice Created Apr 1, 2009

It turns out that when removing everything else on the page so that it is just bare HTML, the cuepoint works correctly without having to click multiple times.

When additional content is loaded on the page, that is what causes the problem. There is no other javascript items or dynamic code running on the page...just lots of tables and graphics.

Any possible solutions or something else I should try?

Has nobody ever run into this same problem before?

Same here.

I'm trying to toggle content plugin in for example 4000, 8000 cuepoints. Cuepoints are fired even on 2000, or sometimes else. Not consistent.

Any progress on this? It is happening for me too. Are there any known workarounds?

OK, this sad bit of work-around code seems to do the trick....

var cueCount = 0;
							        onCuepoint: [[2500], function() { 
							            cueCount = cueCount + 1;
							            if (cueCount== 1) {
	  										$f().pause(); 							            
	  									}
  										
						               
						            }], 

 

Well, for me it works:



HTML setup for the player

<!-- include latest Flowplayer javascript file -->
<script language="javascript" src="path/to/flowplayer-3.2.6.js"></script>

<!-- player container with optional splash image -->
<a href="path/to/video_file" id="playerContainer">
	<img src="path/to/splash_image" />
</a>

JavaScript coding

Following script will install Flowplayer into our player container

<script language="javascript">
// our custom configuration is given in third argument
flowplayer("playerContainer", "path/tohttp://releases.flowplayer.org/swf/flowplayer-3.2.7.swf",{
clip: {
  onCuepoint: [[2500], function () {
    this.pause();
  }]
}
});
</script>

Crystal ball mode: do you have set onCuepoint as a player property? This might cause the problem. It is a clip property.

We're having the exact same problem.

After debugging all morning, I noticed this "re-triggering" is persistent but doesn't happen on every cuepoint... so the only way to really experience the problem is to setup an example with at least 4 cuepoints.

I posted a forum topic about this issue along with a couple demonstrations of the problem.

I'm anxious to resolve this bug, for sure.

What I notice is that sometimes the cuepoints trigger at slightly different times than they were set - perhaps due to variations of buffering time. When the files are smaller, and there is less buffering, this happens less often.

I think that this is the underlying issue. It get triggered once at the wrong time; and once at the right time.

I'm not quite sure whether this helps: The time values of cuepoints are rounded - to 100 Miliseconds. Maybe there is an underlying javascriptprob with int/float conversion.

I can reproduce it now, also with the example above. It does indeed not happen every time.

I also tried to completely unset the cuepoints onBeforeResume and to reset them onResume to no avail.

I do not think it is a rounding problem as this happens with full second cuepoints too. I can only speculate that the interaction between metadata retrieval and player actions is not precise enough. But it certainly is not the advertised behaviour, i.e. it is a bug ;-)

An undesirable workaround is to add a full second to the scrubber during the pause so you can "hurdle" any time issues between the metadata and player:

onPause:

current_time = $f().getTime();
new_time = Math.ceil(current_time) + 1;
$f().seek(new_time);

I found that adding less than a second (0.5) doesn't work.

Unfortunately, the flow of the movie or mp3 becomes choppy ("Bonasera, what have I done to... [pause][resume]... so disrespectfully?")

I found a way that worked where the desired effect of the cuepoint is to pause the video that doesn't involve skipping any of the content.

I setup an onPause function on the clip that sets a global variable to the current timestamp of the video. The onCuepoint function then checks to see if that global variable is either undefined (hasn't been set yet) or if the cuepoint doesn't match the paused timestamp.

onPause: function(){
	pauseTimeStamp = this.getTime();
}

onCuepoint: [
	[**whatever your cuepoints are**],
	function(clip, cuepoint) {
		if(typeof pauseTimeStamp == 'undefined' || cuepoint != (pauseTimeStamp * 1000)){
			this.pause();
		}
	}
]

I multiplied the pauseTimeStamp by 1,000 because the getTime() function outputs seconds, and the cuepoint is set as milliseconds.

This method should work on any other player & clip actions that relate to the action you're trying to execute in the onCuepoint action. We're trying to pause the clip and onPause is available, so this might be the only case where this method works.

This is incredibly helpful. Thanks!