3 ms·
this will definitely need to be hardware-supported for decoding. on my phone, the decode time far exceeds the time it would take to serve up a bigger jpg file.
by leeoniya 12y ago
this will definitely need to be hardware-supported for decoding. on my phone, the decode time far exceeds the time it would take to serve up a bigger jpg file.
the demos reminded me what browsing on dialup was like. in fact dialup was better cause at least the decoding/loading was progressive/incremental, which doesnt seem to be the case here. i assume it's just the way the decoder is implemented?
- 0x0 12y agoAlso unfortunately it seems to crash MobilrSafari something fierce when you start to zoom. :-/
- vidarh 12y agoIt just needs to be implemented natively. On the demo page the decoding is done in javascript.
- dletozeun 12y agoA native implementation like the JPEG decoder would be fine. The bundled JS decoder implementation is elegant but not efficient on mobile platform (stalling here for seconds on iPad 3 / iOS 8 / chrome while JPEG ones are displayed instantaneously)
- expr- 12y agoI decided to give it a try on a low-spec Android tablet, running latest version of Firefox. Got coloured horizontal stripes instead of a proper picture for every BPG example – and not just once; I was unable to view the images on the tablet. Not quite production-ready, I think.
- masklinn 12y agoSimilar issue with Firefox/Android, the Lena BPG images are completely scrambled to hell. Safari/iOS and Chrome/Android worked with no issue. Desktop Firefox also worked.