-
Notifications
You must be signed in to change notification settings - Fork 3
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
"quality" settings gives a hint that my photo will be reconverted? #14
Comments
This uses existing darktable export file formats / output options, the output and options are exactly the same as if you were to set the target storage to "file on disk", but only allowing what's supported on Wikimedia Commons. It works off the raw/input file and applies the processing pipeline, there is no quality loss inherent to this plugin. Darktable does not have an option to output a copy of a (JPEG) file without going through its processing pipeline. |
My jpg was 2.1 mb, on Commons I found that it size if 2.6 mb - so it was reencoded :( This is bad, I cannot use such great plugin because of this :( Should I create a ticket about this in Darktable itself? |
The issue you are describing is more relevant to darktable, yes. I don't understand what is your use-case. Any image you open through darktable will go through its processing pipeline. Are you using darktable to develop your (ideally RAW) images? If yes then you will get exactly the same image out whether you chose "file on disk" or "Wikimedia Commons" on the darktable target storage. Otherwise, if you have JPEG images that you want to upload without doing any processing then there are other tools that do just that. If you developed an image in darktable and saved it to disk (so that you have both the (ideally RAW) original image and the JPEG output), then make sure you are still working off the original RAW image rather than the already processed JPEG image (or darktable will process it again with whatever is in your default pipeline). |
Allowing ext=="" in |
Done in b21c2f2 . I had to add an additional extension check because register_storage_supported is no longer sufficient to check if a file format is supported. |
Updated the plugin, now I see the
|
I made a crash causing typo, sorry. It's fixed in b68b1e2 |
Related on that - looks like avif is supported by MediaWiki - would you like to add that too? |
|
It's not yet supported on Wikimedia Commons per https://phabricator.wikimedia.org/T257719 |
What type of file are you trying to upload? |
xxx.JPG |
I added case insensitivity in 3c4738a |
Updated, tried again:
|
I added a fix in cc7f446 , I don't know if it will work with copy but at least the error message will be slightly more useful. |
|
I don't know why uploading image copies yields no extension. I normally get something like
image.path has the original file's extension so it could be taken from there in make_image_name and _register_storage_store_final_format_check if the temporary file's is empty. |
Hi, no insights about how to solve this? |
Yes, the solution is
I don't have time to work on it at the moment (PRs welcome) |
Thanks, I tried - but I found that |
That's unfortunate. Thanks for trying. If we have no way to check that the copied file format is compatible then I guess the next best thing is to make copy an activable flag in the settings with a warning in the tooltip. |
register_storage_store() receives
In logs I see
Why? Is it possible to print error details? |
But I want to upload the original quality.
The text was updated successfully, but these errors were encountered: