files_videoplayer icon indicating copy to clipboard operation
files_videoplayer copied to clipboard

files_videoplayer doesn't play certain MP4 files after upgrading to NC 16.0.1

Open micredd opened this issue 6 years ago • 14 comments

After upgrading to Nextcloud 16.0.1, the built-in files_videoplayer app no longer plays some MPEG4 video files. Dragging the unplayable file directly into the browser plays the file normally.

I should stress that only some MP4 files no longer play; it's not as if the mime type was removed completely. All files, working and non, were pulled from YouTube, so I cannot speak for how they were encoded. All worked prior to the upgrade, however.

The server's log is clean at log level 2, though I did notice Nextcloud ran a repair of mime types during the upgrade process, a la

[updater] Info: \OC\Repair::step: Repair step: Repair mime types
at 2019-05-18T14:44:23+00:00

Not sure if this is a typical step in the upgrade process; I've never been inclined to pay attention to it before.

Setup

  • Server: Debian 9.9 (Stretch) with PHP 7.3 (Sury's PHP repository)
  • Nextcloud 16.0.1, tested with and without opcache enabled, with and without PHP-FPM
  • Client: Firefox 60.6.3 ESR (tested with Debian 9 and Windows 10)

Expected behaviour

Files_videoplayer should play an MP4 file as it did in Nextcloud versions < 16.0

Actual behaviour

The player displays the following error: "The media could not be loaded, either because the server or network failed or because the format is not supported."

Steps to reproduce

  1. Play a 360p MP4 video pulled from YouTube,
  2. Upgrade from Nextcloud 15.0.8 to Nextcloud 16.0.1,
  3. Disable the new "Viewer" app to make files_videoplayer the default again,
  4. Attempt to play the same video again.

micredd avatar May 18 '19 15:05 micredd

Hi, I have the same problem with 16.0.0

PxSonny avatar Oct 16 '19 05:10 PxSonny

have it in 17 also

geiseri avatar Nov 20 '19 04:11 geiseri

I think it might be related to enabling #enable-experimental-web-platform-features in chrome. It works again when I turn it off.

geiseri avatar Nov 24 '19 17:11 geiseri

Interesting, how to do that?

Le lun. 25 nov. 2019 à 01:29, Ian Reinhart Geiser [email protected] a écrit :

I think it might be related to enabling #enable-experimental-web-platform-features in chrome. It works again when I turn it off.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/nextcloud/files_videoplayer/issues/130?email_source=notifications&email_token=ABTJTCOM2GWDSF32E26FN7DQVK2WZA5CNFSM4HN2QIYKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEFAQN2Q#issuecomment-557909738, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABTJTCJGDISFGWQZRS2UCJ3QVK2WZANCNFSM4HN2QIYA .

-- Regards, Sonny Alves Dias

CTO Email: [email protected] Mobile: +86 186 2107 5301 <008618621075301> Web: www.pixelmatic.com [image: Facebook] https://www.facebook.com/pixelmatic [image: Twitter] https://twitter.com/pixelmatic [image: LinkedIn] https://www.linkedin.com/company/pixelmatic

PxSonny avatar Nov 25 '19 02:11 PxSonny

Same problem on 17.0.3

danjde avatar Feb 22 '20 20:02 danjde

In Chromium, I disabled the experimental web platform features under (chrome://flags), and all mpeg 4 files (video and audio) are a problem tried with the windows Edge Browser and these files do work. It must have something to do with some modern browser features.

GeneralRancor avatar Feb 26 '20 06:02 GeneralRancor

+1

error occured after upgrading to 18.0.3. But: none of my browsers (FF, Chrome, Opera, Safari) can open mp4-files. Before it was no issue.

I think there is some issue with the video-player and the video.js - I also did update the mimetypes, but no success.

bunducafe avatar Apr 05 '20 09:04 bunducafe

+2

error occured after upgrading to 18.0.3. But: none of my browsers (FF,Adroid app) can open mp4-files. Before it was no issue. Chrome is ok.

huoang avatar Apr 08 '20 05:04 huoang

@huoang: Interesting, that Chrome is working in your case... here it does not.

When I do upload new mp4 files, they are played with no issue. Yet I still cannot play the old mp4s in none of my browsers.

I find it somewhat strange that the update procedure corrupts playing any old video files on the server. I would be very pleased if I could solve that issue differently than re upload all the files again.

bunducafe avatar Apr 08 '20 08:04 bunducafe

@bunducafe .yeah,Chrome Indeed can play the intro.mp4 smoothly.Furthermore,I uploaded another mp4 whose size was about 20M,but this time chrome could only play the audio,there was a small video black window left in the middle of chrome. I have no idea of why this happened.

huoang avatar Apr 08 '20 13:04 huoang

It's still strange. I had a look into this issue github.com/nextcloud/files_videoplayer/pull/153 but dit id not do the trick.

I have difficulties playing videos in all browsers and no matter whether they are mp4, m4v or mov. And no matter if they are in a shared folder or accessable via shared via link.

bunducafe avatar Apr 21 '20 11:04 bunducafe

Do the videos work if you drag them into an empty browser window?

You can try to compare video codecs with ffmpeg or some other tool to make sure they are all compatible with the browser.

Then you can compare file sizes or checksums before and after the upload. I'm pretty sure Nextcloud doesn't alter video files :wink:

Instagit avatar Apr 27 '20 14:04 Instagit

Any updates on this? I'm still having this issue with any mp4 files recorded with my phone cameras (Google Pixel 7 Pro, and Poco X3 NFC). Other mp4 videos, such as screen recordings, do work, however. Using Nextcloud All In One v4.1.0 (with Nextcloud 25.0.2) on Ubuntu 22.04 aarch64. It doesn't happen on the Android app, so it must be a local issue. Happens with both Firefox (deb) and Brave on Ubuntu 22.10. ubuntu-restricted-extras is installed. Any idea what I'm missing?

EDIT: u/K_C_Shaw on reddit pointed out that it's likely due to HEVC/H.265 compression. The memories app will apparently transcode these videos, but may be slow, depending on wether or not your CPU or GPU supports hardware transcoding. HW transcoding also requires additional setup, which is detailed in the NC AIO readme.

SingerJonathan avatar Jan 23 '23 01:01 SingerJonathan

Problem still exist on 25.0.2

Rossum93 avatar Sep 10 '23 12:09 Rossum93