Replies: 1 comment
-
Strangely I figured that the max resolution is always half the source. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
I'm not sure if I have a bug or if it's just a missuse so I put my issue in the question.
I use the latest version of the medialibrary (9.4.2)
My issue is that when I generate responsive images the generated images are half the resolution it should be.
For example, if I use this https://helpx.adobe.com/content/dam/help/en/photoshop/using/convert-color-image-black-white/jcr_content/main-pars/before_and_after/image-before/Landscape-Color.jpg which is 1601 x 664px
They result in these images

I register the MediaConversions in the model like this
As I use this package in Nova I tried both current nova fields with the least option possible as the setup is done in the model to avoid interfering
They both give the same result. What is strange is the I can see the higher resolution being created but they are deleted right after.
To try to debug this I also tried to manually add the image via url with this command
The main difference with the nova packages is that I still have the higher resolution images left. They are not deleted after being added.
But for both, when I display the html it's limited to a lower resolution.
I can see in both case (with and without a nova package) that the responsive_images field in the database is the same with the higher resolution being 770 x 485px.
Here is how I output the html in blade just in case
This is the html output
Does anyone have an idea of what's going on ?
Am I missing something or should I try something ?
Beta Was this translation helpful? Give feedback.
All reactions