the fade-in is jerky

[botswanabub]

on a rpi4 (4gb, usb3 device) I have the problem that the fade-in / changes of the fotos is very jerky. Is it a config problem, size problem (4k res.) or an module issue? Can't find anything about but found an high activity on htop while changing the foto.

[KristjanESPERANTO]

Shot into the blue: Please try export ELECTRON_ENABLE_GPU=1 && npm run start instead of npm run start to start the mirror.

[botswanabub]

hi, thanks for your relay, I read something about before and add this line without success.

my script started by pm2

echo 'on 0.0.0.0' | cec-client -s -d 1 cd ./MagicMirror export ELECTRON_DISABLE_GPU=1 DISPLAY=:0 npm start

[KristjanESPERANTO]

ELECTRON_DISABLE_GPU is not in the current code base of MagicMirror. Have you checked ELECTRON_ENABLE_GPU?

[botswanabub]

omg ... you are right, classic copy&paste mistake. I changed, now it's more fluently/better but still jerky.

[botswanabub]

update: pi5 - 4gb - usb3, same "problem". still a bit jerky.

[KristjanESPERANTO]

Can you try lowering the resolution as a test?

[botswanabub]

hi, yes reduced to fullhd and for me seems to be the same, perhaps a bit better again. could that be a file size issue, I had not tried yet with other pics but the current are about 1-3mb as they a not special prepared.

[KristjanESPERANTO]

The file size is a good approach we can follow :+1: Can you create smaller versions of the problematic image and test them?

If the file size turns out to be the cause of the problem, maybe we can somehow build in a process that makes the images smaller at startup or something.

[botswanabub]

once I redueced the file size to 200k - 1,5M ... should not be a problem right now. may be a render problem?

[botswanabub]

update: meanwhile, because the other broke, I changed to a pi5 8gig NVME and the MM into a docker container. once again a bit better ... not that logical