Hey guys, I am a new owner of a Samsung LxxxD550 and have taken an interest in getting PMS (I am using official v1.50.0) and AllShare working properly together. I have added to the current .conf (v1.4.3). Once I've cleaned it up I'll post it here with a list of changes and reasons.
Currently, most supported formats are streaming well:
- mkv, divx, and vobs stream perfectly
- wmv sometimes has sync and stutter issues but skipping back and then fwd again fixes it
- Full DVD quality mpg's are viewable but suffer from an irritating stutter throughout.
- I've tested m2ts encoded with bitrates of 25Mbps and 12Mbps. Streaming 25Mbps is like watching a DVD on a 486... it doesn't work. 12Mbps streams well but stutters during "busy" scenes. On the plus side, DTS-HD streams perfectly and all embedded audio tracks are selectable during playback.
My gut says this TV doesn't have the processing ability to use the full 100Mbps Ethernet, hence the problem with m2ts (The conspiracist in me wants to blame samsung for locking the port via software to enhance wireless-n dongle sales
). Does anyone have a similar experience with wired streaming and is able to compare with the performance of the wireless-n dongle?
Edit: I've been investigating and my HDD is not working 100% which contributes to stuttering on the m2ts streams.
Transcoding with MEncoder is not useable:
1) Video playback crashes after some minutes. PMS then shows "current bitrate: 0 Mb/s" but the transcoding buffer continues to grow. Exiting and then returning to the film resumes playback but crashes again shortly after.
Edit: Transcoding crashes on my server when viewing via the PS3 aswell so it's not an AllShare problem. Now to find out what changed (it was working perfectly a week ago!)
2) Once initial buffering is done and the video is about to play, the bitrate briefly spikes to 780Mb/s. It can also spike randomly during playback.
3) Seek/jump functions do not work.
Which logs should I be looking at and how can I get them? Currently I only know about the Traces menu and dubug.log but can't see what the problem is from there.
The following, taken from the e-manual with reference to AllShare limitations, may be a clue to the root of the problems: "If the Index Table is in error, the Seek (Jump) function is not supported."
Any advice will be greatly appreciated!
I think this is the winning combination indeed. I've looked back in the thread for several logged hosts and they all have "SEC_HHP_" as connecting pattern.
The UserAgentAdditionalHeaderSearch worked in the past and it does not conflict with the UserAgentSearch, so it would be best if it stayed in to maintain backwards compatibility.
Agreed. My setup requires the modified agent search and is not affected by the UserAgentAdditionalHeaderSearch.
SubJunk wrote:Why is MaxVideoBitrate limited to 25Mbps? Wouldn't it be better to leave that line out, since people can set it for themselves in the program? 25Mbps would be way too low for me.
I have committed the new version to our SVN repository, too.
The e-manual for my set recommends a MaxVideoBitrate of 30Mbps for MPEG-1/2, 25Mbps for H264 and VC1, and 8Mbps for all other supported formats. I've also looked at format specifications for a few other Samsung AllShare devices and they're more or less the same. I guess its easier to set it here so that your other devices are not limited?