Voyager Air and Samsung Smart TV

[gnanet]

I hope it is accepted to join this thread, because it relates to the subject Voyager Air v1.2.7 & DLNA.

 

I will tomorrow test with some other ethernet-switch, but did anyone experiencd following:

 

Symptom:

Allshare play on Samsung Smart TV stops randomly with kind of device not available message, and some seconds later the Corsair pops up again as Allshare device.

 

Setup:

- LAN connected Samsung Smart TV UE32D5500

- On the same switch Corsair Voyager Air cmfair-red-1000-eu

- edimax router set-up as a simple switch

- TP-Link TL-WR1043ND with DD-WRT v24-sp2 (08/07/10) std - build 14896

for DHCP and NAT

 

Assumptions:

minidlna dies and restarts for some reason, or is over-sensitive to lan hiccups, what is not the case with Mediatomb on linux machine in the same lan (which was turned off while problem occured)

[gnanet]

I also found a small but really important note in the Release notes of 1.2.7:

In order to prevent corruption of the library database it is recommended that you turn off the Network Media Server, using this settings interface, before turning off the drive.

 

This is VERY important, because it seems that minidlna is blocking the system if its files are corrupted, so on next no WIFI or LAN access works, only USB

[alan sh]

I have found that the samsung implementation of dlna is not very good.It can freeze, drop the connection and not play certain videos whereas if I play the same source (my synology device) through my panasonic bluray player onto my tv, it all works ok.

 

Alan

[gnanet]

I have found that the samsung implementation of dlna is not very good.It can freeze, drop the connection and not play certain videos whereas if I play the same source (my synology device) through my panasonic bluray player onto my tv, it all works ok.

 

Alan

I dont question your findings, but based on my experience the already really old Mediatomb ( which i use on my Notebook and Mediaserver-PC ) has only issues if i try to stream over WIFI, but over cable it has no problems with my Samsung Smart TV, also unfortunately i had not much time to try minidlna on the same machine.

[gnanet]

found right now a clue in the forums of openmediavault:

http://forums.openmediavault.org/viewtopic.php?f=13&t=1703

 

maybe the disconnections from minidlna have to do with the setting "#network_interface=eth0" maybe also being not uncommented, and then minidlna gets confused between wlan and eth0 .

 

any thoughts on this?