Comments on: Flash Video Issue: loadbar (size) vs playbar (time) usability http://blog.circlecube.com/2009/05/review/flash-video-issue-loadbar-size-vs-playbar-time-usability/ Evan's Interactive Actionscript Exploration Mon, 15 Mar 2010 12:53:04 +0000 hourly 1 By: eRez http://blog.circlecube.com/2009/05/review/flash-video-issue-loadbar-size-vs-playbar-time-usability/#comment-1230 eRez Wed, 11 Nov 2009 14:03:37 +0000 http://blog.circlecube.com/?p=842#comment-1230 there's a way to overcome this, but it depends on the video type you play - it works for me with mp4 files. i haven't actually tried it myself, but i think you can use this information. when you receive the video's meta-data ('onMetaData'), you get an object with various parameters of the video file. in some cases (my guess is that it depends on the video's compression type) one of the properties is called 'seekpoints', which is an array of objects for every seek-point in the video (again - it depends on the video's compression), each of them with 2 properties: time - in seconds, and offset - in bytes. using the 'totalBytes' and 'duration' properties, you can run a calculation which will enable you to compare for every seek point its relative time position and size position. this technique could have problems: for example, if there's a 10 seconds gap between 2 seek points, and 20% difference between each seek-point bytes-loaded, you won't be able to know what's going on between the 2 seek-point. anyhow - hope this will give you a head start there’s a way to overcome this, but it depends on the video type you play – it works for me with mp4 files. i haven’t actually tried it myself, but i think you can use this information.
when you receive the video’s meta-data (‘onMetaData’), you get an object with various parameters of the video file. in some cases (my guess is that it depends on the video’s compression type) one of the properties is called ’seekpoints’, which is an array of objects for every seek-point in the video (again – it depends on the video’s compression), each of them with 2 properties: time – in seconds, and offset – in bytes. using the ‘totalBytes’ and ‘duration’ properties, you can run a calculation which will enable you to compare for every seek point its relative time position and size position.
this technique could have problems: for example, if there’s a 10 seconds gap between 2 seek points, and 20% difference between each seek-point bytes-loaded, you won’t be able to know what’s going on between the 2 seek-point.
anyhow – hope this will give you a head start

]]> By: circlecube http://blog.circlecube.com/2009/05/review/flash-video-issue-loadbar-size-vs-playbar-time-usability/#comment-1153 circlecube Mon, 29 Jun 2009 15:00:03 +0000 http://blog.circlecube.com/?p=842#comment-1153 Still nothing really. Any suggestions? Still nothing really. Any suggestions?

]]> By: ezalife http://blog.circlecube.com/2009/05/review/flash-video-issue-loadbar-size-vs-playbar-time-usability/#comment-1152 ezalife Mon, 29 Jun 2009 09:34:20 +0000 http://blog.circlecube.com/?p=842#comment-1152 Hi, <br>did you ever get a response to this issue?<br>i'm having exactly the same problem but assume it can be fixed as you-tube (which is flash video) seems to get around this.<br><br>If you did get this solved i'd greatly appreciate any direction.<br><br>regards, Rich Hi,
did you ever get a response to this issue?
i'm having exactly the same problem but assume it can be fixed as you-tube (which is flash video) seems to get around this.

If you did get this solved i'd greatly appreciate any direction.

regards, Rich

]]>