Question on how to use Seek in Plus Player
Hi,
we were using DivX encoder and web player in a closed environment for some time now. To be more specific, we are building measuring devices that record, realtime divx encode and upload videos using umts internet connection.
We got a internet java applet that shows videos using the divx web player. The (automatic :-/) 2.0.0 download was a little confusing, you might imagine. Now i upgraded to 2.0.1 (hope this one gets to automatic distribution as quickly as 2.0.0).
Everything is back to non-confusing but the seek-command.
C Open 'http://abc:abc@def.com/a/examble.avi'
< Status 17 (download_start, nice)
< Time 0 (?)
< Time 0 (?)
< Status 15 (buffering_start, nice)
< Status 1 (open_done, nice, now i can invoke seek - at least on web player "minus")
C Seek DOWN 100
C Seek UP 50
< Status 16 (buffering_stop, maybe nice)
< Status 10 (playing)
< Time 0 (? - the player actually plays from position 0)
< Time 1
< Time 2
< Time 3
...
No Error Messages.
Is there a new way to use the seek command? I would like that, getting rid of the DOWN/UP method and calculating fractions instead of directly using a seek-to time.
To be complete, my code to include the player:
<object classid="clsid:67DABFBF-D0AB-41fa-9C46-CC0F21721616" width="320" height="240" codebase="http://go.divx.com/plugin/DivXBrowserPlugin.cab" id="IE_divx"><br /> <param name="mode" value="null"/><br /> <param name="allowContextMenu" value="false"/><br /> <param name="previewImage" value="http://gdb.fesa-aufmass.de/public/fesa.gif"/><br /> <param name="autoPlay" value="false"/><br /> <param name="bannerEnabled" value="false"/><br /> <param name="statusCallback" value="videoStatusChanged"/><br /> <param name="timeCallback" value="videoTimeChanged"/><br /> <embed type="video/divx" id="MZ_divx" width="320" height="240" mode="null" autoPlay="false" allowContextMenu="false" bannerEnabled="false" previewImage="http://gdb.fesa-aufmass.de/public/fesa.gif" statusCallback="videoStatusChanged" timeCallback="videoTimeChanged" pluginspage="http://go.divx.com/plugin/download/"/><br /> </object>
All the news about the unaccurate-seeking-issue are more than 1 year old and there is still no solution?
peskypescado said the problem should have been fixed with a later release in 2010, but it just stayed the old unaccurate percental method.
I´m trying to use the the web-player for an e-learning-website but without a better seeking-method for avi files it´s just unusable.
(see as well: http://labs.divx.com/node/15417)
Thanks alot for your Reply.
I am still having issues with the seek function and reduced our application to a simple javascript-only testing page.
http://www.fesa-aufmass.de/divxwebtest/test.html
What it does:
1. Load DivX Web Player 1.5 (works fine) or 2.02 (no luck)
2. Provide a button to start the video after everything is loaded.
When clicking on the button:
1. open a movie (created by divx codec)
2. wait for status code 1
3. seek some %
4. wait for timecode to reach 10 seconds
5. stop the video
With Player 1.5 it works fine (despite beeing asked to upgrade to broken version 2.02). It does play a few seconds of the video as it should.
With Player 2.02 it still doesn't work. Tried many workarounds like ignoring timestamps i dont want to see, waiting, use 'UP' seeking only, all without any luck. I have to mention the behaviour did change from 2.01 to 2.02... but i cant say if it got better or worse.
Hope this can be resolved soon - your encoder is pretty fast (we do realtime encoding on Atom N270 cpu at approx. 40% load - 320x240 at 25fps) and very reliable. DivX is still the solution of choice - but its not nice to instruct users like 'download from our 1.5 link only, dont upgrade as recommended' etc.
In addition to the seek method, may I also ask that getter methods be provided for the setup methods in the JavaScript API, such as - getVolume, getTitle etc. Or is it available but not documented?
First off, 2.0.2 just got released last week so you might want to check that out.
http://www.divx.com/en/software/divx-plus/web-player
Second, looks like the JS seeking API is having some inconsistent behavior. It works fine for me for certain fractions, but will be quite off for others. I will have our engineers look into this issue.
Also, we are aware of the quirkiness of the current method for seeking using JavaScript and a future release later this year will have the ability to do time based seeking.