Why Samsung TV "loses" minidlna server
I will write a short post only because I myself suffered for a long time and looked for an answer to it, but in the end I had to figure it out myself.
We have:
- Samsung TV with the function of SMART TV and, accordingly, AllShare, which replaces DLNA support, as people say, because somewhere they have something that does not meet the specifications and therefore they could not call it DLNA. Well, God bless him, I decided not to understand these subtleties.
- home server on Linux, which downloads, stores and shows movies on TV through this very DLNA. The minidlna was chosen as the DLNA server by pointingthe sky in the Fedora repository.
Problem:
- we regularly encounter the fact that we want to watch this movie itself, turn on the TV ... and we don’t have our server in the SOURCE list or in the interface of AllShare itself. It's a shame. Especially when guests come and you tell them with enthusiasm you tell us how cool your new TV is showing, that you have your own server and on it we will now choose a high definition movie.
After restarting minidlna, the TV server finds it immediately. I could not find an answer to the question formulated in the title, or close in form. Also, I could not find anywhere in available information about how DLNA works at the network level (just don’t have to poke fingers into the full English-language specifications of the protocol, it’s also quite difficult to figure out, but I’m not going to write my own implementation). And only bydeep analysis of poking buttons and examining the output of tcpdump I understood how it works and what the problem is.
')
So:
minidlna server sits itself and listens to the port (which you set in the settings), and occasionally broadcasts what it is here. And the TV turns on and for some reason does not interrogate anything about whether there is anyone here. And it turns out that from the moment you turn on the TV until the moment when the minidlna server shows signs of life, the TV knows nothing, and what the “update” button does is a great mystery (at least for me). And it becomes a problem, as you usually turn on the TV in order to watch a movie.
Decision:
maybe there are more correct solutions, but I am stupid in the minidlna config (by default in the /etc/minidlna.conf file) I set the parameter
I think you can put less, but enough for me and so much for happiness. That is, the maximum waiting until the TV sees the server is 30 seconds. By default, this parameter in the Fedorov package is set to 900, that is, the wait time is up to 15 minutes.
We have:
- Samsung TV with the function of SMART TV and, accordingly, AllShare, which replaces DLNA support, as people say, because somewhere they have something that does not meet the specifications and therefore they could not call it DLNA. Well, God bless him, I decided not to understand these subtleties.
- home server on Linux, which downloads, stores and shows movies on TV through this very DLNA. The minidlna was chosen as the DLNA server by pointing
Problem:
- we regularly encounter the fact that we want to watch this movie itself, turn on the TV ... and we don’t have our server in the SOURCE list or in the interface of AllShare itself. It's a shame. Especially when guests come and you tell them with enthusiasm you tell us how cool your new TV is showing, that you have your own server and on it we will now choose a high definition movie.
After restarting minidlna, the TV server finds it immediately. I could not find an answer to the question formulated in the title, or close in form. Also, I could not find anywhere in available information about how DLNA works at the network level (just don’t have to poke fingers into the full English-language specifications of the protocol, it’s also quite difficult to figure out, but I’m not going to write my own implementation). And only by
')
So:
minidlna server sits itself and listens to the port (which you set in the settings), and occasionally broadcasts what it is here. And the TV turns on and for some reason does not interrogate anything about whether there is anyone here. And it turns out that from the moment you turn on the TV until the moment when the minidlna server shows signs of life, the TV knows nothing, and what the “update” button does is a great mystery (at least for me). And it becomes a problem, as you usually turn on the TV in order to watch a movie.
Decision:
maybe there are more correct solutions, but I am stupid in the minidlna config (by default in the /etc/minidlna.conf file) I set the parameter
notify_interval=30I think you can put less, but enough for me and so much for happiness. That is, the maximum waiting until the TV sees the server is 30 seconds. By default, this parameter in the Fedorov package is set to 900, that is, the wait time is up to 15 minutes.
Source: https://habr.com/ru/post/152763/
All Articles