Slow down of Hyperion.ng

I’ve disabled add-ons autoupdate and made full-reinstall of Hyperion.

1 Like

So, two hours later got slowdowns again with regular content (not IPTV). Pity :frowning:

actually I noticed when i play old avi files the the backlight works which i think is really strange - with newer and high resolution video files nothing happens.

I’m not sure, but I read somewhere, that disabeling hardware acceleration for video playback could fix that. But you could try, if it makes a difference^^

yesterday i got your new (test) version of hyperion.ng working.
you need to uninstall the addon (including config!) and build a new config via web-config-page.
now slowdowns are really not as often as before anymore! and the slowdown itself is shorter.
that means it just halt a moment and then playback continues. so the slowdown of about 10sec is waaay shorter and i love it.
@Portisch: thank you very much! it seems you are at the right track!

thx, but the problem isn’t yet fixed!
I have done a lot of logging - but the “error” isn’t included.

This shows the issue: The “normal” ttd (TimeToDisplay) is ~ 180ms. Then when the slow downs happen it goes down to -10000. The the reset will happen.

	Line 8298: 2019-03-09 22:08:19.574 T:3347014448   DEBUG: CVideoPlayerVideo::OutputPicture - ttd:180ms pts:4148.167 Clock:4147.986 Level:0 elapsed:0.005ms
	Line 8327: 2019-03-09 22:08:19.622 T:3347014448   DEBUG: CVideoPlayerVideo::OutputPicture - ttd:173ms pts:4148.208 Clock:4148.035 Level:0 elapsed:0.007ms
	Line 8340: 2019-03-09 22:08:19.661 T:3347014448   DEBUG: CVideoPlayerVideo::OutputPicture - ttd:176ms pts:4148.250 Clock:4148.074 Level:0 elapsed:0.006ms
	Line 8369: 2019-03-09 22:08:19.701 T:3347014448   DEBUG: CVideoPlayerVideo::OutputPicture - ttd:178ms pts:4148.292 Clock:4148.113 Level:0 elapsed:0.006ms
	Line 8372: 2019-03-09 22:08:19.702 T:3347014448   DEBUG: CVideoPlayerVideo::OutputPicture - ttd:218ms pts:4148.333 Clock:4148.115 Level:1 elapsed:0.003ms
	Line 8417: 2019-03-09 22:08:19.826 T:3347014448   DEBUG: CVideoPlayerVideo::OutputPicture - ttd:136ms pts:4148.375 Clock:4148.238 Level:0 elapsed:0.006ms
	Line 8449: 2019-03-09 22:08:19.865 T:3347014448   DEBUG: CVideoPlayerVideo::OutputPicture - ttd:139ms pts:4148.417 Clock:4148.277 Level:0 elapsed:0.004ms
	Line 8476: 2019-03-09 22:08:19.951 T:3347014448   DEBUG: CVideoPlayerVideo::OutputPicture - ttd:95ms pts:4148.458 Clock:4148.363 Level:0 elapsed:0.006ms
	Line 8502: 2019-03-09 22:08:19.990 T:3347014448   DEBUG: CVideoPlayerVideo::OutputPicture - ttd:97ms pts:4148.500 Clock:4148.402 Level:0 elapsed:0.005ms
	Line 8532: 2019-03-09 22:08:20.075 T:3347014448   DEBUG: CVideoPlayerVideo::OutputPicture - ttd:53ms pts:4148.542 Clock:4148.488 Level:0 elapsed:0.006ms
	Line 8538: 2019-03-09 22:08:20.114 T:3347014448   DEBUG: CVideoPlayerVideo::OutputPicture - ttd:56ms pts:4148.583 Clock:4148.527 Level:1 elapsed:0.005ms
	Line 8566: 2019-03-09 22:08:20.199 T:3347014448   DEBUG: CVideoPlayerVideo::OutputPicture - ttd:13ms pts:4148.625 Clock:4148.612 Level:0 elapsed:0.006ms
	Line 8665: 2019-03-09 22:08:20.249 T:3347014448   DEBUG: CVideoPlayerVideo::OutputPicture - ttd:4ms pts:4148.667 Clock:4148.662 Level:0 elapsed:0.006ms
	Line 8677: 2019-03-09 22:08:20.325 T:3347014448   DEBUG: CVideoPlayerVideo::OutputPicture - ttd:-29ms pts:4148.708 Clock:4148.737 Level:0 elapsed:0.005ms
	Line 8698: 2019-03-09 22:08:20.373 T:3347014448   DEBUG: CVideoPlayerVideo::OutputPicture - ttd:-35ms pts:4148.750 Clock:4148.785 Level:0 elapsed:0.006ms
	Line 8730: 2019-03-09 22:08:20.449 T:3347014448   DEBUG: CVideoPlayerVideo::OutputPicture - ttd:-69ms pts:4148.792 Clock:4148.861 Level:0 elapsed:0.005ms
	Line 8745: 2019-03-09 22:08:20.497 T:3347014448   DEBUG: CVideoPlayerVideo::OutputPicture - ttd:-75ms pts:4148.833 Clock:4148.909 Level:0 elapsed:0.006ms
	Line 8770: 2019-03-09 22:08:20.573 T:3347014448   DEBUG: CVideoPlayerVideo::OutputPicture - ttd:-110ms pts:4148.875 Clock:4148.985 Level:0 elapsed:0.004ms
	Line 8800: 2019-03-09 22:08:20.621 T:3347014448   DEBUG: CVideoPlayerVideo::OutputPicture - ttd:-116ms pts:4148.917 Clock:4149.033 Level:0 elapsed:0.005ms
	Line 8830: 2019-03-09 22:08:20.706 T:3347014448   DEBUG: CVideoPlayerVideo::OutputPicture - ttd:-160ms pts:4148.958 Clock:4149.119 Level:0 elapsed:0.006ms
	Line 8842: 2019-03-09 22:08:20.745 T:3347014448   DEBUG: CVideoPlayerVideo::OutputPicture - ttd:-157ms pts:4149.000 Clock:4149.158 Level:0 elapsed:0.006ms
	Line 8874: 2019-03-09 22:08:20.831 T:3347014448   DEBUG: CVideoPlayerVideo::OutputPicture - ttd:-202ms pts:4149.042 Clock:4149.244 Level:0 elapsed:0.005ms

Normally one frame takes ~41ms for 24 frames per second.
You can see when the slow down happens each second frame take double of the time:

22:08:19.622
22:08:19.661  39ms
22:08:19.701  40ms

22:08:20.497
22:08:20.573  76ms
22:08:20.621  48ms
22:08:20.706  85ms
22:08:20.745  39ms

But the “why” can not be found in the log, not in kernel or kodi log.

2 Likes

Please keep digging, you are the only hope :sunny:

May I found the sync issue!
It is running now for 4h on my “simulation/testing” system without any slowdown. :crossed_fingers:
I just created a playlist with repeat all of a local movie. And it is running and running and running…

You will need the new devel image CoreELEC-Amlogic.arm-9.0-devel-1552547772 (based on 9.0.1).
Please remove the testing addon 9.0.1.100.2. This can be deleted!
There is a new hyperion.ng 9.0.1.100.1 addon zip in the folder.
This new zip is only including a little fixup and it isn’t needed for testing. It would just be nice if somebody can confirm it’s working “normally”. The slowdown should also be fixed with the actual addon from the repo.

Edit: I added a 4k testversion: CoreELEC-Amlogic.arm-9.0-devel-1552566980-4k.tar
Maybe someone can test this with the amvideocap0 grabber option and a 4k TV…

Edit2: The first tests on the real system shows strange behaviour. I think there is still something wrong…

3 Likes

“Edit2: The first tests on the real system shows strange behaviour. I think there is still something wrong…”

What behaviour? I want to test, but so it make no sense for me.

I am going to test your built this evening with live tv (no 4k).
I need to update to your image via tar update and install normal addon from repo, right?

Yep, please also test the addon zip I uploaded.

The addon zip causes freeze on start of stream (720p).
With the addon from repo…test is ongoing.:crossed_fingers:

edit: freeze after about 30minutes. after reboot freeze on start of stream…wtf?
i think i need to go back to previous dev built for tonight -.-

Same here, modified add-on causes system failure almost immediately after a play is started. Original add-on testing in progress :slight_smile:

Edit: Unfortunately, the system also hangs pretty soon with the original add-on.

The test version freezes the system with the modified addon and with the repository one.

Currently I am on official 9.0.1 with hyperion disabled :cry:

I uploaded today a new image. This should work now! Please test if the hyperion slow downs are gone. Please use the hyperion addon from the repo and amvideocap0 as grabber.

[S905/S912 Image]

3 Likes

Thanks for trying, really :slight_smile: But, system still hangs after ~30 min :cry:

Really? It’s running here on my S912 now for more than 5h without any slow down. What CPU you using? grabber? Frequency? Hyperion.conf? What SD card is used where CE is running?
When a lot of operations are happen or a old SD card is used it can lead to frame skipps and problems. I use a class 10 SD card.

Not a slowdown, system hang. Mecool K1 Pro (S905D), grabber amvideocap0 with all by-default settings (10 FPS), conf-file created from scratch, CE internally installed. System hangs exact same way as with previous test version (with sound looping).

You know “CE internally installed” isn’t supported officially? I never get a complete system hang.
The version before was crap - just compare it to the release 9.0.1. Before starting a video open a ssh connection or better UART connection and enter this: journalctl -f -o short-precise -k or this if using uart: echo 8 > /proc/sys/kernel/printk
This will print out dmesg “live” to the console so I if it hangs maybe the last lines give info about it.

Of course :slight_smile: But this is an only possible option for me, and i never had any similar issues with it on 4 my heavy-using devices. I got a total system hang only with this test builds. I will try to collect dmesg output while hanging, thanks for the idea :slight_smile:

Just a guess: do you use the dirtyregions parameter with your S912? I don’t need it for mine S905 (there is no reason), could it be a reason for (in)stability in some manner?