<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Tutorials &#8211; Hugin Panorama</title>
	<atom:link href="https://huginpanorama.com/tutorials/feed/" rel="self" type="application/rss+xml" />
	<link>https://huginpanorama.com</link>
	<description>Professional Open-Source Panorama Stitcher &#38; HDR Creator</description>
	<lastBuildDate>Wed, 21 Oct 2026 03:17:49 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=7.1.3</generator>

<image>
	<url>https://huginpanorama.com/wp-content/uploads/2026/04/favicon-150x150.png</url>
	<title>Tutorials &#8211; Hugin Panorama</title>
	<link>https://huginpanorama.com</link>
	<width>32</width>
	<height>32</height>
</image> 
	<item>
		<title>Milky Way Panoramas with Hugin: Shoot Wide, Stitch Clean</title>
		<link>https://huginpanorama.com/milky-way-panorama/</link>
					<comments>https://huginpanorama.com/milky-way-panorama/#respond</comments>
		
		<dc:creator><![CDATA[Admin]]></dc:creator>
		<pubDate>Wed, 21 Oct 2026 03:16:05 +0000</pubDate>
				<category><![CDATA[Tutorials]]></category>
		<guid isPermaLink="false">https://huginpanorama.com/milky-way-panorama/</guid>

					<description><![CDATA[Quick answer: A Milky Way panorama is an ordinary panorama shot under extraordinary light conditions — or rather, the lack of them. The shooting discipline changes completely: fast wide lens wide open, high ISO, short exposures timed by the 500 rule, focus set on a bright star, and every camera setting locked to manual. And...]]></description>
										<content:encoded><![CDATA[<p class="wp-block-paragraph"><strong>Quick answer:</strong> A Milky Way panorama is an ordinary panorama shot under extraordinary light conditions — or rather, the lack of them. The shooting discipline changes completely: fast wide lens wide open, high ISO, short exposures timed by the 500 rule, focus set on a bright star, and every camera setting locked to manual. And one honest warning up front: Hugin&#8217;s automatic control-point finder struggles on dark sky frames, so expect to place some control points by hand on bright stars. The result — a stitched arc of the galactic core over a clean foreground — is worth every minute.</p>
<h2 class="wp-block-heading">Camera settings for night panoramas</h2>
<p class="wp-block-paragraph">Start with the classic astrophotography recipe and treat every number as a starting point, not a law. Use your fastest wide lens <strong>wide open</strong> (f/2.8 or faster if you have it), set ISO somewhere in the <strong>1600–6400</strong> range depending on how dark your sky is, and shoot <strong>RAW</strong> — night frames need every bit of highlight and shadow latitude when you develop them. The exposure time is governed by the <strong>500 rule</strong>: divide 500 by your lens&#8217;s focal length (use the full-frame equivalent on a crop-sensor camera) and you get roughly the longest shutter speed in seconds before stars start trailing visibly — 500 ÷ 24mm ≈ 20 seconds, for instance. It is a rule of thumb, not physics: high-resolution sensors show trailing sooner, so check a test frame at 100% and shorten if the stars are eggs rather than points.</p>
<p class="wp-block-paragraph">Lock everything down. Manual exposure, manual white balance (so frame-to-frame colour cannot drift), image stabilisation off on a tripod, and a remote release or self-timer so you never touch the camera during a frame. Our general <a href="/shooting-panoramas-for-hugin/">panorama shooting guide</a> covers the tripod discipline; at night it matters twice as much, because a nudged frame is not discovered until you are home.</p>
<h2 class="wp-block-heading">Focus: the step that ruins more night panoramas than any other</h2>
<p class="wp-block-paragraph">Autofocus is useless in the dark, and the infinity mark on the lens barrel is only approximately honest. Switch to live view, magnify the brightest star or a distant light you can find, and focus manually until it is the smallest, tightest point you can make it. Then leave the focus ring alone — a strip of tape over it is not paranoia, it is standard practice. Soft stars cannot be rescued in the stitcher, and an arc of twelve soft frames is twelve times the disappointment. While you are setting up, this is also the moment to run your lens through <a href="/hugin-lens-calibration/">Hugin&#8217;s lens calibration</a> if you have not: wide-open fast lenses vignette heavily and distort strongly, and Hugin corrects both far better with a calibrated lens profile than with defaults.</p>
<h2 class="wp-block-heading">Shooting the arc</h2>
<p class="wp-block-paragraph">Shoot the Milky Way as a multi-row arc: a foreground row along the horizon, then one or two rows tilted up to cover the galactic core as it climbs. Overlap generously — <strong>30–50%</strong> between frames, more than you would use in daylight — because the stitcher has so much less to work with in dark frames. Work briskly but calmly: the sky rotates noticeably over twenty minutes, so an arc shot slowly is an arc whose later frames no longer match the geometry of the first ones. If your foreground matters — a barn, a shoreline, a lone tree — shoot it as its own pass: a longer, lower-ISO exposure (or a gently light-painted one) from exactly the same tripod position, to blend in afterwards.</p>
<h2 class="wp-block-heading">Stitching in Hugin: the honest hard part</h2>
<p class="wp-block-paragraph">Convert the RAW frames to 16-bit TIFF with identical settings, then load them into Hugin — and here is the difficulty nobody warns beginners about. CPFind finds control points by matching detail between frames, and a dark sky frame is mostly black noise sprinkled with faint points of light. On bright, structured parts of the Milky Way it may succeed; on sparse star fields it will often fail or, worse, mis-match. The fix is manual and oddly satisfying: in the Control Points tab, place points by hand on the same bright, recognisable stars in both frames of a pair — a dozen solid points beat fifty dubious automatic ones. Anchor the pano with the foreground frames first (they have real detail), optimise, then bring the sky rows in.</p>
<p class="wp-block-paragraph">Two more night-specific traps. First, <strong>light-pollution gradients</strong>: the sky is brighter toward the horizon and darker overhead, and that gradient differs per frame, so seams show as brightness steps — Hugin&#8217;s photometric optimisation and exposure correction reduce them, and shooting the whole arc quickly keeps the gradient consistent. Second, <strong>vignetting</strong>: wide-open lenses darken every corner, and overlapping darkened corners are a classic source of visible banding in night stitches; Hugin&#8217;s vignetting correction, fed by your calibrated lens, handles most of it. For blending the separately shot foreground, the exposure-fusion logic in our <a href="/hugin-hdr-panorama/">HDR panorama guide</a> is the same workflow — different frames for different brightness ranges, combined deliberately rather than by luck.</p>
<h2 class="wp-block-heading">Planning the night: when and where</h2>
<p class="wp-block-paragraph">The Milky Way rewards planning more than gear. Three variables decide whether the trip is worth it. <strong>The Moon</strong> is the big one: a bright Moon washes the galactic core out of the sky, so serious Milky Way panoramas are shot in the moonless window around the new Moon — though a little moonlight can be a gift for the foreground, lighting the landscape so you do not need a separate foreground pass. <strong>The season and your hemisphere</strong> decide when the galactic core is up and how high it climbs; the core is a spring-to-autumn feature in the northern hemisphere and favours the southern sky, which is why planning apps that show the core&#8217;s path over your location are worth using before you drive anywhere. <strong>The location</strong> does the rest: artificial light pollution is the enemy, and even an hour&#8217;s drive from a city changes the sky more than any camera upgrade.</p>
<p class="wp-block-paragraph">On site, arrive before dark if you can. Composing a multi-row arc by headtorch is miserable, and the foreground row you shoot at blue hour — same tripod position, same framing — can blend beautifully with the night rows later. At minimum, scout the foreground in daylight: the perfect silhouette tree at noon is invisible at 1 a.m., and so is the ditch next to it.</p>
<h2 class="wp-block-heading">FAQ</h2>
<h3 class="wp-block-heading">Why can&#8217;t Hugin find control points in my night photos?</h3>
<p class="wp-block-paragraph">CPFind matches visible detail, and dark sky frames offer very little: faint stars and a lot of noise. Place control points manually on the same bright stars in both frames — around a dozen per pair is plenty — and anchor the panorama on the foreground frames first.</p>
<h3 class="wp-block-heading">What focal length is best for a Milky Way panorama?</h3>
<p class="wp-block-paragraph">Wide: roughly 14–24mm (full-frame equivalent) is the usual working range. Wider lenses capture more sky per frame and allow longer exposures under the 500 rule, which is why fast wide primes are the classic choice.</p>
<h3 class="wp-block-heading">Can I stitch a Milky Way panorama from a single row?</h3>
<p class="wp-block-paragraph">Yes, if the arc fits in one row&#8217;s vertical field of view — common with very wide lenses in portrait orientation. Multi-row arcs capture taller compositions and more foreground, at the cost of more frames to align.</p>
<h3 class="wp-block-heading">Do I need a star tracker for panorama stitching?</h3>
<p class="wp-block-paragraph">No. A tracker lets you take longer single exposures, but a stitched panorama is built from short, untracked frames — the 500-rule exposures — which is exactly what Hugin is stitching here.</p>
<script type="application/ld+json">{"@context": "https://schema.org", "@type": "FAQPage", "mainEntity": [{"@type": "Question", "name": "Why can't Hugin find control points in my night photos?", "acceptedAnswer": {"@type": "Answer", "text": "CPFind matches visible detail, and dark sky frames offer very little: faint stars and a lot of noise. Place control points manually on the same bright stars in both frames \u2014 around a dozen per pair is plenty \u2014 and anchor the panorama on the foreground frames first."}}, {"@type": "Question", "name": "What focal length is best for a Milky Way panorama?", "acceptedAnswer": {"@type": "Answer", "text": "Wide: roughly 14\u201324mm (full-frame equivalent) is the usual working range. Wider lenses capture more sky per frame and allow longer exposures under the 500 rule, which is why fast wide primes are the classic choice."}}, {"@type": "Question", "name": "Can I stitch a Milky Way panorama from a single row?", "acceptedAnswer": {"@type": "Answer", "text": "Yes, if the arc fits in one row's vertical field of view \u2014 common with very wide lenses in portrait orientation. Multi-row arcs capture taller compositions and more foreground, at the cost of more frames to align."}}, {"@type": "Question", "name": "Do I need a star tracker for panorama stitching?", "acceptedAnswer": {"@type": "Answer", "text": "No. A tracker lets you take longer single exposures, but a stitched panorama is built from short, untracked frames \u2014 the 500-rule exposures \u2014 which is exactly what Hugin is stitching here."}}]}</script>]]></content:encoded>
					
					<wfw:commentRss>https://huginpanorama.com/milky-way-panorama/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>Batch Stitching in Hugin: PTBatcherGUI &#038; hugin_executor Guide</title>
		<link>https://huginpanorama.com/hugin-batch-stitching/</link>
					<comments>https://huginpanorama.com/hugin-batch-stitching/#respond</comments>
		
		<dc:creator><![CDATA[Admin]]></dc:creator>
		<pubDate>Wed, 21 Oct 2026 02:41:57 +0000</pubDate>
				<category><![CDATA[Tutorials]]></category>
		<guid isPermaLink="false">https://huginpanorama.com/hugin-batch-stitching/</guid>

					<description><![CDATA[Quick answer: Prepare each panorama as a saved Hugin project (.pto), add the projects to the PTBatcherGUI queue, and start the queue: it stitches them one after another, unattended, reporting success or failure per job. For scripted or repeated work, hugin_executor does the same job from the command line — it can run a project...]]></description>
										<content:encoded><![CDATA[<p class="wp-block-paragraph"><strong>Quick answer:</strong> Prepare each panorama as a saved Hugin project (.pto), add the projects to the PTBatcherGUI queue, and start the queue: it stitches them one after another, unattended, reporting success or failure per job. For scripted or repeated work, hugin_executor does the same job from the command line — it can run a project file to completion, and can also run the Assistant workflow on a set of images. Batch stitching turns Hugin from an interactive tool into a render farm of one.</p>
<h2 class="wp-block-heading">Why batch at all</h2>
<p class="wp-block-paragraph">Interactive stitching is fast for one panorama and wasteful for twenty: every render keeps you at the keyboard answering the same dialogs while the CPU does the real work in bursts. Real workloads are bursty in the other direction — a day of shooting virtual tours, a season of real-estate sets, a <a href="/gigapixel-panorama/">gigapixel grid</a> that renders for hours. The batch pattern separates deciding from rendering: you align and approve every project while you are fresh, save them all, and let the queue render them overnight. It is also the safer pattern for big jobs, because a render that fails at 3 a.m. fails as one queue entry with a status message, not as a lost afternoon.</p>
<h2 class="wp-block-heading">Prepare projects the queue can trust</h2>
<p class="wp-block-paragraph">PTBatcherGUI stitches project files, not loose photos, so the preparation step is: build each panorama in Hugin as usual — Assistant or Advanced — check the preview carefully, set the output in the Stitcher tab, and save the .pto project into the folder where the render should land. Everything the render needs is frozen into that file: photos, control points, projection, canvas size, output format. The rule of batch work is that the queue renders exactly what you approved, including your mistakes: a tilted horizon renders tilted, at scale. Preview discipline from our <a href="/how-to-use-hugin/">step-by-step tutorial</a> matters more here, not less. One practical habit: render one representative project interactively first, confirm the output settings and file sizes are what you expect, then clone that pattern across the rest.</p>
<h2 class="wp-block-heading">Run the queue in PTBatcherGUI</h2>
<p class="wp-block-paragraph">Open PTBatcherGUI — it installs alongside Hugin and PT stands for Panorama Tools — and add your saved projects to its list. The queue processes projects sequentially: for each one it runs the full stitch (remapping with nona, blending with Enblend) using the settings stored in the project, writes the output next to the project or as configured, and marks the entry with its outcome before moving on. You can add projects while it works, remove ones that have not started, and leave it running with the machine unattended. Sequential processing is deliberate: a single render can already saturate CPU and disk, so parallel renders would mostly contend for the same resources. When you return, the queue is your report — completed entries, and failures flagged per project rather than discovered one panorama at a time.</p>
<h2 class="wp-block-heading">hugin_executor: the command-line route</h2>
<p class="wp-block-paragraph">Everything the queue does can also be driven from a terminal with hugin_executor, Hugin&#8217;s command-line stitching tool. Its two modes cover the whole batch story: give it a project file and it stitches that project exactly as PTBatcherGUI would; give it a set of image files and it runs the Assistant on them — loading, aligning and producing a rendered panorama from the photos directly. That second mode powers scripted pipelines: a shell script that walks a folder tree of the day&#8217;s shoots, runs the Assistant per folder, and leaves rendered drafts waiting for review in the morning. Command-line runs also log what they did, which makes failures diagnosable after the fact: the log shows which stage (control points, optimization, remapping, blending) a scripted job died in. Exact options are documented in the tool&#8217;s own help and the Hugin manual; start with the project-file mode, which mirrors the GUI queue, before automating Assistant runs.</p>
<h2 class="wp-block-heading">Overnight renders without babysitting</h2>
<ul class="wp-block-list"><li><strong>Disk first:</strong> batch jobs multiply intermediate files. Keep several times the expected output size free, on the drive the projects live on — running dry mid-queue fails every remaining job, not just the current one.</li><li><strong>Power and sleep:</strong> disable system sleep for the render machine, or the queue pauses politely until morning and so does your deadline.</li><li><strong>Order matters:</strong> put the most important or most uncertain project first, so if anything goes wrong it goes wrong early and visibly.</li><li><strong>Draft then master:</strong> for review-heavy work, batch a set of small draft renders first, approve them on screen, then queue the full-resolution renders of the approved projects only.</li></ul>
<h2 class="wp-block-heading">Draft queues: the pattern for review-heavy work</h2>
<p class="wp-block-paragraph">The most useful batch habit is two-stage rendering. First, queue every project at a small draft size and let the machine produce a complete set of previews overnight. Review the drafts on screen in the morning — this is where tilted horizons, missed frames and bad nadirs are cheap to catch — and fix only the projects that need it. Then queue the approved projects at full size for the following night. The draft pass costs a fraction of one full render and routinely saves several. This pattern is how tour and real-estate shooters keep a day of shooting from becoming a week of rendering: the computer, not the photographer, spends the hours, and the photographer&#8217;s judgement is spent once, on finished-looking drafts, instead of repeatedly on settings dialogs.</p>
<p class="wp-block-paragraph">Keep the queue&#8217;s world tidy: one folder per job, projects and their renders side by side, source photos untouched after alignment. Batch rendering punishes improvisation — a renamed folder breaks a dozen queued projects at once — and rewards boring, consistent file management more than any cleverness.</p>
<h2 class="wp-block-heading">When a queued job fails</h2>
<p class="wp-block-paragraph">A failed entry usually repeats a failure you can reproduce interactively in a minute: open that project in Hugin and run the Assistant&#8217;s steps by hand. The usual causes are mundane — a moved or renamed source photo, a full disk, control points that never covered one frame, or an output path that no longer exists. Fix the project, re-add it to the queue, and move on; do not re-queue its neighbours, which rendered fine. Persistent failures on very large projects point at memory and temp space, and the cache and disk guidance in our gigapixel guide applies directly.</p>
<h2 class="wp-block-heading">FAQ</h2>
<h3 class="wp-block-heading">What is PTBatcherGUI?</h3>
<p class="wp-block-paragraph">It is the batch queue program that ships with Hugin. You add saved project files to its list and it stitches them one after another, unattended, marking each job&#8217;s outcome. It renders the settings stored in each project file.</p>
<h3 class="wp-block-heading">Can Hugin stitch a folder of photos without opening the GUI?</h3>
<p class="wp-block-paragraph">Yes, with hugin_executor from the command line: in its Assistant mode it loads a set of images, aligns them and renders a panorama. In its project mode it stitches a saved .pto file exactly like the batch queue does.</p>
<h3 class="wp-block-heading">Should I run several batch jobs in parallel to finish sooner?</h3>
<p class="wp-block-paragraph">Generally no. One render already loads the CPU and disk heavily; parallel renders compete for the same resources and can run slower overall, as well as multiplying temp-disk pressure. The queue&#8217;s sequential processing is the efficient pattern.</p>
<h3 class="wp-block-heading">Why did my queued render fail overnight?</h3>
<p class="wp-block-paragraph">The common causes are a full disk (batch intermediates are large), a source photo that moved, or a project whose alignment was never sound. Open the project interactively — the same failure usually reproduces immediately and points at its cause.</p>
<script type="application/ld+json">{"@context": "https://schema.org", "@type": "FAQPage", "mainEntity": [{"@type": "Question", "name": "What is PTBatcherGUI?", "acceptedAnswer": {"@type": "Answer", "text": "It is the batch queue program that ships with Hugin. You add saved project files to its list and it stitches them one after another, unattended, marking each job's outcome. It renders the settings stored in each project file."}}, {"@type": "Question", "name": "Can Hugin stitch a folder of photos without opening the GUI?", "acceptedAnswer": {"@type": "Answer", "text": "Yes, with hugin_executor from the command line: in its Assistant mode it loads a set of images, aligns them and renders a panorama. In its project mode it stitches a saved .pto file exactly like the batch queue does."}}, {"@type": "Question", "name": "Should I run several batch jobs in parallel to finish sooner?", "acceptedAnswer": {"@type": "Answer", "text": "Generally no. One render already loads the CPU and disk heavily; parallel renders compete for the same resources and can run slower overall, as well as multiplying temp-disk pressure. The queue's sequential processing is the efficient pattern."}}, {"@type": "Question", "name": "Why did my queued render fail overnight?", "acceptedAnswer": {"@type": "Answer", "text": "The common causes are a full disk (batch intermediates are large), a source photo that moved, or a project whose alignment was never sound. Open the project interactively \u2014 the same failure usually reproduces immediately and points at its cause."}}]}</script>]]></content:encoded>
					
					<wfw:commentRss>https://huginpanorama.com/hugin-batch-stitching/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>Hugin Lens Calibration: Fix Barrel Distortion with calibrate_lens_gui</title>
		<link>https://huginpanorama.com/hugin-lens-calibration/</link>
					<comments>https://huginpanorama.com/hugin-lens-calibration/#respond</comments>
		
		<dc:creator><![CDATA[Admin]]></dc:creator>
		<pubDate>Wed, 21 Oct 2026 02:41:36 +0000</pubDate>
				<category><![CDATA[Tutorials]]></category>
		<guid isPermaLink="false">https://huginpanorama.com/hugin-lens-calibration/</guid>

					<description><![CDATA[Quick answer: Photograph a scene full of long straight lines (a building facade works well) with the lens you want to calibrate, load the photo into Hugin&#8217;s calibrate_lens_gui tool, let it detect the lines and mark how they should straighten, and optimize: the tool computes your lens&#8217;s distortion parameters (a, b and c) and field...]]></description>
										<content:encoded><![CDATA[<p class="wp-block-paragraph"><strong>Quick answer:</strong> Photograph a scene full of long straight lines (a building facade works well) with the lens you want to calibrate, load the photo into Hugin&#8217;s calibrate_lens_gui tool, let it detect the lines and mark how they should straighten, and optimize: the tool computes your lens&#8217;s distortion parameters (a, b and c) and field of view. Save the result to Hugin&#8217;s lens database and every future panorama with that lens starts from measured, not guessed, geometry.</p>
<h2 class="wp-block-heading">Why calibration matters for stitching</h2>
<p class="wp-block-paragraph">Every real lens bends the world a little: straight lines bow outward (barrel distortion) or inward (pincushion distortion), most strongly towards the edges of the frame. A stitcher needs to undo that bend before it can fit photos together, because two frames whose edges curve differently cannot agree on where a shared feature sits. Hugin models the bend with the a, b and c parameters of its lens model, plus the field of view. It can estimate these during optimization from your panorama&#8217;s control points — and for forgiving subjects that estimate is fine — but a measured calibration is better data: control points fit tighter, horizons straighten more reliably, and grids of many frames stop drifting. The effect is largest exactly where stitching is hardest, with wide-angle and fisheye lenses at frame edges. If your panoramas show a stubborn wavy horizon or seams that never quite line up, calibration is a prime suspect; the general troubleshooting flow is in our <a href="/how-to-use-hugin/">step-by-step tutorial</a>.</p>
<h2 class="wp-block-heading">What calibrate_lens_gui does</h2>
<p class="wp-block-paragraph">calibrate_lens_gui ships with Hugin as a standalone tool dedicated to this one job. Its method is the straight-line approach: in an undistorted photo, lines that are straight in the world — building edges, window frames, tiles, a horizon — must come out straight. The tool detects long edges in your calibration photo, you confirm or adjust which detected lines to trust, and the optimizer then solves for the lens parameters that make all of them straight at once, along with the field of view. The output is a lens entry you can save into Hugin&#8217;s own lens database, keyed to your camera and lens, ready to be loaded when a project uses that lens. Hugin maintains this database itself — it is the project&#8217;s own store of lens data, accumulated from calibrations like yours.</p>
<h2 class="wp-block-heading">Shoot a good calibration photo</h2>
<p class="wp-block-paragraph">The input photo decides the quality of the result. You need:</p>
<ul class="wp-block-list"><li><strong>Long straight lines in several directions</strong> — horizontal, vertical and ideally diagonal — spread across the whole frame, especially near the edges and corners where distortion lives. A large building facade, a tiled wall, or a modern office front is ideal.</li><li><strong>The exact lens and focal length you stitch with.</strong> Zoom lenses need a calibration per focal length you actually use; a calibration measured at 24 mm says nothing about 35 mm.</li><li><strong>Focus and aperture as you shoot panoramas.</strong> Distortion shifts slightly with focus distance; calibrate at a typical working distance, not at a wall two metres away if your panoramas are landscapes. Take several shots from slightly different positions and calibrate from the best.</li></ul>
<p class="wp-block-paragraph">Avoid scenes whose &#8220;straight&#8221; lines are not: old timber buildings, wavy fences and wide rivers make poor rulers. The shooting discipline overlaps with normal panorama prep — more in our <a href="/shooting-panoramas-for-hugin/">shooting guide</a>.</p>
<h2 class="wp-block-heading">Run the calibration</h2>
<ol class="wp-block-list"><li>Launch calibrate_lens_gui and load your calibration photo (or photos — multiple images of line-rich scenes can be combined).</li><li>Let the tool detect lines, then review them: keep long, genuinely straight edges that reach towards the corners; delete detections along shadows, cables or anything actually curved.</li><li>Run the optimization. The tool adjusts the a, b and c distortion parameters and the field of view until the selected lines straighten. Inspect the corrected preview: the lines should look ruler-straight without the image warping grotesquely at the corners.</li><li>Save the lens to the lens database with a recognisable name (camera + lens + focal length). In future Hugin projects, load these parameters when the EXIF identifies that lens, instead of starting from defaults.</li></ol>
<h2 class="wp-block-heading">Fisheye notes</h2>
<p class="wp-block-paragraph">Fisheyes are the special case. Their &#8220;distortion&#8221; is mostly not a defect but a different projection — the image is supposed to look bent — so the straight-line method must be told it is dealing with a fisheye lens type, and the goal shifts from &#8220;make it look rectilinear&#8221; to &#8220;measure the exact mapping so the stitcher can reproject it correctly&#8221;. Lines near the very edge of a circular fisheye&#8217;s image circle are the most informative and the most fragile; include them if they are sharp. For stitching work such as 360 sets and <a href="/gigapixel-panorama/">multi-row grids</a>, a fisheye or wide lens calibrated once will quietly improve every project that follows.</p>
<h2 class="wp-block-heading">Verify the calibration on a real panorama</h2>
<p class="wp-block-paragraph">Do not trust a calibration because the tool accepted it — test it the way it will be used. Stitch a familiar test set with the saved lens entry loaded and compare against the same set stitched from defaults: control points should fit with a smaller average error, the horizon should sit straighter in the preview, and straight architecture near the frame edges should stop bowing. If results get worse, the calibration photo was the problem — usually lines that were not truly straight, or too few lines near the corners — and re-shooting it beats tweaking numbers. Keep the calibration photo itself archived with a note of the lens and focal length; when you later wonder which measurement a database entry came from, the photo answers.</p>
<p class="wp-block-paragraph">One calibration per configuration is the rule: change the focal length, the focus distance regime or the camera body behind an adapted lens, and you have a new configuration that deserves its own entry in the database rather than borrowing the old one.</p>
<h2 class="wp-block-heading">When calibration is not the answer</h2>
<p class="wp-block-paragraph">Calibration fixes geometry, not photography. Parallax from rotating around the wrong point, moving subjects, and exposure jumps will still ruin stitches with a perfectly calibrated lens — those are capture problems, covered in the shooting guide. And small residual errors are normal: Hugin&#8217;s optimizer still fine-tunes parameters per project, now starting from your measured values instead of from zero. Think of calibration as giving the optimizer a head start it can trust.</p>
<h2 class="wp-block-heading">FAQ</h2>
<h3 class="wp-block-heading">What are Hugin&#8217;s a, b and c lens parameters?</h3>
<p class="wp-block-paragraph">They are the coefficients of Hugin&#8217;s lens distortion model: together they describe how strongly your lens bends straight lines at increasing distances from the image centre. calibrate_lens_gui measures them from photos of straight-lined scenes.</p>
<h3 class="wp-block-heading">Do I need to calibrate every lens I own?</h3>
<p class="wp-block-paragraph">Only the ones you stitch with, at the focal lengths you stitch at. Prime lenses need one calibration each; zooms need one per focal length you use. The saved lens database entry is reused across all future projects.</p>
<h3 class="wp-block-heading">Can I calibrate a lens from an existing panorama photo?</h3>
<p class="wp-block-paragraph">If it contains long, reliably straight lines reaching the corners, yes — a facade shot from a previous set can serve. A dedicated calibration photo with lines in several directions across the frame gives a cleaner result.</p>
<h3 class="wp-block-heading">Does Hugin use the Lensfun database?</h3>
<p class="wp-block-paragraph">No. Hugin keeps its own lens database, built from calibrations performed with its tools. Entries you save with calibrate_lens_gui live in that database and are applied to your projects directly.</p>
<script type="application/ld+json">{"@context": "https://schema.org", "@type": "FAQPage", "mainEntity": [{"@type": "Question", "name": "What are Hugin's a, b and c lens parameters?", "acceptedAnswer": {"@type": "Answer", "text": "They are the coefficients of Hugin's lens distortion model: together they describe how strongly your lens bends straight lines at increasing distances from the image centre. calibrate_lens_gui measures them from photos of straight-lined scenes."}}, {"@type": "Question", "name": "Do I need to calibrate every lens I own?", "acceptedAnswer": {"@type": "Answer", "text": "Only the ones you stitch with, at the focal lengths you stitch at. Prime lenses need one calibration each; zooms need one per focal length you use. The saved lens database entry is reused across all future projects."}}, {"@type": "Question", "name": "Can I calibrate a lens from an existing panorama photo?", "acceptedAnswer": {"@type": "Answer", "text": "If it contains long, reliably straight lines reaching the corners, yes \u2014 a facade shot from a previous set can serve. A dedicated calibration photo with lines in several directions across the frame gives a cleaner result."}}, {"@type": "Question", "name": "Does Hugin use the Lensfun database?", "acceptedAnswer": {"@type": "Answer", "text": "No. Hugin keeps its own lens database, built from calibrations performed with its tools. Entries you save with calibrate_lens_gui live in that database and are applied to your projects directly."}}]}</script>]]></content:encoded>
					
					<wfw:commentRss>https://huginpanorama.com/hugin-lens-calibration/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>Little Planet Photos in Hugin: Stereographic Projection Tutorial</title>
		<link>https://huginpanorama.com/little-planet-tutorial/</link>
					<comments>https://huginpanorama.com/little-planet-tutorial/#respond</comments>
		
		<dc:creator><![CDATA[Admin]]></dc:creator>
		<pubDate>Wed, 21 Oct 2026 02:41:14 +0000</pubDate>
				<category><![CDATA[Tutorials]]></category>
		<guid isPermaLink="false">https://huginpanorama.com/little-planet-tutorial/</guid>

					<description><![CDATA[Quick answer: A little planet is a stereographic reprojection of a full 360×180 panorama. Take a finished equirectangular image (or the original 360 project) in Hugin, set the projection to Stereographic, rotate the view so the ground — the nadir — sits in the centre, choose a square-ish canvas, and render. If your source does...]]></description>
										<content:encoded><![CDATA[<p class="wp-block-paragraph"><strong>Quick answer:</strong> A little planet is a stereographic reprojection of a full 360×180 panorama. Take a finished equirectangular image (or the original 360 project) in Hugin, set the projection to Stereographic, rotate the view so the ground — the nadir — sits in the centre, choose a square-ish canvas, and render. If your source does not cover the whole sphere, the planet gets a hole or a torn edge; full-sphere input is the whole secret.</p>
<h2 class="wp-block-heading">What a little planet actually is</h2>
<p class="wp-block-paragraph">The &#8220;little planet&#8221; (or tiny planet) look wraps the world into a floating ball: the ground becomes a disc in the middle, buildings and trees sprout from its edge, and the sky wraps around the outside. It is not a filter — it is the stereographic projection, a mathematically respectable way of flattening a sphere that happens to look delightful. Hugin includes Stereographic among its output projections, so if you already have a 360 panorama project, you own everything needed. If you do not have a 360 set yet, start with our <a href="/stitch-360-panorama/">360 stitching guide</a>; a little planet is a five-minute detour at the end of that workflow, not a separate discipline.</p>
<h2 class="wp-block-heading">Start from a full-sphere source</h2>
<p class="wp-block-paragraph">The requirement that makes or breaks the effect: the source must cover the entire sphere, 360×180 degrees. A wide but partial panorama cannot wrap into a closed ball — the missing sky or ground becomes a wedge-shaped gap or a smeared pole. Two ways in:</p>
<ul class="wp-block-list"><li><strong>From a 360 project:</strong> open the saved .pto project you stitched the equirectangular from, and simply change the output — the original photos give you the best quality.</li><li><strong>From a finished equirectangular file:</strong> create a new project, add the equirectangular image as a single photo, and set its lens type to Equirectangular with a 360-degree field of view. Hugin now treats the file as a complete sphere it can reproject.</li></ul>
<p class="wp-block-paragraph">Either way, check the nadir before you start: whatever is at the bottom of the sphere becomes the centre of your planet, so a visible tripod sits right in the middle of the picture. Patch it first — see our <a href="/remove-tripod-nadir-patch/">nadir patching guide</a> — or plan a composition where the centre is plain ground.</p>
<h2 class="wp-block-heading">Set the stereographic projection</h2>
<p class="wp-block-paragraph">Open the Fast Preview window and set the output projection to Stereographic. The sphere collapses into a disc as you watch. Now rotate the view: you want to look straight down at the nadir, so adjust the pitch by 90 degrees — using the drag tools or the numerical rotation in the preview — until the ground occupies the centre and the horizon forms a ring around it. (Rotate the other way and you get the inverted variant, a &#8220;tunnel&#8221; or &#8220;tube&#8221; view with the sky in the centre — a legitimate effect in its own right, and a useful signpost that you turned the sphere the wrong way.) Roll rotates the planet in its frame; use it to place a dominant feature — a road, a river, the shoreline — where you want it in the composition.</p>
<h2 class="wp-block-heading">Frame and size the canvas</h2>
<p class="wp-block-paragraph">In the Stitcher tab, choose the canvas. Square formats suit the classic planet; a wider canvas leaves sky around a smaller ball, a tighter canvas crops the ball&#8217;s edge into an abstract ring. Resolution follows your source: you cannot invent pixels, and the stereographic mapping spends most of them on the centre, so start from the largest equirectangular you have. Keep the projection&#8217;s field of view at the full sphere; trimming it zooms the planet but quickly exposes the edge artefacts discussed below. Render a TIFF master as usual, per the workflow in our <a href="/how-to-use-hugin/">main tutorial</a>, and export JPG copies for sharing.</p>
<h2 class="wp-block-heading">Common failures and fixes</h2>
<ul class="wp-block-list"><li><strong>A wedge is missing or the ball will not close:</strong> the source was not a full 360×180 sphere. Re-shoot or re-stitch including zenith and nadir frames; there is no setting that substitutes for missing coverage.</li><li><strong>The centre is a smeared starburst:</strong> that is the pole of your equirectangular being magnified. A clean, well-covered nadir (ideally a dedicated nadir frame) keeps the centre sharp; a clear sky at the zenith smears less noticeably than detailed ground does at the nadir.</li><li><strong>The horizon ring is wavy:</strong> the source panorama was not level. Level the sphere in the original project first — a tilted horizon becomes a lopsided planet.</li><li><strong>Buildings at the edge bend oddly:</strong> inherent to stereographic mapping at extreme angles. Choosing a different roll, or a slightly smaller field of view, moves the worst distortion away from your subject.</li></ul>
<h2 class="wp-block-heading">Little planets from drone and travel shots</h2>
<p class="wp-block-paragraph">Some of the most-shared little planets start as drone panoramas: a full sphere captured above a coastline, a village or a landmark, where the ground pattern itself is the picture. The Hugin workflow is unchanged — the drone&#8217;s stitched equirectangular, or its source frames if you stitch them yourself, becomes the input sphere — but the centre of the planet is now the landscape directly below the drone rather than a tripod patch, so the nadir problem mostly disappears and roads, rivers and field boundaries draw the composition for you. Travel photography is the other natural source: one 360 set from a viewpoint, a market square or a temple courtyard yields the conventional tour panorama for your archive and the planet for sharing, from the same shutter presses.</p>
<p class="wp-block-paragraph">For sharing, export the planet at a generous size — social platforms compress aggressively, and the fine detail at the planet&#8217;s edge suffers first — and keep the square crop. If the centrepiece of the ball is a recognisable place, a small caption naming it outperforms the image alone, because viewers read the planet as abstract until the location clicks.</p>
<h2 class="wp-block-heading">Ideas worth stealing</h2>
<p class="wp-block-paragraph">Little planets reward strong geometry: a beach with a clean shoreline, a plaza with radial paving, a forest clearing, a sports field with painted lines. City squares work beautifully because the architecture rings the planet like a crown. Keep one dominant vertical — a tower, a lighthouse, a single tree — and roll the view so it stands at the top of the ball. And keep the full-sphere project: from the same source you can render the normal equirectangular, the planet, and the tunnel, which makes one shoot produce a small series instead of a single image.</p>
<h2 class="wp-block-heading">FAQ</h2>
<h3 class="wp-block-heading">Can I make a little planet from a normal (non-360) panorama?</h3>
<p class="wp-block-paragraph">Not a closed one. Stereographic reprojection needs the full 360×180 sphere; a partial panorama leaves a wedge-shaped gap where the missing coverage belongs. Shoot or stitch a complete sphere first.</p>
<h3 class="wp-block-heading">Which projection does Hugin use for little planets?</h3>
<p class="wp-block-paragraph">Stereographic. Set it as the output projection in the Fast Preview, rotate the sphere so the nadir is centred, and render. The opposite rotation produces the inverted &#8220;tunnel&#8221; look.</p>
<h3 class="wp-block-heading">Why is the middle of my planet blurry?</h3>
<p class="wp-block-paragraph">The centre of the planet is the nadir of your panorama, where equirectangular pixels are most stretched and coverage is thinnest — especially if the tripod area was never properly photographed. A dedicated nadir frame fixes it.</p>
<h3 class="wp-block-heading">What canvas size works best for a little planet?</h3>
<p class="wp-block-paragraph">Start square, at the full resolution your source supports. The stereographic projection concentrates detail in the centre, so a larger source equirectangular (8000×4000 or more) gives noticeably cleaner planets.</p>
<script type="application/ld+json">{"@context": "https://schema.org", "@type": "FAQPage", "mainEntity": [{"@type": "Question", "name": "Can I make a little planet from a normal (non-360) panorama?", "acceptedAnswer": {"@type": "Answer", "text": "Not a closed one. Stereographic reprojection needs the full 360\u00d7180 sphere; a partial panorama leaves a wedge-shaped gap where the missing coverage belongs. Shoot or stitch a complete sphere first."}}, {"@type": "Question", "name": "Which projection does Hugin use for little planets?", "acceptedAnswer": {"@type": "Answer", "text": "Stereographic. Set it as the output projection in the Fast Preview, rotate the sphere so the nadir is centred, and render. The opposite rotation produces the inverted \"tunnel\" look."}}, {"@type": "Question", "name": "Why is the middle of my planet blurry?", "acceptedAnswer": {"@type": "Answer", "text": "The centre of the planet is the nadir of your panorama, where equirectangular pixels are most stretched and coverage is thinnest \u2014 especially if the tripod area was never properly photographed. A dedicated nadir frame fixes it."}}, {"@type": "Question", "name": "What canvas size works best for a little planet?", "acceptedAnswer": {"@type": "Answer", "text": "Start square, at the full resolution your source supports. The stereographic projection concentrates detail in the centre, so a larger source equirectangular (8000\u00d74000 or more) gives noticeably cleaner planets."}}]}</script>]]></content:encoded>
					
					<wfw:commentRss>https://huginpanorama.com/little-planet-tutorial/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>Gigapixel Panoramas with Hugin: Multi-Row Shooting &#038; Stitching</title>
		<link>https://huginpanorama.com/gigapixel-panorama/</link>
					<comments>https://huginpanorama.com/gigapixel-panorama/#respond</comments>
		
		<dc:creator><![CDATA[Admin]]></dc:creator>
		<pubDate>Wed, 21 Oct 2026 02:40:53 +0000</pubDate>
				<category><![CDATA[Tutorials]]></category>
		<guid isPermaLink="false">https://huginpanorama.com/gigapixel-panorama/</guid>

					<description><![CDATA[Quick answer: A gigapixel panorama is just a very disciplined multi-row panorama: shoot a grid of overlapping frames with a longer lens, let CPFind&#8217;s multirow alignment and the optimizer solve the grid in Hugin, raise Enblend&#8217;s memory cache for the render, make sure you have several times the final file size free as temporary disk...]]></description>
										<content:encoded><![CDATA[<p class="wp-block-paragraph"><strong>Quick answer:</strong> A gigapixel panorama is just a very disciplined multi-row panorama: shoot a grid of overlapping frames with a longer lens, let CPFind&#8217;s multirow alignment and the optimizer solve the grid in Hugin, raise Enblend&#8217;s memory cache for the render, make sure you have several times the final file size free as temporary disk space, and queue the job in PTBatcherGUI so it can grind away unattended. The stitching pipeline is identical to a small panorama — only the discipline and the logistics change.</p>
<h2 class="wp-block-heading">Plan the grid before you shoot</h2>
<p class="wp-block-paragraph">Gigapixel images are made with focal lengths that would be absurd for a single-row panorama — moderate telephotos that see a small slice of the scene per frame. Work backwards from the print or the zoom experience you want: decide the final pixel dimensions first, then the focal length and grid follow. A 100-frame grid at 25–50% overlap is unremarkable; large projects run to many hundreds of frames in regular rows and columns. Regularity is the point: a pano head with click stops, or careful manual stepping, so every frame has neighbours on all four sides. Missing one frame leaves a hole that no amount of processing fills, so overlap generously and shoot a few spare frames at the edges. The camera discipline — manual exposure, focus and white balance, rotation around the entrance pupil — is the same as for any Hugin set, and is laid out in our <a href="/shooting-panoramas-for-hugin/">shooting guide</a>.</p>
<h2 class="wp-block-heading">Shoot the grid</h2>
<p class="wp-block-paragraph">Work row by row, in a consistent serpentine or a strict left-to-right pattern you can keep track of, and keep the camera level as the rows stack. Telephoto frames have shallow depth of field and show focus errors cruelly at gigapixel zoom levels, so focus carefully once — on a mid-distance subject — and lock it. Watch the light: a grid takes minutes to shoot, and moving clouds change the scene between the first and last frame, printing a patchwork of brightness into the sky. On changeable days, shoot faster, or accept the sky as it is and rely on the photometric correction to smooth the steps. Bracket only if you truly need the dynamic range; brackets multiply the frame count and the render time by the same factor.</p>
<h2 class="wp-block-heading">Focus and depth of field at telephoto lengths</h2>
<p class="wp-block-paragraph">Telephoto frames magnify focus errors as surely as they magnify the scene. A gigapixel viewer invites the audience to zoom to 100%, where a frame focused a metre too close announces itself as a soft patch in the mosaic. Focus once, deliberately, at a distance that keeps both the subject plane and the important detail inside depth of field at your chosen aperture — then lock focus and do not let the camera refocus between frames. If the scene has genuinely near and far layers, a mid-distance focus at a moderate aperture is the compromise; focus stacking a grid multiplies an already large job beyond reason. Check the first and last frames of the shoot at full magnification on the camera before you pack up: focus drift across a long grid is a reshoot, not a repair.</p>
<h2 class="wp-block-heading">Align a grid in Hugin</h2>
<p class="wp-block-paragraph">Load the whole set into one project. This is the workload CPFind&#8217;s current default was designed for: since 2024 it defaults to the multirow strategy, matching each image against its grid neighbours instead of every image against every other, which keeps alignment time sane on hundreds of frames (the older all-pairs behaviour remains available as an option). The optimizer then solves the grid as one rigid puzzle — and rigidity is your friend: if the shooting was regular, misfits show up as isolated bad pairs you can inspect in the control-point editor, rather than global warping. Calibrating the lens beforehand pays off disproportionately here: a small distortion error, repeated across a hundred frames, becomes visible drift at the far side of the grid. Our <a href="/hugin-lens-calibration/">lens calibration guide</a> shows how to measure your lens&#8217;s distortion parameters once and reuse them.</p>
<h2 class="wp-block-heading">Memory, cache and temp disk: the real bottlenecks</h2>
<p class="wp-block-paragraph">Rendering a gigapixel panorama is an exercise in moving data. Enblend blends the remapped frames in strips and keeps a memory cache — by default 1 GB — which you can raise in the preferences for very large jobs so it swaps less. Temporary disk space is the usual hard limit: the intermediate remapped images (nona writes one per source frame, at output resolution) plus the final file can require several times the size of the finished panorama, on top of your source photos. Put the project and its temp files on your fastest, emptiest drive, and check free space before you start, not after hour three. RAM pressure shows up as a render that crawls rather than fails — if the machine is swapping, a bigger Enblend cache makes it worse, not better; balance the cache against the memory nona and the operating system need. GPU remapping in Hugin remains experimental, so plan on CPU time and patience.</p>
<h2 class="wp-block-heading">Queue it and walk away</h2>
<p class="wp-block-paragraph">Gigapixel renders are the textbook case for the batch queue. Save the aligned project, add it to PTBatcherGUI, and let it process unattended — overnight is a legitimate schedule for a big grid. The full queue workflow, including running several projects back to back, is in our <a href="/hugin-batch-stitching/">batch stitching guide</a>. When the render completes, inspect the output systematically at 100%: sweep the seams in a grid pattern of your own, because a single misaligned frame hides in a gigapixel file like a typo in a novel. If one frame is wrong, fix that frame&#8217;s control points in the saved project and re-render — the project file is the asset; the render is a printout.</p>
<h2 class="wp-block-heading">Output size planning</h2>
<p class="wp-block-paragraph">Decide the deliverable before rendering, because re-rendering is the expensive step. A web zoom viewer wants tiles derived from a big master; print wants the full-resolution TIFF at final size. Render the master once, at the full solved resolution, as a TIFF, and derive everything else from it. Resist rendering at a guessed &#8220;probably enough&#8221; size: with the project saved you can re-render, but a fresh full render is hours, while a downscale from the master is minutes. The general render settings workflow is the same as in our <a href="/how-to-use-hugin/">step-by-step tutorial</a> — only the numbers get bigger.</p>
<h2 class="wp-block-heading">After the stitch: upscaling for print</h2><p class="wp-block-paragraph">One expectation to set before you fall in love with the render button: Hugin outputs your panorama at the resolution your source photos support — it assembles pixels brilliantly, but it does not invent new ones. When a gigapixel stitch is destined for a very large print, a gallery wrap, or a client who keeps asking for &#8216;a bit bigger&#8217;, the standard finishing step is a dedicated AI upscaler, and the one most panorama shooters use is Topaz Gigapixel: it enlarges the finished TIFF with detail reconstruction that plain interpolation cannot match, and it is far better applied once, to the flat master, than to individual frames before stitching. Topaz lists its Personal plan at $149/year ($12/month billed annually) on its site (checked 21 October 2026) — see <a href="/go/topaz" rel="nofollow sponsored noopener">Topaz Gigapixel</a> (affiliate link — we&#8217;re reader-supported; see our <a href="/disclaimer/">disclaimer</a>). Upscaling is a finishing luxury, not a stitching requirement: get the master right first, and only then decide whether the print size truly needs more pixels than you captured.</p><h2 class="wp-block-heading">FAQ</h2>
<h3 class="wp-block-heading">How many photos does a gigapixel panorama need?</h3>
<p class="wp-block-paragraph">It depends on the lens and the target size. With a moderate telephoto and 25–50% overlap, a gigapixel-class result typically means one to several hundred frames in a regular grid. The frame count follows from your final pixel dimensions, not the other way round.</p>
<h3 class="wp-block-heading">Why does my gigapixel render run out of space or crawl?</h3>
<p class="wp-block-paragraph">Intermediate files. nona writes a remapped image per source frame at full output resolution, and Enblend needs scratch room too — several times the final file size is a realistic temp-space budget. A render that crawls is usually swapping; check RAM and the Enblend cache setting.</p>
<h3 class="wp-block-heading">What Enblend cache should I set for a very large panorama?</h3>
<p class="wp-block-paragraph">The default cache is 1 GB. Raising it in the preferences helps Enblend swap less on big jobs, but only up to the free RAM you actually have — an oversized cache forces the operating system to swap instead, which is slower.</p>
<h3 class="wp-block-heading">Can Hugin use my GPU to render faster?</h3>
<p class="wp-block-paragraph">Hugin&#8217;s GPU remapping (via nona) is experimental and not a reliable production path. Plan gigapixel renders around CPU time, temp disk and the batch queue.</p>
<script type="application/ld+json">{"@context": "https://schema.org", "@type": "FAQPage", "mainEntity": [{"@type": "Question", "name": "How many photos does a gigapixel panorama need?", "acceptedAnswer": {"@type": "Answer", "text": "It depends on the lens and the target size. With a moderate telephoto and 25\u201350% overlap, a gigapixel-class result typically means one to several hundred frames in a regular grid. The frame count follows from your final pixel dimensions, not the other way round."}}, {"@type": "Question", "name": "Why does my gigapixel render run out of space or crawl?", "acceptedAnswer": {"@type": "Answer", "text": "Intermediate files. nona writes a remapped image per source frame at full output resolution, and Enblend needs scratch room too \u2014 several times the final file size is a realistic temp-space budget. A render that crawls is usually swapping; check RAM and the Enblend cache setting."}}, {"@type": "Question", "name": "What Enblend cache should I set for a very large panorama?", "acceptedAnswer": {"@type": "Answer", "text": "The default cache is 1 GB. Raising it in the preferences helps Enblend swap less on big jobs, but only up to the free RAM you actually have \u2014 an oversized cache forces the operating system to swap instead, which is slower."}}, {"@type": "Question", "name": "Can Hugin use my GPU to render faster?", "acceptedAnswer": {"@type": "Answer", "text": "Hugin's GPU remapping (via nona) is experimental and not a reliable production path. Plan gigapixel renders around CPU time, temp disk and the batch queue."}}]}</script>]]></content:encoded>
					
					<wfw:commentRss>https://huginpanorama.com/gigapixel-panorama/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>Remove the Tripod from a 360 Panorama: Nadir Patching in Hugin</title>
		<link>https://huginpanorama.com/remove-tripod-nadir-patch/</link>
					<comments>https://huginpanorama.com/remove-tripod-nadir-patch/#respond</comments>
		
		<dc:creator><![CDATA[Admin]]></dc:creator>
		<pubDate>Wed, 21 Oct 2026 02:40:32 +0000</pubDate>
				<category><![CDATA[Tutorials]]></category>
		<guid isPermaLink="false">https://huginpanorama.com/remove-tripod-nadir-patch/</guid>

					<description><![CDATA[Quick answer: The cleanest fix is made while shooting: after the main 360 set, move the tripod and take one handheld frame straight down at the ground it covered. Stitch that nadir frame into the project in Hugin, and the tripod simply disappears under real pixels. If you forgot, the fallback is to extract a...]]></description>
										<content:encoded><![CDATA[<p class="wp-block-paragraph"><strong>Quick answer:</strong> The cleanest fix is made while shooting: after the main 360 set, move the tripod and take one handheld frame straight down at the ground it covered. Stitch that nadir frame into the project in Hugin, and the tripod simply disappears under real pixels. If you forgot, the fallback is to extract a rectilinear straight-down view from the finished panorama, paint the tripod out in an image editor, and merge the patched view back.</p>
<h2 class="wp-block-heading">Why the nadir is always the problem</h2>
<p class="wp-block-paragraph">In a 360 panorama the nadir — the point directly under the camera — is the one place the camera support itself occupies. On the tripod, the down-facing shots capture legs, feet and the pano head instead of floor. In the equirectangular render, that small region is stretched across the entire bottom edge of the image, which is why a tiny tripod becomes a wide smear in flat previews and an obvious mess when a viewer looks down. Every technique below replaces those tripod pixels with real floor pixels, or at least with a deliberate cover. Start from a correctly stitched sphere — our <a href="/stitch-360-panorama/">360 stitching guide</a> covers the base workflow.</p>
<h2 class="wp-block-heading">Best fix: shoot a handheld nadir frame</h2>
<p class="wp-block-paragraph">Prevention beats repair, and the standard field technique takes twenty seconds:</p>
<ol class="wp-block-list"><li>Complete the full 360 set on the tripod as normal.</li><li>Note exactly where the tripod stands, then pick the camera up, tilt it to point straight down at that spot, and — standing to the side so your feet stay out of frame — take one or two shots of the ground from roughly the same height.</li><li>Alternatively, swing the pano head&#8217;s arm or use the head&#8217;s nadir adapter if it offers one, keeping the camera on the rig but displaced from the legs.</li></ol>
<p class="wp-block-paragraph">Back in Hugin, add the handheld nadir frame to the project like any other photo. It overlaps the bottom parts of your ring and down shots, so CPFind can usually place it; because it was taken slightly off the rotation point, check its fit in the preview and give the optimizer freedom on that one image&#8217;s position. Where the tripod legs appear in the other frames, you can draw masks in Hugin&#8217;s mask tools to exclude those regions, forcing Enblend to take the floor from your clean nadir frame instead. The result is a floor that was actually photographed — no cloning artefacts, correct texture, correct perspective.</p>
<h2 class="wp-block-heading">Masking alone: the quick in-Hugin option</h2>
<p class="wp-block-paragraph">If the tripod only intrudes slightly — a foot or two at the very bottom — masks may be enough. In the Advanced interface, open the mask tools for the down-facing images and draw exclude masks over the legs and feet. Enblend will then fill the nadir from whatever other frames cover that ground: usually the lower edges of the ring shots, taken at an angle. Quality depends entirely on how much clean ground those frames contain. A small patch blends invisibly; a large one smears, because the floor is being rebuilt from grazing-angle pixels stretched to fill the pole. Think of masking as the fix for small intrusions, not a substitute for the nadir frame.</p>
<p class="wp-block-paragraph">Do not forget the tripod&#8217;s shadow, which often survives after the legs are masked: it falls on real floor, in frames you are keeping. If the shadow is objectionable, it has to be handled the same way as the tripod itself — covered by the nadir frame&#8217;s pixels where they exist, or painted out in the extracted down-view described next. Shooting with the sun behind a building, or on an overcast day, shrinks both problems at once.</p>
<h2 class="wp-block-heading">The patch workflow: extract, edit, reinsert</h2>
<p class="wp-block-paragraph">For panoramas already shot without a nadir frame, patch the finished sphere:</p>
<ol class="wp-block-list"><li><strong>Extract a down view.</strong> Load the finished equirectangular image into a new Hugin project as a single photo (lens type Equirectangular, full 360 field of view). Set the output projection to Rectilinear and rotate the view to look straight down (pitch −90), with a field of view wide enough to cover the tripod area — around 90–120 degrees is typical. Render that view: you now have an ordinary flat image of the floor with the tripod in the middle.</li><li><strong>Edit it.</strong> In GIMP, Photoshop or your editor of choice, clone, heal or paint over the tripod. Working on the rectilinear view is the whole trick: the floor has normal perspective here, so standard retouching tools behave, instead of fighting the equirectangular pole distortion.</li><li><strong>Reinsert it.</strong> Back in the Hugin project, add the edited view as a second photo — a rectilinear image looking straight down — and let Hugin project and blend it back into the sphere over the original nadir. Render the full equirectangular again.</li></ol>
<p class="wp-block-paragraph">Seams from the patch hide best when the extracted view&#8217;s field of view is generous and the floor is not full of straight lines crossing the patch boundary. On patterned floors — tiles, decking, parquet — align your clone work to the pattern while editing the flat view.</p>
<h2 class="wp-block-heading">The cover-up: mirror ball or logo cap</h2>
<p class="wp-block-paragraph">When there is no floor information at all, the honest fallback is a deliberate cover: many tour producers place a small circular logo or a &#8220;mirror ball&#8221; reflection effect over the nadir. It is fast and looks intentional rather than broken, which is why it is common in quick-turnaround tours and previews. It is not a repair — the floor under it does not exist — and on close inspection in a headset it reads as a cap. Use it when the deadline matters more than the floor, and shoot the nadir frame next time; the shooting-side routine is in our <a href="/shooting-panoramas-for-hugin/">panorama shooting guide</a>.</p>
<h2 class="wp-block-heading">Check your work like a viewer</h2>
<p class="wp-block-paragraph">Always inspect the finished panorama in a real 360 viewer, looking straight down and slowly rotating. The equirectangular flat file hides nadir problems; the viewer does not. Look for clone-stamp repetitions, a patch whose brightness differs from the surrounding floor, and mask edges that cut across shadows. If you render both a patched and an unpatched version from the saved project, you can compare them in seconds — one more reason to keep the .pto file and a TIFF master, as described in our <a href="/how-to-use-hugin/">Hugin workflow tutorial</a>.</p>
<h2 class="wp-block-heading">FAQ</h2>
<h3 class="wp-block-heading">Can I remove the tripod in Hugin without Photoshop?</h3>
<p class="wp-block-paragraph">Partly. If you shot a handheld nadir frame, Hugin alone can complete the job: stitch the clean frame in and mask the tripod out of the other shots. Without that frame, painting the tripod out requires an image editor working on an extracted rectilinear down-view.</p>
<h3 class="wp-block-heading">What is a nadir frame and when do I shoot it?</h3>
<p class="wp-block-paragraph">A photo of the ground where the tripod stands, taken after moving the tripod away — usually handheld, pointing straight down from about the same height. Shoot it at the end of every 360 set; it takes seconds and is the highest-quality source for patching.</p>
<h3 class="wp-block-heading">Why does the patched area look smeared?</h3>
<p class="wp-block-paragraph">Smearing means the patch was rebuilt from pixels at the extreme, stretched edge of fisheye frames. A dedicated nadir frame, or a wider extracted view for the edit-and-reinsert method, gives the patch real, undistorted pixels to work with.</p>
<h3 class="wp-block-heading">Is a logo cap over the nadir acceptable?</h3>
<p class="wp-block-paragraph">For quick previews and fast-turnaround tours, yes — it looks deliberate. For portfolio or paid work, a real patched floor is better, because viewers do look down, especially in headsets.</p>
<script type="application/ld+json">{"@context": "https://schema.org", "@type": "FAQPage", "mainEntity": [{"@type": "Question", "name": "Can I remove the tripod in Hugin without Photoshop?", "acceptedAnswer": {"@type": "Answer", "text": "Partly. If you shot a handheld nadir frame, Hugin alone can complete the job: stitch the clean frame in and mask the tripod out of the other shots. Without that frame, painting the tripod out requires an image editor working on an extracted rectilinear down-view."}}, {"@type": "Question", "name": "What is a nadir frame and when do I shoot it?", "acceptedAnswer": {"@type": "Answer", "text": "A photo of the ground where the tripod stands, taken after moving the tripod away \u2014 usually handheld, pointing straight down from about the same height. Shoot it at the end of every 360 set; it takes seconds and is the highest-quality source for patching."}}, {"@type": "Question", "name": "Why does the patched area look smeared?", "acceptedAnswer": {"@type": "Answer", "text": "Smearing means the patch was rebuilt from pixels at the extreme, stretched edge of fisheye frames. A dedicated nadir frame, or a wider extracted view for the edit-and-reinsert method, gives the patch real, undistorted pixels to work with."}}, {"@type": "Question", "name": "Is a logo cap over the nadir acceptable?", "acceptedAnswer": {"@type": "Answer", "text": "For quick previews and fast-turnaround tours, yes \u2014 it looks deliberate. For portfolio or paid work, a real patched floor is better, because viewers do look down, especially in headsets."}}]}</script>]]></content:encoded>
					
					<wfw:commentRss>https://huginpanorama.com/remove-tripod-nadir-patch/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>HDR Panoramas in Hugin: Bracketed Exposures, Enfuse &#038; True HDR Output</title>
		<link>https://huginpanorama.com/hugin-hdr-panorama/</link>
					<comments>https://huginpanorama.com/hugin-hdr-panorama/#respond</comments>
		
		<dc:creator><![CDATA[Admin]]></dc:creator>
		<pubDate>Wed, 21 Oct 2026 02:40:10 +0000</pubDate>
				<category><![CDATA[Tutorials]]></category>
		<guid isPermaLink="false">https://huginpanorama.com/hugin-hdr-panorama/</guid>

					<description><![CDATA[Quick answer: Shoot each position as a bracketed set of exposures. In Hugin you then choose between two different outputs: exposure fusion with Enfuse, which blends the brackets into one natural-looking, display-ready image, or true HDR, which merges them into a floating-point TIFF or OpenEXR file via hugin_hdrmerge for later tone mapping. Same photos, same...]]></description>
										<content:encoded><![CDATA[<p class="wp-block-paragraph"><strong>Quick answer:</strong> Shoot each position as a bracketed set of exposures. In Hugin you then choose between two different outputs: exposure fusion with Enfuse, which blends the brackets into one natural-looking, display-ready image, or true HDR, which merges them into a floating-point TIFF or OpenEXR file via hugin_hdrmerge for later tone mapping. Same photos, same alignment — the Stitcher tab output decides which one you get.</p>
<h2 class="wp-block-heading">Two outputs that are often confused</h2>
<p class="wp-block-paragraph">Photographers say &#8220;HDR panorama&#8221; for two quite different deliverables, and Hugin makes both. Exposure fusion (Enfuse) takes the well-exposed parts of each bracket — bright sky from the dark frame, shadow detail from the bright frame — and blends them into a normal low-dynamic-range image. The result needs no further processing and avoids the crunchy, over-processed look people associate with HDR. True HDR keeps the full measured brightness range of the scene in a floating-point file (TIFF or OpenEXR — the only HDR formats Hugin writes), which a tone-mapping tool or renderer later compresses for display. Choose fusion for a finished photograph today; choose true HDR when the panorama is an intermediate asset, for example an environment map for 3D work or a file you intend to grade later.</p>
<h2 class="wp-block-heading">Shoot brackets the stitcher can use</h2>
<p class="wp-block-paragraph">Everything from normal panorama shooting applies — manual focus, manual white balance, rotation around the entrance pupil, 25–50% overlap — plus bracket discipline. Fix the aperture and vary only the shutter speed, so depth of field and vignetting stay constant across the bracket. Two stops between frames is a common spacing; three to five frames per position should cover most scenes, from a dim interior with a sunlit window to a sunset landscape. Use a tripod and a remote release: the frames of a stack must align almost perfectly. The full camera-side routine is in our <a href="/shooting-panoramas-for-hugin/">shooting guide</a>; brackets are the one case where a few extra frames cost little and save the shot.</p>
<h2 class="wp-block-heading">Load and align the stacks</h2>
<p class="wp-block-paragraph">Load the whole sequence into Hugin as one project. Hugin recognises bracketed stacks — groups of photos taken from the same position at different exposures — and the Assistant aligns the stack members with align_image_stack, the suite&#8217;s dedicated tool for registering handheld or tripod brackets pixel-perfectly before the panorama geometry is solved. CPFind then finds control points between positions, typically using the middle exposure of each stack as the reference the others hang from. The photometric side matters as much as the geometry here: the optimizer&#8217;s photometric pass models each frame&#8217;s exposure and vignetting so that, for example, the sky in position three can be compared fairly with the sky in position four. If brackets are misdetected — Hugin thinks two positions are one stack — fix the grouping in the Advanced interface before optimizing; a wrong stack assignment produces ghosts that no blending setting will cure.</p>
<h2 class="wp-block-heading">Path A: exposure fusion with Enfuse</h2>
<p class="wp-block-paragraph">For the fused result, choose the exposure-fusion output in the Stitcher tab. Behind the scenes, Enblend&#8217;s sibling Enfuse weights every pixel by how well exposed, saturated and detailed it is, then blends the winners. The fused panorama inherits the natural contrast of the scene with extended detail at both ends — windows hold their view, shadow corners open up, and nothing glows. Fusion is the right default for real-estate interiors, landscapes with bright skies, and any panorama destined straight for the web or print. It is also forgiving of slight movement between brackets, since Enfuse picks per-pixel rather than trusting one whole frame.</p>
<h2 class="wp-block-heading">Path B: true HDR output</h2>
<p class="wp-block-paragraph">For a true HDR master, choose the high-dynamic-range output in the Stitcher tab. Hugin merges each stack with hugin_hdrmerge into floating-point data and writes a TIFF or OpenEXR panorama. Two consequences to plan around: the files are large — a wide panorama in 32-bit float dwarfs its JPG — and the file will look flat and wrong on an ordinary viewer until it is tone mapped, because no screen can show the range it contains. Judge the HDR by its histogram and by a test tone map, not by the murky default preview. Keep the HDR master and derive fused or tone-mapped versions from the same project; re-rendering from the saved project file is always cheaper than re-shooting.</p>
<h2 class="wp-block-heading">Exposure, vignetting and the photometric optimizer</h2>
<p class="wp-block-paragraph">Whichever path you take, run the photometric optimization. Hugin can correct exposure differences and lens vignetting across the whole set so seams do not show as brightness steps. Fisheyes vignette strongly at the edges — exactly where frames overlap — so for fisheye brackets this pass is the difference between invisible joins and a quilted sky. If one frame of a bracket was shot at a stray exposure (an accidental auto-exposure frame), the photometric pass can compensate somewhat, but replacing or removing that frame is cleaner. The general optimization workflow is covered in our <a href="/how-to-use-hugin/">main Hugin tutorial</a>.</p>
<h2 class="wp-block-heading">Ghosts: movement between brackets</h2>
<p class="wp-block-paragraph">Brackets assume a static scene, and real scenes move: trees stir, water flows, people cross the frame, clouds reshape the light during a long multi-position bracket. In a stack, movement means the same pixel claims different content at different exposures, and the merge — fused or HDR — can print that disagreement as a translucent ghost. Hugin&#8217;s deghosting support helps for modest movement between the frames of a stack, but the reliable cures are photographic: shoot brackets quickly, prefer the fused output (its per-pixel choices hide movement better than a global merge), and for scenes with unavoidable motion, consider whether one well-exposed frame per position plus careful RAW conversion gives you enough range without brackets at all. Moving subjects between positions — a person who walks through your panorama&#8217;s overlap zones — are a stitching problem rather than an HDR one, handled with masks as described in the main tutorial.</p>
<h2 class="wp-block-heading">Which should you choose?</h2>
<ul class="wp-block-list"><li><strong>Finished photo for web, print or a client:</strong> exposure fusion (Enfuse).</li><li><strong>Interior with extreme window contrast, delivered today:</strong> fusion — it was designed for exactly this.</li><li><strong>Environment/lighting asset, VFX plate, or maximum grading freedom later:</strong> true HDR (float TIFF or OpenEXR).</li><li><strong>Both:</strong> render fusion now, save the project, and render HDR from the same project whenever you need it.</li></ul>
<p class="wp-block-paragraph">For very large bracketed sets — many positions × several brackets — rendering time and scratch-disk space grow fast; the planning advice in our <a href="/gigapixel-panorama/">gigapixel panorama guide</a> applies to bracketed giants too.</p>
<h2 class="wp-block-heading">FAQ</h2>
<h3 class="wp-block-heading">What is the difference between Enfuse and HDR in Hugin?</h3>
<p class="wp-block-paragraph">Enfuse blends bracketed exposures into one normal, finished image by picking the best-exposed pixels. True HDR merges brackets into a floating-point TIFF or OpenEXR file that preserves the scene&#8217;s full brightness range for later tone mapping.</p>
<h3 class="wp-block-heading">How many bracketed exposures do I need per position?</h3>
<p class="wp-block-paragraph">Three frames spaced two stops apart covers most scenes; five frames help with extreme contrast such as a dark interior with bright windows. More important than count is consistency: fixed aperture, fixed focus, fixed white balance.</p>
<h3 class="wp-block-heading">Why does my HDR panorama look flat and grey?</h3>
<p class="wp-block-paragraph">A floating-point HDR file contains far more brightness range than a screen can display, so its default preview looks compressed and dull. That is expected — the image is finished only after tone mapping. The file itself is not broken.</p>
<h3 class="wp-block-heading">Can Hugin align handheld brackets?</h3>
<p class="wp-block-paragraph">Within limits. Hugin&#8217;s align_image_stack registers the frames of a stack before stitching, which handles small tripod-free shifts. Large movements, or subjects that move between brackets, will still ghost — a tripod remains the reliable option.</p>
<script type="application/ld+json">{"@context": "https://schema.org", "@type": "FAQPage", "mainEntity": [{"@type": "Question", "name": "What is the difference between Enfuse and HDR in Hugin?", "acceptedAnswer": {"@type": "Answer", "text": "Enfuse blends bracketed exposures into one normal, finished image by picking the best-exposed pixels. True HDR merges brackets into a floating-point TIFF or OpenEXR file that preserves the scene's full brightness range for later tone mapping."}}, {"@type": "Question", "name": "How many bracketed exposures do I need per position?", "acceptedAnswer": {"@type": "Answer", "text": "Three frames spaced two stops apart covers most scenes; five frames help with extreme contrast such as a dark interior with bright windows. More important than count is consistency: fixed aperture, fixed focus, fixed white balance."}}, {"@type": "Question", "name": "Why does my HDR panorama look flat and grey?", "acceptedAnswer": {"@type": "Answer", "text": "A floating-point HDR file contains far more brightness range than a screen can display, so its default preview looks compressed and dull. That is expected \u2014 the image is finished only after tone mapping. The file itself is not broken."}}, {"@type": "Question", "name": "Can Hugin align handheld brackets?", "acceptedAnswer": {"@type": "Answer", "text": "Within limits. Hugin's align_image_stack registers the frames of a stack before stitching, which handles small tripod-free shifts. Large movements, or subjects that move between brackets, will still ghost \u2014 a tripod remains the reliable option."}}]}</script>]]></content:encoded>
					
					<wfw:commentRss>https://huginpanorama.com/hugin-hdr-panorama/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>How to Stitch a 360° Panorama in Hugin (Equirectangular, Step by Step)</title>
		<link>https://huginpanorama.com/stitch-360-panorama/</link>
					<comments>https://huginpanorama.com/stitch-360-panorama/#respond</comments>
		
		<dc:creator><![CDATA[Admin]]></dc:creator>
		<pubDate>Wed, 21 Oct 2026 02:39:41 +0000</pubDate>
				<category><![CDATA[Tutorials]]></category>
		<guid isPermaLink="false">https://huginpanorama.com/stitch-360-panorama/</guid>

					<description><![CDATA[Quick answer: Load your full set of shots in Hugin, set the correct fisheye lens type, align with CPFind, then in the Fast Preview choose the Equirectangular projection and a 2:1 canvas (for example 6000×3000 or larger). Level the horizon, check the zenith and nadir, and render a TIFF or JPG. Those steps turn a...]]></description>
										<content:encoded><![CDATA[<p class="wp-block-paragraph"><strong>Quick answer:</strong> Load your full set of shots in Hugin, set the correct fisheye lens type, align with CPFind, then in the Fast Preview choose the Equirectangular projection and a 2:1 canvas (for example 6000×3000 or larger). Level the horizon, check the zenith and nadir, and render a TIFF or JPG. Those steps turn a ring of fisheye frames into a proper 360×180 panorama that any 360 viewer can display.</p>
<h2 class="wp-block-heading">What makes 360 stitching different</h2>
<p class="wp-block-paragraph">An ordinary panorama covers part of the view; a 360 panorama must wrap the entire sphere — 360 degrees around and 180 degrees from zenith (straight up) to nadir (straight down) — with the left edge joining the right edge seamlessly. The container for that sphere is the equirectangular image: twice as wide as it is tall, with the horizon on the middle row. Because the wrap-around seam and the poles are where problems hide, 360 stitching rewards a disciplined set of source photos. If you are new to Hugin itself, work through our <a href="/how-to-use-hugin/">step-by-step Hugin tutorial</a> first; this guide focuses on the 360-specific decisions.</p>
<h2 class="wp-block-heading">Shoot (or prepare) a complete sphere</h2>
<p class="wp-block-paragraph">Most 360 sets are shot with a fisheye lens on a panoramic head, rotating around the lens entrance pupil in a ring of shots, plus a zenith shot pointing up and one or two nadir shots pointing down. The overlap rule from general panorama work — roughly 25–50% between frames — applies with extra force at the poles, where equirectangular mapping stretches every pixel. Gaps at the zenith or nadir cannot be invented by the stitcher; they show up as holes or smeared stars in the render. Our <a href="/shooting-panoramas-for-hugin/">shooting guide</a> covers ring sizes and settings per lens. Sort the set before loading: all ring, zenith and nadir frames belong in one project.</p>
<h2 class="wp-block-heading">Load the set and set the lens type</h2>
<p class="wp-block-paragraph">Add all images in the Assistant. The critical 360-specific step is the lens type: a fisheye must be declared as what it is — Circular fisheye for a lens that projects a full circle, Full frame fisheye for one that fills the frame diagonally. If Hugin guesses a rectilinear (Normal) lens from the EXIF, CPFind may still find points, but the optimizer will fight the geometry and the sphere will not close cleanly. For a dual-fisheye 360 camera export, each frame is a circular fisheye and the pair is shot back-to-back; treat the two circles as two fisheye photos with a very wide field of view. Once the lens type is right, click Align. CPFind&#8217;s current multirow default handles rings well; for a single ring plus zenith/nadir, check afterwards that the up and down shots actually received control points — their overlap areas are small and highly distorted.</p>
<h2 class="wp-block-heading">Set the equirectangular output</h2>
<p class="wp-block-paragraph">In the Fast Preview window, set the projection to Equirectangular and confirm the field of view covers the full sphere: 360 degrees horizontal, 180 vertical. Then, in the Stitcher tab, set the canvas to a strict 2:1 ratio — width exactly twice the height. 6000×3000 is a sensible minimum for viewing on screens; larger masters such as 8000×4000 or more keep detail for zoomable tours, at the cost of longer Enblend renders and bigger files. If the field of view is slightly less than full — a common outcome when the nadir frames are missing — the canvas will not be a full sphere and 360 viewers will show it cropped or pinched; either add the missing frames or accept a partial panorama and export it as a wide cylindrical image instead of pretending it is a full 360.</p>
<h2 class="wp-block-heading">Level the horizon</h2>
<p class="wp-block-paragraph">A tilted 360 is nauseating in a headset and sloppy on screen: the whole world leans. Use the drag controls in the Fast Preview to rotate the sphere until the true horizon sits exactly on the middle line of the preview and vertical features — door frames, building edges — stand vertical. If your set includes identifiable vertical lines, the Advanced interface lets the optimizer use vertical control points (lines marked as vertical) to force this precisely. Level before you render, because rotating a finished equirectangular in an ordinary editor wraps pixels across the seam and softens the image.</p>
<p class="wp-block-paragraph">Spend the extra minute this deserves, because levelling errors are amplified by every 360 viewer: a two-degree tilt that looks harmless in the flat preview becomes a world that slides sideways as the viewer pans. A reliable trick is to find one strong vertical that should be perfectly upright — a door frame or building corner near the middle of a frame — rotate until it is vertical, then confirm with a second vertical on the opposite side of the sphere. If the two disagree, the set itself contains geometry problems (usually parallax or a mis-set lens type), and no rotation will satisfy both; fix the cause rather than averaging the error.</p>
<h2 class="wp-block-heading">Handle the zenith and nadir</h2>
<p class="wp-block-paragraph">The zenith (sky) usually takes care of itself if you shot an up frame; a small hole in a clear sky can be blended invisibly. The nadir is the problem child, because your tripod stands there. Options, in order of quality: shoot a separate handheld nadir frame after moving the tripod, and let Hugin stitch it in — the full workflow is in our guide to <a href="/remove-tripod-nadir-patch/">nadir patching and tripod removal</a>. Or mask the tripod out of the down shots in Hugin and accept a small blended patch. Or cover the spot with a mirror-ball or logo cap in post — acceptable for quick previews, less so for paid tours. Inspect the bottom of the sphere in a 360 viewer before delivering: equirectangular previews hide nadir flaws because the area is stretched across the whole bottom edge of the flat image.</p>
<h2 class="wp-block-heading">Export for 360 viewers</h2>
<p class="wp-block-paragraph">Render a TIFF master from the Stitcher tab, then export a JPG copy for distribution. Viewers and platforms expect the 2:1 equirectangular JPG, ideally with the standard 360 metadata that identifies it as a spherical photo; if your viewer shows the file as a flat wide image, that metadata is what is missing, and dedicated 360 tools can inject it. Keep the TIFF: re-levelling, re-patching the nadir or re-exporting at another size — for example for the <a href="/little-planet-tutorial/">little planet</a> treatment — should never start from the compressed JPG. For multi-row gigapixel-scale spheres, the memory advice in our <a href="/gigapixel-panorama/">gigapixel guide</a> applies unchanged.</p>
<h2 class="wp-block-heading">Publishing your 360</h2><p class="wp-block-paragraph">A finished equirectangular JPG is not yet a tour anyone can visit — it needs a viewer or a host. You have three practical routes. Social platforms (Facebook, YouTube for video) accept 360 images with the metadata discussed above, free and zero-friction, but with their compression and their rules. Dedicated hosting platforms are the professional route: <a href="/go/cloudpano" rel="nofollow sponsored noopener">CloudPano</a> (affiliate link — we&#8217;re reader-supported; see our <a href="/disclaimer/">disclaimer</a>) builds branded virtual tours with hotspots and floor plans and can publish to Google Street View (its Pro Plus plan was $33/month billed annually when we checked on 21 October 2026), while Kuula is the long-standing community favourite for straightforward tour hosting and embedding. And for your own website, a self-hosted viewer such as Pannellum costs nothing but a little setup. Whichever route you choose, publish from the quality JPG and keep the TIFF master archived — hosting platforms come and go, masters are forever.</p><h2 class="wp-block-heading">FAQ</h2>
<h3 class="wp-block-heading">What size should a 360 panorama from Hugin be?</h3>
<p class="wp-block-paragraph">The canvas must be 2:1 — width exactly twice height. 6000×3000 is a workable minimum for screen viewing; 8000×4000 or larger is better for tours where visitors zoom in. The source photos&#8217; resolution sets the practical ceiling.</p>
<h3 class="wp-block-heading">Why does my 360 panorama have a visible seam where the edges join?</h3>
<p class="wp-block-paragraph">The left-right wrap seam shows when exposure differs across the set or the horizon is not level. Shoot with manual exposure and white balance, let the photometric optimization even out brightness, and level the horizon in the Fast Preview before rendering.</p>
<h3 class="wp-block-heading">Can Hugin stitch photos from a dual-lens 360 camera?</h3>
<p class="wp-block-paragraph">Yes, if you export the two fisheye circles as separate images and declare the lens type as Circular fisheye. Alignment needs enough shared detail in the overlap band; texture-poor scenes (white ceilings, clear sky) are the hard cases for any stitcher.</p>
<h3 class="wp-block-heading">Why is there a hole or smear at the top or bottom of my panorama?</h3>
<p class="wp-block-paragraph">Those are the zenith and nadir. A smear means the area was covered by only the extreme edge of a fisheye frame; a hole means it was never photographed. Shoot dedicated up and down frames — the stitcher cannot invent missing sphere.</p>
<script type="application/ld+json">{"@context": "https://schema.org", "@type": "FAQPage", "mainEntity": [{"@type": "Question", "name": "What size should a 360 panorama from Hugin be?", "acceptedAnswer": {"@type": "Answer", "text": "The canvas must be 2:1 \u2014 width exactly twice height. 6000\u00d73000 is a workable minimum for screen viewing; 8000\u00d74000 or larger is better for tours where visitors zoom in. The source photos' resolution sets the practical ceiling."}}, {"@type": "Question", "name": "Why does my 360 panorama have a visible seam where the edges join?", "acceptedAnswer": {"@type": "Answer", "text": "The left-right wrap seam shows when exposure differs across the set or the horizon is not level. Shoot with manual exposure and white balance, let the photometric optimization even out brightness, and level the horizon in the Fast Preview before rendering."}}, {"@type": "Question", "name": "Can Hugin stitch photos from a dual-lens 360 camera?", "acceptedAnswer": {"@type": "Answer", "text": "Yes, if you export the two fisheye circles as separate images and declare the lens type as Circular fisheye. Alignment needs enough shared detail in the overlap band; texture-poor scenes (white ceilings, clear sky) are the hard cases for any stitcher."}}, {"@type": "Question", "name": "Why is there a hole or smear at the top or bottom of my panorama?", "acceptedAnswer": {"@type": "Answer", "text": "Those are the zenith and nadir. A smear means the area was covered by only the extreme edge of a fisheye frame; a hole means it was never photographed. Shoot dedicated up and down frames \u2014 the stitcher cannot invent missing sphere."}}]}</script>]]></content:encoded>
					
					<wfw:commentRss>https://huginpanorama.com/stitch-360-panorama/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>How to Use Hugin: Stitch Your First Panorama Step by Step</title>
		<link>https://huginpanorama.com/how-to-use-hugin/</link>
					<comments>https://huginpanorama.com/how-to-use-hugin/#respond</comments>
		
		<dc:creator><![CDATA[Admin]]></dc:creator>
		<pubDate>Wed, 21 Oct 2026 02:39:19 +0000</pubDate>
				<category><![CDATA[Tutorials]]></category>
		<guid isPermaLink="false">https://huginpanorama.com/how-to-use-hugin/</guid>

					<description><![CDATA[Quick answer: Open Hugin, stay in the Simple interface, and work down the Assistant tab: load your images, click Align so CPFind finds control points and the optimizer fits them together, preview the result in the Fast Preview window to pick a projection and straighten the horizon, then set the canvas size and file format...]]></description>
										<content:encoded><![CDATA[<p class="wp-block-paragraph"><strong>Quick answer:</strong> Open Hugin, stay in the Simple interface, and work down the Assistant tab: load your images, click Align so CPFind finds control points and the optimizer fits them together, preview the result in the Fast Preview window to pick a projection and straighten the horizon, then set the canvas size and file format in the Stitcher tab and click Create panorama. The ten minutes below walk through each step — and what to check when the automatic result is not quite right.</p>
<h2 class="wp-block-heading">What you need before you start</h2>
<p class="wp-block-paragraph">Hugin stitches overlapping photographs of the same scene, so your source photos matter more than any setting. Aim for roughly 25–50% overlap between neighbouring frames, and shoot with manual exposure, manual white balance and manual focus so frames do not change brightness or focus mid-sequence. Our companion guide on <a href="/shooting-panoramas-for-hugin/">how to shoot panoramas for Hugin</a> covers the camera side in detail. On the software side you need a current Hugin install — see the <a href="/download/">download page</a> for the official 2025.0.1 installer, with platform notes in our guides to <a href="/hugin-for-windows/">Hugin for Windows</a> and <a href="/hugin-for-mac/">Hugin for Mac</a>. One important limitation: Hugin does not stitch RAW files directly, so export RAW shots as 16-bit TIFFs from your RAW converter first.</p>
<p class="wp-block-paragraph">If this is your very first stitch, do not start with your masterpiece. Take a simple test set — four or five frames of an ordinary scene with plenty of texture, shot from one spot — and run the whole pipeline on it. A test set teaches you the interface in minutes, at trivial render sizes, and separates &#8220;I misunderstand a setting&#8221; from &#8220;my photos are hard to stitch&#8221;, two problems that feel identical when they arrive together on an important set.</p>
<h2 class="wp-block-heading">Step 1: Load your images in the Assistant</h2>
<p class="wp-block-paragraph">Launch Hugin and you land in the Simple interface, on the Assistant tab. The Assistant is a three-step pipeline — load, align, create — and the first step is simply adding your photos. Click the load-images control in the Assistant and select the whole set, or drag the files into the window. Hugin reads the EXIF data in your images to detect the camera and lens, and it usually recognises the focal length and lens type automatically. If it cannot identify a fisheye or an unusual lens, set the lens type yourself before going further — the common choices are Normal (rectilinear) for ordinary lenses, Full frame fisheye and Circular fisheye for fisheyes, and Equirectangular for an already-stitched 360 image. Wrong lens information is the single most common cause of failed stitches, because every later calculation builds on it.</p>
<h2 class="wp-block-heading">Step 2: Align — control points and optimization</h2>
<p class="wp-block-paragraph">Click Align, and Hugin does the heavy lifting in two passes. First, CPFind — Hugin&#8217;s built-in, patent-free control-point generator — scans every overlapping pair of photos and marks matching features: corners, textures and edges that appear in both frames. These matched pairs are the control points. Second, the optimizer adjusts each photo&#8217;s position (yaw, pitch and roll), the lens field of view and the distortion parameters until the control points line up as tightly as possible, in both geometry and, with photometric optimization, brightness. Since the 2024 release, CPFind defaults to a multirow strategy that suits the row-by-row way panoramas are usually shot. When Align finishes, Hugin shows you a preview and reports how well the fit went — a small average control-point distance means the optimizer found a consistent solution.</p>
<h2 class="wp-block-heading">Step 3: Check the fit before you stitch</h2>
<p class="wp-block-paragraph">Do not rush past the preview. In the Fast Preview window, look for the classic symptoms of a bad fit: a horizon that waves up and down, vertical lines in buildings that lean in different directions in different frames, or visible doubling on near objects. A wavy horizon usually means the optimizer needs help with the horizon line; doubling on near objects usually means parallax — the camera rotated around the tripod screw instead of around the lens entrance pupil — and no software setting fully repairs that after the fact. If one photo sits obviously out of place, switch to the Advanced interface (covered below), open the control-point editor, and inspect the points for that pair: a handful of wrong matches on a repetitive pattern such as windows or waves can drag a whole panorama out of shape, and deleting the bad points and re-optimizing often fixes it.</p>
<h2 class="wp-block-heading">Step 4: Choose a projection and straighten up in the Fast Preview</h2>
<p class="wp-block-paragraph">The Fast Preview window is where your stitched photos become a composed panorama. Pick a projection that fits your scene and field of view:</p>
<ul class="wp-block-list"><li><strong>Rectilinear</strong> keeps straight lines straight and looks like an ordinary photograph — ideal for narrower views, but it stretches corners badly beyond roughly 100–120 degrees.</li><li><strong>Cylindrical</strong> is the forgiving default for wide horizontal panoramas shot in a single row.</li><li><strong>Equirectangular</strong> covers the full 360×180 sphere and is the format 360 viewers expect — see our dedicated <a href="/stitch-360-panorama/">360 stitching guide</a>.</li><li><strong>Stereographic</strong> produces the playful &#8220;little planet&#8221; look; <strong>Panini</strong> and <strong>Architectural</strong> help interiors keep verticals upright without extreme corner stretch.</li></ul>
<p class="wp-block-paragraph">Use the drag tools in the preview to centre the composition, and drag vertically to level the horizon until vertical features stand upright. Take a moment here: a level, well-centred preview is much easier than fixing a tilted render later.</p>
<h2 class="wp-block-heading">Step 5: Exposure and output settings in the Stitcher tab</h2>
<p class="wp-block-paragraph">Switch to the Stitcher tab to define the deliverable. The canvas size is proposed from your photos&#8217; resolution and the field of view — you can accept the suggestion or type your own width, and Hugin keeps the proportions. For an ordinary panorama, the standard low-dynamic-range output is what you want: Hugin corrects exposure differences between frames, blends them with Enblend so seams disappear, and writes the result. Choose the file format deliberately: TIFF (8- or 16-bit) for a master file you plan to edit further, JPG for sharing, PNG when you need lossless output with transparency support in your workflow. The Stitcher tab is also where the HDR and exposure-fusion outputs live, but leave those alone for your first panoramas — the defaults produce a clean, natural result.</p>
<h2 class="wp-block-heading">Step 6: Create the panorama</h2>
<p class="wp-block-paragraph">Click Create panorama (in the Assistant, the final step does the same). Hugin now hands the project to its workhorse tools: nona remaps each photo into the chosen projection, and Enblend merges the remapped frames into one seamless image, smoothing exposure steps as it goes. A progress window shows each stage. Small panoramas finish in seconds; a large multi-row set can take minutes, and very large jobs can be handed to the batch queue instead — see our <a href="/hugin-batch-stitching/">batch stitching guide</a>. When it completes, open the output file and inspect it at 100% along the seams: look for ghosting where something moved between frames, and for soft doubling on detailed textures.</p>
<h2 class="wp-block-heading">When the Assistant result is imperfect: the Advanced interface</h2>
<p class="wp-block-paragraph">The Assistant assumes a well-shot, single set of photos. Switch to the Advanced interface when reality is messier — mixed exposures, a fisheye the EXIF misread, bracketed sets, or a panorama where one frame refuses to fit. The Advanced interface exposes what the Assistant hides: the full photo list with per-image lens and exposure values, the mask tools (exclude a tripod leg, a passer-by, or include a region deliberately), the control-point editor for adding or deleting points by hand, and direct optimizer control so you can choose exactly which parameters are optimized and in what order. A practical workflow used by experienced stitchers: run the Assistant first, save the project file, then switch to Advanced and refine only what the preview shows is wrong. If the same lens keeps producing slightly bent results, calibrate it once with <a href="/hugin-lens-calibration/">calibrate_lens_gui</a> and reuse the saved lens parameters for every future set.</p>
<h2 class="wp-block-heading">The project file is the real output</h2>
<p class="wp-block-paragraph">Everything you decided — photos, lens data, control points, projection, canvas — lives in the project (.pto) file, and the features described in this guide reflect the current 2025.0.1 release (see <a href="/hugin-latest-version/">what changed in the latest version</a>). Save the project next to its render, every time. With the project saved, a panorama is never finished or ruined: you can re-render next year at print size, swap one photo, change the projection from cylindrical to stereographic, or hand the whole job to the batch queue, all without re-shooting or re-aligning. Experienced users treat the rendered TIFF as a printout and the .pto as the negative. Name both consistently — project name and render name identical apart from the extension — and future-you will not have to guess which render came from which alignment.</p>
<h2 class="wp-block-heading">Five habits that make every stitch better</h2>
<ul class="wp-block-list"><li><strong>Shoot for the stitcher:</strong> manual everything, generous overlap, rotate around the entrance pupil.</li><li><strong>Save the project file</strong> before rendering — the .pto file lets you re-render at another size or fix one photo without starting over.</li><li><strong>Judge at 100%</strong> along seams, not at fit-to-screen size.</li><li><strong>Render a TIFF master</strong> and derive JPGs from it, so re-edits never start from a compressed file.</li><li><strong>Fix capture problems at capture:</strong> parallax, moving subjects and exposure jumps are shooting issues first, software issues second.</li></ul>
<h2 class="wp-block-heading">FAQ</h2>
<h3 class="wp-block-heading">Is Hugin free, including for commercial work?</h3>
<p class="wp-block-paragraph">Yes. Hugin is open-source software released under the GPL, so you can use it for personal and commercial projects at no cost. Our <a href="/is-hugin-safe/">safety and licensing overview</a> explains what to check before installing.</p>
<h3 class="wp-block-heading">Why does Hugin say there are no control points between two photos?</h3>
<p class="wp-block-paragraph">Usually the pair does not overlap enough, the lens type or focal length is wrong, or the overlapping area is featureless (clear sky, blank wall, open water). Check the lens settings first, then add control points manually for that pair in the Advanced interface.</p>
<h3 class="wp-block-heading">What is the difference between the Simple and Advanced interfaces?</h3>
<p class="wp-block-paragraph">The Simple interface runs the guided Assistant workflow: load, align, create. The Advanced interface exposes the underlying project — photos, masks, control points and optimizer settings — for manual correction and complex sets such as brackets and fisheyes.</p>
<h3 class="wp-block-heading">Can Hugin stitch RAW files?</h3>
<p class="wp-block-paragraph">Not directly. Convert RAW images to 16-bit TIFF first (Darktable and RawTherapee are common choices), then stitch the TIFFs. This also gives you consistent white balance and exposure across the set before stitching.</p>
<script type="application/ld+json">{"@context": "https://schema.org", "@type": "FAQPage", "mainEntity": [{"@type": "Question", "name": "Is Hugin free, including for commercial work?", "acceptedAnswer": {"@type": "Answer", "text": "Yes. Hugin is open-source software released under the GPL, so you can use it for personal and commercial projects at no cost. Our safety and licensing overview explains what to check before installing."}}, {"@type": "Question", "name": "Why does Hugin say there are no control points between two photos?", "acceptedAnswer": {"@type": "Answer", "text": "Usually the pair does not overlap enough, the lens type or focal length is wrong, or the overlapping area is featureless (clear sky, blank wall, open water). Check the lens settings first, then add control points manually for that pair in the Advanced interface."}}, {"@type": "Question", "name": "What is the difference between the Simple and Advanced interfaces?", "acceptedAnswer": {"@type": "Answer", "text": "The Simple interface runs the guided Assistant workflow: load, align, create. The Advanced interface exposes the underlying project \u2014 photos, masks, control points and optimizer settings \u2014 for manual correction and complex sets such as brackets and fisheyes."}}, {"@type": "Question", "name": "Can Hugin stitch RAW files?", "acceptedAnswer": {"@type": "Answer", "text": "Not directly. Convert RAW images to 16-bit TIFF first (Darktable and RawTherapee are common choices), then stitch the TIFFs. This also gives you consistent white balance and exposure across the set before stitching."}}]}</script>]]></content:encoded>
					
					<wfw:commentRss>https://huginpanorama.com/how-to-use-hugin/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
	</channel>
</rss>
