Serviio

Can the below ffmpeg -i indicate what the reason is??

Windows 10.


ffmpeg -i <file name> produced this:

ffmpeg version N-76741-g8eadabf Copyright (c) 2000-2015 the FFmpeg developers
built with gcc 5.2.0 (GCC)
configuration: --enable-gpl --enable-version3 --disable-w32threads --enable-avisynth --enable-bzlib --enable-fontconfig --enable-frei0r --enable-gnutls --enable-iconv --enable-libass --enable-libbluray --enable-libbs2b --enable-libcaca --enable-libdcadec --enable-libfreetype --enable-libgme --enable-libgsm --enable-libilbc --enable-libmodplug --enable-libmp3lame --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libopenjpeg --enable-libopus --enable-librtmp --enable-libschroedinger --enable-libsoxr --enable-libspeex --enable-libtheora --enable-libtwolame --enable-libvidstab --enable-libvo-aacenc --enable-libvo-amrwbenc --enable-libvorbis --enable-libvpx --enable-libwavpack --enable-libwebp --enable-libx264 --enable-libx265 --enable-libxavs --enable-libxvid --enable-libzimg --enable-lzma --enable-decklink --enable-zlib
libavutil 55. 7.100 / 55. 7.100
libavcodec 57. 15.100 / 57. 15.100
libavformat 57. 16.100 / 57. 16.100
libavdevice 57. 0.100 / 57. 0.100
libavfilter 6. 15.100 / 6. 15.100
libswscale 4. 0.100 / 4. 0.100
libswresample 2. 0.101 / 2. 0.101
libpostproc 54. 0.100 / 54. 0.100
Input #0, matroska,webm, from 'File.mkv':
Metadata:
encoder : mkv2rls x264-tv version built on 2016.10.12
Duration: 00:57:22.96, start: 0.000000, bitrate: 2348 kb/s
Stream #0:0(eng): Video: h264 (High), yuv420p, 1280x720, SAR 1:1 DAR 16:9, 25 fps, 25 tbr, 1k tbn, 50 tbc (default)
Stream #0:1(eng): Audio: ac3, 48000 Hz, stereo, fltp, 192 kb/s (default)

H.264 video with Dolby Digital audio. Nothing I can see that would cause a problem. Does the file appear in Folder view?

No, it doesn't appear at all in any view.

I now think I understand what the problem was/is:

The mkv video file was inside a folder, and that folder plus FreeNAS network share + W10 somehow made anything inside that folder inaccessible.

Trying to look at "permissions", or whatever the tab is called in english, W10 states that no users or groups have any access whatsoever...

I'n not really up to speed on W10 + FreeNAS and SAMBA shares, it seems.

Yes, remote network share access can be tricky. Also remember that by default the Serviio service runs under the Local Service user account, which by nature has very few network permissions. Changing the user account Serviio uses to a specific user that has permission to access the network share is usually the easiest way to resolve these issues.

My serviio runs as a special serviio user, and that user has standard network access.

My example with the content of a container folder being inaccessible was for the serviio user and also myself and another admin user. Noone could access this folder.

When downloaded to a local folder on the serviio server machine, there was no access problem.