Closed Bug 823588 Opened 13 years ago Closed 8 years ago

[Video] Unsupported Video files formats are not displayed with an error in Video App's File Browser

Categories

(Firefox OS Graveyard :: Gaia::Video, defect)

ARM
Gonk (Firefox OS)
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: cschmoeckel, Unassigned)

Details

(Whiteboard: inarirun1, inarirun2, leorun3, leorun4, retest_leorun4, )

Attachments

(3 files)

Summary: After loading an unsupported video file onto the device, the file cannot be located in the Video App's File Browser. Steps: 1. Have an unsupported video file ready on the PC (ex.: http://support.apple.com/kb/HT1425) 2. Connect the phone to the computer via USB 3. Move the video file into the phone's Video folder 4. Disconnect the phone 5. Launch the video app Result: The unsupported video file does not appear in the File Browser Expected Result: Unsupported video files are displayed in the File Browser of the Video App with an error message. Build: 20121217070202 This issue fails test case #3662 - [Video] Unsupported videos added to the video playlist are marked indicating the error
Test Run 2 Issue still occurs on Unagi in Build 20130104070203
UCID videoplay-020 Testcase can be found here https://moztrap.mozilla.org/results/case/61055/
Whiteboard: testrun 2
Hardware: x86_64 → ARM
OS: Windows 7 → Gonk (Firefox OS)
Unsupported video files still do not show up in the Video Player browser and have no invalid file type error displayed. Build ID: 20130130070201 Kernel: Dec 5 Gecko http://hg.mozilla.org/releases/mozilla-b2g18/rev/4593f3e765eb Gaia f7f5a0cd17e3d04308cc5850b254947e127122b9
Whiteboard: testrun 2 → testrun 2, testrun 4
Whiteboard: testrun 2, testrun 4 → testrun 4
Unsupported video files still do not show up in the Video Player browser and have no invalid file type error displayed. Unagi Build ID: 20130225070200 Kernel: Dec 5 Gecko: http://hg.mozilla.org/releases/mozilla-b2g18_v1_0_1/rev/3a5a27992a75 Gaia: 5691a16fff8e1403c75ed9d6f3a443b7e58198c6 UCID: Videoplay-020 Test case ID: https://moztrap.mozilla.org/runtests/run/859/env/305/?pagenumber=1&pagesize=20&sortfield=order&sortdirection=asc&filter-id=3662
Whiteboard: testrun 4 → testrun 4, testrun 5.1
Whiteboard: testrun 4, testrun 5.1 → testrun 5.1
Need a requirements check on this one
Keywords: qawanted
UCID: Videoplay-020 As a user, I want videos in unsupported formats to be listed with an error indicator and details about what's wrong with the format and how I might fix it, so that I'm not confused about why a file I placed on the card is not appearing.
Requirement states the video should be listed. Current behavior is that it is not. Removing 'qa wanted'.
Keywords: qawanted
Whiteboard: testrun 5.1 → testrun 2, testrun 5.1
Environmental Variables: Inari Build ID: 20130416070200 Kernel Date: Feb 21 Gecko: http://hg.mozilla.org/releases/mozilla-b2g18_v1_0_1/rev/6bac24e14538 Gaia: c883af5ecd0998f78d9aaa4c2337c842e1dbb5a0 The same issue reproduces on "Inari" device. According to the test case ID: 4453, The unsupported files shouldn't appear in the video list. https://moztrap.mozilla.org/manage/cases/?pagenumber=1&pagesize=20&sortfield=created_on&sortdirection=desc&filter-id=4453 The test case ID:3662 says the unsupported files should appear in the video list. https://moztrap.mozilla.org/manage/cases/?pagenumber=1&pagesize=20&sortfield=created_on&sortdirection=desc&filter-id=3662 One of these test cases are invalid and need to be invalidated or updated
UCID:videoplay-020
Whiteboard: testrun 2, testrun 5.1 → inarirun1
Whiteboard: inarirun1 → inarirun1, inarirun2
Whiteboard: inarirun1, inarirun2 → inarirun1, inarirun2, leorun3
Attached file logcat
Whiteboard: inarirun1, inarirun2, leorun3 → inarirun1, inarirun2, leorun3, leorun4
In MozTrap disabled TC#4453 - [Video] Video List View - Do not display unsupported video formats This test case uses an old and removed UCID: videoplay-001
Whiteboard: inarirun1, inarirun2, leorun3, leorun4 → inarirun1, inarirun2, leorun3, leorun4, retest_leorun4
What is the correct UX behavior for this case? Let me know so I can either koi? nom it or remove the referring testcases altogether.
Flags: needinfo?(firefoxos-ux-bugzilla)
Flagging Rob on this one since Media is his domain, though UX is still prioritizing blockers.
Flags: needinfo?(firefoxos-ux-bugzilla)
Video thumbnail generation API(Bug 873959) will be implemented in future. When it is implemented, some hw is going to use different video codec for thumbnail generation and video playback. There could be a case that thumbnail generation failed, but play back is possible. For example, normal android's sw codec can decode only H.264 baseline profile.
Whiteboard: inarirun1, inarirun2, leorun3, leorun4, retest_leorun4 → inarirun1, inarirun2, leorun3, leorun4, retest_leorun4, burirun1
Test case 3662 disabled for v1.2 until bug 873959 is implemented.
Whiteboard: inarirun1, inarirun2, leorun3, leorun4, retest_leorun4, burirun1 → inarirun1, inarirun2, leorun3, leorun4, retest_leorun4,
I've some personal feeling about this issue at: https://groups.google.com/forum/#!topic/mozilla.dev.gaia/l8R_nI8Dsvc For short, I don't think I should be punished when I follow the public information to put a valid MP4 on my phone. It's totally different with the situations that I put some obvious unplayable files like MKV or RMVB. I said "punished" because as an ordinary user, I have no chance to know what's happened. All things I know is my MP4 file, even I'm sure it's encoded with H264+AAC codec (slightly beyond a ordinary user's knowledge), it just won't even show in the playlist. This is very confused and frustrated. *NI because David Flanagan suggested me that "I recommend that you file a bug and set needinfo for Chris Lam (the new UX designer for Video) and also John Hu. Implementing what you suggest should not be too hard, (though it is complicated by the fact that the .mp4 extension can be music or video, so the sdcard scanning process has to divide files into three categories: playable video, unplayable video and not-a-video. (Currently unplayable videos get lumped with not-a-video files and just don't show up.)"
Flags: needinfo?(johu)
Flags: needinfo?(clam)
I can implement that once Chris gives us some suggestion about this case.
Flags: needinfo?(johu)
Attached video can_play_on_Nexus4
One of the subtle part of MP4 issue is it depends on device, even for FirefoxOS. This video is a Nexus4 running FirefoxOS (Gecko 26, v1.2). It can show and play as normal.
Hey all, Let's show the unsupported videos in the list.
Flags: needinfo?(clam)
Chris, May you give us some wireframe when we meet unsupported videos??
Flags: needinfo?(clam)
Regarding comment# 17, I've looked into the ability to distinguish between not-a-video and unplayable vidoes. I'm not sure how we're going to do it. Currently, if we discovery a video is not playable, we don't try to load it. If we say an unplayable video is a video, we will try to load it and we will fail (at least that is my experience while testing with mp4 and mov -- quicktime -- files). At that point, there is an issue distinguishing between a valid but unplayable video and a corrupt video (we detect corrupt videos by detecting an error when loading the video). I suppose we can simply not load unplayable videos since we won't be able to generate a thumbnail for them anyway.
NI jsavory for ux input
Flags: needinfo?(clam) → needinfo?(jsavory)
(In reply to Russ Nicoletti [:russn] from comment #22) > Regarding comment# 17, I've looked into the ability to distinguish between > not-a-video and unplayable vidoes. I'm not sure how we're going to do it. Currently, we don't know if a video is an unplayable or not-a-video because we view them as unplayable videos. And the definition of not-a-video is hard to define because we use file extension to enumerate all video files. And all files with valid extensions are tried to load by video element. Here is an example: When a plain text file ending with .mp4, we will try to load it with offscreen video element. If onerror is fired, we view this file as an unplayable video file just because it's extension is mp4 and is unplayable by video element. There is another case that we can load the video file to video element but cannot draw it on the canvas, bug 869289 comment 3. In this case, we view this file as a playable video file but use a default image to be its thumbnail.
Attached file UnsupportedVideo.pdf
Sorry for the (very) long delay on this one. I've attached a mini spec that Katie put together, which will hopefully answer any UX questions. If this bug is still valid, feel free to needinfo me again if there are further questions.
Flags: needinfo?(jsavory)
Firefox OS is not being worked on
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: