Previews from the publisher
Introduce a mobile message, then emphasize two concise capabilities inside the device. An oversized phone dominates one side while a supplied presenter remains in a tall close crop; the labels arrive only after the main message is established. This 6.8-second shot illustrates claims you provide, without operating a mobile app or testing whether its capabilities exist.
Choose two capabilities that actually support the main message and can be substantiated separately. Use the labels to direct attention, not to make an untested mobile mockup appear functional.
/creatormotion-split-phone-callouts Turn my supplied explanation into a white-yellow B-roll scene using the Phone Feature Callouts effect. Use the text, data and media I provide, and ask for any required input that is missing.Prepare a short phoneTitle, message and at most two callouts. Keep capability claims accurate for the subject you are explaining; the example labels are illustrative copy rather than tested functionality.
Supply a continuous local presenter take of at least 6.8 seconds through --media. The video is muted and zoomed into a tall crop. Inspect the face and body framing and never loop a shorter take. No alpha-matte cutout is used.
Reuse mobile-screen and chat-avatar or replace those exact keys with --images MAP.json. Relative paths resolve beside the map and unmentioned defaults remain. The screen is a raster background beneath editable overlays, so text baked into the image does not change with phoneTitle or message. Follow the image policy when adapting material.
Prepare Node.js 22+, FFmpeg and HyperFrames CLI 0.8.30. From the extracted package run node scripts/create.mjs --out /absolute/PROJECT --data /absolute/CONTENT.json --style white-yellow --media /absolute/PRESENTER.mp4. Use another documented palette or semantic --overrides as needed. Read the motion specification, DESIGN.md and image policy before adapting materials.
Run the generated project’s lint, validate and inspect checks, then render with the printed command. Inspect actual MP4 frames at entry, every focus change and the final reading hold for seams, clipping, contrast and media overlap. Keep essential text and interface targets readable; compare all four palettes with identical content after module changes. Narration is separate, and a silent preview does not establish audio synchronization. Inspect the message-to-label sequence and the intentional lower-edge phone crop in actual MP4 frames. Check that both callouts remain legible within the device, with no essential text hidden by the crop. Keep the tall presenter separate from the primary reading area.
Yes. phoneTitle, message and callouts are JSON inputs, with four palettes and semantic overrides. The clock, workspace label and input placeholder are fixed scene text; raster background text needs an image replacement.
Yes. Bring a continuous local presenter take covering the 6.8-second composition. The two still-image slots have defaults, but those do not replace speaker footage. No alpha matte is required here.
Yes. Preserve the message before the two internal capability labels and keep the phone dominant. Re-render after changes and check the stamped label states, presenter crop and final reading interval.
No. Callouts are supplied strings. An animated offline or organization label does not demonstrate that a real product has those functions.
The oversized device intentionally crosses the frame edge. Review essential content within the visible viewport; use a different layout or adapt the scene if the lower controls must be shown.
Select a star to share your experience.
No reviews yet. Ratings appear once readers share real experiences.
+7
Use this Skill to create broll animation.
+7Use this Skill to create broll animation.
+7Use this Skill to create broll animation.
+7Use this Skill to create broll animation.
+7Use this Skill to create broll animation.
+7Use this Skill to create broll animation.
+7Use this Skill to create broll animation.
+7Use this Skill to create broll animation.