[DrJogalog]

Copied 6 files locally, all of gradual sizes from 0.5MB to 6MB. It seems that anything of about 4MB or above encounters this issue. The intermittant juddering when panning occurs on them all regardless of size. I have no issues playing movies including high bitrate 1080p movies and HVEC encoded content. I have tested the "multi slideshow screensaver" too, and although I cannot do a like for like test, it doesn't seem to show any differences in its output regardless of the filesize on all its screensaver options. Whatever the issue, it only seems be occuring on this screensaver currently. Memory and CPU are not an issue here either.

Now this is probably where support becomes limited. This issue is occurring on a MiniMX arm s905 device running a custom LibreElec install internally. I have not had any issues until this last update and it has always run flawlessly for my requirements (which is just playing videos from a local NAS and the picture screensaver). I'll check the logs for any clues although I am too sure what i'll be looking for. Thanks.

[ronie]

upload a Debug Log to some pastebin site and i'll have a look as well.

[DrJogalog]

Tested with debugging enabled and could see the screensaver taking a long time to read the larger fiiles (2 seconds+) from the NFS shares. So switched the screensaver to read locally and got the same, although slightly reduced timings. An extract from the log is below. The 1795 and 2085 are the files above 4MB. The 007 image is the 0.5MB one. So it looks like I have a speed issue reading picture files now which I assume wasn't there on previous versions. (I'll look at the ffmpeg line too to see if I can work out what means).

Full log with 9MB of spammed CEC errors at the end removed. http://pastebin.com/ZCAYYJEa

Code:

00:15:17.502 T:4033864608   DEBUG: DoWork - took 2074 ms to load /storage/pictures/IMG_2085.JPG
00:15:20.716 T:4033864608   DEBUG: DoWork - took 2244 ms to load /storage/pictures/IMG_1795.JPG
00:15:22.965 T:4033864608   DEBUG: ffmpeg[F06FE3A0]: [swscaler] No accelerated colorspace conversion found from yuv420p to bgra.
00:15:23.043 T:4033864608   DEBUG: DoWork - took 550 ms to load /storage/pictures/IMG_2998.JPG
00:15:26.696 T:4033864608   DEBUG: ffmpeg[F06FE3A0]: [swscaler] No accelerated colorspace conversion found from yuv422p to bgra.
00:15:26.720 T:4033864608   DEBUG: DoWork - took 179 ms to load /storage/pictures/CIG_IMG007.jpg
00:15:30.897 T:4033864608   DEBUG: ffmpeg[F06FE3A0]: [swscaler] No accelerated colorspace conversion found from yuv420p to bgra.
00:15:30.968 T:4033864608   DEBUG: DoWork - took 400 ms to load /storage/pictures/CIG_IMG004.jpg
00:15:34.978 T:4033864608   DEBUG: ffmpeg[F06FE3A0]: [swscaler] No accelerated colorspace conversion found from yuv420p to bgra.
00:15:35.048 T:4033864608   DEBUG: DoWork - took 429 ms to load /storage/pictures/IMG_3169.JPG
00:15:42.807 T:4033864608   DEBUG: ffmpeg[F06FE3A0]: [swscaler] No accelerated colorspace conversion found from yuv422p to bgra.
00:15:42.832 T:4033864608   DEBUG: DoWork - took 114 ms to load /storage/pictures/CIG_IMG007.jpg
00:15:48.841 T:4033864608   DEBUG: DoWork - took 2071 ms to load /storage/pictures/IMG_2085.JPG
00:15:51.184 T:4033864608   DEBUG: ffmpeg[F06FE3A0]: [swscaler] No accelerated colorspace conversion found from yuv420p to bgra.
00:15:51.262 T:4033864608   DEBUG: DoWork - took 473 ms to load /storage/pictures/IMG_2998.JPG
00:15:55.120 T:4033864608   DEBUG: ffmpeg[F06FE3A0]: [swscaler] No accelerated colorspace conversion found from yuv420p to bgra.
00:15:55.194 T:4033864608   DEBUG: DoWork - took 355 ms to load /storage/pictures/CIG_IMG004.jpg
00:16:00.975 T:4033864608   DEBUG: DoWork - took 2072 ms to load /storage/pictures/IMG_1795.JPG
00:16:03.241 T:4033864608   DEBUG: ffmpeg[F06FE3A0]: [swscaler] No accelerated colorspace conversion found from yuv420p to bgra.
00:16:03.322 T:4033864608   DEBUG: DoWork - took 403 ms to load /storage/pictures/IMG_3169.JPG
00:16:07.085 T:4033864608   DEBUG: ffmpeg[F06FE3A0]: [swscaler] No accelerated colorspace conversion found from yuv422p to bgra.
00:16:07.108 T:4033864608   DEBUG: DoWork - took 154 ms to load /storage/pictures/CIG_IMG007.jpg
00:16:12.957 T:4033864608   DEBUG: DoWork - took 1974 ms to load /storage/pictures/IMG_2085.JPG
00:16:15.355 T:4033864608   DEBUG: ffmpeg[F06FE3A0]: [swscaler] No accelerated colorspace conversion found from yuv420p to bgra.
00:16:15.434 T:4033864608   DEBUG: DoWork - took 432 ms to load /storage/pictures/IMG_2998.JPG

[DrJogalog]

When does the screensaver decide to load the next image? 0.5seconds before it needs to display it? I just increased the delay betwwen transitions from 4 seconds to 6 thinking it may give it time "to load", but it made no difference other than to keep the image on screen a little longer. The fade to black and "pop" of the next image is still apparent when the next image file is over 4 MB. If I am unable to find the cause of this issue, is their an internal setting I can change in an xml so the next image s "queued" earlier?

Thanks again for your help.

[ronie]

the timings are handled in the python code.

in case you want to test it, increase the preloading time to 3000ms here:
https://github.com/XBMC-Addons/screensav...ui.py#L156

and adjust the 'count' by subtracting 3 instead of 1:
https://github.com/XBMC-Addons/screensav...ui.py#L283

[DrJogalog]

Nice one. Thanks Ronie. I'll have a play with the PY script later.

[DrJogalog]

Thanks Ronie. The workaround did the trick. Unless I can find the cause of this delay, i'll have to make these changes on every update of the plugin. Thanks again.

[Ewoks]

Slideshow Screensaver


this screensaver can:

• show video fanart, music fanart or use a custom pictures folder
  
• enable slide, crossfade or pan/zoom transition effects
  
• optionally display picture filename, picture date as well as other picture info
  

...

Would be good if there are screenshots on the first post in this thread so we get a clue how it looks like, how settings looks like etc...

[ronie]

i'm not that talented ;-)
but if you could create some, i'll add them to the first post.

[GooseK]

I've been happily using PSS for years now - thanks for all the work, it's been really great. This is the first time I've hit a problem. Ever since I upgraded from Jarvis to Krypton 17.0 on Windows, it seems to not be resizing large images properly and causing a freeze. Relevant part of log:

21:59:09.864 T:6580 DEBUG: CImageLoader:oWork - took 220 ms to load T:\16x9 World\JP Morgan Library, New York.jpg
21:59:33.939 T:6580 DEBUG: CImageLoader:oWork - took 261 ms to load T:\16x9 World\Kalalau, Hawaii.jpg
21:59:46.146 T:6580 DEBUG: CImageLoader:oWork - took 452 ms to load T:\16x9 World\Paseo Explanada de Espana, Alicante, Spain.jpg
21:59:46.265 T:1372 ERROR: CD3DTexture::Create - failed to create texture.
21:59:46.265 T:1372 DEBUG: CDXTexture::CDXTexture: Error creating new texture for size 7952 x 4473.
21:59:46.265 T:1372 ERROR: CGUIFontTTFDX::CreateVertexBuffer - Failed to create vertex buffer.
21:59:46.266 T:1372 ERROR: Previous line repeats 1 times.
21:59:46.266 T:1372 ERROR: CRenderSystemDX::FinishCommandList - Failed to finish command queue.
21:59:46.267 T:1372 DEBUG: CRenderSystemDX:resentRenderImpl - device removed
21:59:46.269 T:1372 ERROR: DXGI_ERROR_DEVICE_REMOVED
21:59:46.270 T:1372 DEBUG: CWinSystemWin32::OnDisplayLost - notify display lost event
21:59:46.502 T:1372 DEBUG: HookOpenAdapter10_2: hook into pOpenData->pAdapterFuncs->pfnCreateDevice
21:59:46.505 T:1372 DEBUG: HookCreateDevice: hook into pCreateData->pDeviceFuncs->pfnCreateResource
21:59:46.506 T:1372 DEBUG: CRenderSystemDX::CreateDevice - on adapter Intel® HD Graphics 530 (VendorId: 0x8086 DeviceId: 0x1912) with feature level 0xb100.

... so it stops on the last image it successfully loaded and sits there. When I come back and try to activate Kodi again, it tries to reload the skin (Mimic) and crashes.

[ronie]

perhaps something related to image loading changed in kodi between v16 and v17.
i'm sorry, but i have no idea what any of those log messages mean.

[GooseK]

In case anyone else hits the same problem, batch resizing images to a maximum of 3840x2160 (4K) seems to be an effective workaround.

[scott967]

In case anyone else hits the same problem, batch resizing images to a maximum of 3840x2160 (4K) seems to be an effective workaround.

You might want to post to the windows support forum, as this seems like something the windows video devs should be aware of.

scott s.
.

[theraddest]

Hi!

I tested this addon on my rpi3 with a small, local folder of 20 jpg. The addon will only display certain images, not all. There seems to be no discernable difference in the images as far as drastic changes in filesize. None of the files appear to be corrupt. Any idea why this would be happening?

[Finchy]

Hi all

I love this screensaver addon on Kodi on our Shield TV as it lets it have all our photos randomly show when we're paused or not watching a TV show or movie, so many thanks to the developer for it.

A quick question though; occasionally I find photos are a little jerky when they move, and I'm wondering if it's when they are larger photos (between 3 and 4 and 8meg jpegs, most of them). Is there a best resolution for photos when using them with this screensaver? I can resize them all fairly easily - should I do it to the TV's max resolution? Or are they better left at a higher resolution and let the Shield TV just manage them?

Edit: Hmmm, looking back through the thread it seems a few people are having a similar issue on various devices. I'll have a go at resizing them to under 4meg when I get the chance, see if that improves things.