Given the title of this thread, I figured it was best to put these two comments in here, so others with the same problems or struggles might easily find them.
1. First off, it has been a long time since the Fmp-X5 had a firmware update from Sony and so the 4K Amazon prime feature never arrived on the devices as announced. But more importantly the netflix app on this (£400 dedicated netflix) device seems to be failing behind, and now regularly crashes out to the front-end (netflix/mediaplayer screen) when switching from watching one show to another in the list.
The problem seems to occur when the netflix app has stale information (in its advert thumbnail/s), as when we re-access netflix, the advert section has been updated. (doing the update internet content from the network menu doesn't fix this; nor did a reset of the device or switching fibre broadband providers virgin/BT)
So the question is: When are Sony going to update the firmware to make the netflix app as current as the Ps4 app to stop it from crashing on a daily basis?
2. The second issue is, that after using handbrake to try and encode h.265 content to use with the device via usb stick, it would seem the online manual for the device - accessed through the menus - is woefully documented for letting people use their own HEVC/h.265 files with the Fmp-X5.
The major problem is, that the manual makes no mention of needing to use MKV containers for the h.265/HEVC video files - as opposed to MP4 containers – and yet, these mkv files are invisible to the device's filesystem, unless the user overrides their file extension to mp4. So in conjunction with the need for a more current netflix app, the FMP-X5 really needs a firmware update to allow the default MKV file extensions to be used for HEVC files in the filesystem.
At the same time, it would make sense to add detail to online manual file specification requirements. So that users would know that they want to be encoding using an MKV container, using the h.265/HEVC Main10 (8/10bit colour 4:2:0) or Main (8bit colour 4:2:0) profile.
The file below is a great example of how the device's filesystem can't play a perfectly valid refernece encodied h.265 file, because the file correctly uses the mkv file extension, but the device wants it changed to MP4 – despite the file not being a MP4 container or not containing mp4/h.264 encoded content
http://www.libde265.org/hevc-bitstreams/bbb-3840x2160-cfg02.mkv
