State the lighting and white-balance limitations. Compare controlled images where available and avoid calling a colour defect from differently processed photographs.
Forum Replies Created
Case 37 — Case finishing: distinguish a reflection from a surface mark · source wording exercise
A bright line appears in one polished-case image. What additional evidence would distinguish a mark from reflected light?
Review focus: source wording. Retain the source wording beside any paraphrase. Use the original answer fragment “A mark should be assessed across multiple views; aggressive polishing…” as the discussion anchor; no new event or result is supplied.
Exercise RWF-27495/37: address this question within its stated limits.
Case 9 — Movement identification: the limits of a rotor photograph
Describe visible bridge shapes and markings separately from the proposed identification. Ask a qualified watchmaker to inspect it if identification matters for servicing; do not open the case merely for a forum answer.
Case 40 — Packing photographs: document condition without exposing an address · source wording exercise
Reader check for “Packing photographs: document condition without exposing an address”: distinguish the discussion point “Remove names, addresses, barcodes and tracking tokens from public…” 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.
Ask a qualified watchmaker about a suitable test for that individual case and record the test date and method. A photograph or a caseback engraving is not proof of water resistance.
On alignment, a clarifying point: is the misalignment visible straight on, or only from an angle? Parallax on a raised bezel can make a perfectly aligned pip look half a click off when viewed slightly from the side. Photograph straight above the dial before calling it misaligned.
Case 31 — Crystal reflections: why a dark patch is not a coating test
Clarification for “Crystal reflections: why a dark patch is not a coating test”: the point beginning “No single lighting setup settles…” 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 6 — Timegrapher reading context: what do rate, amplitude and beat error actually tell me?
I ran a watch on a basic timegrapher and got +6 s/d, 245 degrees amplitude and 0.8 ms beat error, dial up, about an hour after winding. Is this good, bad or normal? I don't want to send it for service on a single reading.
Exercise RWF-19078/6: address this question within its stated limits.
Case 25 — Crystal reflections: why a dark patch is not a coating test
Clarification for “Crystal reflections: why a dark patch is not a coating test”: the point beginning “No single lighting setup settles…” 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 6 — Lug-to-lug and end-link overhang in wrist photographs
Limit of the answer in “Lug-to-lug and end-link overhang in wrist photographs”: “Record lug-to-lug and the effective span…” is an excerpt from the discussion, not an independent verification. A reader needs the relevant original material before treating an interpretation as established. Review focus: scope. Keep the stated question separate from any broader claim.
Method note for “Strap compatibility: width is only the first measurement”: use “Measure the lug opening and document bar diameter,…” 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.
Case 7 — 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.
Summary draft for “Maintenance question: how do I tell if an automatic actually needs service?”: the answer addresses “The calendar interval is a conservative…”; the related point is “Useful signs, in rough order of seriousness: power reserve noticeably shorter…”. 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.
Reader check for “Lug-to-lug and end-link overhang in wrist photographs”: distinguish the discussion point “Record lug-to-lug and the effective span…” 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: scope. Keep the stated question separate from any broader claim.
Clarification for “Movement identification: the limits of a rotor photograph”: the point beginning “Describe visible bridge shapes and markings separately…” 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.