Skip to content
RepWatchForumSign in

Forum Replies Created

Viewing 15 posts - 1 through 15 (of 20 total)

Ask for profile shots of both case sides and a lug-top shot at an angle. Polishing shows as rounded edges, softened bevels or lug holes that look shallower than they should. Compare against a known-good reference image of the same model, not memory. A side-by-side tells you far more than a description.

Case 22 — Disputed observation: is this dial colour shift real or just lighting?

The difficulty is that phone cameras adjust white balance automatically, and blue dials are especially sensitive. Two photos of the same dial under different light can easily look like a 'batch difference'. Any comparison needs both dials in the same frame, under the same light, ideally next to a neutral grey or white reference card.

Case 47 — QC photographs: perspective or a genuinely tilted index? · source wording exercise

Reader check for “QC photographs: perspective or a genuinely tilted index?”: distinguish the discussion point “Compare two independently aligned images before drawing a conclusion; an overlay…” 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.

Lume photos are close to useless for comparison unless exposure is fixed. Phones raise exposure automatically in the dark, so a dim watch can look as bright as a strong one. For a fair photo comparison: same charge method, same delay after charging, manual exposure, and both watches in the same frame.

Case 4 — Lume comparison: keep exposure and charging conditions consistent

Clarification for “Lume comparison: keep exposure and charging conditions consistent”: the point beginning “Treat the comparison…” 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.

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.

Case 43 — Maintenance question: how do I tell if an automatic actually needs service? · source wording exercise

Method note for “Maintenance question: how do I tell if an automatic actually needs service?”: use “Useful signs, in rough order of seriousness: power reserve noticeably shorter…” 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.

Use the same numeral, camera axis and approximate image scale. Keep the uncropped originals alongside the detail crops and distinguish optical balance from physical window alignment.

Case 31 — First QC request: the minimum useful information

Correction note for “First QC request: the minimum useful information”: retain the wording beginning “State the model configuration, the specific concern and…” in the record. If later material changes it, add the date, the changed wording and the source for that change; do not invent a completed correction here. Keep the stated question separate from any broader claim.

Case 38 — QC checklist: prioritise observable faults over pixel hunting · source wording exercise

Method note for “QC checklist: prioritise observable faults over pixel hunting”: use “Explain what the full-size image shows, what the crop adds and…” 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.

First, a clarifying question: how many links are on each side of the clasp right now? Fit often improves by moving one link from the 6 o'clock side to the 12 o'clock side, or the reverse. That doesn't change length, but it shifts where the clasp sits under the wrist, and a centred clasp feels less tight.

First identify the caliber, lift-angle setting, winding state and measurement position. Without those fields, the rate, amplitude and beat-error values lack enough context for a useful comparison.

Method note for “Comparing dial colour under different lighting”: use “State the lighting and…” 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 21 — Comparison thread: 38mm vs 40mm versions of the same field watch, with a dated correction log

I'm putting together a side-by-side of the 38mm and 40mm versions of a common three-hand field watch design. The aim is a reference post we can fix over time instead of repeating the same arguments. Corrections go in a dated log at the bottom. What should the table include besides case diameter, and which specs are usually misreported?

Exercise RWF-09593/21: address this question within its stated limits.

Jewel count describes bearings used in a movement design; it is not a quality ranking. Compare the documented movement architecture and service support rather than assuming a higher count makes one watch better.

Viewing 15 posts - 1 through 15 (of 20 total)