MP4 videos fail to play
MP4 videos fail to play with the following error messages:
- No video with supported format and MIME type found.
- Video can't be played because the file is corrupt.
- NS_ERROR_DOM_MEDIA_FATAL_ERR (0x806e0005)
- Error no decoder found for audio/mp4a-latm
example video #1 on https://tekeye.uk/html/html5-video-test-page
other notes:
- issue began a 1-2 weeks ago
- issue does not exist on chrome browser
- MP4 videos can be downloaded and played successfully in applications other than firefox
- other video formats play successfully in firefox
- issue persists in troubleshoot mode
- issue persists with hardware acceleration on/off
- issue persists with tracking protection on/off
- media.mp4.enabled is set to true
MP4 videos fail to play with the following error messages:
# No video with supported format and MIME type found.
# Video can't be played because the file is corrupt.
# NS_ERROR_DOM_MEDIA_FATAL_ERR (0x806e0005)
# Error no decoder found for audio/mp4a-latm
example video #1 on [https://tekeye.uk/html/html5-video-test-page https://tekeye.uk/html/html5-video-test-page]
other notes:
* issue began a 1-2 weeks ago
* issue does not exist on chrome browser
* MP4 videos can be downloaded and played successfully in applications other than firefox
* other video formats play successfully in firefox
* issue persists in troubleshoot mode
* issue persists with hardware acceleration on/off
* issue persists with tracking protection on/off
* media.mp4.enabled is set to true
All Replies (8)
It works for me. see screenshot Desktop or laptop Manufacture and Model?
Edition Windows 11 Pro Insider Preview Version 22H2 Installed on 30-Sep-22 OS build 25211.1010 Experience Windows Feature Experience Pack 1000.25211.1010.0
issue persists with new profile
sprain5494 trɔe
more notes:
- issue exists in 105.0
- video plays in 104.0.2, but not audio
sprain5494 trɔe
Can you update to the current version and see what happens? It works for me in Win7. see screenshot
Did you test in Safe Mode?
jonzn4SUSE said
Can you update to the current version and see what happens?
issue persists in 106.0.1
