2014-10-12, 17:55
(2014-10-09, 20:38)menakite Wrote: @popcornmix I'm experiencing a strange issue with your latest newclock4 updates, on XBian.Tried to investigate it further. It seems I only get this with 25 fps videos.
I have a build from 20141004 that is working fine (unfortunately I don't have a backup of the newclock4 patch file). Yesterday I have updated to latest master and latest newclock4, I've also updated the firmware.
From time to time I randomly get a blank screen and no audio when using passthrough. I have tried to:
* disable GPU accelerated resampling (set to High) - this, and the firmware, seem to be the only changes since 20141004;
* disable Adjust PLL (set to any other value), just to be sure;
* both.
A debug log doesn't show anything relevant and anyways no ERROR lines.
When this happens, CEC is still working (indeed I can stop the video, and the GUI is then shown).
If I disable passthrough the issue magically disappears. So far I have only tested with AC3 (2.0, 5.1) videos. My TV also supports DTS so I'll test later.
I know this is usually related to the power supply, but I've measured it a few months ago, and I'm not sure why disabling passthrough would fix it if that's the case.
I'd like to try the older firmware and I'm wondering if it'd be safe to do so (I'll make sure to disable GPU resampling), or it would explode.
Edit: if it's relevant, all acceleration settings are enabled, so I'm using OMXPlayer.
The video still continues even if I don't see anything. *Some times* it recovers itself after a few seconds (rarely minutes), otherwise I have to stop the playback, resume from there and rewind.
I've noticed 25 fps videos were played at 50, so I have tried adding this to advancedsettings.xml:
Code:
<video>
<adjustrefreshrate>
<override>
<fpsmin>24.99</fpsmin>
<fpsmax>25.01</fpsmax>
<refresh>25</refresh>
</override>
</adjustrefreshrate>
</video>
I *think* (as I said, it's random, so I'm not sure...) the issue is more rare now, but I still get this.
As a test I have also tried config_hdmi_boost up to 7, but it didn't change anything.
Any suggestion on how to further debug this? (As I already said, a debug log when this happens is not different from a debug log when it doesn't.)