Skip to content

fix(raw): remove the RAW Decode panel; one fixed decode that never sh… - #2

Merged
Redrum624 merged 1 commit into
mainfrom
claude/youthful-hamilton-s04iwn
Oct 10, 2026
Merged

Redrum624 merged 1 commit into
mainfrom
claude/youthful-hamilton-s04iwn

Conversation

@Redrum624

@Redrum624 Redrum624 commented Oct 10, 2026 •

Copy link
Copy Markdown
Owner

…ows a dark base

Reported: a PEN-F ORF opened dark and grey. Decoding the file with both LibRaw engines and the app's exact flags gives a correct image, so the bad state came from the decode-settings machinery on the user's build.

  • RAW Decode panel, remembered decode defaults and the Settings RAW section removed. Every RAW opens with DCB + blended highlights + camera match; options older builds persisted per photo are ignored, so single and batch exports always match the editor.
  • Highlight recovery (post-decode) moved under Basic Adjustments for RAW photos, on the shared SliderRow.
  • A failed camera match no longer leaves the -W (un-brightened) base on screen: the native rung re-decodes with auto-brighten, the result is flagged cameraMatched:false and never written to the disk cache. Verified on the ORF: matched 0.319 mean, forced failure 0.401 instead of the dark base.
  • cameraMatchWorker.cjs is asarUnpacked and loaded from app.asar.unpacked in packaged builds; base cache key bumped (cm2) so bases cached by earlier builds miss once.

What does this PR do?

Related issue

Checklist

  • pnpm run typecheck passes
  • pnpm run lint passes (0 problems)
  • pnpm run test passes
  • I added/updated tests where it made sense
  • I updated docs (README / CHANGELOG) if user-facing behavior changed

Screenshots (if UI-related)

…ows a dark base

Reported: a PEN-F ORF opened dark and grey. Decoding the file with both
LibRaw engines and the app's exact flags gives a correct image, so the
bad state came from the decode-settings machinery on the user's build.

- RAW Decode panel, remembered decode defaults and the Settings RAW
  section removed. Every RAW opens with DCB + blended highlights +
  camera match; options older builds persisted per photo are ignored,
  so single and batch exports always match the editor.
- Highlight recovery (post-decode) moved under Basic Adjustments for
  RAW photos, on the shared SliderRow.
- A failed camera match no longer leaves the -W (un-brightened) base
  on screen: the native rung re-decodes with auto-brighten, the result
  is flagged cameraMatched:false and never written to the disk cache.
  Verified on the ORF: matched 0.319 mean, forced failure 0.401 instead
  of the dark base.
- cameraMatchWorker.cjs is asarUnpacked and loaded from
  app.asar.unpacked in packaged builds; base cache key bumped (cm2) so
  bases cached by earlier builds miss once.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01CKGuP5pugDLEdjbRdfvFUV
@Redrum624
Redrum624 merged commit f00109f into main Oct 10, 2026
1 check passed
@Redrum624
Redrum624 deleted the claude/youthful-hamilton-s04iwn branch October 10, 2026 15:59
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

Successfully merging this pull request may close these issues.

2 participants