For those who don’t know the tool: Maya is a core DCC from Autodesk for modeling, rigging, animation, and FX, with lookdev via LookdevX and node FX via Bifrost, plus pipeline handoff through USD.

The headline feature is editorial glue

Maya 2027.1 adds support for OpenTimelineIO in the Sequencer, enabling interchange of editorial cut data between DCC and timeline tools.

Sequencer gets editorial glue, not just buttons

Maya 2027.1 adds import and export support for OpenTimelineIO, with OTIO data being a standardised equivalent to XML for supported sequence, track, shot, audio, and file reference information. OTIO import preserves camera assignments and camera attributes, and reconstructs tracks from stored track information. The same workflow includes additional shot-level data such as labels, colors, thumbnails, and frame range information.

Sequencer also gets a round of editorial workflow updates beyond OTIO. Autodesk claims improvements to timeline exchange, shot editing, audio handling, playblast output controls, and scripting access. Shot creation now works directly on a selected track, or from a selected Time Slider range. Shot editing includes an updated hold workflow where hold frames come from a dedicated Hold mode while you drag shot edges. That sounds small until you try it on a cut with a dozen micro-trims and discover you do not need to invent a new swearing dialect.

Audio behavior becomes stricter. Sequencer uses only audio associated with the sequence. Audio not linked to Sequencer gets ignored, and Sequencer audio does not mix with Trax audio. A new Time Slider audio menu option called Use Sequencer Sounds controls that behavior. Playblast Shot Options adds Display Size controls for output resolution, with options listed as From Window, From Render Settings, Custom, and From Image Attributes. Output resolution depends on the chosen Display Size and Scale settings. Zooming in Sequencer now centers on the cursor when you use the mouse wheel, which helps the tiemline stop teleporting away from the thing you actually meant to inspect.

As always, new interchange formats look great in demos and get weird at 2 a.m. Test OTIO import and export on your real sequences before you bet a delivery on it.

MotionMaker focuses on editing clarity

Autodesk positions 2027.1 as a release with AI-powered tools and everyday workflow updates, and MotionMaker gets the everyday part this time. MotionMaker now shows frame ranges directly on clips and active windows. The stated goal is clearer timing feedback and behavior aligned with Sequencer.

Character naming gets a cleanup. Autodesk standard characters display simplified names in the UI, dropping the adsk_ prefix while keeping internal identifiers for compatibility. Character definitions also support a display name attribute used in the Create menu and character creation options.

New keyboard shortcuts navigate to the adjacent start frame before or after the current action clip in the timeline, aimed at faster clip-to-clip movement while editing. Updates to character registry handling also reduce redundant processing when creating MotionMaker registries.

Smart Bevel keeps hunting the ugly edge cases

Smart Bevel receives quality updates described as handling more complex geometry with fewer errors, with the practical promise of less manual cleanup on geometry with many intersecting edges.

Cutback relaxation improves to help prevent straight-edge segments from shifting, aimed at hard-surface models that mix linear and smooth forms. Smart Bevel also reduces spikes and jagged sawtooth corners in certain edge cases. Limiting works better across intersection types, with improvements intended to stop bevel results from crossing. Intersections previously missed are now detected.

Arc welding of new junctions becomes more thorough, and isolated arc removal becomes more reliable. Smart Bevel also improves handling of edge sequences that previously failed to bevel, with the result described as proper beveling and prevention of holes or missing faces at junctions along the sequence. Preset support expands so Smart Bevel presets can now save the Remove Isolated Arcs state.

Bifrost adds a search box and more sim and rig polish

Bifrost 3.1.0.8 adds a way to find where specific nodes are used in the graph, plus other new features and improvements. The same version lists updates for rigid body simulation, including per-instance colors, plus performance improvements for rigging and viewport drawing. New high-level compounds include deform_onto_mesh_UVs, wrap_deform_by_mesh, and wrap_deform_by_points. Rigs built with Bifrost now support Maya Cached Playback for improved performance, with a stated limitation that Cached Playback only works if the rig uses no feedback ports.

USD for Maya targets variants, and pins the manager

The USD plugin update listed as USD for Maya 0.36 adds support for targeting specific variants to receive edits, including changes to geometry and materials. The USD Variant Manager can now be pinned to its current display to prevent it from updating when you change selection. That is the kind of feature you only notice after it saves you from editing the wrong thing during a review.

LookdevX projects textures, searches graphs, and stays Arnold-friendly

LookdevX 2.1.0 adds texture projection nodes for mapping textures without UV coordinates. The workflow described uses the Node Library under Autodesk to add a projection node into the graph, connect a texture input, then connect the output to a material. Eight projection types are available: Planar, Spherical, Cylindrical, Ball, Cubic, Tri-Planar, Concentric, and Perspective. A Projection node combines all types into one node, with switching done inside the node so the texture updates on the object.

LookdevX also adds Graph Editor search to find nodes by name, aiming to reduce scrolling in larger graphs. Universal SRT manipulator support lands for the first matrix44 input port on LookdevX nodes, letting you edit that transform directly in the viewport via the usual manipulator workflow.

Arnold and Substance updates ride along

Autodesk lists Arnold for Maya 5.6.1.1 as part of the update, with changes since 2027 including a tech preview of Flow Render, custom AOVs for volume shaders, MIKKTSpace normal mapping support, and additional updates. Maya 2027.1 also includes Substance 3D 3.0.6.

Treat both as pipeline changes, even if you never touch a shader graph. Renderer and material tooling changes can break assumptions in templated scenes, and reliabel output beats exciting output when a client stares at a schedule.

Platforms and pricing

Maya 2027.1 is available for Windows 11, RHEL, and Rocky Linux 8.10 and 9.7, plus macOS 14.0 and later. The software is rental-only, with subscriptions listed as US$255 per month or US$2,010 per year. In many countries, artists earning under US$100,000 per year and working on projects valued under US$100,000 per year qualify for Maya Indie subscriptions, listed as US$330 per year. Maya Creative 2027.1 is also available, listed as pay-as-you-go with prices starting at US$3 per day and a minimum spend of US$300 per year. It has the same new features as Maya 2027.1, except for Bifrost.

New tools and innovations should always be tested before use in production, ideally on real shots and real assets, not a perfect demo cube that never gets a change request.

https://help.autodesk.com/view/MAYAUL/2027/ENU/?guid=GUID-F923AA68-6CE5-4292-88EA-292F5A786BA2

The post Maya 2027.1 adds OTIO to Sequencer first appeared on DIGITAL PRODUCTION and was written by Bela Beier.

For those who don’t know the studio: Lux Aeterna delivers documentary and natural history VFX including CG environments, FX, and compositing, and it mixes scanned data with CG for shows made with broadcasters and streamers.

History likes receipts

Historical reconstruction only works when the images carry the same authority as the research. The studio leans on archaeological reference, field documentation, and specialist feedback to keep reconstructions grounded, especially when the brief asks for ancient humans that look plausible in stills and in sequence work.

Two recent projects show how far that approach goes. Secrets of the Neanderthals needed a cave interior rebuild and physical remains that read like real bones. Human pushed further, asking for early human avatars built from actor scans and refined against scientific consultation, plus maps and timelines driven by datasets.

Bones first, drama second

For the Neanderthal work, the team recreated the interior of Shanidar Cave in northern Iraq, the site of one of the largest ever discoveries of Neanderthal remains. It used a mix of reference drawings, photographs, and expert advice from professors at the University of Cambridge and Liverpool John Moores University to guide accuracy, including cases where remains had been damaged or moved from their original positions.

Skeleton placement used inverse kinematics so the bones could interact with the ground in a natural way. The pipeline also dealt with scan data arriving as a 3D point cloud, then converting it into polygons that could support a usable cave reconstruction. That conversion problem tends to separate demo reels from production, because bad meshing reads instantly, even when the camera does not linger.

Point clouds, polygons, and the cave that ate your schedule

The cave build started with LiDAR scans that came in as a 3D point cloud. The team developed algorithms to convert the points into polygons for the reconstruction, then used Houdini to isolate areas of scan data so the mesh could be assembled and recombined like a 3D jigsaw. That kind of procedure-heavy work sits squarely in the Houdini mindset: build repeatable ops, then iterate until the scan stops looking like scan data and starts looking like a place.

The result aims for a CG environment that matches the real location closely enough that it can carry the weight of the story, while also supporting the additional CG work needed for the remains and the shot context. In a documentary pipeline, that matters because the images often sit right next to photography, maps, and archive material, with no cinematic lighting trickery to hide behind.

Lux Aeterna delivered 60 shots for a single series, and that number matters because it hints at the production scale when planning resources. WE might e talking about geological and evolutionary tiespans in the story, but delivery is far more rapid.

Full bodies: photogrammetry, casting, and millimetre arguments

The later project asked for historically accurate avatars built from scans of real performers, refined with skeletal research and scientific input. It was a five-part series produced by BBC Studios Science Unit for the BBC and PBS NOVA, hosted by paleoanthropologist Ella Al-Shamahi, and it frames visual effects as a way to tell a story spanning hundreds of thousands of years without a written record.

The workflow combined ultra-high-resolution body scans with iterative model refinements guided by BBC Studios and scientific advisors. It worked with London-based scanning studio Sample & Hold, which describes custom head and body photogrammetry systems and a photogrammetry robot for objects. In practice, that puts photogrammetry into the same category as any other acquisition step: controlled capture, predictable output, and a pipeline that can survive the boring parts like data cleanup and repeat scans.

The stated goal was four historically accurate avatars representing Jebel Irhoud, Neanderthals, Homo floresiensis, and Homo erectus, based on scientific data and real-world actors. Alongside the character work, the project also required prehistoric environments and landscapes to show migration and later disappearance of early human life across the globe. The work targets ancient humans, but it does not tolerate ancient guesswork.

Maps, timelines, and the part nobody notices until it breaks

A second strand of the work focused on animated maps and timelines that visualised migration, development, and disappearance across millennia. The graphics are being built using datasets provided by BBC Studios Science Unit researchers and scientific consultants, and not as speculative graphics.

One specific challenge involved changing coastlines and submerged landmasses, where the team created transitions and overlays to keep the visuals clear while staying scientifically accurate. That is the kind of “small” work that carries a lot of editorial risk: the map has to be readable, the timing has to serve the cut, and the choices have to stay consistent across episodes.

On the delivery scale, the project description states sixty crafted shots across five hour-long episodes, and it frames the approach as avoiding prosthetics and overly stylised effects while using a hybrid of photogrammetry, consultation, and minimalist Compositing.

What to take away if you do this for a living

If your job involves building reconstructions that sit next to real-world evidence, the takeaway is simple: acquisition quality and reference discipline decide how much time you spend “fixing” later. Scan data arrives noisy, research notes arrive detailed, and schedules arrive optimistic. The pipeline has to translate all three into images that read as plausible without distracting from the content. And as always, test any new workflow, plugin, or automation step on a throwaway shot before you bet a delivery on it. Just like with rare fossils, you don’t want to play loose with the materials.

https://www.lavfx.com/
https://www.lavfx.com/secrets-of-the-neanderthals
https://www.lavfx.com/blog/human

P.S. You have NO idea how big the challenge was not to replace “Ancient Humans” and “Prehistoric” with the users of one ore more DCC-packages….

The post Lux Aeterna rebuilds ancient humans first appeared on DIGITAL PRODUCTION and was written by Bela Beier.

For those who don’t know the tool: Stylized Tree Asset Generator is a Blender Geometry Nodes based tree builder for stylized environments, with Eevee focused shading and toolsets that also run in Cycles.

Pines, at last, for people who hate needles

Stylized Tree Asset Generator now includes a dedicated Stylized Pine Tree Asset Generator as part of its 2.0 update. The new pine toolset comes with new assets, textures, shaders, and materials, and keeps the same general workflow as the original tree generator to stay consistent.

The update also targets speed and housekeeping. Version 2.0 replaces deprecated nodes from Blender 4.2, optimizes UV storage, and cleans up and optimizes the Geometry Nodes setup. It also adds directional control to the wind feature and ships an updated user guide.

If you were already using the original generator for quick background dressing, the pine addition is welcome because it expands the library beyond broadleaf shapes and lets you cover the classic stylized use case: conifers in midground forests, mountain ranges, and gamey dioramas without modeling individual branches by hand.

Painterly Trees for Blender: ShapeScape Studio Blooms

What it actually builds and how far you can push it

The core promise is a Geometry Nodes setup that lets you shape trees quickly, then dial resolution up or down depending on what you need. You can go from low poly silhouettes to more detailed results by adjusting resolution and density inputs, keeping a tighter leash on polygon count.

The tool generates automatic UVs so you can bake textures. That makes it easier to take a procedural look, commit it, and move on, whether you need a static asset for a library or a one-off hero tree that still has to survive export.

It also supports using your own mesh to shape the leaves. That is the escape hatch for people who like procedural trunks but want art-directed foliage shapes, or who already have leaf cards and want the generator to place them. There is also a Random Generator input intended to produce infinite variations with similar characteristics. In practice, that is the difference between a forest and a cloning accident, especially when you need dozens of trees that read as a family but do not look copied.

Some of the shading work targets Eevee. The product notes say the shading was designed in Eevee and may not work as intended in Cycles by default, while the rest of the tools work in both render engines. So if your pipeline leans on Cycles, expect to tweak materials rather than treating the lookdev as drop-in.

Painterly Garden: 200+ Ghibli-Style Foliage Assets for Blender

Presets, shaders, normals, and the parts you will actually notice

Stylized Tree Asset Generator includes preset textures and materials aimed at getting you to a usable look quickly. It lists 10 leaf texture presets, 16 trunk presets, and 12 hand-painted procedural leaf textures. Those sit alongside procedural textures that remain adjustable, so you can keep the preset as a starting point rather than a locked style.

For shading, it includes a custom toon shader for the trunk and two shading groups for leaves, one designed for simpler use and one offering deeper controls. It also includes four sets of custom normals meant to help you land the shading style you want and to keep shading stable when you animate wind and use the scatter tool.

The update also keeps the wind feature in the toolbox, and adds direction control. That matters because wind without direction tends to look like your trees are trying to shake off a bad rig. Directional control lets you line up motion with camera moves or scene beats, instead of getting random flapping.

This is also where teh usual production advice applies: test it in a real shot, with your real render settings, before you roll it into a template file and wonder why the farm hates you.

Compatibility and versions

The newest versions of the tool are made for Blender 4.2 and newer, while still including older versions of the tools as far back as Blender 3.3. If your studio sits on a locked version for a show, that matters, because it suggests you can still run a supported variant without forcing an upgrade mid-production. The 2.0 update specifically calls out node maintenance aligned with Blender 4.2, including replacing deprecated nodes and cleaning up the node graphs. That kind of update tends to be invisible until it is missing, at which point your node tree becomes an archeological dig.

V2.0 Update
Huge update of my Stylized Tree Asset Generator, you can now make Stylized Pine Trees!
And it's 25% off right now on @superhivemarket https://t.co/noDDhYwniC https://t.co/AlV1OYbOUM pic.twitter.com/tWZSN5v4fK

— Rei (@Reipart_) May 6, 2026

Pricing and the temporary deal situation

Pricing is tiered on Superhive Market. A Standard License is listed at $12.50 and includes textures, shading nodes, geometry nodes, and tools. An Asset Pack Standard License is listed at $16.50 and adds the full asset pack. A Commercial Use option is listed at $42 and includes the asset pack while allowing commercial use.

If you are evaluating it for production, the practical move is to grab it, build a handful of trees that match your show style, bake what you need, and push them through your actual export and render path. Then decide whether it becomes a staple, a one-off, or a neat toy that lives in a personal toolkit.

https://superhivemarket.com/products/stylized-tree-generator

The post If you yearn for the pines, go Blender first appeared on DIGITAL PRODUCTION and was written by Bela Beier.

Motion designer Mike Gaynor built Caddis over four months in nights and weekends, and pitched it as the layer timeline you already know paired with a node graph inside every single layer.

Work starts in a familiar stack of layers, with keyframes and timing edits on a timeline. Select a layer and its node contents appear in a graph panel beside the timeline and viewport. The idea is to avoid choosing a single paradigm when motion work often lives between both. Inside that per-layer grahp, the beta already includes more than 100 nodes to wire together. Nodes can drive parameters directly, with examples like linking rotation to scale, scale to audio, and audio to color.

Caddis Layers can stay simple, or turn fully procedural

A layer can stay as basic as one line of text, or expand into a fully procedural build with fields, shapes, video, and audio flowing through it. The demo frames it like patching a modular synth, with links between values, movement, and math. The product site leans into the same concept with a promise of visual logic in place of expressions, and a workflow where every parameter becomes something you can wire, modulate, or replace. It also positions the node graph as the home for compositing work like blending, masking, and mattes. Color tokens appear in the demo as a way to recolor a whole project in one click. The demo also shows saving subgraphs as recipes, then reusing or sharing them as a single file.

Responsive comps, plus GPU-native rendering

The demo says designs can be responsive, showing a resize from 16 by 9 to 9 by 16 with the layout adapting on its own. Caddis describes itself as a native desktop app on a modern GPU pipeline. The website calls out GPU-native rendering, aiming for a responsive viewport while iterating, and exports without leaving the tool. Treat that as a marketing claim until your own workstation agrees. Either way, new tools and innovations should be tested before use in production, ideally on real shots, real deadlines, and at least one truly cursed client change request. Beta is coming, so we obviously haven’t tried it yet – sign up as well, we’ll learn together what actually appears when Caddis comes out.

Import and export reality check

Caddis positions itself as an alternative rather than a drop-in replacement for After Effects and does not import After Effects projects. Instead, it works by importing media and rebuilding comps inside the app. On export, the product site lists standard formats including Apple ProRes, MP4, and image sequences including H.264 and ProRes, plus PNG and OpenEXR image sequences, and standard web formats. The demo additionally names WebM and GIF, plus PNG sequences, as native.

Caddis Pricing, beta status, and platform notes

Caddis is free during beta. The product site lists a $99 launch price for early adopters and $129 regular pricing, positioned as a one-time purchase with no subscription. The software should be compatible with macOS 12.0 or later, with a Windows version due shortly after launch. If you plan to roll it into a pipeline, assume the usual early-tool homework: bake out deliverables, double-check colour management expectations, and confirm the layer graph behaviour does not change between beta waves.

https://www.caddis.app/

The post Caddis mixes layers with nodes per layer first appeared on DIGITAL PRODUCTION and was written by Bela Beier.

For those who don’t know the tool: Boris FX Sapphire is a multi host VFX plug-in suite for editors and compositors, used in After Effects, Premiere, Media Composer, and OpenFX hosts like Resolve, Flame, and Nuke.

Defocus that tries to behave like glass

Boris FX ships Sapphire 2026.5 with a new effect called Advanced Defocus, built to recreate lens blur character rather than just blur pixels. In Sapphire, artists can start from presets, including ones built from real-world lens references and more stylised options, then dial in Defocus Width plus relative width and height for anamorphic style stretching.

Advanced Defocus focuses on the lens kernel, where artists shape bokeh as circles, polygons with adjustable sides and roundness, or custom shapes. It also includes controls to introduce imperfections tied to aperture blades, such as adjustable blade notches, as well as options for colour fringing and noise. The tool targets everything from cheap, dirty glass to high-end primes, depending on how far you push those controls.

The lens vignette section adds classic edge darkening, but also an optcial vignette control that changes distortion toward the frame edges. A Matte Box control goes past soft cropping by simulating uneven light entry, slightly darkening one side while also clipping individual defocused highlights.

From grungy to clean

Advanced Defocus also includes lens textures that break up overly uniform bokeh, with parameters that range from subtle variation to grungy lens looks. Extra controls include highlight boosting, chromatic-style fringing, and grain management to match the foreground and background.

In Adobe After Effects, Advanced Defocus appears under Effect in the Sapphire Blur plus Sharpen category. The effect can work as a straight lens emulation pass, a stylised motion graphics treatment, or a transition building block. A workflow shown in Blackmagic DaVinci Resolve Fusion uses Advanced Defocus to soften a keyed background for more believable depth, then adds sensor-style grain to help match elements. Another workflow in After Effects links defocus controls across layers, uses Affect Alpha to defocus type with the background, and offsets values to keep the illusion that typography sits closer to camera.

For edits, Advanced Defocus can also drive transitions inside VEGAS Pro by building an S Transition in the Sapphire Builder variant designed for transitions. That approach ties animation to the transition length on the timeline rather than keyframing, and then applies the same peak values to both incoming and outgoing clips.

Glare gets a rebuild, and flares get louder

Sapphire 2026.5 reworks S_Glare with smoother rendering, richer spectral color, and updated parameters including highlight isolation, cleaner rays, and more natural falloff, plus new styles that widen the look range beyond traditional glare.

In Adobe After Effects, S_Glare sits under the Lighting category and behaves the same across Sapphire hosts. The first control to touch is Threshold: raise it for fewer glares, lower it for more, and expect wildly different results depending on the footage. Sapphire 2026.5 also changes what the defaults look like compared with older versions, so the same effect can start from a different baseline than legacy installs.

Presets matter a lot for S_Glare, but the preview can mislead. Results change with viewer zoom level, so checking at 100 percent gives a more reliable read before you commit. Presets also store Threshold, so loading a preset often means rebalancing Threshold right away to avoid either nothing happening or everything exploding.

If glares drift or slip onto areas you do not want, Threshold Blur becomes the other big lever. Lowering Threshold Blur picks up many more points of interest, which can reduce slippage but may add jitter. A practical balancing rule shown here is: when Blur comes down, Threshold goes up, then you fine-tune from there.

Sapphire includes integrated Mocha inside the effect for masking control. A workflow shown here uses an object brush and Mask ML to generate a mask, then inverts the Mocha mask so glare stays in the scene but stops emanating from a subject.

S_Glare also appears as an embedded component in S_NightSky, where you can open the glare editor, load glare presets, and adjust glare size to customise the look directly within the NightSky effect.

Procedural ridges, more presets, faster stacking

A new Texture Ridges effect generates ridge-like patterns from noise, with controls for octave scaling, speed, frequency, contrast, and layering to build animated surface detail and abstract motion design textures. Sapphire 2026.5 also adds more than 100 new and improved presets, including anime, sci-fi, and abstract fractal motion graphics looks.

Effect Builder gets an interface update aimed at faster custom effect and transition creation, plus new built-in Dots and Noise tools. If you build stacks for repeatable looks, this is the part worth a quiet test session before you let it touch client shots.

Pricing and updates

Sapphire ships as a plug-in collection with subscriptions, upgrade and support plans, and perpetual licenses. Subscriptions start at 545 US dollars per year or 80 US dollars per month. Customers with current Sapphire or Boris FX Suite subscriptions, or with Sapphire upgrade and support plans, get the 2026.5 release obviously as a free update. If you aren’t sure: get the free Trialversion. As always, test new tools and presets in your own pipeline before you rely on them in production.

https://borisfx.com/products/sapphire/#whats-new

The post Boris FX Sapphire 2026.5 adds Advanced Defocus first appeared on DIGITAL PRODUCTION and was written by Bela Beier.

For those who don’t know the tool: The Pixel Farm makes PFTrack, a node based matchmove and reconstruction tool that exports to DCCs like Autodesk Maya, Foundry Nuke, SideFX Houdini, Blender and Unreal Engine, with improved dense point clouds via OpenUSD.

Hero Cloud is a new reconstruction node

PFTrack Build 26.05.19 adds Hero Cloud, a node that generates a measured dense 3D point cloud from a single tracked plate. It sits in the Geometry category and runs downstream of a solved camera, turning an ordinary camera solve into spatial data you can actually measure against. Hero Cloud claims to be through-the-lens reconstruction, meaning it extracts depth from the camera movement in the shot rather than relying on a separate photogrammetry set or a LiDAR scan.

The node targets a familiar production reality: you get a brief that needs measured 3D, but the the on-set… people…. said “Fix it in Post, heheeheeh” and did not capture the extra data for cases like set extension, CG integration, lighting reference, forensic analysis, architectural measurement, and archival footage where you cannot go back and reshoot reference. If the plate is all you have, Hero Cloud aims to make that plate pull double duty.

Hero Cloud works on plates PFTrack can track and solve, and works footage sources that include cinema cameras, drones, body cams, dash cams, action cameras, mirrorless and DSLR cameras, CCTV, and archival film. Basically, every type of video. Camera metadata can help but it is not required, and the Camera Sensor Database can cover common cameras automatically, with the Camera Solver able to estimate parameters when metadata is missing.

There is a catch, and it is the same catch as every method that tries to infer depth from motion: the shot needs parallax. Locked off shots or shots with very little movement can produce sparse or unreliable results. Most production footage, including handheld stationary shots, can still have enough movement to produce usable reconstruction, while deliberate camera motion tends to produce richer results.

A cleaner route into splat training

PFTrack 26.05.19 adds a Postshot export option that writes Hero Cloud point clouds and associated tracked cameras in COLMAP format. In other words, matchmove and reconstruction can stay in the same app up to the point where you hand off to splat training.

If you already live in the Gaussian Splatting world, COLMAP is a common interchange format and COLMAP itself has both GUI and command line workflows. The practical value here is that you do not have to glue together separate tracking, reconstruction, and export steps before you ever open Jawset Postshot. You track the plate, generate the cloud, export in COLMAP format, then train the splat.

This is an artist friendly route into a workflow that has historically leaned on command line tooling. That is a reasonable and recommendable goal, but it still deserves the usual pipeline skepticism: try it on a real shot and verify your coordinate frames, scaling, and camera consistency before you let it anywhere near a deliverable.

USD point clouds now carry more than positions

The same build extends USD export to support dense point clouds with per point normal and colour data, because a point cloud that only carries XYZ positions often becomes a dumb scaffold the moment it leaves its origin app. Normals and colour help downstream tools treat the cloud as more than a vague spatial fog, and can make it easier to use for measurement, placement, modelling reference, and lookdev decisions.

Improved integration with USD aware tools including Unreal Engine, Maya, and Houdini. It also claims (!) improved FBX export reliability for very large dense point clouds, aimed at users who previously hit issues exporting big clouds via FBX.

If your pipeline already standardises on USD, this is the kind of unglamorous export detail that can decide whether a new feature becomes a daily tool or a demo-only party trick. Still, test it on your actual asset scale and on your actual DCC import settings. Export support is never a substitute for shot-based validation, and you only find the sharp edges when production hits them, much like furniture at night can only be found with toes and shins.

Photo Mesh gets a single shot input path

Studio and Enterprise editions receive an update to Photo Mesh that enables it to consume Hero Cloud point clouds as input. That creates an internal single-shot path from tracked plate to dense cloud to surfaced textured mesh, without leaving PFTrack. The Pixel Farm describes Photo Mesh as the highest fidelity route when you have a planned photo set, while Hero Cloud covers the case where you only have the hero plate.

In practical terms, this puts a reconstruction option closer to matchmove, and it reduces the number of handoffs in the middle of a cmaera tracking job. Whether it replaces any external reconstruction tooling depends on what you already trust for meshing, texturing, and scale fidelity, but the internal integration is at least a coherent story: generate the cloud, feed it into Photo Mesh, then export into the rest of your pipeline.

The viewport tweak you will actually use

26.05.19 also adds an Active Camera viewport option in viewer windows, with a snap to active clip toggle. It sounds minor, and it is, which is why it will get used: quick visual verification against the source plate tends to catch mistakes faster than hunting through node outputs. The release notes pitch it as useful for checking Hero Cloud reconstruction, but the feature applies anywhere you want a fast way to see what the tracked camera saw.

Trial and licensing notes

Solo trial mode now enables full export functionality for seven days. The release notes describe this as enough time to take a plate from track through Hero Cloud and out to Postshot or USD, rather than being limited to evaluating the toolset without export.

For Studio, the release notes state it is available on rent to buy for 5 or 30 days, or as a perpetual purchase. The PFTrack Creator Program page states PFTrack Solo licenses sell for £699. Treat that as a price reference for Solo licensing, not a promise of regional pricing or bundles.

What this changes in real work

Hero Cloud aims to shift PFTrack from a pure matchmove and survey friendly reconstruction hub toward a single shot scene reconstruction step that can be used even when the onset data plan fell apart. The strongest parts of the release are not flashy, they are connective tissue: COLMAP export for Postshot, denser USD point cloud payloads, and a meshing path that stays inside the same graph.

It is also a reminder that the industry has started to treat point clouds as a first class asset, not only a temporary byproduct. When point clouds export with colour and normals and survive the trip into USD aware DCCs, they become reusable poitn based reference that can support layout, set extension decisions, and reconstruction driven previs.

https://www.pftrack.com/post/pftrack-build-26-05-19-is-now-live

https://www.pftrack.com/post/hero-cloud-tutorial

The post PFTrack gets Hero Cloud first appeared on DIGITAL PRODUCTION and was written by Bela Beier.

For those who don’t know the tool: Clip Studio Paint does illustration, comics, and 2D animation on desktop and mobile, and sits alongside the wider Clip Studio app and its cloud and asset ecosystem.

Version 5.0 is about speed and control

Celsys puts Clip Studio Paint 5.0 on iPad, iPhone, Android, Windows, and macOS as a new major release, updating drawing performance and workflow comfort, with new tools aimed at getting cleaner results without constantly switching modes.

If you spend your day in line work, the headline feature is Smart Shape. You draw with any pen or brush, then long press to tidy a line, curve, or shape without jumping to a separate figure tool. That idea reads small, but it targets the exact kind of micro friction that adds up over a hundred panels or a long day of design passes. It is also the kind of feature that can change muscle memory, so plan a short retraining window before you bet client work on it.

The 5.0 feature list also calls out faster rendering with large brushes using a new setting that trades quality for speed, and improved rendering speed for thick watercolor edge settings. Stroke previews can help reduce brush lag when you draw with high stabilization. The blur tool and brushes with Running Color also change blending behavior, so colors outside the brush cursor or selection stop blending in that mode.

Smart Shape wants cleaner lines without a new tool

Smart Shape lives in the same place as your usual brushes, and it tries to keep you there. Instead of switching away from your current drawing tool, you trigger the cleanup by holding your stylus down at the end of a storke, then let the app resolve it into a cleaner result. That matters most when you bounce between sketchy exploration and precise technical marks, where changing tools can feel like slamming the brakes every few seconds.

On the settings side, Smart Shape can be toggled in Preferences under Tool. That makes it easy to turn on for inking sessions and turn off when you want raw, messy exploration, without building separate workspaces just to keep it from interfering.

The update also introduces velocity as a new brush dynamic, with a velocity graph added to Pen Pressure Settings and Tilt Settings as an option for brush size and opacity input dynamics. In plain terms, you can push values higher the faster you draw, which is useful when you want quick flicks to behave differently from slow, controlled marks.

3D gets hands, fog, and more paintable surfaces

On the 3D side, Clip Studio Paint 5.0 adds a hand model to the 3D materials, positioned as a reference tool for drawing hands. The tool includes adjustable hand shapes, and it works with hand pose materials and a Hand Scanner for quick posing. That puts a dedicated hand reference directly in the same scene where you already stage characters and props, instead of forcing a second app or a browser tab for reference.

The 3D feature list also expands where you can draw directly on 3D objects, including UV mapped vertices plus 3D primitives and 3D drawing figures. It also adds the ability to group multiple 3D models into a folder and move or rotate them as one, which fits the way artists actually block scenes, especially when you want to keep a kitbash cluster behaving like a single prop.

Fog gets a specific upgrade too. You can set Fog type to Height on a 3D layer and define fog based on the height of the 3D space, including whether it starts from above or below. It is a simple knob, but it can help with depth cues in backgrounds, quick lighting mood boards, and concept paintovers.

For internal workflows, the EX edition gets batch export textures on 3D layers when you select them with the Object tool. That lets you export all textures of a custom material or model at once, which sounds mundane until you are the person who keeps getting asked to deliver “all the textures, please” five minutes before a handoff.

If you follow concept art workflows, the net effect is less time fighting reference and more time iterating on design.

Layer ops and UI cleanup aim at real work

A production painting app lives or dies by small operations, and 5.0 targets a few that show up constantly. Tonal correction commands can now apply to multiple layers at once, applying color corrections to each selected layer. That is useful when you keep values separated by material, pass, or shot element, but still need consistent global tweaks without flattening.

The Fill tool also gets a speed and accuracy improvement, pitched as faster processing with more accurate results. If your pipeline includes lots of flat color blocking for comics, animation layouts, or stylized game art, faster fill behavior is the kind of quiet win that saves real time.

Interface changes focus on reducing terminology and palette friction. Sub Tools get merged into Tools, and tool icons can pop up with related palettes. The Material palette gets a new History folder to show recently used materials, plus easier search and sorting.

In 5.0.4, image materials and template materials, including 3D hand model materials, can sync to the Clip Studio cloud and publish to Clip Studio Assets. That is a practical detail for teams, classrooms, or anyone jumping between machines, as long as you are comfortable with the asset management implications and you test your sync behavior before relying on it in a deadline week.

Licensing and

Celsys lays out multiple ways to get 5.0, depending on whether you subscribe or buy perpetual on Windows and macOS.

New perpetual licenses list at 63 Dollars for Clip Studio Paint PRO 5.0 and 277 Dollars for Clip Studio Paint EX 5.0 on Windows and macOS. Discounted perpetual upgrades from 4.0 to 5.0 list at 29 USD for PRO and 83 $ for EX, with a PRO to EX discounted upgrade to 5.0 listed at 243$

Update Pass pricing for 12 months on Windows and macOS lists at 11$ for PRO and 32$ for EX. Active subscribers and Update Pass users can update to 5.0 as part of their plan.

If your daily setup includes a pen display, a few of these changes will feel less like “new features” and more like fewer tiny interruptions between you and the canvas. Test Smart Shape with your usual brush presets, stabilization settings, and tablet drivers. Test the new blur behavior on the exact kind of painterly blends you rely on. Test 3D grouping and paint on model workflows with the kinds of assets you actually use, especially if you share files across machines or collaborators. New tools and innovations should be tested before use in production, even when the change looks small.

https://www.clipstudio.net/en/dl/release_note/latest/

https://www.clipstudio.net/en/news/202603/11_01/

The post Clip Studio Paint 5.0 with 3D hands first appeared on DIGITAL PRODUCTION and was written by Bela Beier.

For those who don’t know the tool: DroneSiteBuilder is a script for Autodesk 3ds Max that reads drone photo metadata to assemble terrain, map context, and matched cameras, bundling GeoBuild and CameraMatch and supporting handoff to Blender, SketchUp, and Autodesk Maya.

What DroneSiteBuilder is trying to fix

DroneSiteBuilder Enterprise turns a folder of drone photos into a full site context scene inside the 3ds Max ecosystem: terrain, aerial drape, buildings, roads, land cover features, points of interest, and one matched camera per photo.

The pipeline reads XMP metadata per image and uses it to place helpers at ground level and flight altitude, then creates a renderer-aware camera per photo and refines orientation using vanishing point detection. The tool targets 3ds Max 2020 or newer on Windows and uses Python 3.9 through 3.12 with NumPy and OpenCV, plus optional modules for the Google path.

First use, abbreviated

Install a standalone Python build and make sure Add Python to PATH is enabled during install, because the tool does not rely on the 3ds Max built-in Python. Place DroneSiteBuilder_Enterprise.ms and vp_detector.py in the same folder and do not install under Program Files, since Windows blocks writes there.

Launch 3ds Max and load the script via drag-and-drop into a viewport or via Scripting > Run Script. Paste your licence key into the activation dialogue and activate, with support for an Enterprise key format and existing CameraMatch Studio keys. After activation the key caches locally for thirty days and the rollout opens.

For the first build, keep original DNG or JPEG drone files in a single folder, keep filenames ending in digits, and keep an internet connection available for the auto fetch steps. Pick a terrain DEM source, keep NOAA GEOID18 enabled for continental US sites and disabled outside the US, then run Process Folder of Drone Photos and accept the summary dialogue. Inspect the result by comparing a matched camera view against the source photo.

The new checkbox: Google Photorealistic 3D Tiles

Enterprise v1.2 adds an opt in mode that fetches Google Photorealistic 3D Tiles and imports them into 3ds Max as a single merged glb, covering the photo bounding box. The intention is simple: pull a photogrammetric backdrop mesh with terrain, textures, and buildings baked into one continuous model, using the same dataset shown in Google Earth.

The Google path requires a Google Maps Platform project with billing enabled and the Map Tiles API enabled, plus a saved API key in the rollout. The manual describes 1,000 root tileset requests per month free and a per 1,000 price after that, with one DroneSiteBuilder run treated as one root tileset request. If the fetch fails, the tool reports common causes like missing API enablement, low coverage, EEA billed accounts being blocked for this endpoint, missing Python modules, and older 3ds Max builds needing a glTF importer.

This is also where the gaudrrails get real: the Google import produces mesh only content with baked textures, so you do not get separate terrain, buildings, roads, and features objects to isolate, re material, or hide by category.

The standard path is still the controllable one

If you leave the Google option off, the pipeline builds a layered context using public services. Terrain comes from USGS 3DEP in the US or OpenTopography worldwide, aerial imagery comes from Esri World Imagery as a single bounding box JPEG, and vector context comes from OpenStreetMap via Overpass.

The scene builds under a single root helper so you can move, rotate, or scale the entire site as one unit, while cameras intentionally sit outside that parent chain to support camera transplant between scenes. If buildings and roads fail to appear on a run, the manual provides a manual Overpass refetch button that rebuilds buildings, roads, and land features without disturbing terrain, drape, helpers, or cameras.

OpenStreetMap accuracy varies by location and that the resulting geometry accuracy for this context layer sits in the one to six meter range. It contrasts that with paid city model providers such as AccuCities when millimeter level detail matters.

Export and handoff from 3ds Max

DroneSiteBuilder does not change how 3ds Max exports, but it does influence what you export. The standard path creates distinct terrain, buildings, roads, and feature objects you can selectively include in deliverables, while the Google path imports a tile based mesh group that is already baked.

For broad DCC and engine handoffs, 3ds Max includes a built in exporter for glTF and supports export workflows for USD, with export options available through File export and USD and USDZ format selection when the USD tooling is installed. For USD pipelines, the official OpenUSD plugin for 3ds Max is published on GitHub, and Autodesk documentation describes supported USD content types including meshes and cameras.

If your downstream is realtime, glTF targets web and interactive use cases, and you can also push common interchange paths like FBX into engines such as Unity and Epic Unreal Engine, depending on your studio conventions. For camera and layout continuity between scenes, the bundle includes a camera transplant workflow that exports camera data to JSON and recreates it with full precision in another scene.

Practical reality check

This toolkit aims to comperss a traditional drone to 3D context workflow into a short unattended run. The promise stands or falls on your input photos keeping XMP metadata intact, on your site area having decent public map coverage, and on you verifying the result against the plate before trusting it.

We don’t know the price yet, but if you already own the camera match tool in the Studio version, you get it for free, apparently. Quoting: Existing CameraMatch Studio licence keys activate the full DroneSiteBuilder bundle. Studio holders do not pay twice. 

Try both context modes on a test job: the standard layered build when you need controllable components and re-lighting freedom, the Google mesh mode when you need a fast photogrammetry backdrop and can live with mesh-only content and licensing constraints.

https://jamiecardoso-mentalray.blogspot.com/2026/03/dronesitebuilder-enterprise-v12-one.html

https://jamiecardoso.gumroad.com/

The post DroneSiteBuilder adds Google 3D Tiles option first appeared on DIGITAL PRODUCTION and was written by Bela Beier.

In this video we will explore how we can simulate realistic “kick up dust” from wind that is blowing over a surface in Maxons Cinema 4Ds internal Pyro simulation tool. The most likely use case is the effect you probably know from a helicopter taking of or landing.
As I learned yesterday, this effect is known as “downwash”.

Learn how to solve for air pressure and use the output of the moving airfield to automatically create and simulate dust picked up from the ground and carried away by the air movement realistically.

CHAPTERS

00:00 Intro

00:48 Tut Overview

01:31 C4D Scene Setup: Geometry

03:02 About Pyro Solvers

04:33 Setting up a Pyro Domain

08:26 Setting up the Downwash Wind

10:33 Setting up Vectors (Velocity)

14:57 Offsetting the Collision Landscape

15:57 Caching the 1st (Base) Simulation

16:30 Setting up the Dust Emitter Vertex Map

18:33 Simulation Scene Object

20:21 Field Force

20:49 Finalizing the Downwash Sim

23:00 Looking at the Results

Download the Tut Scene by becoming a Patreon member. No matter which tier!

VIDEO RELATED LINKS:
Maxon’s Official Website: https://www.maxon.net/
Octane C4D Otoy Official Website: https://render.otoy.com/forum/viewfor…

---

If you’ve ever wondered what happens when a VFX artist spends too much time obsessing over pixels and lighting, well, welcome to my world! You can find all my latest experiments, tutorials, and general nerdy shenanigans here:

Website: silverwing-vfx.de
Patreon: patreon.com/SilverwingVFX (Get scenefiles for all of my tutorial scenes also while supporting me)
Instagram: instagram.com/silverwingvfx (Finished 3D projects and engagement with the community)
YouTube: youtube.com/@SilverwingVFX (Updates and news about my work and what I am up to)

And if you’re into retro gaming and deep-dive nostalgia, check out the big article I wrote for this magazine: my love letter to the legendary Game Boy. Because nothing says “true love” like an 8-bit screen and a battery life that could outlast modern smartphones.

The post C4D Pyro Tutorial: Helicopter Kickup Dust first appeared on DIGITAL PRODUCTION and was written by Raphael Rau.

For those who don’t know the tool: MoonRay is a production path tracer with a USD Hydra render delegate for tools using OpenUSD, positioned in rendering and lookdev next to ASWF staples like OpenColorIO.

The Academy Software Foundation has added MoonRay as a hosted project, keeping the renderer under foundation governance while opening contributions to a broader community. DreamWorks Animation developed MoonRay as an open source production path tracing renderer and has used it on every one of its feature films since 2019, including The Wild Robot and The Bad Guys 2. The project uses the Apache 2.0 license and is developed in C++.

MoonRay includes support for distributed rendering and a pixel matching XPU mode that processes bundles of rays on the GPU as well as the CPU. It also includes bundled path tracing and a USD Hydra render delegate for integration into content creation tools that support the OpenUSD standard, which should make interactive preview workflows less of a custom science project in teh average pipeline.

The ASWF angle

MoonRay now sits alongside other hosted efforts in the ASWF roster, including OpenEXR, OpenVDB, OpenTimelineIO, and Open Shading Language. If your facility already treats OpenColorIO as plumbing, this is the same neighborhood.

For contributors, the project points developers to openmoonray.org and to the ASWF Slack workspace for a MoonRay channel at slack.aswf.io. Documentation is published at docs.openmoonray.org, and the source repository lives under the OpenMoonRay organization on GitHub.

Keynote season meets SIGGRAPH season

ASWF Open Source Days runs in Los Angeles on July 19 to 20, 2026, and the schedule aligns with SIGGRAPH 2026 timing. The keynote comes from DreamWorks Animation CTO Bill Ballew, with a talk titled How to Train Your Renderer: MoonRay’s Journey from DreamWorks’ Dragons to the ASWF.

The event listing describes July 19 as the main program day in Los Angeles, followed by July 20 as a full day of open source Birds of a Feather sessions within SIGGRAPH. The Call for Proposals remains open through May 24, 2026, via the Open Source Days event site.

As always, test new tools and new governance setups before you bet a production schedule on them, even when the feautres list looks exactly like what your render wranglers asked for.

https://openmoonray.org/

https://www.aswf.io/

The post MoonRay Renderer joins ASWF as hosted project first appeared on DIGITAL PRODUCTION and was written by Bela Beier.

For those who don’t know the tool: Beeble builds AI relighting and video transformation tools for VFX, post, and virtual production, and Canvas is its very new node based environment that wires SwitchX and SwitchLight into repeatable shot workflows.

A node graph, but for AI outputs you can wrangle

Canvas lands as a node based AI compositing environment aimed at complex workflows across VFX, post, and virtual production. The pitch is straightforward: put AI video models, compositing utilities, and workflow automation into one visual system so teams can iterate across multiple shots without rebuilding the same logic over and over.

In practical terms, it targets the part of the job where you already juggle plates, masks, reference stills, and multiple look directions, then repeat that dance across a sequence.

What is actually in the box

Canvas presents itself as a node graph workflow editor for final render, with a catalog grouped into Input, AI Tools, Edit, and Utility. Input supports text prompts plus image files in PNG, JPEG, or WebP, and video files in MP4 or MOV. In other words, it starts where most editorial and comp workflows already start: media in, decisions next.

https://digitalproduction.com/2026/05/20/beeble-canvas

The AI Tools section includes a node for SwitchX, the same model as the standalone product, with source and alpha handled as video inputs. It also includes an LLM node that can generate files from a prompt with up to four media inputs, plus image generation and video generation nodes that can route to external models. For rotoscoping style work, Canvas includes a Video Matte node that outputs an alpha matte plus RGBA, with an automatic mode and an interactive selection mode, plus options aimed at general footage and green screen keys.

On the classic comp side, the Edit nodes cover the expected utility moves: extract a frame, trim, crop, resize, curves, invert, flip, and morphology operations like erode and dilate. Utility nodes cover housekeeping: sticky notes, routing for cleaner graphs, a viewer, side by side compare, and export. It’s not fully Nuke yet, but…

That combination matters because it lets artists keep the media prep and look development steps next to the model calls, instead of bouncing between separate tools and hoping filenames stay honest.

Relighting and PBR passes, now wired into the graph

The system includes access to SwitchLight for generating physically based rendering passes. In the Canvas node catalog, the VFX Pass Generator extracts PBR material maps including BaseColor, Normal, Depth, Roughness, Specular, and Metallic from image or video using SwitchLight 3.0.

That puts relgihting adjacent tasks into the same graph where you also assemble mattes, feed references, and generate variations. It also matches the stated intent of supporting controllable, iterative pipelines across multiple shots, not one off experiments.

Automation, batches, and the part everyone really wants

Canvas claims to be built around repeatability: build workflows once, apply them to shot sequences, and automate iteration without rebuilding node logic shot by shot. It also calls out batch processing and maintaining scene consistency across projects.

Those claims describe the correct pain point. Anyone who has ever reconnected the same five nodes fifty times will understand why a programmable layer matters. Still, treat the automation story like any new tool claim: test it in your own pipeline with your own edge cases before you bet any delivery on it.

The API angle: SwitchX in your pipeline, with pricing details

SwitchX API for video transformations in YOUR pipeline

Alongside Canvas, the SwitchX API is positioned for studios and developers who want to integrate video transformation and relighting capabilities directly into custom pipelines and software environments.

The developer portal offers a REST style workflow with uploads, job creation, and polling, and it explicitly supports 720p and 1080p output. It also has pay as you go credits in US Dollar, and pricing can start at $0.10 per generation. That pricing applies to the API offering as described there, while Canvas pricing is not specified, since it is part of Bebble Online.

Beeble Studio: 4K AI relighting on YOUR desktop

Availability, media assets, and credits

Canvas is available now via the Beeble platform, with a launch video hosted on YouTube (The Video we embedded above…) .

The boring but necessary reminder

New tools and innovations should be tested before use in production, especially when they touch shot consistency, automation, and delivery formats. Run a small sequence through, break it on purpose, and see how it fails before you trust it on a deadline.

https://docs.beeble.ai/beeble/canvas
https://docs.beeble.ai/beeble/overview

The post Beeble Canvas first appeared on DIGITAL PRODUCTION and was written by Bela Beier.

For those who don’t know the tool: Scene Auditor Pro is an add-on for Blender scenes that inspects datablocks and dependencies, then supports cleanup before export to Unreal Engine or Unity.

The Outliner is fine until it is not

Big productions rarely die from a single catastrophic mistake. They usually drown in tiny leftovers. Unused meshes that never got purged. Materials duplicated by imports. Textures that ballooned from sensible to cinematic for no reason. A scene that used to open instantly now takes a long sip of coffee before it even shows you a viewport.

Scene Auditor Pro positions itself as a response to that slow creep. The add-on builds a logical dependency graph from scratch rather than relying solely on the Outliner. It aims to show how objects, meshes, materials, textures, collections, and datablocks connect, so cleanup stops being a guessing game and becomes a decision.

A dependency graph that treats everything as suspicious

Scene Auditor Pro puts dependency visualization at the center: The add-on visualizes relationships across core Blender elements and linked datablocks. The point is not another pretty node view. The point is to make it obvious what is actually connected to what, and what sits alone, because orphaned and semi-orphaned data rarely announces itself. It hides in files as technical debt, and then turns up later as longer load times, higher memory use, and render slowdowns that feel impossible to diagnose.

Orphans, duplicates, and the usual suspects

The add-on includes orphan datablock detection. It calls out hidden unused meshes, materials, textures, actions, node groups, and datablocks as targets for discovery before they inflate file size and memory usage. That matters, because Blender files often accumulate leftovers in those categories during iteration.

Scene Auditor Pro also includes duplicate material and texture detection. The feature is a way to detect repeated assets across large scenes and identify opportunities to reduce unnecessary duplication. This targets common scenarios like kitbash heavy scenes, imported ArchViz content, and large environment work where the same texture set can show up under slightly different names and quietly waste memory.

The tool also looks for oversized texture maps and texture heavy materials as slowdowns – to surface the heavy hitters fast, including visibility into the largest assets and memory heavy elements. One of the claims is that it helps identify the real reasons scenes become slow or bloated, which stays in the realm of a marketing claim until you validate it on your own scenes.

Some parts read like a checklist of production annoyances, including unknown dependencies that make cleanup risky and heavy scenes with unclear bottlenecks. That is a pretty accurate description of Tuesday in many studios.

Export prep for engine pipelines

Scene Auditor Pro is part of pipeline and export validation duties, for Unreal Engine pipelines and Unity exports, plus ArchViz workflows, production cleanup, and scene handoff preparation. The theme here is less about pure Blender housekeeping and more about making sure scene data stays sane when it leaves Blender.

It also looks for missing UV maps or oversized textures as issues that can break game pipelines. If you do a lot of handoffs, the idea of seeing dependencies and unused datablocks before export can save time, or at least give you a clearer explanation for why a scene behaves badly.

Auto optimization, with a lot of caution tape

The add-on offers a step by step auto optimization approach with backup, emphasizing asset safety. It advises running auto optimization multiple times for best results. It also says that the tool will not touch data without explicit user action, and it describes multiple safety nets, transparency about what will happen, and reversibility through undo methods.

Those safety statements set expectations properly. Cleanup tools can be the fastest route to a broken scene if they run without restraint (Almost as bad as letting an AI agent loose). Here, the add-on leans into a safety first posture as a design goal, even if you will still want to test it thoroughly on duplicates of real production files.

Availability and pricing

Scene Auditor Pro is offered via Gumroad for 15 USD.

https://tarulahsanbd.gumroad.com/l/SceneAuditorPro

The post Scene Auditor Pro targets Blender bloat first appeared on DIGITAL PRODUCTION and was written by Bela Beier.

For those who don’t know the tool: Dash runs inside Unreal Engine as an asset browser plus world-building toolkit. The Fab build ships the Content Browser only, while the website installer can also unlock the wider toolset with a paid license.

Two installs, one idea

Polygonflow now offers Dash in two distinct ways: as a free plugin on Fab and as the full Dash installer from the Polygonflow website.

The Fab listing calls the package “Dash – Advanced Asset Manager” and in this version, it is “just” a content browser that lets you search and drag and drop local assets into any UE5 project. It includes tagging for your own assets with a stated limit of up to 1,000 assets tagged per month, plus a Smart Collection System for organizing assets.

The website installer route matters more, because the Dash Content Browser itself has been available for free since Dash version 1.9.0, but the free license is limited to the Content Browser side of the toolset. The free license includes the supported libraries, the tagging system, and the centralized browsing experience across UE5 projects, but not other Dash tools such as Easy Scattering, Procedural Meshes, Physics Tools, or Material and Atmospheric Tools.

What is actually different between Fab and the website build

The Fab version includes the Content Browser only, and explicitly points to the website download if you want the full plugin toolset. The website build splits into two experiences. The free license stays content-only, meaning you use the Content Browser, library integrations, tagging, and centralized asset browsing. A paid license can unlock the other Dash tools, Easy Scattering, Procedural Meshes, Physics Tools, and Material / Atmospheric Tools. So the practical difference is not the content browser UI, it is how far you want to go beyond asset browsing once you are inside the same plugin shell.

Included libraries, and why that matters more than the tagline

Both the Fab listing and the Dash docs have the same core set of integrated libraries: Quixel Megascans via Fab or Quixel Bridge downloads, Amazon Berkeley Objects with 6,900 models, ambientCG with 2,300 textures plus HDRIs and decals, Poly Haven with 1,900 assets plus textures and HDRIs, The Base Mesh with 1,400 models, and the IES Library with 1,300 lighting presets.

On the website side, the Dash Asset Marketplace lives inside the Content Browser, with the Dekogon library and a Sierra library entry that includes one free pack.

Polygonflow also supports browsing and importing content across multiple UE projects from inside the project you are currently working in. The docs add a warning on version compatibility for external browsing: UE5 projects are forward compatible but not backward, so you can browse content from the same or older UE5 versions, not newer.

Custom assets, right now

In the Project Library tab, you can currently add your own static meshes, textures, and blueprints. The tagging flow focuses on making assets searchable beyond filenames and folder names, and the content browser adds collections for grouping assets into reusable sets.

Pricing and the usual production warning

On Fab, Dash – Advanced Asset Manager is free. Commercial pricing for paid Dash licenses is 8€ for students, 20€ per Month for professionals below the 250.000$ barrier, and 95€ per month for bigger studios. Test any new browser, tagging, or library workflow on a non-critical project before it touches production depots and shared team setups.

https://www.fab.com/listings/865301e9-2d26-425d-8f3c-e0aadf35da61
https://docs.polygonflow.io/advanced/free-content-browser

The post PolygoFlow Dash asset manager goes free on Fab first appeared on DIGITAL PRODUCTION and was written by Bela Beier.

For those who don’t know the tool: Wacom Art Pen 2 is a rotation aware stylus for Intuos Pro, Cintiq, and MovinkPad Pro 14, with app support in Photoshop, Illustrator, Clip Studio Paint, and Krita.

The twist you actually use

Barrel rotation sounds like a party trick until you map it to something that pays rent. The Art Pen 2 sends rotational angle data, so supported brushes can react to how you twist the pen in your hand. That lets you change stroke width and character by rotation alone, closer to how a flat brush, chisel marker, or calligraphy nib behaves. This is not a new concept in digital art, but it has been oddly rare in modern stylus lineups. The practical win is fewer mode switches. Instead of bouncing between brush presets, you keep one tool and steer it with your wrist.

Specs that matter, not vibes

The pen uses battery free EMR and includes three buttons. Pressure goes up to 8,192 levels, with tilt support. There is a built in nib holder in the barrel that stores three spare nibs, so you can swap tips without digging through your desk drawer of tiny regrets.

There are three newly developed nib types: Art Pen 2 Carbon Shaft POM Nibs, Art Pen 2 POM Nibs, and Art Pen 2 Felt Nibs. The pen ships with a Carbon Shaft POM nib installed. The nibs are exclusive to the Art Pen 2 and do not interchange with Pro Pen 3 nibs. The pen also skips interchangeable button plates, grips, and balance weights.

If you relied on modular pen bodies, this is a hard line. If you only care about a stable feel and consistent response, fewer moving parts can be a feature.

Compatibility is specific, and that is good news

On hardware, the pen lists support for MovinkPad Pro 14, Intuos Pro models PTK470, PTK670, and PTK870, plus Cintiq 16 DTK168, Cintiq 24 DTK246, and Cintiq 24 touch DTH246. Cintiq Pro models DTH172, DTH227, and DTH271 are slated for support later this year.

On software, barrel rotation support depends on the app. Listed support includes Adobe Photoshop 2026, Adobe Illustrator 2026, Clip Studio Paint v4.1 or later, with v4.3 or later on Android, and Krita 5.2.14 or later. Some other apps also support barrel rotation, and more app support is planned.

Price, availability, and the fine print

The Art Pen 2 lists at $99.95 on the official store page. Availability is described as “soon”. Wacom positions this as a return of a rotation sensitive pen the community asked for.

As always, test new input gear and driver combinations before you roll them into production. Brush engines, driver updates, and app versions can interact in fun ways that only reveal themselves at 2 a.m. on delivery week.

Where this lands for post, VFX, and realtime artists

Whether that is worth it depends on your apps, your devices, and how much you already built your muscle memory around rotation driven brushes. The good news is that the compatibility lists are concrete, and the nib ecosystem is clearly separated from the Pro Pen 3 world, so you can plan purchases without guessing.

https://estore.wacom.com/en-us/wacom-art-pen-2-acp70000dz.html
https://community.wacom.com/en-us/art-pen-2/

The post Wacom Art Pen 2 does a barrel roll first appeared on DIGITAL PRODUCTION and was written by Bela Beier.

Mesh first, regrets later

Tangenten positions Puppet Pin Tool as a mesh deformation tool for the Fusion page inside DaVinci Resolve, built around a node you drop into a comp and feed with an image. The first stop is the mesh tab, where the plugin generates a triangulated mesh automatically.

Mesh generation follows the non-transparent pixels of the input, so cutouts with clean alpha give cleaner boundaries. The mesh can be adjusted with generation controls when the automatic result needs a nudge, including cases where you want tighter coverage around thin shapes or want to avoid clipping at edges. Everything else in Puppet Pin lives on top of the automatic mesh step. Pins grab vertices from that mesh, then move them around. Deformers move pins. Solvers push the rest of the vertices into place. Locators output motion data from the whole mess.

Pins: source, destination, and mseh wrestling

Pins in Puppet Pin have two positions. A source position defines where the pin grabs vertices from, and a destination position defines where those vertices get moved to.

The workflow starts in the pins tab. Adding a pin enables it and switches the viewer into source pin view so you can place it exactly where you want. After placing source pins, create controls switches the viewer into destination pin view and gives you per pin viewer controls you can drag to pose the subject.

For quick pose edits, this stays pleasantly direct: place pins on key body parts, generate controls, then pull and rotate until the silhouette behaves. The demo workflow uses four pins for a simple pose tweak, with pins on feet, hips, and neck to bend and tilt the figure.

Pin radius acts like the pin’s grip size. Increasing radius makes a pin grab and lock down more vertices, and it also enables rotation and expansion controls. Radius becomes essential once you want feet to stay planted or once secondary motion from other pins starts pushing things you intended to keep still.

Pins also include a render layer control that changes triangle render order. That makes it possible to decide which parts draw in front when pieces overlap after deformation, like choosing whether a tail renders in front of a body or behind it.

Keyframes and loops, because artists like sleep

Puppet Pin supports standard keyframing on pin controls, and the tutorial example builds a short loop by animating a neck pin across a 30 frames per second section. Two keyframes set the motion, then spline controls apply smoothing and a ping pong loop for a back and forth cycle.

This is the kind of tiny feature that saves real time. You can rough a loop from a still without opening another tool, without baking a bunch of transforms, and without manually copying and pasting keyframes to fake a cycle.

It also means Puppet Pin fits neatly into the existing Fusion animation muscle memory: set keyframes, shape curves, loop when needed, and keep moving. If you plan to drop it into a show, test the whole setup in your own comps before you trust it with client deadlines.

Deformers: follower, wave, and IK FK rigs

The deformers tab adds another layer, letting you build relationships between pins so you can animate less and get more motion for free. A follower deformer makes one or more pins follow a target pin. In the example setup, the hip pin follows the neck pin, with amplitude and delay controls creating softer secondary motion.

The post Tangenten Puppet Pin brings mesh warping to Resolve first appeared on DIGITAL PRODUCTION and was written by Bela Beier.

With *Das szenische Portal RT*, Andreas Resch has developed a real-time system for live events that combines a physical stage, virtual scene spaces, camera feeds and musical inputs to create a hybrid performance environment. The approach is primarily aimed at live formats featuring improvising musicians and is conceived as a modular virtual stage extension rather than a mere background projection.

Andreas Resch works in a field where one is usually expected to choose between art and technology. He has evidently chosen both, and this is no disadvantage for this project. Classical music training on the piano and church organ, coupled with an early start in programming, later work on SGI Onyx-based training simulators in Munich, followed by stints in animation, simulation, tracking, projection mapping, virtual physics and mixed reality.

This combination of music, imagery and technical development has long been a recurring theme in Resch’s work. Since 2020, he has demonstrated in several projects how audiovisual staging, virtual spaces and live performance can be combined. Das szenische Portal V1.0 already relied on a form of live performance in which Resch played the piano whilst a surreal, distorted virtual reinterpretation of a physical painting exhibition was projected onto a large screen as an endless film. This was presented live on several occasions and ultimately served as the precursor to what is now being continued as a real-time system.

At present, Das szenische Portal RT is primarily an art project, a prototype and a technical development. However, according to Resch, project-based applications are conceivable: anyone requiring a suitable configuration for an event can, in principle, integrate him and his software. Enquiries? Questions? Idea? Sent them to innovation@virtual-paradises.org. Resch can also envisage further development with a partner from the product or events sector to expand the existing prototype into a robust production or rental solution.

Unreal Engine as the basis for the stage extension

With the scenic portal RT, Resch revisited the concept from 2024 onwards and completely redeveloped the system in Unreal Engine. The first working version was created in 2025. The aim is a virtual stage section that does not simply hang behind the real stage like a particularly ambitious backdrop, but forms a hybrid production together with the physical structure. The ambition is therefore greater than mere decorative projection. The virtual scene is intended to become part of the stage space.

The bigger, the better, of course. LEDs, a good projector etc. with a screen, … The prototype has so far only been tested on an 85-inch monitor. The size also depends on the actual stage dimensions to ensure a good overall design. Every event here is unique. 

The effect is based on a geometrically structured overall concept that closely interlinks physical and virtual image elements. Resch describes this as a form of hybrid stage, in which objects from the virtual projection appear to extend into the physical stage space. This approach becomes particularly relevant where improvising musicians are involved. Audio signals, whether from digital or acoustic instruments, can spontaneously trigger events in the virtual scene, thereby directly influencing the visual narrative. The stage, in other words, listens in. Something that rarely happens even in everyday life.

Live input, triggers and virtual events

For the prototype, Resch first developed several three-dimensional stage sets in Unreal Engine. He then implemented real-time communication between the computer and a Korg KRONOS workstation, which serves as an external trigger source for scene events.

In the test configuration, three live webcams and the KRONOS were continuously fed into a specially developed Blueprint system. This interprets audio and video data and translates it into dynamic events within the virtual scene.

The Blueprints

Nevertheless, this allows for artistic, surreal constellations to be achieved with the video
projection surfaces, such as embedding a performer into a picture frame, which, as shown here, begins to float alongside the concert grand piano. A triggered Niagara system could then be attached to the picture frame, for example, which reacts to the music and scatters sheet music around the room, etc.

The live video of the performance on the keyboard could, for example, be superimposed over the virtual grand piano’s keyboard to make the artist’s hands visible in the virtual representation.

These include object transformations, cloth in the wind, collisions, Niagara effects, camera control, choreography, scene changes and other VFX actions. Central control is handled via Unreal Engine’s sequencer, in which specific sequences are defined in an endless loop, such as camera paths through the scene. Technically speaking, this is the point where performance, event logic and scene organisation converge.

What goes into the pipeline?

A pipeline that integrates external tracking processes can run on anything that communicates with Unreal Engine. Tools such as VooCAT, 3ds Max, C4D, Houdini, Blender, Datasmith, and Unreal Engine itself form the basis for tracked image sequences (or AI-generated image spaces as virtual environments), for example, via a camera backplate or a projection map. An imported 3D point cloud serves not only as a spatial reference but also provides coordinates for the placement of additional events.

The real space is not surveyed, as there are no parallactic references, as in a virtual production. Ideally, however, the real space is photographed so that the virtual worlds can be constructed to ‘inherit’ surfaces and geometric features from the real space. The real stage can then also be furnished with haptically appropriate objects to create visual harmony.

Unfortunately, a comprehensive “field test” of the system’s behaviour is still pending. The Blueprint system must always be adjusted to the target instrument’s requirements and signal strength using appropriate parameters.

A key structural feature is the separation between internal and external triggers. Within the 3D scene, an audio source selected by the artist can be statically positioned and function as playback. These internal signals trigger defined processes within the scene, such as Niagara effects or other pre-prepared reactions. External audio signals from microphones or digital stage signals, on the other hand, activate other types of events.

Two Niagara systems were present at the demonstration, triggered internally via a stored scene sound. With two additional webcam inputs and an external signal from the KRONOS workstation, the system ran stably on the aforementioned “small computer”. The latency times were “noticeably” correct. Geometrically, this took place in a 3D model of the Colosseum, after all.

In this way, an internal beat can underpin the basic structure of a sequence, whilst external impulses additionally influence, shift or disrupt the scene. This makes sense for live formats because it mediates between predictability and reaction – that is, between show control and what musicians simply love to do: something unexpected.

Modular structure and live video

The modular blueprint structure is designed to allow the appearance and behaviour of the virtual stage section to be freely adapted to the artist, song or event format. The project is therefore not conceived as a rigid show package, but as a flexible framework within which specific logic for individual pieces or client requirements can also be implemented.

Ideally, a large LED wall is provided on the physical side, though projection via a projector is also possible in principle. The prototype was tested on a Windows PC with 16 GB RAM and an RTX 3060, running Unreal Engine 5.5.4. Depending on the complexity of the scene, two to four webcams can currently be integrated in real time. Their live images appear on defined projection surfaces within the virtual stage section. In this way, both artists and audience become part of the virtual world, not as a post-production effect, but as an ongoing component of the production.

It is precisely this integration of live video that is one of the more interesting aspects of the concept. When the audience appears, for example, as a background projection within the virtual stage section, the viewer may get the impression that the real stage opens up at the back into another room. This is more than an animated background and less than a completely virtual production. It is precisely in this intermediate zone that the appeal of the project lies.

A ‘field test’ is still needed here. During the prototype demonstration, the room was quite dark. The pianist was locally lit and clearly visible. The camera image of the audience was “normalised” using a blue screen, i.e. the brightness was adjusted so that the people on the projection screen could be clearly recognised. A test in a larger, much better-lit hall is still pending.

First presentation on a small scale

An initial live presentation took place in a small, private setting with selected guests. It was deliberately not aimed at a specialist audience, but at interested visitors, including visual artists. A photorealistic 3D model of the Colosseum served as the simulated stage set, displayed on an 85-inch monitor in Full HD at 70 fps. Resch himself took on the role of the live-performing artist at the KRONOS workstation, simultaneously controlling the behaviour of the virtual world.

Two live cameras (Full HD Rapoo webcams, i.e. very affordable equipment) captured him from the side and from above, with a view of the keyboard; additionally, the audience was integrated into the event-driven 3D world as a video projection. 

For Resch, this presentation is proof that traditional stage technology and a responsive virtual universe can be meaningfully combined. The audience reacted with clear amazement. This is not yet a technical acceptance test nor a production benchmark, but at least a useful test of whether the basic idea works on a perceptual level. That, too, is not entirely unimportant in the live sector.

Between prototype and production tool

The scenic portal RT is continually evolving. With current gaming hardware, 4K output and higher frame rates should also be possible in the future. In parallel, Resch is working on a musical project that is being developed partly using AI platforms. He defines the musical structures himself, whilst AI is used for arrangement and instrumentation.

For performers, narration and singing in fantastical worlds, he cites HIGGSFIELD AI. Whilst this is a separate project, it points the way forward: real-time, virtual staging, music, simulation and AI-assisted content creation are increasingly merging here. To what extent does the availability of online AI content generators depend on the ‘current state of things’? Which platforms will still be available by the end of the year (see SORA) and which ones have working APIs, must be checked again before each performance. The checklist is getting longer.

The bottom line is that the RT scenic portal is neither a classic media server product nor a ready-made event graphics package. It is a custom-developed real-time system based on Unreal Engine, trigger logic, live input and modular scene control. Whether this will become a widely applicable tool for the events sector ultimately depends, as is so often the case, not on the idea itself, but on robustness, workflow suitability and scalability. The idea itself is certainly technically interesting. Not every stage needs a surreal real-time parallel universe. But it would also be a shame if it were always just an LED wall with wave animations.

Want to know more? virtual-paradises.com and here is the associated YouTube channel: https://youtube.com/@VirtualParadises

The post Das szenische Portal RT: When the Stage Starts Listening to the Music first appeared on DIGITAL PRODUCTION and was written by Bela Beier.

Simple Tree Tools 3.0 targets artists who want tree and plant generation to behave like the rest of a Houdini graph: parameter driven, non-destructive, and easy to rewire when a shot brief changes at 6pm.

The toolset runs in Houdini 20.5 or later. The supported editions depend on the license tier and include FX, Core, Indie, Apprentice, and Education. In day-to-day use, the pitch is straightforward: generate species with controls that stay editable, shape plants with growth responses, and keep the whole thing inside a network you can hand to the next person without a sacred PDF explaining which button not to touch.

Procedural generation, but with plant brains

The feature list leans hard into procedural generation. The tools aim to generate any species of tree with non-destructive, parameter-driven controls, covering everything from small plants to large trees.

Plant shaping focuses on environmental response through tropisms. The named list includes Gravitropism, Phototropism, and Thigmotropism, with several others also mentioned. For art direction, growth can be guided using guide curves or vector fields.

If you live in the Houdini tag archive, this sits comfortably in the same mental drawer as other procedural effects tools: the value comes from staying editable until the last responsible moment, not from making a single perfect hero tree once.

Scan extension nodes for the trunk people

3.0 also includes scan extension tools aimed at hybrid workflows: scanned trunks, procedural branches, and a bridge between them.

Two nodes are important: Scan Initialize and Scan Stitch. The stated goal is to seamlessly extend scanned geometry and blend procedural branches onto high-resolution trunks with physical and UV-mapped transitions. That matters for asset teams that already keep a scan library but still need variation and shot-specific dressing without resculpting every new silhouette.

If your environment’s pipeline already leans on library assets and a sprinkle of procedural dressing, this positions the tool neatly inside CGI environments work, where consistency and iteration speed beat heroic one-offs. Test your scan handoff carefully, though, because any workflow that mixes geometry sources can surprise you in UVs, scale, and downstream exporting.

Wind, growth, and the licensing reality check

Licensing and commercial use come with unusually plain language. The toolset uses one-time purchase licensing with no subscriptions or recurring fees, and purchases cover all v3.x updates delivered automatically through Gumroad. Future major versions such as v4.0 may require a separate purchase, with a discounted upgrade price mentioned.

The FAQ states you can sell models, renders, asset packs, game assets, and film work created with the tools if you only hold a Limited Commercial license. You cannot redistribute the tool’s own HDA files. The Non-Commercial tier restricts use to personal learning and non-revenue work, and it ships as .hdanc files, which forces Houdini into non-commercial mode when those nodes exist in a project.

If you buy a paid license while staying on Houdini Apprentice, the FAQ states it does not remove export restrictions. The tool does not alter your Houdini license limitations, so you need to match your tool license to your Houdini license to avoid unpleasant surprises in prodution.

Support runs through email (nirfse3d at gmail.com) – refunds generally are not offered due to the digital nature of the product, with an invitation to reach out if a serious issue appears. As always, treat new tools like new plugins: build a small test scene, push it through your actual export path, and only then let it into a network that people depend on.

Pricing and tiers

Pricing has four tiers: The Non-Commercial tier is free and a good way to test the tools. The Limited Commercial tier costs $99 and targets hobbyists and freelancers with annual revenue under $100k USD. The Full Commercial tier costs $229 and targets hobbyists and freelancers with annual revenue above $100k USD. A Studio tier costs $1,299 and is described as a site-wide studio license. So, for the big players, not as little ones.

The plugin also has file type differences by tier. Non-Commercial uses .hdanc. Limited Commercial uses .hdalc. Full Commercial uses .hda. The Studio tier also lists .hda.

Individual licenses allow installation on up to two personal machines for a single user. The Studio license covers unlimited installs within a single facility.

https://simpletreetools.com
https://nwestfelt.gumroad.com/l/SimpleTreeTools-v3

The post Simple Tree Tools 3.0 goes procedural first appeared on DIGITAL PRODUCTION and was written by Bela Beier.

For those who don’t know the Project: Blender Studio ships open movie assets, training, and production tooling built around the Blender DCC, including add-ons and pipeline workflows for animation and rendering, as well as battletesting the whole Blender Pipeline.

The film release, minus the fluff

Singularity is out as a short film in 4K HDR, framed as a painterly space adventure directed by Andy Goralczyk. It follows a small creature whose home gets destroyed by an ominous black hole, pushing it toward a group of luminous creatures and a mysterious celestial being.

The release matters less for the plot and more for what it packages with the movie. The singularity includes downloads of ALL production assets, frames, and high quality encodes under a Creative Commons Attribution license. That makes it usable as real-world test data for storage, conform, and review, not just a nice watch on a big screen.

Painterly look, procedural muscle

The production leans into a watercolor inspired style led by art director Vivien Lulkowski, mixing hand-crafted textures and brush strokes with generative effects. That combination aims for an organic look in the creatures while keeping the black hole graphic and geometric.

On the tool side, the film was created with the most recent in-development version of the DCC, and the team expanded the Brushstroke Tools library with new painterly assets. They also used Geometry Nodes to develop procedural “crowd animation” systems (The quotation marks are about the Crowds, not the system), which makes the project a handy reference if you want to compare node-based instancing logic against your own setups or caching strategy.

If you want a fast internal taxonomy for the kind of work this project touches, it sits squarely in animation and practical stylization, with enough proceduralism to interest anyone who keeps one eye on Geometry Nodes changes.

Story development, and what you can actually access

A dedicated story development “article “log” exists by director Andy Goralczyk, but the page requires a login to read the full content – you can support Blender Studio with a subscription for access to training.

HDR is the real production test here

The 4K HDR part is not a sticker, it is a workflow commitment. HDR delivery usually forces decisions about monitoring, transforms, and what you consider the master, especially when you also need an SDR version that holds up. The projectfocuses on watching it on a large screen, but for post teams the more interesting angle is that it gives you real files to validate ingest, grading, and export choices with.

If you are sanity-checking what HDR usually means in standards terms, ITU-R BT.2100 defines image parameter values for HDR television used in production and programme exchange. That is the kind of reference point that helps when your pipeline debates drift into vibes.

Practical take for production people

Treat the release like a compact pipeline exam. Download the encodes and frames, throw them at your review stack, test your HDR monitoring chain, and see what breaks first. If you plan to reuse any assets, read the license terms carefully, because attribution requirements can collide with real-world deliverable constraints.

https://studio.blender.org/projects/singularity/

The post Blender Singularity lands in 4K HDR first appeared on DIGITAL PRODUCTION and was written by Bela Beier.

The ProArt Display PA16USV centers its pitch on 12G-SDI. One BNC input handles uncompressed 4K at 60 Hz and targets direct camera-device monitoring with ultra-low latency, using the SDI family standardized by SMPTE. That matters when you want the same signal type your carts and villages already trust, without detouring through converters.

The panel is a 15.6-inch IPS at 3840 by 2160 with 282 PPI. It ships with an anti-glare surface, a typical contrast ratio of 1200 to 1, and 170-degree viewing angles. Response time is rated at 5 ms gray to gray with a maximum refresh rate of 60 Hz. You also get the expected alternates: one HDMI 2.0 port, plus a USB-C port that supports DisplayPort Alt Mode. A USB hub port is in there as well, with USB 3.2 Gen 1 Type-C, and USB-C power delivery is at 7.5 W. Not enough for a laptop, but enough for most phones.

Color specs, presets, and the reality of 400 nits

Color coverage is listed as 100 percent sRGB and 100 percent Rec.709. sRGB ties back to the sRGB standard published by the IEC, and Rec.709 is the broadcast workhorse from the ITU. Factory calibration targets Delta E under 2, with Calman Verified status via Calman, and the box also includes a colour pre-calibration report.

Preset modes include Native, sRGB, Adobe RGB, DCI-P3, DICOM, Rec.709, HDR, and two user modes. HDR support is HDR10, which the industry commonly references through work from the Consumer Technology Association and related standards bodies. The monitor also lists multiple HDR10 curve options: PQ Hard Clip, PQ Optimized, and PQ Basic.

Brightness is typical at 400 cd per square meter. That number can work fine for studio carts and shaded setups, but it puts outdoor reality checks firmly on you, not the spec sheet. If you plan to use this as your primary village screen, run your own midday tests before you show up with confidence and a single C-stand.

This is also where good process still beats good marketing: even with a calibrated panel, you should validate your full monitoring chain in your own environment, including signal path, LUT handling, and who gets to touch the settings. The best surprise on set is no surprise.

Mounting, handling, and the box you keep

On the physical side, the monitor supports VESA 75 by 75 mm mounting. It also has a 1/4-inch tripod socket, tilt from plus 20 degrees to plus 70 degrees, a Kensington lock, and an ambient light sensor. Net weight is at 1.4 kg including the stand, and 1.3 kgs without the stand.

Bundled accessories vary by region, but the list includes a mini stand and an HDMI cable, plus USB-C cable, power cord, and power adapter. Warranty details on the tech specs page list LCD ZBD warranty as yes, 3 years. Power consumption is specified as under 15 W, with power saving mode under 0.5 W and power off mode under 0.3 W.

There is also a clear nudge to keep the packaging: the carton can be reused as a monitor hood. The packaging hood comes with a caveat that its condition will naturally deteriorate over time and is not covered by the warranty.

If you have ever hacked together a hood out of whatever the rental house cardboard gods provided, this detail will either make you smile or make you wonder how many folds it takes before it looks like a crushed matte box.

Picture tools and desktop control

The display supports PiP and PbP. It also supports DisplayWidget Center, a monitor management app from ASUS that lets you adjust settings with a mouse instead of the monitor buttons.

In practical terms, that combination points at two workflows: live camera feed over SDI for set decisions, and laptop-based review over HDMI or USB-C for DIT and post-adjacent tasks. The PiP and PbP options can help when you need to compare sources quickly, but you still need to confirm how your specific devices negotiate formats and framerates in the field.

If you live in the world of tight Rec.709 handoffs and client screens, the real test is not the spec list. It is whether the monitor holds up under real cables, real power, and real people.

Pricing, warranty, and the parts that need a footnote

The monitor costs 850€ in Germany, with a similar Amazon Price, and used samples landing somewhere between 500€ and 600€. As always, treat new monitoring gear like any other new link in the chain: test it before you put it in front of a director, a client, or a colorist who can spot a gamma wobble at twenty paces.

https://www.asus.com/de/displays-desktops/monitors/proart/proart-display-pa16usv/

P.S. The PA16USV now ships in Germany, after a longer wait than many expected. At FMX, conversations with two on-set VFX-people pointed at the gap for this screen: they want 12G-SDI monitoring in a smaller, more affordable package than the usual set-village screens. This is also why we pulled this one back on the list, since we have hands-on testing lined up for this panel very soon. Keep your eyes peeled.

The post ProArt goes 12G-SDI portable first appeared on DIGITAL PRODUCTION and was written by Bela Beier.

If you build lookdev in Cinema 4D with Redshift, you already know the ritual: import textures, create a material, wire the usual suspects, then repeat until your wrist files a complaint. dding_one sells a small utility called RS Node Tools that aims at exactly that loop. The focus sits on PBR texture sets and the annoying, frequent job of connecting maps to the right inputs. The product description frames it as “auto connect PBR textures” with automatic mapping so you can spend less time on housekeeping and more time pushing the look.

What it actually tries to solve

In practical terms, that makes it a fit for artists who already have a Redshift material strategy and simply want the fastest path from a folder of textures to a connected graph. If your studio already enforces naming conventions and texture packing rules, tools like this often land as a quick local speed boost for lookdev, previz, and small teams.

It also means you should treat it like any other automation layer. Test the results on a couple of hero assets, check color space handling, validate roughness and metalness intent, and confirm the node graph matches your pipeline expectations before you trust it across a whole scene.

Pricing that does not block a test run

RS Node Tools uses pay what you want pricing on Gumroad, with a minimum that starts at 0 USD. Pricing beyond that is the 5$ Supporters License, which is also for COmmercial Use.

That pricing model makes it easy to trial in a real scene instead of a toy setup. Drop it into a scratch project, run it on three texture sets from different sources, and see whether it saves you time without creating cleanup work afterward.

Production reality check

Automation can be a gift and a trap in equal measure. When it works, it removes the low value parts of a task. When it fails, it fails fast and at scale.

So treat RS Node Tools like you would any plugin that touches shading graphs: validate output, verify naming and connections, and keep a clean rollback path. New tools and innovations should always be tested before use in porudction, especially when they rewrite repetitive steps you normally spot check by muscle memory.

Where it fits in a modern C4D and Redshift stack

Redshift node workflows in Cinema 4D keep trending toward more node centric material authoring, and that naturally increases the number of connections artists need to manage. Tools that reduce graph wiring time become more interesting as soon as a project hits volume: lots of assets, lots of variations, lots of deadlines.

https://ddingone.gumroad.com/l/RS-Node-Tools

The post RS Node Tools speeds Redshift nodes first appeared on DIGITAL PRODUCTION and was written by Bela Beier.