darktable-org / darktable-org/darktable
jp2 files and faststone
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 13.1k
- Forks
- 1.4k
- Avg merge
- 22h 14m
- Merged PRs (30d)
- 198
Description
Is there an existing issue for this?
- I checked and did not find my issue in the already reported ones
Describe the bug
When I export a file as JP2000 JP2 file, faststone seems to read it but the picture is far too bright. I have no possibility to find if it is a problem from darktable or from faststone
Steps to reproduce
open a ARW file (in my case)
do processing
save as JP2 file
open this file in faststone
Expected behavior
export correctly
Logfile | Screenshot | Screencast
No response
Commit
No response
Where did you obtain darktable from?
darktable.org / GitHub release
darktable version
5.0.0
What OS are you using?
Windows
What is the version of your OS?
Windows 11
Describe your system
No response
Are you using OpenCL GPU in darktable?
I dont know
If yes, what is the GPU card and driver?
No response
Please provide additional context if applicable. You can attach files too, but might need to rename to .txt or .zip
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No source file, test, log, or sample file is identified in the issue. Start by reproducing the ARW-to-JP2 export on Windows 11 and comparing the result in FastStone; done means determining whether darktable's JP2 export causes the brightness difference and adding a focused regression test or documented diagnosis.
Written by the indexing model from the issue text.
Assessment
- Domain
- computer-graphics
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100