Project

General

Profile

Feature #10835

Tor Browser has no MPEG-4 video support on Jessie

Added by intrigeri over 3 years ago. Updated over 3 years ago.

Status:
Resolved
Priority:
Elevated
Assignee:
-
Category:
-
Target version:
Start date:
01/01/2016
Due date:
% Done:

100%

Feature Branch:
feature/11403-tor-browser-6.x
Type of work:
Wait
Blueprint:
Starter:
Affected tool:
Browser

Description

I have at least one report that says:

"THE VIDEO PLAYBACK (HTML5) SIMPLY DOES NOT WORK ON MOST WEB SITES.  YOUTUBE
DOES FUNCTION BUT IS SLOW AND JERKY. VIDEO PLAYBACK IS WORKING FINE ON
1.8.1".


Related issues

Related to Tails - Feature #11403: Migrate to Tor Browser 6.0.x based on Firefox 45.2 Resolved 05/09/2016

History

#1 Updated by intrigeri over 3 years ago

  • liveleak.com:
    • 1.8.1 streams videos
    • 2.0~beta1 proposes to open with/download videos
    • bugfix/10798-fix-file-associations proposes to open with/download videos

#2 Updated by intrigeri over 3 years ago

I should try installing gstreamer0.10-ffmpeg from oldstable since it seems to be the missing part:

Alternatively, having Tor Browser build against GStreamer 1.0 would probably fix this.

#3 Updated by intrigeri over 3 years ago

  • Subject changed from Evaluate regressions for in-browser video streaming on Jessie to Tor Browser has no MPEG-4 video support on Jessie
  • Status changed from Confirmed to In Progress
  • Priority changed from Normal to Elevated
  • % Done changed from 0 to 10
  • Type of work changed from Test to Communicate

There's nothing we can realistically do about it on the Tails side, so I tried to get things moving on the Tor Browser side: https://trac.torproject.org/projects/tor/ticket/17970#comment:11.

I'm adding this to the list of known issues.

#4 Updated by sajolida over 3 years ago

I can't play mixcloud on Tails 2.0 either (I'm pretty sure it works in Tor Browser on Debian Jessie but I could double-check if needed). It was working in Tails 1.8. For example: https://www.mixcloud.com/dstormrecordings/tails-from-the-darkside-vol1-bstorm-2013/.

I get "Oh snap, there was a playback error! Press play to try again."

#5 Updated by intrigeri over 3 years ago

  • Assignee changed from intrigeri to sajolida
  • QA Check set to Info Needed

I can't play mixcloud on Tails 2.0 either (I'm pretty sure it works in Tor Browser on Debian Jessie but I could double-check if needed).

Yes, please double-check on regular Jessie (if it works there, without gstreamer0.10-ffmpeg installed, then it's most likely a different bug, and would be better handled separatedly.

#6 Updated by sajolida over 3 years ago

Sorry for the delay. Actually:

#7 Updated by intrigeri over 3 years ago

  • Assignee changed from sajolida to intrigeri
  • Target version changed from Tails_2.0 to Tails_2.2

Sure, but a system upgraded from Wheezy can potentially still have gstreamer0.10-ffmpeg installed. That's why I was asking if you had it installed on the system you were talking of. Whatever, I'll take it over from this point and will ask again if I realize that I need the answer to this question.

  • mixcloud doesn't work on Jessie in the latest Tor Browser (probably 5.0.7 but I could double check if needed).

OK, thanks. I'll check this out and will see if it's a different bug from this one, or not.

#8 Updated by intrigeri over 3 years ago

  • QA Check deleted (Info Needed)

#9 Updated by londonsilver over 3 years ago

Solution for this issue in 2.0 is for above video link, as well as youtube.com/html5 checks (as well as spiegel.de videos mentioned in #tails) the following changes to about:config

media.fragmented-mp4.exposed false
media.fragmented-mp4.ffmpeg true
media.fragmented-mp4.gmp true
media.mediasource.enabled true
media.mediasource.mp4.enabled true
media.mediasource.webm.enabled true
media.mediasource.ignore_codecs == true <-- this bool must be created

who doesn't want to wait for 2.0.1 (and uses persistence):
- do a fresh reboot (to be sure to have a clean Tails prefs.js)
- do above changes
- save /home/amnesia/.tor-browser/profile.default/prefs.js
- after reboot restore it to /home/amnesia/.tor-browser/profile.default/

Note: dotfile feature doesn't work for this. prefs.js from dotfiles is linked correctly but not recognized by TB and next config change the link is replaced by an actual file.

#10 Updated by londonsilver over 3 years ago

no option to edit a post a few minutes? :(

it's media.fragmented-mp4.exposed == true

sorry.

#11 Updated by intrigeri over 3 years ago

Solution for this issue in 2.0 is for above video link, [...]

media.mediasource.enabled true
media.fragmented-mp4.exposed true
media.fragmented-mp4.ffmpeg true
media.fragmented-mp4.gmp true

I confirm that with these four changes, I can view the dailymotion video linked above. Also, https://html5test.com/ says I have H.264 support, which is not the case out-of-the-box on Tails 2.0. Thanks!

Next step is to check whether these changes might cause regressions in terms of functionality, security, or web fingerprinting.

My understanding of https://trac.torproject.org/projects/tor/ticket/16429 (found via https://trac.torproject.org/projects/tor/ticket/15703) is that mediasource should be safe in itself in current Tor Browser in terms of stream isolation, but this doesn't tell me if changing the default handling of video is safe too. I'll ask the Tor Browser developers.

Regarding the other suggested prefs:

media.mediasource.mp4.enabled true

... is on by default.

media.mediasource.webm.enabled true

This ticket is about MPEG-4 video, and as far as I can tell WebM video works fine in Tails 2.0 already, so I see no need to modify WebM handling and will skip this one unless I'm explained why it maters.

media.mediasource.ignore_codecs == true <-- this bool must be created

I could not find where it's used in the Tor Browser source code, and I see no difference when I add it => I'll disregard this one unless I'm explained why it matters.

#12 Updated by intrigeri over 3 years ago

I'll ask the Tor Browser developers.

Done: https://trac.torproject.org/projects/tor/ticket/17970#comment:18

#13 Updated by londonsilver over 3 years ago

@intrigeri
The other settings were necessary to get the blue OK-marks on all features at youtube.com/html5
Regarding ignore_codecs you can check the difference between
media.mediasource.ignore_codecs == true
and 'no entry' yourself at youtube.com/html5 *.

BTW: Not that I minded (I solved it for me) but why would you wait for the next bug report if you can fix/support it all at once?

  • can't check it now, my 1.8.2 behaves differently than 2.0

#14 Updated by intrigeri over 3 years ago

Yay, but MSE doesn't seem to be very mature in FF38ESR, so I'd rather not enable it for more than what's needed to fix regressions that 2.0 introduced compared to Tails 1.x. My understanding is that MSE support for WebM would rather be a new feature, so it's handled differently.

#15 Updated by intrigeri over 3 years ago

  • Target version changed from Tails_2.2 to Tails_2.4

This will be fixed "for free" once we are based on ESR45: https://trac.torproject.org/projects/tor/ticket/17970#comment:20, so postponing to Tails 2.4 that will have it.

The prefs to enable MSE seem too risky to enable by default: https://trac.torproject.org/projects/tor/ticket/17970#comment:19. Let's not crash the browser.

#16 Updated by londonsilver over 3 years ago

as "Target version changed from Tails_2.2 to Tails_2.4"

I advance my suggestion from "who doesn't want to wait for 2.0.1" to "who doesn't want to wait for 2.4"
Just see above. If your browser/system really becomes unstable (I cannot support such a statement from my everyday experience!): Just reboot and don't/undo do the changes ;)

#17 Updated by intrigeri over 3 years ago

  • Assignee changed from intrigeri to anonym
  • QA Check set to Info Needed

anonym, wanna take this one that should be fixed for free when we move to Firefox 45 ESR in Tails 2.4 (which you'll be handling, presumably)? Basically all that needs to be done is checking if the test videos linked above work with FF45.

#18 Updated by anonym over 3 years ago

  • QA Check deleted (Info Needed)
  • Type of work changed from Communicate to Wait

intrigeri wrote:

anonym, wanna take this one that should be fixed for free when we move to Firefox 45 ESR in Tails 2.4 (which you'll be handling, presumably)? Basically all that needs to be done is checking if the test videos linked above work with FF45.

Yup, I'll do it as part of the work needed for the FF45 bump.

#19 Updated by anonym over 3 years ago

  • % Done changed from 10 to 50
  • Feature Branch set to feature/11403-tor-browser-6.x

Everything mentioned here (dailymotion, mixcloud) works in an image built from the feature/11403-tor-browser-6.x branch.

#20 Updated by anonym over 3 years ago

  • Related to Feature #11403: Migrate to Tor Browser 6.0.x based on Firefox 45.2 added

#21 Updated by anonym over 3 years ago

  • Status changed from In Progress to Fix committed
  • Assignee deleted (anonym)
  • % Done changed from 50 to 100
  • QA Check set to Pass

#22 Updated by anonym over 3 years ago

  • Status changed from Fix committed to Resolved

Also available in: Atom PDF