I have recently encountered a problem with the netStream.seek()
method. I have built a video application for my doctoral
dissertation that extensively uses the seek function with a "scrubber
bar" and buttons that allow the user to move through a video in 10
second and 1 minute increments.
When I pilot tested the application this summer, I used a 20
minute flv video that was loaded into the application and everything
worked just great. Now I am having problems with the seek() method.
When I use the scrubber bar, or any button to move forward through
the video, the video 'snaps back' to a location that is nowhere near
where I need it to go. For example, if I move the playhead position
to 23 minutes and 14 seconds, the video might snap back to 9 minutes
and 34 seconds and never allow me to jump to that spot in the video.
I have to let the video play to that spot.
I think that the root of all of my problems is that I have built
the application around progressive downloading of the video rather
than streaming. Now that I am using larger videos of 45 and 55
minutes, this may be the root of all of my problems. Is this my
problem or is there another aspect that I need to troubleshoot?
Thanks for any help that you can provide,
Kevin Shorner-Johnson
-------------------------------------------------------------
To unsubscribe from this list, simply email the list with unsubscribe in the
subject line
For more info, see http://www.affug.com
Archive @ http://www.mail-archive.com/discussion%40affug.com/
List hosted by http://www.fusionlink.com
-------------------------------------------------------------
