You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm having some issue when running JPG decoding from SPIFFS,
The same sketch running from SD card runs perfectly.
The same JPG image is on SD card and on spiffs.
What i'm seeing when calling jpegInfo() is that values are shifted down:
Width 0
Height 160
Components 128
and so on...
Picture is 160x128.
This is only happening when running sketch from SPIFFS.
The image is uploaded to SPIFFS via Arduino ESP8266 Sketch Data Upload tool.
I uploaded JPG image for reference.
Best Regards,
Nikola
The text was updated successfully, but these errors were encountered:
This is not something I have encountered. I suspect this is a bug in the SPIFFS code that is part of the ESP8266 board package core. See here. In which case this should be fixed when version 2.4.0 of the Arduino core is released.
OK, update: I have witnessed a similar problem where the values returned by jpegInfo() are wrong. This appears to be due to a corrupted pointer that affects the values read out of a struct that contains the values. One of the values (Components) is a hard coded value of 1 and this seems to end up being reported as a different value.
I think this might be a bug in the ESP8266 core but have not been able to isolate the root cause.
Hi all,
Great library! you made a great job!
I'm having some issue when running JPG decoding from SPIFFS,
The same sketch running from SD card runs perfectly.
The same JPG image is on SD card and on spiffs.
What i'm seeing when calling jpegInfo() is that values are shifted down:
Width 0
Height 160
Components 128
and so on...
Picture is 160x128.
This is only happening when running sketch from SPIFFS.
The image is uploaded to SPIFFS via Arduino ESP8266 Sketch Data Upload tool.
I uploaded JPG image for reference.
Best Regards,
Nikola
The text was updated successfully, but these errors were encountered: