Skip to content
RepWatchForumSign in

Forum Replies Created

Viewing 15 posts - 1 through 15 (of 23 total)
QCReader 07234Participant

Case 12 — Packing photographs: document condition without exposing an address

Photograph the item and protective packing separately from the label. Remove names, addresses, barcodes and tracking tokens from public images while keeping originals privately.

QCReader 07234Participant

Case 15 — Timegrapher reading context: what do rate, amplitude and beat error actually tell me?

The reported numbers alone do not establish damage or the need for service. Confirm the setup, collect comparable readings and ask a watchmaker to assess a concerning or changing pattern.

QCReader 07234Participant

Method note for “Lume comparison: keep exposure and charging conditions consistent”: use “Repeat with equal light source, charging duration, elapsed time and camera…” 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.

QCReader 07234Participant

Case 4 — Comparing versions without mixing case sizes

Correction note for “Comparing versions without mixing case sizes”: retain the wording beginning “Match reference, dimensions 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.

QCReader 07234Participant

Micro-adjust spacing varies by clasp. Measure the actual change at each setting rather than assuming a standard number of millimetres; compare the usable range with the link length.

QCReader 07234Participant

Case 10 — Timegrapher reading context: what do rate, amplitude and beat error actually tell me?

Amplitude depends on the movement and measurement setup. Compare it with appropriate specifications and a qualified watchmaker’s assessment; a universal pass/fail threshold would be misleading.

QCReader 07234Participant

Clarification for “Disputed observation: is this dial colour shift real or just lighting?”: the point beginning “The difficulty is that phone cameras adjust white balance automatically,…” 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.

QCReader 07234Participant

Case 4 — Reading a timegrapher recording without losing the context

Clarification for “Reading a timegrapher recording without losing the context”: the point beginning “Keep the complete recording and ask for the…” 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.

QCReader 07234Participant

Correction note for “Comparing dial colour under different lighting”: retain the wording beginning “State the lighting 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.

QCReader 07234Participant

Lug width is the essential one: the inside distance between the lugs where the strap fits. Measure with a ruler marked in millimetres, ideally reading it under magnification. Most watches use even numbers (18, 20, 22mm), but odd widths exist. If you measure 19 or 21, measure again and check the manufacturer spec before ordering.

QCReader 07234Participant

Case 27 — Model comparison: dive bezel action and alignment, how to compare fairly

People keep comparing the bezels on two similar dive-style watches. One is called crisp, the other mushy, and alignment complaints come up for both. What would a fair comparison look like, and what is actually a defect versus a preference?

Exercise RWF-18883/27: address this question within its stated limits.

QCReader 07234Participant

Reader check for “Date window centring: compare the same date at the same angle”: distinguish the discussion point “Use the same numeral, camera axis…” 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.

QCReader 07234Participant

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

Two glowing dials are shown with different camera exposure and unknown charging time. What can the images establish?

Exercise RWF-16210/13: address this question within its stated limits.

QCReader 07234Participant

Case 23 — Forum comparison archive: link the evidence and the correction

Correction note for “Forum comparison archive: link the evidence and the correction”: retain the wording beginning “Add a dated correction near the original conclusion…” 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.

QCReader 07234Participant

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.

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