![]() ![]() Dans la doc de ma TV il est bien indiqué que le format MKV est supporté, sauf qu’en réalité cela ne fonctionne que via le port USB, et pas par l’Ethernet. La TV détecte donc le contenu multimédia du NAS et lit les formats qu’elle supporte. The newer mkv files were upload by ftp, and so I thought the problem was caused by the mkv container. Un NAS multimédia est un serveur qui sera reconnu par les appareils à la norme DLNA comme par exemple une TV. Minidlna is not mapping permissions nor running as user nobody - so it was simply not able to read the files.īecause I uploaded the earlier files by samba, they had different permissions and minidlna could read them. So, accessing the files through samba worked fine, because samba maps the user to nobody and is therefore able to read the files. After ftp uploading (because samba gives me only 20 MB/s, while ftp is about 80-100 MB/s) I changed the owner by cli to nobody and thought this would be fine, but forgot about checking the read permissions - the files are marked for owner access only (700). Its owned by user nobody, and samba maps the guest account to this user. I uploaded my files by ftp in the public samba folder. So, thinking about the problem I got struck by the lightning of epiphany: Permissions! Since this files have been mostly avi ones, the problem has to be some more general and not only related to mkv. Yesterday after uploading some more files to my system the players did not see them though minidlna, too.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |