<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Home on Ariel Marin — Architectural Visualization</title><link>https://arielsmarin.com/</link><description>Recent content in Home on Ariel Marin — Architectural Visualization</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Sat, 20 Jun 2026 00:00:00 -0300</lastBuildDate><atom:link href="https://arielsmarin.com/index.xml" rel="self" type="application/rss+xml"/><item><title>Automating a Render Queue with Python and systemd</title><link>https://arielsmarin.com/blog/automating-a-render-queue-with-python-and-systemd/</link><pubDate>Sat, 20 Jun 2026 00:00:00 -0300</pubDate><guid>https://arielsmarin.com/blog/automating-a-render-queue-with-python-and-systemd/</guid><description>&lt;p&gt;My render node used to be driven by a folder of &lt;code&gt;.bat&lt;/code&gt; files and hope. This post
walks through the small Python daemon that replaced them — about 300 lines, no
framework, running under systemd on Debian.&lt;/p&gt;
&lt;h2 id="requirements"&gt;Requirements&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;queue render jobs from any machine on the LAN;&lt;/li&gt;
&lt;li&gt;survive renderer crashes without losing the queue;&lt;/li&gt;
&lt;li&gt;notify me when a job finishes or fails.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="the-queue"&gt;The queue&lt;/h2&gt;
&lt;p&gt;Jobs are plain JSON files dropped into a watched directory — no database, no broker.
The filesystem &lt;em&gt;is&lt;/em&gt; the queue, and &lt;code&gt;mv&lt;/code&gt; is atomic:&lt;/p&gt;</description></item><item><title>Render Queue Worker</title><link>https://arielsmarin.com/lab/render-queue/</link><pubDate>Sat, 20 Jun 2026 00:00:00 -0300</pubDate><guid>https://arielsmarin.com/lab/render-queue/</guid><description>&lt;p&gt;A small daemon that turns a watched directory into a render job queue. Jobs are JSON
files; claiming a job is an atomic &lt;code&gt;mv&lt;/code&gt;; recovery after a crash means moving files
back. No database, no broker, no web UI.&lt;/p&gt;
&lt;h2 id="design-notes"&gt;Design notes&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;The filesystem is the queue — &lt;code&gt;mv&lt;/code&gt; gives atomicity for free.&lt;/li&gt;
&lt;li&gt;systemd handles restarts, logging and memory limits.&lt;/li&gt;
&lt;li&gt;Notifications go out through a Telegram bot on job completion or failure.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="status"&gt;Status&lt;/h2&gt;
&lt;p&gt;Running in production on my render node since mid-2026. Next step: a &lt;code&gt;--dry-run&lt;/code&gt;
mode that estimates job duration from scene statistics.&lt;/p&gt;</description></item><item><title>Hillside Residence</title><link>https://arielsmarin.com/projects/hillside-residence/</link><pubDate>Sun, 10 May 2026 00:00:00 -0300</pubDate><guid>https://arielsmarin.com/projects/hillside-residence/</guid><description>&lt;p&gt;The house steps down the slope in three volumes, and the imagery had to make that
movement legible: how the roofline follows the terrain, how each level opens to a
different layer of the canopy.&lt;/p&gt;
&lt;p&gt;We worked from the architects&amp;rsquo; BIM model, rebuilt the terrain from survey data, and
developed a restrained material palette — board-formed concrete, blackened timber,
large glass planes. The lighting concept centers on two moments: low warm sun cutting
through the trees, and the blue hour when the interior reads as a lantern.&lt;/p&gt;</description></item><item><title>A Practical Linear Workflow for Archviz</title><link>https://arielsmarin.com/blog/a-practical-linear-workflow-for-archviz/</link><pubDate>Wed, 08 Apr 2026 00:00:00 -0300</pubDate><guid>https://arielsmarin.com/blog/a-practical-linear-workflow-for-archviz/</guid><description>&lt;p&gt;Most &amp;ldquo;my render looks flat&amp;rdquo; problems are not lighting problems. They are color
management problems that &lt;em&gt;masquerade&lt;/em&gt; as lighting problems.&lt;/p&gt;
&lt;h2 id="the-short-version"&gt;The short version&lt;/h2&gt;
&lt;p&gt;Your renderer computes light in linear space. Your monitor displays gamma-encoded
images. Every texture, light value and post-production step has to respect that
boundary — or you end up compensating with ever-stronger lights and crunchy contrast.&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;Fix the pipeline once, and stop fighting every image individually.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;h2 id="where-it-goes-wrong"&gt;Where it goes wrong&lt;/h2&gt;
&lt;ol&gt;
&lt;li&gt;Albedo textures imported as linear when they are sRGB.&lt;/li&gt;
&lt;li&gt;HDRIs double-corrected on import.&lt;/li&gt;
&lt;li&gt;Post-production applied to already display-referred images.&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;A quick sanity check for albedo values:&lt;/p&gt;</description></item><item><title>Atrium Interior</title><link>https://arielsmarin.com/projects/atrium-interior/</link><pubDate>Mon, 02 Mar 2026 00:00:00 -0300</pubDate><guid>https://arielsmarin.com/projects/atrium-interior/</guid><description>&lt;p&gt;A triple-height void organizes the building&amp;rsquo;s public life. The brief asked for images
that communicate scale without losing warmth — a balance handled mostly through
lighting temperature and the density of entourage.&lt;/p&gt;
&lt;p&gt;The vertical format was essential here: the signature image looks straight up through
the void, compressing all three levels into a single frame.&lt;/p&gt;</description></item><item><title>Contact Sheet Generator</title><link>https://arielsmarin.com/lab/contact-sheet/</link><pubDate>Wed, 11 Feb 2026 00:00:00 -0300</pubDate><guid>https://arielsmarin.com/lab/contact-sheet/</guid><description>&lt;p&gt;Clients review sets of images, not single files. This CLI takes a folder of renders
and produces a single annotated contact sheet: filename, resolution, and an optional
note under each thumbnail.&lt;/p&gt;
&lt;div class="highlight"&gt;&lt;pre tabindex="0" class="chroma"&gt;&lt;code class="language-text" data-lang="text"&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;contact-sheet ./renders --columns 4 --out review-r03.png
&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;h2 id="why"&gt;Why&lt;/h2&gt;
&lt;p&gt;Every delivery used to involve ten minutes of manual layout in an image editor.
Now it&amp;rsquo;s one command in the delivery script.&lt;/p&gt;
&lt;h2 id="status"&gt;Status&lt;/h2&gt;
&lt;p&gt;Prototype — works for my delivery format; flags and defaults still shifting.&lt;/p&gt;</description></item><item><title>Courtyard House</title><link>https://arielsmarin.com/projects/courtyard-house/</link><pubDate>Tue, 18 Nov 2025 00:00:00 -0300</pubDate><guid>https://arielsmarin.com/projects/courtyard-house/</guid><description>&lt;p&gt;Competition deadlines compress everything. This set — three exteriors and one
interior — was produced in five days, from a clean SketchUp volume to final boards.&lt;/p&gt;
&lt;p&gt;The images lean on strong shadow patterns from the pergola and a single, consistent
time of day, which kept the set coherent and the review cycles short.&lt;/p&gt;</description></item><item><title>Riverside Office</title><link>https://arielsmarin.com/projects/riverside-office/</link><pubDate>Mon, 25 Aug 2025 00:00:00 -0300</pubDate><guid>https://arielsmarin.com/projects/riverside-office/</guid><description>&lt;p&gt;Developer marketing work with a clear goal: the building had to feel inevitable in
its context. We matched drone photography of the site, calibrated the camera and sun
to the shoot metadata, and composited the tower into the real riverfront.&lt;/p&gt;</description></item><item><title>Pendant Lamp Study</title><link>https://arielsmarin.com/projects/pendant-lamp-study/</link><pubDate>Sat, 14 Jun 2025 00:00:00 -0300</pubDate><guid>https://arielsmarin.com/projects/pendant-lamp-study/</guid><description>&lt;p&gt;A self-initiated exercise in restraint: a single spun-aluminum pendant, rendered
under thirty different lighting setups. No post-production allowed — every image had
to work straight out of the renderer.&lt;/p&gt;
&lt;p&gt;Studies like this feed directly back into client work; half of my go-to studio
lighting rigs came out of this series.&lt;/p&gt;</description></item><item><title>About</title><link>https://arielsmarin.com/about/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://arielsmarin.com/about/</guid><description>&lt;p&gt;I&amp;rsquo;m Ariel — an architectural visualization artist. I create images for architects, developers
and designers: modeling, materials, lighting, rendering and post-production, from early
concept studies to final marketing imagery.&lt;/p&gt;
&lt;p&gt;Most of my work sits between architecture and computer graphics. Understanding how light,
materials and optics behave — physically and perceptually — is a central part of the craft,
and it&amp;rsquo;s what keeps me close to the technical side of image-making.&lt;/p&gt;</description></item><item><title>Contact</title><link>https://arielsmarin.com/contact/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://arielsmarin.com/contact/</guid><description>&lt;p&gt;For commissions, collaborations or a quote, email me at
&lt;a href="mailto:arielsmarin@gmail.com"&gt;arielsmarin@gmail.com&lt;/a&gt;.&lt;/p&gt;
&lt;h2 id="requesting-a-quote"&gt;Requesting a quote&lt;/h2&gt;
&lt;p&gt;To make the first reply useful, include if possible:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;project type (residential, interior, commercial, product);&lt;/li&gt;
&lt;li&gt;number of images and target resolution;&lt;/li&gt;
&lt;li&gt;available material (CAD/BIM model, drawings, references);&lt;/li&gt;
&lt;li&gt;deadline.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;I usually reply within one business day.&lt;/p&gt;
&lt;p&gt;You can also find me on GitHub, LinkedIn and Instagram — links in the footer.&lt;/p&gt;</description></item></channel></rss>