mirror of
https://github.com/storytold/vectorcraft.git
synced 2026-10-24 09:46:59 -06:00
andeecollardandClaude Opus 5.5
17a602d1dc
The public documentation says Image Trace warns about images larger than 1500 pixels on a side but traces them, only more slowly. VectorCraft traced them silently, and refused any trace of more than 2,000,000 anchors, which a 4000 x 3000 photo at High Fidelity Photo nearly reaches (1.9 million on a code-drawn photo) and a noisier one passes. - imageTrace.make and makeAndExpand return `warnings`: one for an image over 1500 px on a side (traced, but more slowly; a lower-fidelity preset or a smaller copy is quicker), one for an image over 64 MP that was traced from a scaled-down copy. The app shows the first in the status bar. - MAX_TRACE_ANCHORS is 8,000,000 natively (2,000,000 on wasm, where a page has at most 4 GB). Measured through imageTrace.make on code-drawn photos: about 90 bytes an anchor kept in the document; 7.9 million anchors kept 685 MB with an 876 MB peak (4000 x 3000, Full Tone at Colors 100, Paths 100, Noise 1, 37 s). - The refusal keeps its translated advice: raise Noise, lower Paths or Colors, or pick a lower-fidelity preset. Tests: a_large_image_traces_with_a_warning (1600 x 40 and 1500 x 8 code-drawn images, make and make-and-expand), trace_warnings_name_a_large_or_scaled_down_image, a compile-time check of the limit's range, and a UI test that the status bar shows the note. Source: https://helpx.adobe.com/illustrator/using/image-trace-results-optimization.html Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_018tBcdwNhptqtmX32JCGFzB