vycdev / vycdev/Kromacut

Compare Kromacut color/TD accuracy against HueForge outputs

Open
#55 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement help wanted
Dominant language
TypeScript
Stars
278
Forks
31
Avg merge
13h 32m
Merged PRs (30d)
4

Description

Kromacut would benefit from a validation pass comparing its color and TD behavior against equivalent HueForge workflows.

This is not necessarily a request to copy HueForge behavior. The goal is to better understand where Kromacut matches expectations, where it differs, and whether those differences point to bugs, calibration issues, UX gaps, or intentional model differences.

This likely needs help from someone who has access to HueForge.

Useful comparison areas:

  • Same source image processed in Kromacut and HueForge.
  • Same or comparable filament colors and TD values.
  • Similar layer height, total height, and print settings.
  • Previewed output comparison.
  • Printed output comparison, if possible.
  • Notes on where Kromacut appears more/less accurate.
  • Cases where TD values produce unexpected results.
  • Cases where auto-paint choices differ significantly.

Possible outputs from this research:

  • Example images and project/settings files.
  • Screenshots of both previews.
  • Photos of printed results.
  • Notes on setup differences.
  • Follow-up issues for specific bugs or UX improvements.

Important note:
This should be treated as validation and research, not as a requirement that Kromacut must exactly match HueForge. If the tools differ, the useful question is whether Kromacut?s result is predictable, explainable, and accurate for its own model.

Desired outcome:
Build a clearer understanding of Kromacut?s real-world color/TD accuracy and identify any concrete improvements needed in calibration, auto-paint, preview, or print guidance.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by processing the same source image in Kromacut and HueForge using comparable filament colors, TD values, layer height, total height, and print settings. Record preview comparisons, printed results if possible, setup differences, and unexpected TD or auto-paint behavior. Done means a reproducible set of examples and notes that identify concrete calibration, preview, UX, or print-guidance follow-ups.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
computer-graphics, testing-qa
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.