2015-02-03, 21:16
If we want to discuss that on a technical level,
Then here are all the facts, users should know:
- You surely know the the cubox won't do 23.976 hz and therefore cannot sync to the video clock needed most bluray rips are shipped. Therefore dts-hd, truehd will drop and dupe every now and then. Users have to switch to LPCM. 24.0 fps playback should work
- You should also know that Live TV (1080i50) was a really, really hard task and we are only approximately there, where the PI currently is with _stable_ software. None of this code has been pushed, things like RenderCapture are still missing and the two hard working devs are not overall happy, yet.
- Concerning the throughput, when I measure the ddr3 max bandwidth and compare it to a video I think, if everything goes well you will be able to play 1080p ~ 44 (44 progressive frames decoded and displayed)
- The Pi (2) has two years of advantage in kodi / xbmc adjustment and optimization
I really hope, that you can finde a workaround for this.
Then here are all the facts, users should know:
- You surely know the the cubox won't do 23.976 hz and therefore cannot sync to the video clock needed most bluray rips are shipped. Therefore dts-hd, truehd will drop and dupe every now and then. Users have to switch to LPCM. 24.0 fps playback should work
- You should also know that Live TV (1080i50) was a really, really hard task and we are only approximately there, where the PI currently is with _stable_ software. None of this code has been pushed, things like RenderCapture are still missing and the two hard working devs are not overall happy, yet.
- Concerning the throughput, when I measure the ddr3 max bandwidth and compare it to a video I think, if everything goes well you will be able to play 1080p ~ 44 (44 progressive frames decoded and displayed)
- The Pi (2) has two years of advantage in kodi / xbmc adjustment and optimization
Quote:"All other TMDS clocks are not supported; the TMDS clocks divided or multiplied by 1,001 coefficients are not supported." §33.2.6.1
I really hope, that you can finde a workaround for this.