no QOI thumbnail displayed (SuperSlicer 2.5.59)

marvineer

Hi folks,

I noticed that none of my own qoi thumbnails show up on PanelDue.
I use SuperSlicer Version 2.5.59

In DWC, the thumbnails are displayed correctly (both sizes). So I suspect a problem in the PanelDue firmware or a bug in SuperSlicer/PrusaSlicer.

As a reference those are the files i tested it with:
qoi_48x48_512x512_failed.gcode (generated by SuperSlicer 2.5.59 - this does not show up on my PanelDue)
qoi_128x128_1024x1024_failed.gcode (generated by SuperSlicer 2.5.59 - this does not show up on my PanelDue)
qoi_works.gcode (this works on my PanelDue)

My System:
Duet 6HC with SBC (Version 3.4.5)
PanelDue 5i (Version 3.4.1-5.0i) with custom logo
DWC (Version 3.4.5)

I tried it with the standard binaries without a logo as well and I even tried this, but there was no change in behavior for me.

Does anybody have the same problem or even a possible solution?

Thanks!

Phaedrux

Did you upload blank.bin?

@marvineer said in no QOI thumbnail displayed (SuperSlicer 2.5.59):

I tried it with the standard binaries without a logo as well and I even tried this, but there was no change in behavior for me.

marvineer

@Phaedrux said in no QOI thumbnail displayed (SuperSlicer 2.5.59):

Did you upload blank.bin?

I firstly uploaded blank.bin via DWC, after that the standard PanelDueFirmware-3.4.1-5.0i.bin - same behaviour

marvineer

I investigated this a bit further (even installed cura to test images from another source, but it was the same behavior):

i tried the following files:

qoi-test_512x512_and_160x160.gcode : did not show a thumbnail on PanelDue
qoi-test_160x160.gcode : this apparently worked and the thumbnail loaded on PanelDue!

So it seems like as soon as a second thumbnail greater than the maximum (160 x 160 pixels) is in the file, PanelDue won't show any thumbnail at all.

To test this theory I tried the following files:

qoi-test_128x128.gcode : this works
qoi-test_161x161.gcode : as expected, this doesn't work (greater than the maximum size PanelDue allows)
qoi-test_160x160_and_512x512.gcode : this does not show a thumbnail on PanelDue
qoi-test_128x128_and_160x160.gcode : this works

So I am fairly comfortable to say, that PanelDue skips a thumbnail while it shouldn't.

droftarts

@marvineer To be fair, in the release notes, it does say

Add support for QOI thumbnails in gcode files (supports one QOI image with max size 160x160)

https://github.com/Duet3D/PanelDueFirmware/releases/tag/3.4.1

I've set up my slicers to produce a single QOI image of 160x160 pixels, and that's been working well. However, I've marked this as a bug, because as you point out, it does work so long as both QOI images are under 160x160. Most likely it skips the QOI section entirely as soon as it sees a bigger image than 160x160, no matter if it's first or second in the file, due to memory limitations on the PanelDue when parsing the gcode file. But I'll ask someone to look at it.

Ian

Exerqtor

I'll also jump on this and report that the thumbnails suddenly ain't working on my Paneldue either.

They have worked ever since it became a feature, I'm outputting both 64x64 & 400x400 from the Slicer (PrusaSlicer 2.6.0-a6 in my case).

dc42

@Exerqtor @marvineer I have found a cause of this issue and fixed it in the 3.5beta source code.

Exerqtor

@dc42 said in no QOI thumbnail displayed (SuperSlicer 2.5.59):

@Exerqtor @marvineer I have found a cause of this issue and fixed it in the 3.5beta source code.

Goodie, so were close too a 3.5b3 soon btw?

dc42

@Exerqtor said in no QOI thumbnail displayed (SuperSlicer 2.5.59):

Goodie, so were close too a 3.5b3 soon btw?

I'm aiming for later this week.

mfs12

https://github.com/Duet3D/PanelDueFirmware/issues/283

mfs12 created this issue in Duet3D/PanelDueFirmware

closed Fix qoi thumbnail selection #283

Exerqtor

@mfs12
I regret to say this issue still exist (for me at least) in RRF 3.5b3 ‍

EDIT:
Turns out it works if you have the larger of two resolutions first (confirmed with 400x400, 64x64 & 400x400, 160x160).

dc42

@Exerqtor please post a link to your file. My guess is that RRF is still not scanning enough of the start of the file to find all the images. Is there a reason that you need all 4 of them?

Exerqtor

@dc42
I've got it working now when i put the large res first in PrusaSlicer ( i had it the other way around first when it didn't work 64x64, 400x400).

Oh no i'm only using two images(400x400, 160x160). i just tried out 400x400, 64x64 for the sake of testing.