# How to create an AI camera orbit from one image: prompts, workflow, and fixes We executed three camera-arc briefs in Aixio: a lamp product concept, a frozen cup editorial moment, and a pavilion concept opener. The result has visible parallax and suspended objects, but it is a small viewpoint change, not a verified 360-degree loop. Here are the exact inputs, submitted prompts, settings and checks. A convincing camera orbit needs more than a subject turning in place. The foreground and background must change relative to each other as the viewpoint moves, while the subject keeps its shape. This experiment tests a small camera arc around an original frozen still life: a ceramic cup, a suspended lemon slice, visible droplets and two depth landmarks. ## Give the camera move a job before generating The existing cup scene belongs in an editorial sequence: a two-second title still introduces the frozen moment, the four-second arc becomes the visual pause, and a two-second end card directs the viewer to the visual recipe. This is an illustrative beverage concept, not a demonstration of pouring or factual product behavior. Add the title and CTA after generation so they remain readable. Choose an arc when the job needs changing overlaps between a subject and objects at different depths. Choose a pan to reframe a composition without asking for new sides, or a zoom to draw attention to a detail. A camera arc is a poor choice when newly invented geometry could mislead a buyer. We used three different briefs and independently generated source images: ### Fictional brass desk lamp Audience and placement: Product designer; motion card after the static hero and before specifications What must pass: Stable shade rim, stem and base; relative landmark movement; no invented hardware Downstream CTA: Review finish options Evidence: Real original source, video, inspection frames and finished handoff below. ### Frozen cup editorial moment Audience and placement: Beverage/editorial designer; short visual pause between title and ingredient detail What must pass: Cup/handle recognizable, suspended lemon, changing rod/cube overlaps; input counting miss disclosed Downstream CTA: Explore the visual recipe Evidence: Real source and video, plus an eight-second edit verified in browser playback. ### Fictional timber pavilion Audience and placement: Architecture concept designer; opener before plans/material boards What must pass: Coherent roof, post count, entrance and horizon; foreground/building/background parallax Downstream CTA: View concept plans Evidence: Real original source, video, inspection frames and finished handoff below. The lamp and pavilion are distinct subjects with different failure criteria; neither is another pose of the cup. Their sources are original fictional concepts. For factual commerce or property work, use owned accurate photographs and independent views; this demonstration cannot validate hidden product details or a building's layout. Shopify documents video as product-page media, while Runway's architecture guide emphasizes depth and shot sequencing. These establish useful workflow contexts, not measured commercial benefits or Seedance Mini results. [Shopify product media](https://help.shopify.com/en/manual/products/product-media), [Runway sequencing guide](https://runway.com/resources/real-estate-walkthrough-video). ## Transfer the manual workflow deliberately Keep the model/settings, accepted Start-frame attachment, continuous four-second small arc and original-output inspection fixed. Change the subject, actual immutable details, landmarks, framing, acceptance criteria, caption and CTA. Do not paste the cup's droplets into a lamp prompt. Read the accepted source and name the parts that are actually present. Source generation, source acceptance, Canvas attachment, live quote review, submission, playback judgment and choice of usable segment are manual. Frame sampling and local export can be automated after downloads. We saved a private camera Skill and applied its version 1 to the lamp and pavilion stages. This is a manual Canvas workflow with a reusable instruction; it does not automate source acceptance, input attachment, settings, quality judgment or editing. The submission audit below distinguishes a recorded Skill reference from instructions actually present in the submitted prompt. Runway's image-to-video guide advises separating motion instructions from image appearance and checking artifacts and implied motion in the input. We use that as input-design guidance; its model-specific success examples do not establish Seedance Mini efficacy. [Runway image-to-video guide](https://help.runwayml.com/hc/en-us/articles/48324313115155-Image-to-Video-Prompting-Guide). ## What the creator actually used The Reddit post by u/AndrewJumpen displayed 2.3K net votes and 225 comments when inspected on October 6, 2026. Those counts show attention, not views, conversion or a success rate. The creator shared a frozen-instant prompt and linked Pablo Dawson’s MiniMax-H3 360 Orbit LoRA. That method combines a specialized adapter with the same image as both first and last keyframe. The adapter is a material part of the workflow; copying its words into a different model does not reproduce it. Sources: [creator post](https://www.reddit.com/r/StableDiffusion/comments/1wuzyq0/orbiting_lora_first_and_last_frame_in_minimax/) and [model card](https://huggingface.co/pablodawson/MiniMax-H3-360-Orbit-LoRA). The original shared prompt, credited to the creator, is: > One frozen instant. Only the camera moves. In a continuous 360 orbit. Preserve every person and object in exactly the same world position, orientation, shape and pose throughout the shot. Airborne objects remain suspended at the captured height and angle: no wobbling, shaking, spinning, drifting, falling or continued action. Keep faces, hands, clothing, liquids and the background motionless while retaining their natural appearance. Camera parallax is the only source of apparent movement. No cuts, zoom, morphing or added objects. We borrowed its separation of camera and scene motion. We changed the subject, move and input setup for the supported Aixio test. ## Prepare an image that makes motion easy to inspect ![Original generated source: cup, suspended lemon and droplets with depth landmarks](/images/blog/camera-orbit/source.jpg) Use an image you own or generate an original scene. Keep the main subject separated from its background. Give it a visible asymmetric feature, such as a colored handle, so a turning or morphing subject is easy to spot. Add objects at different depths: their relative movement helps distinguish camera parallax from a flat pan or zoom. Avoid tiny faces, flowing smoke, dense splashes and overlapping suspended objects for the first test. Our exact submitted source prompt is below. ```text Photorealistic studio still life, one frozen instant captured by high-speed photography. A single ivory ceramic cup with a cobalt-blue handle stands on a dark matte table. One thin lemon slice is suspended upright 12 cm above the cup, and exactly five separate water droplets hang beside it at different heights. No flowing liquid, no splash curtain, no people, no lettering. A small red cube sits behind and to the left of the cup; a narrow vertical brass rod stands farther behind on the right, providing clear depth landmarks. Clean warm gray seamless background, side lighting, crisp silhouettes, realistic ceramic and water, medium-wide three-quarter view, generous empty space around every suspended object. ``` Our image missed the exact five-droplet request, but kept a separated cup, floating lemon and both depth landmarks. We retained the counting error and changed the video instruction to preserve all visible droplets. Inspect the generated image before starting the video. Count the droplets, check the handle and ensure that each depth landmark is visible. A malformed source is an input problem; a longer video prompt cannot reliably repair it. ## Run a modest arc before requesting a full orbit In Aixio Canvas, add a video generator and attach the accepted original image as its start frame. Select Seedance 2.0 Mini. The inspected settings are 720p, four seconds and audio off; the current video quote is 3.93 credits. Confirm the live quote again before submitting. The original image used Seedream 5.0 Pro, quoted at 1.17 credits. Prices and available settings may change. The exact video prompt submitted in this test is: ```text One frozen instant. Only the camera moves. During this four-second shot the camera slowly arcs 30 degrees clockwise around the cup at constant height and constant distance, keeping the cup centered. Preserve the cup, cobalt handle, suspended lemon slice, all visible water droplets, red cube and brass rod in exactly the same world position, orientation and shape throughout. The lemon and droplets remain suspended at their captured heights: no wobbling, shaking, spinning, drifting or falling. No pouring, ripples or continued action. Camera parallax is the only source of apparent movement. The background landmarks shift relative to the cup because the camera changes viewpoint. No cuts, zoom, morphing, added objects or full rotation. ``` The prompt separates scene motion from camera motion, specifies constant camera height and distance, and limits the move to 30 degrees. It explicitly preserves the suspended objects and asks for relative movement of the depth landmarks. It does not request a full loop or invent an end-frame input that the test has not used. The actual UI sequence was: 1. Add an Image node; set Seedream 5.0 Pro, Size 2K, Count 1; paste the image prompt and Generate. 2. Inspect the completed image and download its original. 3. Add a Video node; set Seedance 2.0 Mini. 4. Click Attach, choose Image 1 under From this canvas, and confirm Start frame. 5. Paste the video prompt; open Settings and set 720p, 4s, Audio Off. 6. Check the quote and approved total; Generate once, wait, then download the original. 7. Watch the clip and compare sampled frames. Submit the video only after the source passes inspection and the whole package has an approved cap. Wait for completion before changing the input. Download the original video and keep the original image, exact prompt, settings and generation record together. ![Camera arc planning diagram, not a generated video frame](/images/blog/camera-orbit/plan.svg) *Planning diagram only; the actual source and video are shown separately.* ## Inspect start, middle and end Compare three frames from the same clip. Does the brass rod shift relative to the cup? Does the red cube reveal a different side? Does the cup remain upright while the handle changes visibility through viewpoint alone? Then watch the full video for drifting droplets, a falling lemon, changing object counts, cuts and zooms. A smooth-looking clip can still fail the frozen-scene condition. ## The real output: a useful small arc ![Actual four-second camera-arc video](/images/blog/camera-orbit/camera-arc.mp4) *Original exported video. The 720p preset produced an 834 x 1112 H.264 file at 24 fps, with a file duration of 4.042 seconds and no audio stream. Its framing is wider than the 1664 x 2496 source. We did not crop it to conceal that change.* ![Inspection samples from the same video, left to right at approximately 0.5, 1.5, 2.5 and 3.5 seconds](/images/blog/camera-orbit/inspection.jpg) ![Last-frame inspection at 3.95 seconds](/images/blog/camera-orbit/end.jpg) The brass rod moves toward the right edge relative to the cup. The red cube becomes more hidden behind the cup and handle. The lemon exposes more of its rind. These are useful visual signs of a changed viewpoint, beyond a simple flat translation. The lemon and droplets remain suspended in the inspected frames, with no obvious falling action in playback. The cup and handle remain recognizable; tiny droplets and newly exposed details are not a geometric guarantee. The prompt requested 30 degrees clockwise at constant height and distance. We did not measure the camera trajectory, so neither the exact angle nor a perfect world-space freeze is established. The input already failed the exact droplet count. This is a useful creative arc, not validated reconstruction or a seamless loop. The cup case used two paid submissions and cost 5.101 credits. The whole three-case package is costed below; displayed quotes round to two decimals, while the generation ledger retains three. ## Put the accepted shot into an editorial card ![Eight-second editorial sequence: title, actual camera arc, recipe CTA](/images/blog/camera-orbit/editorial-sequence.mp4) This local prototype uses the accepted source as a two-second title card, the first four seconds of the actual arc, and a two-second recipe CTA. The caption is added after generation. The source is fitted into the video’s native 834 × 1112 frame with padding, preserving its aspect instead of stretching it. Export: silent H.264 MP4, 24 fps, eight seconds, browser-friendly fast-start metadata. The end card makes the cut explicit; no seamless-loop claim. It is an illustrative editorial handoff, not a published campaign. ## Product case: a lamp motion card The audience is a product designer reviewing a fictional desk-lamp concept. Place this card after a static hero and before the specifications or finish board. The shade rim, single green stem and oval base make shape drift easy to inspect; the white block and dark column separate depth. An arc changes their overlap. A zoom would inspect the finish more directly, and is preferable if shape accuracy matters more than depth. ![Original fictional lamp source](/images/blog/camera-orbit/lamp-source.jpg) Source preparation: Seedream 5.0 Pro, 2K, auto aspect, one image. The accepted source is 2048 × 2048. The stem leans despite the straight-stem wording; the object is coherent, so the video brief preserves the accepted image rather than pretending that instruction passed. ```text Photorealistic product photograph of one fictional brass desk lamp on a matte charcoal tabletop. A compact asymmetric conical brass shade tilted slightly down, a single straight dark green stem and a broad oval brass base; no cable, no logo, no text. Three-quarter frontal view showing the shade rim, stem and entire base clearly. One small matte white block behind on the left and a slim dark column farther behind on the right provide separated depth landmarks. Warm neutral seamless studio background, soft side light, crisp geometry, no motion blur, ample margin around the lamp, no cropped parts. Original design concept, no people. ``` We wrote a subject-specific brief, applied the saved Skill in the video composer, then explicitly retained its camera instructions in the submitted prompt. Source attached through Attach → Your files; Seedance 2.0 Mini, 720p, four seconds, audio off. Exact submitted text: ```text Product detail brief: the brass desk lamp remains rigid. Preserve the shade rim, dark green stem and oval base. Keep the lamp stationary while the two background landmarks change their overlap. the attached skill Continuous four-second shot. The camera makes a slow small clockwise arc around the stationary subject, keeping it centered at constant apparent scale and camera height. Preserve its visible geometry and orientation. Foreground and background landmarks shift relative to the subject because the viewpoint changes. Keep the scene and lighting steady. One smooth shot with the whole subject in frame. ``` ![Actual lamp camera arc](/images/blog/camera-orbit/lamp-arc.mp4) ![Lamp inspection at 0, 1, 2 and 3.8 seconds](/images/blog/camera-orbit/lamp-inspection.jpg) The white block travels toward the stem and reveals another side; the dark column shifts farther right. The shade rim, single stem and base remain recognizable in playback and samples. This passes our creative motion-card checks: changing depth overlaps, complete subject, no obvious added hardware or cuts. It does not establish exact camera angle or manufacturing geometry. The 720p preset exported a 960 × 960 video; preset names do not specify one universal pixel size. ![Eight-second lamp concept card](/images/blog/camera-orbit/lamp-sequence.mp4) The lamp handoff follows a two-second concept title, the actual four-second arc and a two-second “Review finish options” card. Place it after the static hero; the next asset should be an accurate finish board, not another invented product view. ## Architecture case: a concept opener The audience is an architecture concept reviewer. The shot introduces a fictional pavilion before plan drawings and material boards. Use an arc to read the roof overhang and post/entrance overlap against a foreground stone and distant tree. Use a static view for dimensions or a real multi-shot walkthrough for a property's actual layout. ![Original fictional pavilion source](/images/blog/camera-orbit/pavilion-source.jpg) Source preparation: the same image settings, but a different brief and independently generated 2496 × 1664 landscape source. It shows three prominent front posts, a recessed glass entrance and a stone plinth. The roof is shallow pitched rather than the requested flat roof. We accepted it as a fictional concept, disclosed that miss, and preserved the roof actually present. A flat roof that is mandatory in a real brief would require source repair before motion. ```text Photorealistic architectural visualization of one fictional single-story timber pavilion on level gravel. Broad flat roof with one clearly visible overhang, three timber posts on the visible front, a recessed glass entrance toward the right and a continuous low stone plinth. Three-quarter exterior view from the front left, straight vertical lines, all roof corners inside the frame. One low dark stone in the near foreground on the left and one slender tree farther behind the pavilion on the right create clear depth separation. Still dry scene, overcast daylight, no people, no vehicles, no lettering, no motion blur. Original architectural concept, not an existing property. ``` We placed the existing private Skill node, chose Use for video, attached this pavilion through Your files, changed the default model to Seedance 2.0 Mini, and set 720p, four seconds, audio off. Exact first submitted text: ```text Architectural establishing brief: preserve the pavilion roof edges, three front posts, recessed entrance and stone plinth. Keep the horizon level and the foreground stone and distant tree still. ``` ![First pavilion attempt, retained failure evidence](/images/blog/camera-orbit/pavilion-first.mp4) ![First pavilion frame comparison](/images/blog/camera-orbit/pavilion-first-inspection.jpg) The first clip changes viewpoint, but the opening clips the left roof edge and the subject becomes smaller. Its changing roof profile is ambiguous from one view; we cannot prove whether every newly exposed surface is faithful. It failed our complete-roof and constant-scale checks. The Skill reference was present, but explicit camera instructions were absent from the submitted text. That is a concrete prompt-transfer limitation, not proof that the Skill caused the visual failure. We used the one correction allowance on the same source/settings, making camera motion and roof constraints explicit: ```text Continuous four-second shot. Only the camera moves in a slow small clockwise arc around this stationary pavilion, at constant height, distance and apparent scale. Preserve the roof pitch, straight roof edges, three front posts, recessed entrance and stone plinth exactly as shown in the input. The foreground stone and distant tree remain stationary; their overlaps with the pavilion change only because of the viewpoint. Keep the whole roof in frame, horizon level, lighting steady. No zoom, roof bending, changing post count, cuts or added objects. ``` ![Corrected pavilion raw output](/images/blog/camera-orbit/pavilion-arc.mp4) ![Corrected pavilion samples at 0, 1, 2 and 3.8 seconds](/images/blog/camera-orbit/pavilion-inspection.jpg) The foreground stone changes its overlap with the posts while the tree separates from the roof. The three front posts, entrance and plinth remain recognizable, with no obvious cut. The corrected opening still clips the left roof edge, and constant scale is not established. We accepted only the final two seconds for the concept opener, where the complete roof is visible, then held the accepted end frame. This is an editing repair, not an all-constraints-passed claim. Newly revealed timber/roof details remain generated, not verified architectural facts. The raw output is 1112 × 834, 24 fps, 4.042 seconds, no audio. ![Eight-second pavilion opener: title, selected two-second arc, end-frame hold, CTA](/images/blog/camera-orbit/pavilion-sequence.mp4) The handoff uses title 0–2s, raw video 2–4s placed at edit 2–4s, accepted end frame 4–6s, and “View concept plans” 6–8s. Follow it with the actual concept drawings and material board. The failed first clip stays available above; no extra paid generation was made. ## What saved-Skill reuse actually proved The private Skill **Small camera arc · rigid scene · article test**, version 1, stores this common instruction: ```text Continuous four-second shot. The camera makes a slow small clockwise arc around the stationary subject, keeping it centered at constant apparent scale and camera height. Preserve its visible geometry and orientation. Foreground and background landmarks shift relative to the subject because the viewpoint changes. Keep the scene and lighting steady. One smooth shot with the whole subject in frame. ``` Keep that instruction fixed. Replace the subject-specific brief and source; manually review framing, immovable details, live quote and final geometry. Both video records contain the same saved Skill ID/version and their own correct source. However, the lamp's submitted prompt includes the camera instruction explicitly, whereas the pavilion's first submitted prompt contains only its architectural brief. A Skill chip or connection alone is therefore insufficient evidence that the desired camera instruction reached the provider. The pavilion result and any bounded repair are recorded above. This is an executed reuse test with an observable limitation, not a promise of automatic cross-subject success. ## Fix the cause, not every word at once ### The cup turns but the background stays fixed What to inspect: Landmark parallax One possible next change — currently untested: Explicitly keep the subject fixed and describe the camera traveling around it; reduce the requested arc. ### Droplets fall or the lemon spins What to inspect: Their position and orientation across frames One possible next change — currently untested: Replace action verbs with a captured frozen instant and list the suspended objects explicitly. ### Handle or hidden surfaces change shape What to inspect: Newly revealed regions One possible next change — currently untested: Use a smaller viewpoint change; a single image cannot establish unseen geometry. ### The clip is almost still What to inspect: Whether the camera moved at all One possible next change — currently untested: Test a clearer small arc with visible depth landmarks rather than demanding identical beginning and end. ### A flat pan masquerades as an orbit What to inspect: Differential foreground/background movement One possible next change — currently untested: Use a source with clear depth separation and inspect parallax. ### The source already has ambiguous objects What to inspect: Original image before video One possible next change — currently untested: Repair or replace the source within the same bounded allowance. These are diagnostic proposals, not demonstrated repairs. Comments on the source post describe residual blinking and moving smoke or hair; those reports helped define the checks, but they are not our own test results. ## When a different method is needed A precise, complete 360-degree loop is a different target from this prompt-driven camera arc. The linked orbit adapter has a documented first/last-frame method and a narrow training domain. Meridian is another documented approach: it estimates geometry from input video, renders a camera reference and generates missing regions. It requires its own geometry model and adapters; it is not an Aixio setting. Its documentation also notes that unseen surfaces are synthesized and large viewpoint changes can drift. See the [Meridian model card](https://huggingface.co/Viggle/Meridian). For this article, the useful reusable recipe is: prepare a clear original image, constrain the camera move, preserve scene motion separately, inspect parallax and shape, then make one diagnosed correction within the authorized cap. An attractive output is not evidence of recovered 3D geometry. ## Deliver the shot with context All three local handoffs are silent eight-second H.264 MP4s at 24 fps with fast-start metadata: two-second title still, four-second motion section and two-second task CTA. The pavilion motion section contains two selected seconds plus a two-second end-frame hold; the lamp and cup use four seconds of their raw clips. Sources are fitted without stretching to each native video frame. Titles and CTAs are added after generation. Keep the visible fictional-concept labels; replace the CTA with a real destination in the downstream page or presentation. No product page, ad, property tour, public Skill or article has been published. Before generating, we reviewed the full package, available displayed balance of 1,942 credits and one correction reserve. The final three images cost 3 × 1.170; four videos including the one pavilion correction cost 4 × 3.931: **19.234 credits across seven paid submissions**. The two new cases plus correction used 14.133 credits, within the approved additional cap. No purchase or further retry was made. Live prices may change; review your own whole-plan quote and precise ledger before retrying. ## Reuse the recipe [Download the manual camera-arc recipe](/images/blog/camera-orbit/workflow-recipe.md) and [exact tested prompts and settings](/images/blog/camera-orbit/prompts.json). Replace the subject and depth landmarks deliberately; the three cases are actual runs with their own inputs and briefs. Saved-Skill reuse is audited above; no automated batch is claimed. Stop after one diagnosed correction within your own approved cap rather than repeatedly gambling on hidden geometry. ## Questions readers can check ### Is this a full 360-degree camera orbit? No. The real Aixio output is a modest camera arc. The creator's specialized adapter is a separate documented method, and its full-loop result was not recreated here. ### Should I attach the same image as the last frame? That is part of the creator's LoRA method. This test used a single Start frame in Seedance 2.0 Mini. It did not test an identical last frame, so we do not recommend it as an established fix for this model. ### Can the video reveal the true back of my product? A single image does not establish unseen surfaces. Use real additional views for factual product geometry; treat invented sides as creative output and inspect them before commercial use. ### Which fixes were actually tested? We changed five droplets to all visible droplets before the first cup video. The pavilion received one corrective submission after roof/scale drift; its exact revised prompt and outcome are shown above. Other troubleshooting suggestions remain untested. The shared creator prompt belongs to its credited specialized method. The official [Seedance 2.0 announcement](https://seed.bytedance.com/en/blog/seedance-2-0-official-launch) describes the wider model family's reference and camera capabilities. Our Mini variant's settings and result are established by the actual Aixio run above, not inferred from every full-model feature.