Scene 01Take 1●
Watch the thirty-second travel edit
This example follows Toronto → Montreal → Quebec City. The map establishes each place, then a five-second picture scene gives it a moment of its own. Two map movements connect the cities; the video finishes with a short scope card. It is a complete thirty-second edit, rather than a list of possible formats.
The complete travel movie and its poster combine AlbumMap’s original AI illustrations and cards with a map adapted from Geographical Adventures by Sebastian Lague, using NASA, Natural Earth, Flagpedia and HYG v3 sources. These named example files are shared under CC BY-SA 2.5. Keep the complete travel-source credits and change notes with copies; both credit formats are also included in the input pack. The record identifies the original pictures, prepared cards and map input. No music or narration is used.
The pictures are AI-generated illustrations of possible landmark scenes, not photographs documenting a visit. The captions are invented teaching copy. Use your own photographs and actual memories when making a personal travel video; the sample shows how to place and frame them.
Download the input and reproduction pack or the descriptive transcript and timing. The pack includes the unchanged original PNGs, prepared picture cards, the source map clip, map-source credits, an edit sheet and a runnable assembly script. It is not a native editor project.
Scene 02Take 1●
Give each city one picture and one sentence
| Stop | Sample media | Caption | Picture time |
|---|---|---|---|
| Toronto | travel-toronto-illustration.png | A first afternoon by the water. | 5 seconds |
| Montreal | travel-montreal-illustration.png | A quieter moment at the port. | 5 seconds |
| Quebec City | travel-quebec-illustration.png | One last evening before home. | 5 seconds |
The three pictures have different jobs: an opening waterfront scene, a quieter middle scene and a final evening scene. The map answers where; the short caption supplies the memory. For a real trip, replace these illustrative captions with something the group actually remembers, such as who suggested the stop or what changed the plan.
Keep each chosen item attached to its known city. A filename or upload order is not proof of location. If a photograph’s place is unresolved, keep it in a separate unlocated chapter until someone can identify it.
Use the travel-photo organization example when the source files are scattered. This guide begins after the three selected items and their locations are known.
Scene 03Take 1●
Use the twelve-second map as the edit spine
Create the map sequence with the tested three-stop route tutorial. That guide contains the place-selection controls, screenshots, camera values and separate website save/preview/export checks. This example reuses its twelve-second local map clip with numbered markers.
The bare map has two seconds at each city and two three-second illustrative Fly legs. It uses approximate city centers and overhead framing. Those arcs explain the order of places; they are not a checked road itinerary, airline schedule or record of how anyone traveled.
For this finished edit, the three picture scenes are inserted after their city holds in an external assembly step. They were not uploaded to the hosted builder for this demonstration. The native map remains twelve seconds; the assembled story becomes thirty seconds. If you instead attach stop media in the website, read its updated duration and preview it again, because media can reserve additional display time.
Scene 04Take 1●
Keep the whole source picture in the frame
Each source image is 1536 × 1024, a 3:2 shape. The final video is 1280 × 720, a 16:9 shape. The sample fits the whole picture into a 750 × 500 area at x=265, y=150, leaving a dark surround with the city title and caption above the picture. It scales the picture proportionally and does not crop its edges.
This keeps the tower, bench, waterfront and roofline available for the viewer to inspect. Filling the whole widescreen frame would require a different crop or layout. Try that only after deciding which edges can be lost. For a person in a real photograph, check the face, hands and surrounding context before accepting a crop.
The five-second picture scenes remain still. The map supplies the movement, so the pictures do not also need a pan or zoom. A simple hard cut makes the change from geography to memory clear. The sample contains no crossfade overlap to subtract from the time budget.
Scene 05Take 1●
Follow the actual thirty-second timeline
| Finished time | Scene | Source |
|---|---|---|
| 0:00–0:02 | Toronto map hold | Source map 0:00–0:02 |
| 0:02–0:07 | Toronto picture and caption | First prepared picture card |
| 0:07–0:10 | Map movement to Montreal | Source map 0:02–0:05 |
| 0:10–0:12 | Montreal map hold | Source map 0:05–0:07 |
| 0:12–0:17 | Montreal picture and caption | Second prepared picture card |
| 0:17–0:20 | Map movement to Quebec City | Source map 0:07–0:10 |
| 0:20–0:22 | Quebec City map hold | Source map 0:10–0:12 |
| 0:22–0:27 | Quebec City picture and caption | Third prepared picture card |
| 0:27–0:30 | Scope and input credit | Prepared ending card |
Twelve seconds of map, fifteen seconds of pictures and a three-second ending total thirty seconds. If you add a spoken clip, give it a specific interval or place it over an existing scene. Do not count the same seconds twice.
Scene 06Take 1●
Rebuild the sample or adapt it in your editor
- Extract the input pack into one folder. Keep the original images and source map there so the timing sheet can be traced to its inputs.
- For the exact prepared edit, use Python 3 and FFmpeg on your PATH, then run: python assemble-travel.py. It creates render-parts and three-city-travel-demo.mp4 locally.
- In another video editor, import the map clip and three pictures. Split the map after its first two seconds and after source second seven, then place a five-second picture scene after each city hold.
- Fit each whole picture, add its city and one caption, then append the three-second ending. The prepared cards in the pack show the finished layout.
- Export the complete timeline and play the actual output, including its final frame. Check the three city names against the picture order.
The supplied runner was checked with the prepared assets on 24 October 2026. It performs local processing and does not upload, publish or change a website project. The finished file is H.264, 24 fps, 720 frames and silent. It has no narration or soundtrack requiring a music license.
Scene 07Take 1●
Review the story at the viewing size
- Check that every picture follows the correct city hold and that both map moves remain in chronological order.
- Pause each picture scene. Verify the whole image, the city title and the caption without relying on a large editor preview.
- For phone sharing, test fullscreen as well as the small inline player. Offer the short written story or transcript beside it.
- Keep synthetic examples clearly labeled. Do not present an illustrative landmark scene as proof of a journey or a current venue condition.
For a portrait version, use the vertical photo-video workflow. This landscape project gives each of three selected pictures its own clear place in the finished story.
End card
That’s a wrap
Helpful answers
Frequently asked questions
Why is the finished edit longer than the map clip?
It adds three separate five-second picture scenes and a three-second ending to the twelve-second map: 12 + 15 + 3 = 30 seconds.
Were the sample pictures uploaded to the hosted map builder?
No. This demonstration uses a local map render and assembles the picture scenes separately in FFmpeg. The route tutorial documents the distinct website workflow.
Are the sample images actual trip photographs?
No. They are original AI-generated teaching illustrations. The article, video picture cards and input pack disclose that scope.



