MemeGIF Opus 5.5 Guide: Glass Earbud Product Film
Study the fictional Aura earbud film with MemeGIF. Review glass, unboxing, exploded views, lighting, and source-based checks before planning your own project.
Start here: open MemeGIF Opus for transparent-product launch films.
Watch Aura — Hear the Light, the released glass-earbud film. The supplied 32.000-second film presents fictional transparent earbuds and their charging case through opening, floating components, exploded views, light sweeps, and a final brand card. LemoLab’s statement on code-made films attributes the collection to Claude Opus 5.5. Those sessions and a local reproduction have not been independently verified here; these commands require a separate terminal.

Original Aura film frame. Credit: LemoLab. The product is fictional. Review it as a reference for MemeGIF.
1. Understand the glass before adjusting the camera
Read the transparent-material studio specification. The scene uses Three.js transmission, strip-light reflections, and procedural floor caustics. Clear glass needs something to reflect or refract; increasing transparency alone can make it disappear. Light expresses the concept, not measured acoustic performance.
Inspect product.js for geometry/materials, studio.js for lighting, story.js for timing, and main.js for staging and titles. Keep the reference MP4 separate. Check the opening, distinct exploded layers, and readable reassembly. The source links its light pulses to the score rather than independent timers.
Begin an MemeGIF product-film treatment with a visual question: what should the viewer understand about the object after watching it move? Separate that communication goal from an unverified product claim. MemeGIF can help explore a presentation, but a glowing shell or moving light is a design metaphor rather than evidence about sound quality, battery life, or manufacturing readiness.
Keep the fictional Aura study distinct from an original MemeGIF product brief. Write a description of your own object's silhouette, visible parts, surface treatment, and intended message before choosing camera effects. In MemeGIF, that compact object definition provides a reference for revisions. Without it, an attractive shot may quietly change the concept that the next shot is supposed to explain.
When reviewing an MemeGIF glass concept, first determine whether the viewer can distinguish the shell from its contents. Transparency is useful only when important contours and internal parts remain readable. Inspect the object against the actual background in the MemeGIF preview. A pleasing glow can hide boundaries just as easily as darkness can, so judge visibility rather than brightness alone.
Describe a clear order of discovery in your MemeGIF treatment: introduce the object, expose the relevant detail, show the meaningful change, and confirm the result. Keep each stage connected to the communication goal. The MemeGIF brief should explain why a close view or separated component matters instead of treating every available effect as something the film must include.
2. Prepare the reproduction workspace
Use Git, Node 20+, FFmpeg/ffprobe, and Python 3.11–3.13 or uv. Run the following in a new directory, or reuse a reviewed existing clone. Setup installs the browser and voice dependencies, not a completed film.
git clone https://github.com/lemomo-ai/lemo-opuscar.git aura-study
cd aura-study
export LEMO_OPUSCAR_HOME="$PWD"
sh plugin/skills/lemo-opuscar/scripts/setup.sh deps voice
D=styles/glass-product/demo
mkdir -p evidence
git rev-parse HEAD > evidence/commit.txt
npm ls --depth=0 > evidence/node-packages.txt
Preserve dependency versions; check Inter Tight, Kokoro, and WebGL. This case synthesizes music and effects; it does not require an HDRI or sample-bank replacement.
The external source workspace and the MemeGIF web project have different responsibilities. The commands below prepare the author's code for local reconstruction; they are not instructions to paste into the browser's prompt field. Keep output folders separate. A named MemeGIF project, an untouched author release, and an attributed local study should remain identifiable when you later compare their visual decisions.
Before rebuilding the reference, retain a dependency note beside your MemeGIF planning document. Confirm which source files, fonts, and voice inputs exist, and record any missing requirement. Do not call an incomplete render a successful reproduction. An MemeGIF concept can remain useful while the separate local build is waiting for a clearly identified input or a supported runtime.
Preserve the original author film and create a separate location for actual local review output. Keep MemeGIF previews in their own project history. When an inspection note mentions a reflection, timing issue, or unreadable title, attach it to a specific file. That avoids carrying a defect from the reference into an MemeGIF revision request that concerns a different version.
3. Paste this new reproduction prompt
Newly written for this tutorial, not the author’s original prompt:
Reproduce Aura — Hear the Light from the supplied author film and glass-product
source. Inspect the commit, locks, STYLE.md, DEMO.md, CREDITS, core APIs, and
build.sh. Identify missing files or unsupported dependencies before execution;
otherwise proceed through the documented build without adding approval gates.
Preserve the fictional earbuds, case opening, component separation, reassembly,
light sweeps, and closing card. Keep author attribution. Invent no real-product
specifications, performance results, original prompts, or successful runs.
Check the source's 32-second, 1920x1080, 24-fps configuration. Trace geometry,
lighting, camera and sound to product.js, studio.js, story.js and main.js.
Keep component positions deterministic under arbitrary and reverse render(t).
Maintain readable exploded layers, shell visibility, floor clearance, and the
shared snap/light/music cue. Do not paint fake screen-space reflection streaks.
Use the actual build script; inspect every error and listen to regenerated
speech. Test the opening, macro focus, snap boundary, caption holds and ending.
Retain editable code, dependency records, model/provider/effort/session details,
prompts and human diffs. No external generated media or publishing.

Another original-release frame; judge component movement in the complete sequence. Compare this reference separately from your MemeGIF preview.
Use the reproduction prompt for an attributed study of the supplied case. An original MemeGIF request should instead identify your own object, story, framing, and deliverable. Keep the purposes separate in the written brief. Do not describe the author's model sessions as MemeGIF verification, and do not assume that the web tool installs the external repository or exposes its rendering engine.
For an MemeGIF motion request, simplify the product message before listing material effects. Select the visible change that best explains the concept, then reserve enough screen space for the object and a readable title. MemeGIF's supported styles and duration choices define the web project. The author film's length, narrated soundtrack, and local source remain a separate reference workflow.
Define what must remain recognizable across an MemeGIF sequence: the object outline, the relationship between shell and internal parts, and the intended closing identity. Keep requested camera movement distinct from a redesign. MemeGIF revisions are easier to assess when a reviewer can see whether the change improved presentation or introduced a different object that no longer matches the accepted concept.
Write an inspection question beside each planned MemeGIF passage. For an opening, ask whether the object is identifiable. For a separated view, ask whether the parts and their relationships are readable. For a closing card, ask whether the message has space to settle. Use those questions to review MemeGIF output instead of approving a sequence solely because its lighting looks elaborate.
4. Build and repair observed defects
sh "$D/build.sh"
node core/render/still.mjs "$D" 9.3 14.6 15.9583333333 16 16.0416666667 26.8 \
--out evidence/aura-review
The script creates speech, score, events, mix, and subtitles; renders at 24 fps with three workers; then muxes and checks the final audio. The still times are source-based review points, not new observations.
For washed-out glass, inspect emitter strength and tone mapping. For unreadable exploded layers, adjust focus and viewing angle. A stale reflection calls for checking camera/world updates, not adding another glow. Use this targeted instruction:
Repair only the observed reflection, separation, clearance, or timing defect.
Preserve the source story and duration. Show the material/camera/cue diff,
render adjacent frames, then replay with sound. Do not conceal errors with cuts.
Review the source study's opening as a sequence, then apply that observation habit to an MemeGIF preview. Follow the case and visible object through the movement, looking for intersections, unexplained jumps, or changing proportions. State the actual mismatch before requesting a correction. An MemeGIF revision should address the observed passage while preserving the composition and identity that already communicate clearly.
A separated-component view in an MemeGIF concept should reveal relationships rather than create an ornamental cloud of parts. Check whether objects remain distinct, whether their ordering is understandable, and whether the following movement explains where they belong. Compare the complete passage in MemeGIF; an attractive still cannot show whether reassembly is coherent or whether a part disappears during the transition.
Judge MemeGIF reflections against the intended object shape. Follow a bright edge as the camera moves and ask whether it helps define the shell or looks detached from it. In the local source study, inspect the responsible material and camera code. In MemeGIF, describe the visible continuity problem without claiming access to the author's strip-light scene or low-level reflection controls.
Keep picture and sound acceptance separate when comparing the external film with an MemeGIF project. Listen to the reconstructed narration and effects in the local export, and check their relation to the visible action. MemeGIF's silent motion output should be described as silent. A visual timing study can inform a later sound workflow without pretending that the web generator supplied the reference soundtrack.
5. Verify the export
OUT=styles/glass-product/glass-product.mp4
ffprobe -v error -count_frames -show_streams -show_format -of json "$OUT"
ffmpeg -v error -i "$OUT" -f null -
Expect 768 picture frames at 24 fps for unchanged 32-second source settings. Check dimensions, full narration, and the closing fade separately; a web release need not be byte-identical to a rebuilt file. Watch the entire MP4.

Original-film frame. Keep its LemoLab attribution. Keep this author frame separate from MemeGIF outputs.
Archive source, prompts, session records, revisions, checks, and output. Lemo code is MIT; Aura’s typography and voice credits retain separate licenses. Preserve notices and the fictional-product description.
For MemeGIF export review, distinguish technical readability from creative acceptance. A file that decodes successfully can still contain a cropped object, an unreadable closing card, or an abrupt ending. Reopen the actual exported file at its intended display size. Record which MemeGIF version you inspected, and keep unresolved issues explicit instead of borrowing a success statement from the author's released example.
Compare the opening and ending when assessing an MemeGIF product story. The final view should make the intended change understandable rather than merely repeat an attractive silhouette. An original MemeGIF project can use a different ending from Aura, but the closing composition should still confirm its own message. Allow readable identity and settled motion to contribute to that conclusion.
If an MemeGIF revision improves the light but alters an accepted object, compare it against the saved baseline before adopting it. Name the changed outline, component, or title and decide whether that change belongs in the brief. Keep useful experiments separately. This prevents an MemeGIF sequence from accumulating incompatible versions under a shared final label that hides their differences.
Share an MemeGIF concept with its brief, saved version, and known limitations. Keep author-film credits with the reference and source dependency records with the local reconstruction. Identify any later editing or sound work separately. A reviewer should be able to understand the MemeGIF deliverable on its own, while seeing exactly which other files support the study and which claims remain untested.