Closed Bug 785999 Opened 12 years ago Closed 11 years ago

Ogg fileReader createObjectUrl (no server involved) no duration seeking in player

Categories

(Core :: Audio/Video, defect)

14 Branch
x86_64
Windows Server 2003
defect
Not set
normal

Tracking

()

RESOLVED FIXED

People

(Reporter: bugzilla, Unassigned)

References

Details

User Agent: Mozilla/5.0 (Windows NT 5.2; WOW64; rv:14.0) Gecko/20100101 Firefox/14.0.1
Build ID: 20120713134347

Steps to reproduce:

I have a problem with Ogg files and Duration/Seeking in player without Server communication. 
Because the Audio file is binding via filereader and createObjectUrl so no server is involved in this situation. 
Chrome handle this situation automatic and i have the timeline in player and it is possible seeking from the beginning to the end of the file,  in Firefox not.

I tested some dirty workarounds but not happy with this.


Actual results:

http://jsfiddle.net/fGR7t/

Use audio files with dif. Length (some more than 2h) take a look and test it with Chrome, too. 
Chrome have nice solution (i know the Ogg spec says "server should do send byte range" but with no server involving... you know what i mean "filereader, createObjectUrl")


Expected results:

Other words: All stuff only handle on client side. How become Duration/Seeking in Firefox (Player)?
Component: Untriaged → Video/Audio
Product: Firefox → Core
Depends on: 730765
Is this still broken? I tried the jsfiddle.net example and it seems to work.
It should be fiexed since FF18 (<a href="https://bugzilla.mozilla.org/show_bug.cgi?id=730765" title="Media cache shouldn't be used when loading from blob: urls">Bug 730765</a>).

And yeah it looks like it works. 
Tested on Win7 64bit with Big Buck Bunny over 800MB and audio podcast over 5 hours - perfectly duration and seeking in all cases (the stuff i tested before is working now for me) [ Chrome is now crashing ;) ]
Thanks! I've marked it fixed, thanks to bug 730765.
Status: UNCONFIRMED → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.