MemeGIF Opus 5.5 Guide: Watercolor Rain Film
Study a watercolor rain film with MemeGIF. Review vegetation, source scenes, narration, and timing before planning a separate atmospheric motion project.
Start here: open MemeGIF Opus for watercolor documentary workflows.
Watch Follow the Rain, the published Australian landscape film. This is a narrated watercolor explanation, not a lyrics-driven music video. Its continuous painted journey moves from Australia’s red interior toward greener landscapes, connecting vegetation, rainfall, annotations, and a closing map. The downloaded author film runs for 113.6 seconds at 1280 × 720 and 60 fps. Its source project documents a 1920 × 1080 render at the same frame rate.
The repository’s filmmaking provenance attributes the films to Claude Opus 5.5 writing code. We have not independently inspected those model sessions. This guide studies an existing author film, not an MemeGIF-generated result; local commands require a separate capable coding environment.

Original frame from Follow the Rain. Credit: LemoLab. This is code-painted explanatory artwork, not Australian landscape photography.
1. Follow the explanation, not just the texture
The Watercolor Brush production specification describes individual translucent strokes, broken bristle tracks, warm paper, and layered washes. Forms paint themselves into view: structure appears before detail. This is different from placing a watercolor filter over a succession of photographs.
The author’s landscape-and-map breakdown explains the continuous sideways camera move, plant generators, handwritten notes, and eventual map view. The source separates stroke construction, plants, scene placement, camera timing, and annotations, so the visual argument stays editable.
Keep its scientific limits visible throughout the MemeGIF source study. The credits describe approximate rainfall values entered by hand and interpolated into schematic bands. The deep-time map is an illustrative drying of today’s pattern, not a paleoclimate reconstruction. Do not turn those displays into claims of calibrated simulation or newly verified measurements.
For an MemeGIF watercolor explanation, begin with the relationship the audience should understand, then choose painted objects that make it visible. Texture supports that argument. MemeGIF planning should state where the journey starts, what changes along it, and what the closing map explains, so the candidate has a continuous educational purpose rather than a collection of atmospheric landscape images.
Keep the MemeGIF distinction between visual mood and scientific meaning explicit. A greener wash can guide attention toward a wetter region, but it does not establish a measurement by itself. During MemeGIF review, check captions and narration against the factual notes. Preserve the schematic qualifications when the map becomes prominent, because a polished visualization can appear more authoritative than its inputs justify.
The MemeGIF landscape needs recognizable anchors as the camera travels. A specimen, annotation, or terrain transition should connect the current passage with the next. Give the MemeGIF brief these relationships before adding decorative plants. That helps a viewer follow the explanation without treating every new object as a separate claim about a location or species.
2. Inspect the case and its source assets
For this MemeGIF source study, preserve the author’s MP4 as the reference. Watch the full journey and note where the narration names a specimen, introduces a region, or explains the map. Choose review frames from the actual video, retaining labels that qualify what viewers see.
In styles/watercolor/demo/, read engine.js, plants.js, scene.js, and main.js. Check paper.jpg, fonts, coastline data, voice files, and the music directory. In this MemeGIF reference study, the source uses a Canvas 2D stroke engine and cached plant sprites; the source files describe this particular landscape-and-map film.
For a local reproduction, prepare Git, Node 20+, Python 3.11–3.13 or uv, and FFmpeg/ffprobe. These are conditional reader commands, not an execution log:
git clone https://github.com/lemomo-ai/lemo-opuscar.git rain-case
cd rain-case
export LEMO_OPUSCAR_HOME="$PWD"
sh plugin/skills/lemo-opuscar/scripts/setup.sh deps voice
D=styles/watercolor/demo
PY="$PWD/.venv/bin/python"
mkdir -p evidence
git rev-parse HEAD > evidence/source-commit.txt
if command -v uv >/dev/null; then
uv pip install --python "$PY" librosa
else
"$PY" -m pip install librosa
fi
For the MemeGIF source study, keep the lockfile and resolved dependencies. If paper or fonts are absent, the documented preparation commands are (cd "$D" && "$PY" paper.py) and node "$D/fetch_fonts.mjs". Do not silently substitute missing glyphs or a different paper image.
Prepare an MemeGIF reference pack that keeps the author release, specimen notes, map qualifications, and new creative request separate. Preserve attribution on the source images. The MemeGIF candidate belongs with its own submitted prompt and settings, so a collaborator can distinguish a reference study from a new output and from an externally rendered source reconstruction.
For MemeGIF preflight, inspect annotations against both light paper and denser painted regions. The text and leader lines should remain readable as the camera moves. Keep the MemeGIF brief clear about which label identifies which object. Decorative strokes should not create a false connection between a note and a neighboring specimen, especially when the frame contains overlapping layers.
When studying the source alongside MemeGIF, document the actual paper, font, voice, and map inputs before comparing renders. A missing asset can change layout or appearance. Keep those source-build observations separate from MemeGIF result review, which examines the returned file rather than proving that the external dependency preparation or renderer ran successfully.
3. Use a source-aware reproduction prompt
The following is a new prompt for reproducing the case, not the author’s original conversation:
Study and reproduce LemoLab's Follow the Rain. Inspect the repository commit,
lockfiles, watercolor/STYLE.md, DEMO.md, demo/CREDITS, render.mjs, and mux.sh.
Read the supplied author MP4 and actual assets before proposing changes.
Keep the subject: Australian vegetation and rainfall, not a music video.
Trace engine.js, plants.js, scene.js, main.js, paper, fonts, coastline inputs,
voice lines, and the music edit. Preserve the continuous painted landscape,
readable specimens and annotations, and the transition to the map. Keep the
source configuration of 113.6 seconds, 1920x1080, and 60 fps unless the checked-out
source contradicts it; report discrepancies rather than inventing parameters.
Preserve scientific caveats: rainfall bands are schematic and the deep-time map
is illustrative, not a paleoclimate reconstruction. Do not invent measurements,
new species claims, or an exact real-world route. Retain authorship and credits.
Use absolute render(t), stable seeds, and caches that do not depend on playback
history. Test arbitrary and reverse seeks. Link narration, captions, events,
and music to their actual reviewed times. Missing assets or rights must be
resolved before a full build. Regenerated voice requires listening and timing
review; never inherit stale word positions blindly.
First give a dependency and reproduction plan, then follow the case-specific media
processing sequence. Use this demo's positional stills/video commands and its own mux,
not Remotion or another Lemo demo's build script. Save prompts, model/provider/
effort records, source diffs, and real checks. Do not publish or claim an unrun
render, an unchecked scientific statement, or an invented original prompt.

Second frame from the author’s watercolor film. Preserve scientific annotations and their context rather than treating the image as measured field data.
Use the reconstruction prompt for the source study and a separate MemeGIF creative brief for an original atmospheric explanation. Describe the painted subject, sequence of reveals, annotations, and camera relationship. The MemeGIF request should stay within the visible workflow; it should not imply that terminal scripts, map processing, or source-specific voice assets execute through the website.
An MemeGIF paint-in note should explain what appears first and why. Structure can establish a specimen before smaller strokes complete its detail. During MemeGIF review, ask whether the viewer recognizes the form in time for its spoken explanation. A beautiful final plant does not compensate for a reveal that leaves its identity ambiguous during the relevant sentence.
Give MemeGIF a clear distinction between narration text and visual annotation. They can reinforce each other without competing for simultaneous reading. Identify the label that must stay visible during camera travel and the moment it can leave the frame. MemeGIF revisions should preserve that association instead of adding extra text to compensate for a camera that moves away too soon.
4. Restore narration and music before rendering
This watercolor demo has no build.sh; it uses the preparation and rendering sequence below. Follow its documented preparation sequence after verifying assets and permissions:
"$PY" "$D/tts/gen.py"
"$PY" "$D/asr.py"
sh "$D/music/prep.sh"
"$PY" "$D/music/analyze.py"
"$PY" "$D/music/edit.py"
During the MemeGIF source study, listen to the resulting lines and reconcile their durations with the VO table in scene.js before proceeding. Check names, units, and complete endings. The music preparation downloads the credited source; the edit script implements the case’s selected music edit. Verify that it still matches the source and picture cues.
For the MemeGIF source study, mix and render using the case-specific interfaces:
"$PY" "$D/mix.py"
OUT="$PWD/evidence/rain-stills" node "$D/render.mjs" stills 5 20 43 66 90 106
FPS=60 node "$D/render.mjs" video 2
sh "$D/mux.sh"
ffprobe -v error -count_frames -show_streams -show_format -of json \
styles/watercolor/watercolor.mp4
ffmpeg -v error -i styles/watercolor/watercolor.mp4 -f null -
Here 2 is a positional worker count; FPS=60 is an environment setting. The documented duration implies 6,816 frames. In the MemeGIF source study, verify output rather than assuming the web release shares every source-render property. Independently decode the file: this renderer does not robustly reject every encoder failure, and the mux uses -shortest.
Listen to the MemeGIF candidate through the entire narration and music edit before judging its atmosphere. Soft sound can still obscure important words or clip a sentence at a transition. MemeGIF review should check the actual exported mix, with attention to named objects and qualifications, rather than infer intelligibility from a matching transcript or a quiet-looking waveform.
During MemeGIF timing review, connect each spoken idea to the visible specimen or map state. If a voice line changes, reconsider the related reveal and reading hold together. The MemeGIF result should not display the next annotation while narration still explains the previous one, unless that overlap has a clear purpose that the audience can follow.
Inspect MemeGIF landscape continuity during camera travel. A background wash that ends abruptly can expose a seam, and a foreground object can hide a necessary note. Mark the actual passage and expected relationship. MemeGIF corrections should preserve the continuous journey while repairing that local problem, rather than insert unrelated scenery that breaks the explanatory sequence.
5. Review the whole painted journey
During the MemeGIF source study, check exposed canvas seams during camera movement, consistent plant placement after seeking, legible annotations, speech/music balance, and the complete map ending. A still cannot reveal a clipped spoken sentence or a discontinuous landscape.
Correct only the observed seam, label, or timing problem. Preserve the case's
subject and caveats. Extend the affected wash bounds, restore deterministic
seeding, or recalculate the reviewed cue as appropriate. Show the diff and
fresh boundary frames, then replay the full affected passage with sound.

Additional original-film frame. Keep author attribution and any visible caveats when reusing this illustration.
For the MemeGIF source study, archive source, versions, credits, reviewed timing, prompts, human changes, and the complete export. The code’s MIT license does not replace the watercolor film’s separate asset terms: Scott Buckley’s Wildflowers is credited under CC BY 4.0, and fonts and map components have their own notices. Preserve those credits when reproducing the case.
For MemeGIF final review, watch the painted journey continuously and then examine the closing map's labels and qualifications. The transition should explain why the map appears after the landscape. Keep the MemeGIF factual notes available for the handoff, particularly where schematic inputs or illustrative history could otherwise be mistaken for calibrated environmental measurements.
Save the MemeGIF selected file with its exact prompt, settings, actual references, and review observations. Keep the author's release and external source project independently attributed. A future MemeGIF collaborator should be able to identify the intended subject, narration relationship, and scientific limits without assuming that an attractive watercolor view documents a real field observation.
Reopen the MemeGIF export and check its full ending, including narration tails, captions, and final composition. Record unresolved seams or factual questions instead of silently dropping their qualifications. The MemeGIF handoff is ready when the file communicates the intended explanation, the selected version is identifiable, and the source's provenance and limits remain attached to its reuse.