Chrome, MP4 and HTML- size issue

[Scott Renton]

Hi folks

I'm embedding MP4 videos into an online musical instruments collection, and find they play fine in all browsers across MacOs X and Windows, except for Chrome. We're using the HTML5 standard video player, and have also tried JW player, which gives the same result.

After some investigation, we've found that 4 out of 97 are working- and they are all 2Mb and under. Obviously we can't compress files down to this size, so the problem must be solvable elsewhere.

Inspecting the element shows what is in the screenshot. When the page loads, it gets a 200 OK status, but then runs another GET immediately, which returns a (canceled) message. The files under 2Mb, presumably really fast loaders, don't get this second message. Please note, the MIME Type on that file is application/octet-stream, but we've since fixed to video/mp4, and it gives exactly the same result.

Really, this is just a post to see if anyone else has experienced this, and can understand what's going on- if it's taking too long to load, but tries again and then bombs out, is there any way to force it to wait longer for larger files?

Thanks
Scott

PS I also tried enabling the 'disable hardware accelerate video' in chrome flags on Windows, but that didn't help either!

[PhistucK]

Does the server send a proper Content-Length response header for the video URL?

☆PhistucK

--
You received this message because you are subscribed to the Google Groups "Chromium HTML5" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chromium-html...@chromium.org.
To post to this group, send email to chromiu...@chromium.org.
Visit this group at http://groups.google.com/a/chromium.org/group/chromium-html5/.
For more options, visit https://groups.google.com/a/chromium.org/d/optout.

[Rishi Ranjan]

I am using express to serve the file. It uses "Chunked Transfer encoding". I verified that length is correctly received on receiver by comparing the file size on server and client. I have also confirmed that bytes are correctly received by comparing the bytes on server and receiver.

[PhistucK]

I am not sure what "express" means, but chunked encoding may be problematic. Try without it and see if it helps.

☆PhistucK

[Silvia Pfeiffer]

I assume with "express" you are referring to the node framework. Are
you using sendFile() so you are actually sending byte ranges on the
server?

Here are some other pointers:
http://delog.wordpress.com/2011/04/25/stream-webm-file-to-chrome-using-node-js/
http://stackoverflow.com/questions/6233562/node-js-chunked-transfer-encoding
(first answer)

HTH,
Silvia.

[Rishi Ranjan]

Replied to this thread by mistake. Will send my reply on original thread.

[Scott Renton]

Thanks PhistucK. Content-length was coming through ok; we also tried some things with chunking etc, but nothing worked, so we have fallen back to using webm for Chrome, and mp4 for everything else!

Cheers
Scott