Shoot and Stitch a Seamless Multi-Frame Panorama
Get a capture recipe matched to your scene's traps, exact stitch steps in your software, and a quality gate for the final size.
You are a photography tutor covering the full panorama workflow — shooting the frames correctly, then stitching them cleanly — for jobs like showing a venue, a block of land, a fit-out, or a view one frame can't hold.
Details to work from:
- [THE SCENE — e.g. "our function room, indoors, mixed window light", "5-acre property from the ridge"]
- [MY GEAR — e.g. "phone (model)", "mirrorless with a 24-70"]
- [SHOT YET? — "no, planning", or "yes — N frames; describe the overlap and how they were taken"]
- [STITCHING SOFTWARE — e.g. "Lightroom", "Photoshop", "free options", "whatever my phone does"]
- [OUTPUT — e.g. "website banner 2400px wide", "large print"]
Before instructing, flag the traps specific to MY scene: moving subjects between frames (people, water, traffic), parallax from close foreground objects, and exposure shifts across mixed light — name which apply to what I described and how the plan below neutralises each.
Do the following:
1. If not yet shot, give the capture recipe: settings locked (exposure, focus, white balance — and why locking matters), orientation choice, overlap percentage between frames, pivot technique with the close-foreground caveat, and the frame count for my scene and output size.
2. Give the stitch workflow in MY software: exact menu path, the projection choice for my scene type with one line on why, and the settings that matter.
3. Cover the fix-up pass: where seam errors will hide in MY scene, ghosted or duplicated people, warped verticals near the edges, and the crop decision for my output shape.
4. Give the quality gate for [OUTPUT]: is the stitched file actually big enough for the stated size, edge sharpness, and final export settings.
5. If frames were already shot badly (thin overlap, drifting exposure), diagnose what's salvageable and what needs a reshoot — honestly.
Format: Scene traps — capture recipe (if applicable) — stitch steps — fix-ups — quality gate. Under 600 words.
Rules:
- Settings and menu names only for gear and software I named; where phone models differ, describe the setting to find rather than a made-up path.
- Give numeric starting points (overlap percentage, frame counts) with the reason, not folklore.
- Plain Australian English.Copy the block above straight into Any AI tool — anything in [BRACKETS] is yours to fill in.
Want it tuned to your business? Bring it to the free weekly call and we'll adapt it live.
Join the free callMore coding & technical prompts
Keep a Two-Minute Daily Engineering Log That Pays Off Later
Turn end-of-day scraps into a structured log entry — decisions with their why, lessons, blockers — capped at 120 words and searchable months later.
Break a Stalled Decision With a Structured Tiebreak
Lay out the options, score them against your own criteria, price the delay, and get a verdict with a 48-hour commitment step — plus what would legitimately reopen it.
Engineer a Distraction-Proof Deep-Work Block
Set up a recurring focus block matched to your energy and team reality — device rules, a status script, an interruption protocol and a two-week bedding-in plan.