MOV file returns "hlsjs: video file not found"

Hello,

Using Serviio 1.9 on MediaBrowser using Chrome, the MOV files recorded by my drone (DJI Phantom 4) return "hlsjs: video file not found". I was able to start a video once directly on the mediabrowser but after that I just receive the above error. I'm running Serviio on my Synology NAS.

Any ideas?

Thanks in advance

After some research, I found out that this line causes the issue:

  Code:

<Video targetContainer="applehttp" targetVCodec="h264" targetACodec="aac" forceStereo="true" forceVTranscoding="true">
   <Matches container="*" vCodec="h264" profile="high" levelGreaterThan="4.0"/>
</Video>

This line exists in the HTML5 profile in the application-profiles.xml file.

The thing is that removing this line only makes all videos work on High quality. If I try to reduce the quality then they wont work and I will receive the same error.

After commenting out the line above all my videos, movies and series seem to work including my drone videos. I tried this on Chrome, Edge and Firefox and they all work correctly.

[atc98092]

There has also been reports that clearing your browser cache resolves the issue.

[zip]

I'm not sure if the NAS is strong enough to transcode video in real time. What does the log say?

I'm not sure if the NAS is strong enough to transcode video in real time. What does the log say?

The NAS is the DS716+II which has hardware transcoding support (that serviio hopefully supports?) so it should be more than enough. The log doesnt say something conclusive, only that it tries to start the playback. I can perform some more testing or I can send you a video if you want for you to try it.

EDIT: It looks like that Serviio doesnt use the hardware transcoder and because of this the transcoding takes longer to initiate. After I receive the error, if I switch videos and then come back to the one which has already started transcoding then it works correctly since it has already buffered a bit. I have contacted patters in the hopes that he will give me some tips on how to implement the hardware transcoding on the DS716+II as well but now at least I know what the issue is. Can I somehow increase the timeout on the browser itself or is there a workaround for the time being? Thanks