Ghent wrote:Hi Frank123,
I found the problem: I activated the switch in MEncoder to use TSMuxer if the source file is PS3 H.264 compatible. Now I am only dealing with the "stuttering" issue. This makes me wonder because my NetTV can handle H.264 via DLNA by native and I do not no what is causing such a high CPU load then? - Additionally my TV restarts every tie when I stop the playback of HD material via DLNA.
I will try to open a case for this at Philips. Let's see what they are saying.
Thanks for your help and your explanation,
Ghent
when you raise the case with them point them to this thread and we might see some of their inhouse techs/coders feeding back info and perhaps even code to the PS3MS codebase and other devs here, its all good and helps make it more popular as it play on more devices, as we make all the device OEMs aware that PS3MS exists and works with their kit.... and we get their help lines and PR budgets to mention PS3MS as their prefered and cross-platform DLNA server.
Now, i just think its good to clarify:
when people say and refer to "Native playback " that means the playback device, your DLNA capable TV in this case, CAN play a given video without any extra processing..
there are several parts to this to work internally, the given device needs the video codec, the Audio codec AND the Container spitter the the streaming video your trying to stream and play..... so.
a HDTV AVC(video codec)/AAC(Audio codec)/MKV *container)file may Not play on your given device.... and so needs transcoding or changing from the PS3MS side into another container the device can play natively.
however this very same file may play perfectly fine on your device If you just place the unchanged AVC/AAC into an .MP4 container (with for instance avidemux), without any transcoding, re-encoding or other processing on the PS3MS side then needed.
less file processing , less PS3ms PC CPU strain, if theres NO processing involved as the player device can play the Audio/Video/Container natively then your PCs CPU need only push the file onto the (wireless)ethernet wire and be done, and so not need a fast CPU or lots of realtime PC processing....
the fact your seeing High PC PS3MS CPU usage clearly says the PS3MS app is re-processing your streaming video into something else.
the very first thing to know is what are these native codecs and spltter/container your device can play, the second is check your files are matching these codecs/container with something like 'mediainfo'
http://mediainfo.sourceforge.net/enthe third is dont even try to transcode/re-encode these native files on the fly from inside PS3MS, thats a .conf setting, true its not very clear by the options names we see today what you should do, id really like to see a simplyfication and generic clarification of these options, such as adding a
"ThisdeviceWillPlayNativeContainers=avi,wmv,mkv,wmv,ts,m2ts,tp,iso,mp4,mov"
"ThisDeviceWillPlayNativeVideoCodecs=AVC,Mpeg4-part2,xvid,mpeg2"
"ThisDeviceWillPlayNativeAudioCodecs=AAC,mp3,ac3,dts"
"ThisDeviceWillPlayNativeOtherData="PIP,subtitles 1 and 2, whatever"
"If NON of the above, then transcode to=AVC/AAC/MP4"
plus your other pics and data noone really cares about but PR like to add OC...
so to recap, generally speaking for any current or new device, does your device play the files your trying to play natively have these codecs and container onboard, and if so, why is PS3ms transcoding or re-encoding them for no good reason, check your settings to tell it your device can play them as is.... if you have a device thats capable of playing the given file natively then PS3MS should Never be taking up CPU time or effort to re-convert these files and only pushing these onto the wire forthe dvice to play as is. a high CPU use indicates it is converting the file, be sure of yourself it needs.