Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Difference between Inky Frame and Inky Impression in displayed image #208

Open
Sennevds opened this issue Dec 27, 2024 · 0 comments
Open

Comments

@Sennevds
Copy link

I have both the inky impression and frame.
Both use the same (already cropped and dithered image) and get these from a dotnet core api (same endpoint)
The endpoint returns a filestream result with the contentType. This is then locally saved and shown on the display.

With the inky frame (pi pico) nothing is done with the result because it's already dithered but on the inky impression this jpg/png is always converted (because the image loads as RGB mode) which results in a image with reduced colors.
Is there a possibility to not convert in image and just load it as is?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant