No single lighting setup settles that question. Compare multiple controlled angles and describe the visible observation without asserting material specifications that have not been verified.
Forum Replies Created
Case 3 — Forum comparison archive: link the evidence and the correction
Clarification for “Forum comparison archive: link the evidence and the correction”: the point beginning “Add a dated correction near the original conclusion…” belongs to the question as written. It should not be read as a report that a new check, purchase or experiment has been completed. Review focus: scope. Keep the stated question separate from any broader claim.
Compare the observed rate with the exact caliber and cased-watch specification, if available. An example such as -8 seconds per day cannot be declared acceptable solely from its price category.
Case 38 — Comparing dial colour under different lighting · source wording exercise
Method note for “Comparing dial colour under different lighting”: use “Compare controlled images where available and avoid calling a…” as a row heading in a proposed working record. Put the statement, its supporting source or measurement, and any unresolved detail in separate fields. This proposes a format; it supplies no additional evidence. Retain the source wording beside any paraphrase.
Case 18 — Lume questions: why does my lume fade so quickly, and how should I compare it?
A bright initial glow followed by a steep drop is normal for photoluminescent pigments. Afterglow fades fastest in the first minutes and then settles to a dim, long-lasting level that dark-adapted eyes can still read. The real question is whether it's readable after an hour in darkness, not how it looks right after charging.
The calendar interval is a conservative default, not a rule. Useful signs, in rough order of seriousness: power reserve noticeably shorter than spec from full wind, rate drifting outside its usual range, the watch stopping on the wrist, gritty or rough winding, and the date changing slowly or late.
Case 42 — Disputed observation: is this dial colour shift real or just lighting? · source wording exercise
Reader check for “Disputed observation: is this dial colour shift real or just lighting?”: distinguish the discussion point “Two photos of the same dial under different light can…” from its proposed application. The thread offers a way to reason about the question, without adding a personal experience or a newly observed outcome. Review focus: source wording. Retain the source wording beside any paraphrase.
Case 17 — Maintenance question: how do I tell if an automatic actually needs service?
If the manufacturer provides a suitable procedure, a running-time log can support a service enquiry. State the winding method and stop time. A shortened run does not identify the cause by itself.
Clarification for “Date window centring: compare the same date at the same angle”: the point beginning “Use the same numeral, camera axis…” belongs to the question as written. It should not be read as a report that a new check, purchase or experiment has been completed. Review focus: scope. Keep the stated question separate from any broader claim.
Case 1 — Comparing dial colour under different lighting
Clarification for “Comparing dial colour under different lighting”: the point beginning “State the lighting and…” belongs to the question as written. It should not be read as a report that a new check, purchase or experiment has been completed. Review focus: scope. Keep the stated question separate from any broader claim.
Summary draft for “Reading a timegrapher recording without losing the context”: the answer addresses “Keep the complete recording and ask for the…”; the related point is “A single number cannot establish service condition, movement identity…”. Keep both connected to the opening question, and mark any conclusion needing further records as unresolved. Review focus: scope. Keep the stated question separate from any broader claim.
Case 14 — QC checklist: prioritise observable faults over pixel hunting
Summary draft for “QC checklist: prioritise observable faults over pixel hunting”: the answer addresses “Start with function, legibility, assembly and…”; the related point is “Explain what the full-size image shows, what the crop adds and…”. Keep both connected to the opening question, and mark any conclusion needing further records as unresolved. Review focus: scope. Keep the stated question separate from any broader claim.
Clarifying question: does anyone in the thread have access to both versions at once? Without simultaneous comparison, every claim either way is weak evidence. If not, the next best option is photos with a grey card in frame and white balance locked or set manually, which at least makes separate photos roughly comparable.
Method note for “QC photographs: perspective or a genuinely tilted index?”: use “Request a level straight-on image with the hands…” as a row heading in a proposed working record. Put the statement, its supporting source or measurement, and any unresolved detail in separate fields. This proposes a format; it supplies no additional evidence. Keep the stated question separate from any broader claim.
A useful table has columns for date, position, winding state, lift angle, rate, amplitude and beat error. Keep the full recording so settings and stability can be checked.