Video fails to play in browsers
Describe the bug
I use nextcloud about couple of mounth, and install memories. I like it, because it can play video in browser without problem (unlike of photo app). Now when i upload my new videos it fails to play with error:
VIDEOJS: ERROR: (CODE:4 MEDIA_ERR_SRC_NOT_SUPPORTED) The media could not be loaded, either because the server or network failed or because the format is not supported.
All my videos are from my iphone 11 pro max with 4k 60fps settings (hevc, mov). I didnt change any settings, all my half year old videos (and oldest) plays without problem, but new uploaded fails to play on any browsers. Only one thing is changed - i update phone from ios 17 to ios 18, but in meta data i dont see any difference
Steps To Reproduce
No response
Platform
- OS: iOS
- Browser: Chrome, Edge, Safari, Opera
- Memories Version: 7.4.1
- Nextcloud Version: 30.0.4
- PHP Version: 8.2.27
Screenshots
Additional context
This issue have no errors in nextcloud log
These videos are likely HEVC, which the browser doesn't support. You just need to configure transcoding correctly.
It must works with hw acceleration in browser. Got to work it only in vivaldi, but without sound.. probably something changes in ios18, will be search for myself about it. Sorry for opening issue. Thanks anyway!
I had some very old videos myself that I converted from mkv/avi (and many more) to mp4 and noticed that not all video codecs are supported (and the memories android app even seemed color coding specific, but that is another story). I converted these to libx264/h264 mp4 files with ffmpeg and everything worked. I also converted some huge video files from 4k to 1080p and reduced framerates to 25/30fps. This made my entire video library play in a browser without any transcoding or other specific settings. It might be useful for you or anyone else.
To prevent it in the future, you can probably set your camera to save uncompressed video's (h264 instead of h265 if I remembered correctly, or at least somethign to disable HEVC as @pulsejet also suggested). In my (android) camera app there is a setting for it at least.
Since this problem is not memories-specific, you could consider closing the issue.