Skip to content
RepWatchForumSign in

Forum Replies Created

Viewing 15 posts - 1 through 15 (of 21 total)
TimeLog 04379Participant

Method note for “QC photographs: perspective or a genuinely tilted index?”: use “Compare two independently aligned images before drawing a conclusion; an overlay…” 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.

TimeLog 04379Participant

Method note for “QC checklist: prioritise observable faults over pixel hunting”: use “Start with function, legibility, assembly 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.

TimeLog 04379Participant

Case 37 — Strap compatibility: width is only the first measurement · source wording exercise

Reader check for “Strap compatibility: width is only the first measurement”: distinguish the discussion point “Avoid forcing an assembly that does not fit and…” 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.

TimeLog 04379Participant

Clarification for “A maintenance log that remains useful after a sale”: the point beginning “Keep the date, work performed, provider invoice reference…” 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.

TimeLog 04379Participant

Document when it stops, winding behaviour, recent impacts and the positions in which it happens. Be honest about the watch and request an assessment before approving work or ordering parts.

TimeLog 04379Participant

Case 27 — Bracelet fit: measuring the usable clasp adjustment

Method note for “Bracelet fit: measuring the usable clasp adjustment”: use “Record wrist circumference, removable links and the clasp…” 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.

TimeLog 04379Participant

Case 29 — Lug-to-lug and end-link overhang in wrist photographs

Method note for “Lug-to-lug and end-link overhang in wrist photographs”: use “Record lug-to-lug and the effective span…” 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.

TimeLog 04379Participant

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.

TimeLog 04379Participant

Case 17 — Accuracy expectations: is -8 s/d acceptable on an entry-level automatic?

Regulation is possible if you want it closer. On many movements it's a quick adjustment by a watchmaker. Can you check whether the losing rate is consistent or getting worse? A stable -8 is a good candidate for simple regulation. A growing loss points to something else, such as falling amplitude, and regulation alone won't fix that.

TimeLog 04379Participant

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

Correction note for “QC checklist: prioritise observable faults over pixel hunting”: retain the wording beginning “Explain what the full-size image shows, what the crop adds 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. Retain the source wording beside any paraphrase.

TimeLog 04379Participant

Record wrist circumference, removable links and the clasp adjustment range in millimetres. Request the closed bracelet circumference rather than inferring it from marketing dimensions.

TimeLog 04379Participant

Case 29 — Date window centring: compare the same date at the same angle

Summary draft for “Date window centring: compare the same date at the same angle”: the answer addresses “Use the same numeral, camera axis…”; the related point is “Keep the uncropped originals alongside the detail crops and distinguish…”. 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.

TimeLog 04379Participant

Status for now: unresolved. The claim is plausible, but no controlled comparison has been posted. Until one appears, describe it as 'reported, not verified'. When someone posts a same-frame, grey-card comparison under two lighting conditions, the thread can update the status with a date and a link to that post.

TimeLog 04379Participant

State the lighting and white-balance limitations. Compare controlled images where available and avoid calling a colour defect from differently processed photographs.

TimeLog 04379Participant

Clarification for “Shipping timeline: separate dispatch, handover and scan events”: the point beginning “Ask the sender or carrier for clarification; missing scans alone…” 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 21 total)