Closed
Bug 1300062
Opened 9 years ago
Closed 3 years ago
F4V format not playing automatically, only downloaded
Categories
(Core :: Audio/Video: Playback, defect, P3)
Tracking
()
RESOLVED
INCOMPLETE
People
(Reporter: jeremy.judeaux, Unassigned)
References
Details
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/53.0.2785.89 Safari/537.36
Steps to reproduce:
Open F4V video (for example, attachment https://bugzilla.mozilla.org/attachment.cgi?id=735970 from issue 860353)
Actual results:
Firefox shows message "Video can't be played because the file is corrupt"
The video isn't played.
Tested on Windows 10 (Firefox 35, 37, 47, 48) and Max OS El Capitan (Firefox 48)
Expected results:
The video should be played
Works on Windows 10 + Firefox 34.0.5
I've seen nothing related to this change in Firefox 35 Release Notes
It's due to bug 1057879.
https://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=dc352a7bf234&tochange=0753f7b93ab7
If the MP4 parser is able to read the video/audio codec of the F4V video, maybe this container (as mime type "video/x-f4v") should be supported like we did in the past for M4V (bug 875573).
Blocks: 1057879
Component: Untriaged → Audio/Video: Playback
OS: Unspecified → Windows
Product: Firefox → Core
Hardware: Unspecified → All
Comment 2•9 years ago
|
||
We do not support flash video (vp6) and won't in the future.
Status: UNCONFIRMED → RESOLVED
Closed: 9 years ago
Flags: needinfo?(jyavenard)
Resolution: --- → FIXED
Comment 3•9 years ago
|
||
Also note that flash video aren't compatible with html5
Reporter | ||
Comment 4•9 years ago
|
||
(In reply to Jean-Yves Avenard [:jya] from comment #2)
> We do not support flash video (vp6) and won't in the future.
As far as I can tell, it's a F4V container and H.264 codec.
It can be read using HTML5 player in all other browsers. Also it used to be read by Firefox in HTML5 player; I guess if Firefox intends to drop the support of F4V, it should at least be announced in a release?
By the way, supporting F4V is a good way to allow people to migrate to HTML5 player without having to convert (a potentially huge lot of) videos.
Has this regression been fixed? In which release should I expect F4V to work again?
Comment 5•9 years ago
|
||
(In reply to jeremy.judeaux from comment #4)
> (In reply to Jean-Yves Avenard [:jya] from comment #2)
> > We do not support flash video (vp6) and won't in the future.
>
> As far as I can tell, it's a F4V container and H.264 codec.
>
> It can be read using HTML5 player in all other browsers. Also it used to be
> read by Firefox in HTML5 player; I guess if Firefox intends to drop the
> support of F4V, it should at least be announced in a release?
>
> By the way, supporting F4V is a good way to allow people to migrate to HTML5
> player without having to convert (a potentially huge lot of) videos.
>
> Has this regression been fixed? In which release should I expect F4V to work
> again?
it's not a regression per say, f4v would never have worked other maybe with some particular WMF plugin and that's on windows only.
F4V extension indicates that the file is a flash video; it's the wrong extension to use. And support won't be added. it should be rename to .mp4 (or .m4[av])
this file is actually plain mp4; just the major brand is incorrect (f4v); which isn't a valid major brand in mp4.
compatible brands are set up properly... so maybe we could relax the checks a tad and accept incorrectly tagged video.
in any case that video is not properly muxed.
Status: RESOLVED → REOPENED
Ever confirmed: true
Resolution: FIXED → ---
Reporter | ||
Comment 6•9 years ago
|
||
As far as I know, F4V is based on the MP4 format. So for me it's more of a "valid F4V" than a "plain MP4 with incorrect major brand".
I tried reading the file by forcing the extension/type/Content-Type header to mp4, didn't work.
If it's possible to take benefit of the compatible brands to read a video (F4V or whatever-4V), I'd say please do it, I don't see any disadvantage of doing so.
If not, then I guess this bug should be closed as wontfix?
Comment 7•9 years ago
|
||
(In reply to jeremy.judeaux from comment #6)
> As far as I know, F4V is based on the MP4 format. So for me it's more of a
> "valid F4V" than a "plain MP4 with incorrect major brand".
and you'd be wrong.
There's nothing "flash" about this video.
My guess is that the encoder when converting the flash video into mp4, incorrectly set the mp4 type. I suggest you read ISO 14496-12 (ISO BMFF)
f4v extension is for flash file, this isn't a flash video. The extension is wrong, the mimetype provided is wrong.
Reporter | ||
Comment 8•9 years ago
|
||
I think you are mistaking F4V video and FLV video.
From F4V specification http://download.macromedia.com/f4v/video_file_format_spec_v10_1.pdf :
> The open specification of the F4V video file format builds on the standard IEC 14496-12 (MPEG-4 Part 12) ISO
> base media file format. It has a flexible structure and defines specific supported codecs and extensions. The F4V
> video file format thus simplifies the implementation of dynamic media software, facilitating interoperability across
> tools, services, and clients.
Can you point to a site that uses f4v?
It looks MP4-ish to me. Perhaps track 2 is causing us grief.
Input #0, mov,mp4,m4a,3gp,3g2,mj2, from 'FF20_html5_video_image_blurry.f4v':
Metadata:
major_brand : f4v
minor_version : 0
compatible_brands: isommp42m4v
creation_time : 2012-11-19 12:35:00
Duration: 00:00:30.03, start: 0.000000, bitrate: 318 kb/s
Stream #0:0(eng): Video: h264 (High) (avc1 / 0x31637661), yuv420p(tv, bt709), 740x416 [SAR 1:1 DAR 185:104], 169 kb/s, 29.97 fps, 29.97 tbr, 90k tbn, 59.94 tbc (default)
Metadata:
creation_time : 2012-11-19 12:35:00
handler_name : MainConcept
encoder : AVC Coding
Stream #0:1(eng): Audio: aac (LC) (mp4a / 0x6134706D), 44100 Hz, stereo, fltp, 128 kb/s (default)
Metadata:
creation_time : 2012-11-19 12:35:00
handler_name : Mainconcept MP4 Sound Media Handler
Stream #0:2(eng): Data: none (amf0 / 0x30666D61), 0 kb/s (default)
Metadata:
creation_time : 2012-11-19 12:35:00
handler_name : Timed Metadata Handler
Unsupported codec with id 0 for input stream 2
Priority: -- → P3
Reporter | ||
Comment 11•9 years ago
|
||
(In reply to Anthony Jones (:kentuckyfriedtakahe, :k17e) from comment #9)
> Can you point to a site that uses f4v?
We use a lot on restricted areas of englishlive.ef.com, but not in open areas, so I can't link to any page. We are currently migrating to HTML5 player, and found out only Firefox can't read the F4V files.
They probably are several other sites (like the one of the issue 860353), but I don't know any.
Reporter | ||
Comment 12•9 years ago
|
||
I just found out that the F4V video is correctly playing on Firefox Beta 49 (tried Windows, OS X) and Firefox Nightly (tried Windows, Linux).
Has something been fixed, or is this issue just a flag on the Release channel?
Comment 13•9 years ago
|
||
could be bug 1275853.
Comment 14•9 years ago
|
||
still need to amend the sniffer to recognise f4v signature.
Comment 15•9 years ago
|
||
confirmed, it is bug 1275853.
Updated•9 years ago
|
Summary: F4V format "Video can't be played because the file is corrupt" since Firefox 35.0 → F4V format not playing automatically, only downloaded
Comment 16•9 years ago
|
||
Changing the bug title as this bug is fixed.. now it's just a matter of changing the mp4 sniffer if we decide to support those videos.
Reporter | ||
Comment 17•9 years ago
|
||
I've tried the just released Firefox 49. It seems to work well.
I tried serving the f4v file with name "FF20_html5_video_image_blurry.f4v", HTTP Header Content-Type:"video/x-f4v", and HTML source tag with either no type attribute or type="video/mp4". Works in both cases.
<video controls preload="auto" muted autoplay>
<source src="./FF20_html5_video_image_blurry.f4v" type="video/mp4"/>
</video>
<video controls preload="auto" muted autoplay src="./FF20_html5_video_image_blurry.f4v"></video>
I don't know if there is anything else to be done.
Comment 18•9 years ago
|
||
(In reply to jeremy.judeaux from comment #17)
> I've tried the just released Firefox 49. It seems to work well.
>
> I tried serving the f4v file with name "FF20_html5_video_image_blurry.f4v",
> HTTP Header Content-Type:"video/x-f4v", and HTML source tag with either no
> type attribute or type="video/mp4". Works in both cases.
you can't open the file directly as we don't handle the mimetype video/x-flv and it's what a f4v returns (video/x-flv is the official mimetype for those)
One issue I have here, is that it appears that this mimetype is used for both F4V (mp4) and FLV. I am unsure if they should be distinguished. And if we don't that means you will no longer be able to play flv file if you have the flash plugin installed.
Reporter | ||
Comment 19•9 years ago
|
||
If that helps, the only "documentation" I found comes from the blog of a Flash Player Engineer at https://web.archive.org/web/20160406183705/http://www.kaourantin.net/2007/10/new-file-extensions-and-mime-types.html and recommends the use of "video/mp4" for F4V files.
A lot of messages on adobe forums agree with that. I've found one document on adobe site using "video/x-f4v", and no documents associating F4V with "video/x-flv".
So I think you can safely use a different MIME type to distinguish F4V and FLV.
![]() |
||
Comment 20•3 years ago
|
||
No longer supported
Status: REOPENED → RESOLVED
Closed: 9 years ago → 3 years ago
Resolution: --- → INCOMPLETE
You need to log in
before you can comment on or make changes to this bug.
Description
•