PDA

View Full Version : cuePoint precision


sparky_hd
09-14-2006, 08:50 PM
i have a short flv (about 20 seconds) and i'm using the Component Inspector to insert cuePoints. i need to be able to seek to about 8 short segments within the flv.

First question: in the component inspector, why is the smallest increment you can change a cuePoint by only a tenth of a second when it displays the number to the thousandth?

Second question: why do i have one cuepoint at 00:00:13.900 and another at 00:00:15.100 but they start at exactly the same place?

i'm using the method my_FLVplybk.seekSeconds(time:Number) and in the documentation it says is "seeks to a given time in the file, specified in seconds, with a precision up to three decimal places (milliseconds)."

var flv_cue:Object = my_FLVPlayback.findCuePoint("cuename");
my_FLVPlayback.seekSeconds(flv_cue.time);

Rossman
09-14-2006, 09:15 PM
What frames per second is your FLA and what frames per second did you encode the FLV at?

sparky_hd
09-14-2006, 10:46 PM
the fla is 24fps and the flv is 29 or 30. i thought i read somewhere once that the flv rate is independant of the swf?

sparky_hd
09-20-2006, 09:09 PM
ok, i'm REALLY doubting the accuracy of actionscript cuepoints now. i went back to my original .mov and rerendered it with 3 seconds of a still frame between each segment, thinking that surely i could position the cuepoints in within space. But no, if i make the cuepoint at anywhere from 00:00:15.000 to 00:00:16.500, the playhead doesn't reach the action for two full seconds, and if i set the cuepoint anywhere between 00:00:17.000 and 00:00:18.500, the playhead missed the first half second!

Maybe actionscript cuepoints actually have something to do with keyframes? If so, then Macromedia - excuse me, Adobe - has some explaining to do about their documentation.

i'm going to try embedding the cuepoints with the encoder, in which i unfortunately can't hear the audio when scrubbing through the timeline.

Rossman
09-20-2006, 09:23 PM
You can only seek to keyframes, so my guess is that you need to increase the amount of keyframes in the encoding process.

sparky_hd
09-20-2006, 10:50 PM
ok, that explains it well.

i am having much more success using the navigation cuepoints, although the lack of sound in the encoder made finding my points difficult for this particular clip.