# ManYue screentone checks: compare zoom and derivatives against one source
Language: en
Canonical: [ManYue screentone checks: compare zoom and derivatives against one source]()
中文：[中文 HTML]()
English: [English HTML]()
Published: 2026-11-04T00:00:00+08:00
Modified: 2026-11-04T09:36:55+08:00
Author: Bison
Fix source and display conditions when screentones develop waves or shimmer, comparing zoom, an external view and existing derivatives before blaming the artwork.
English translation of the [Chinese original](), translated on 2026-11-04. Original publication dates, attribution, code and version notes are retained.
Dense screentones may show extra waves at some viewing scales, resembling an added clothing pattern. Use an authorised page to compare ManYue with a trusted external viewer, checking whether the effect changes with scale or output file. This produces diagnostic evidence, not a universal anti-moiré setting or an assumption that the display pattern belongs to the artwork.
## Choose a screentone region and a control
Choose a flat screentone area and a clear contour or ordinary text control on the same page, recording their locations. Inspect the complete artwork to exclude intentional stripes or background texture. Prefer an authorised local source rather than comparing a server thumbnail with a full image. Avoid initial recompression or screenshot transfer, which adds processing layers. Preserve the original and identify the file in every observation so comparisons return to the same region.
## Record conditions before changing scale
Record device, app version, orientation, page layout and zoom state. Document any changed external display processing without inventing a dedicated in-app descreening button. Inspect the full page, then enlarge the same region progressively, noting wave position, density and direction. Change one condition at a time instead of rotating, switching layouts and replacing files together. If exact zoom is unavailable, use reproducible descriptions such as fit-to-page or substantially enlarged rather than fabricated percentages.
## Compare the tone against the control
Observe whether contours and text remain clear as the tone waves change. A scale-dependent effect confined to dense regions is useful evidence but does not identify a faulty decoder or scanner. Whole-page blur, blocks or missing areas call for source-quality and loading checks rather than a blanket moiré label. Regular dots visible when enlarged may be the original artwork structure. Distinguish source dots, added waves and compression traces before selecting the next comparison.
## Open the identical source externally
Open the identical file in a trusted image tool and inspect the same fit and enlarged views. A messaging-app derivative is not the source, and “works elsewhere” needs a scale description. Different results establish different display paths, not a specific algorithmic cause. Matching waves do not prove artistic intent either: they may already be baked into scanning or resizing. Describe the observation precisely and leave unverified causes unknown.
## Check whether an existing derivative changes the pattern
For authorised existing derivatives, compare dimensions, format and origin, inspecting both tone and contours. File size alone does not rank clarity because dimensions and compression differ. Preserve evidence of a worse derivative instead of repeatedly recompressing the original. If a new export is needed, use a familiar external tool, save separately and record resizing or compression. There is no universal descreening recipe here: processing can remove fine lines. Choose according to comfortable reading versus detailed study.
## Choose a usable reading condition
Continue with a less distracting view or suitable existing derivative while preserving dialogue and page relationships. Do not blur away fine detail just to remove tone waves, or optimise one patch while losing a spread. Record the prior state before using work-specific settings and check their scope. This is a device-and-page compromise, not a best setting for every comic. Keep source identity and viewing conditions for research so a convenient reading copy is not later mistaken for original evidence.
## Prepare a minimal report instead of uploading a book
A report should describe the same file and region across viewing conditions and include app and system versions. Prefer an original dot-pattern sample if you can make one, labelling it as a similar display case rather than proof of the private page’s cause. A screenshot records one rendering and is not the source; resizing it can change the pattern again. Use descriptions, dimensions and an authorised small sample rather than distributing a protected comic.
## Acceptance and common overdiagnosis
Finish with source identity, tone/control comparison, at least two scale observations, an identical-file external view and a usable reading choice. Improvement with zoom does not certify the source because baked-in waves can also change with display. An ineffective format conversion does not exonerate every viewing path because it may preserve existing patterns. State what evidence rules out and what remains unresolved, stop aimless re-exporting, and retain the original and chosen reading copy until new evidence justifies further checking.
## Related guides and sources
[ManYue small lettering: separate zoom level, source detail and display processing](); [ManYue large-image diagnostics: separate file size, dimensions and loading]().
Checked on November 4, 2026: [Apple public version information]() lists ManYue 2.0.4, requiring iOS / iPadOS 15.0 or later. Feature scope follows the [official App Store description]() and the installed version. This article provides reading and checking methods you can perform; it does not claim step-by-step physical-device or private-server testing. Manual lists, external tools and actually visible controls are identified separately. Code observations do not establish verified behaviour across every release path.