Virtual production and spatial media

Real-time scenes, cameras, capture, XR, volumetric and spatial storytelling

• articleWhat do the Definition magazine interviews with Quite Brilliant and Veles Productions actually claim about time and cost of AI-generated virtual-production environments, and what do they say about limits?
  Corrected 2026-10-24 - see C3-B1127-01; the original statements below are kept for history and are superseded where the correction says so. A May 2026 trade article quotes two named practitioners. Quite Brilliant (London) used AI-generated backgrounds for 15 set-ups over five days and says the result lacks full 3D parallax; its method is a 3D blockout skinned by AI. Veles Productions (Warsaw) says Marble Gaussian splats let a virtual set that took weeks take hours or minutes and calls it "ten times cheaper"; it also lists hallucinations, perspective errors and limited interactivity and says it is phasing Unreal out. These are interview statements; the article gives no measurement method.
• articleHow do engine-exported depth, segmentation and edge passes actually reach these models, and what do the engine and model docs say (or not say) about matching their encodings?
  Corrected 2026-10-24 - see C3-B1071-01; the original statements below are kept for history and are superseded where the correction says so. The one documented engine integration found is CARLA's Unreal Engine 4 branch (merged Aug-Sep 2025): it renders edge, depth and segmentation control videos and sends them with per-control weights to a separately deployed Cosmos-Transfer1 server. Unreal's Movie Render Queue documents EXR passes such as World Depth in world units. No source read states how engine depth units or segmentation colour conventions should be converted to the encoding the Cosmos branches were trained on (depth normalised to [0, 1], randomised-colour masks), so that conversion is an open interface question.
• articleHow many bracketed exposures, at what spacing and range, and with what starting camera settings do practitioners shoot for a lighting HDRI, and where do they disagree?
  Corrected 2026-10-24 - see C3-B1085-03; the original statements below are kept for history and are superseded where the correction says so. Three practitioner sources give bracket recipes: CAVE (5 brackets at 3 stops or 7 at 2), Xuan Prada (5-7 exposures, 3 stops apart) and Greg Zaal (5 at 3 EV, but at least 5 at 2 EV and 9 for unclipped light). By simple arithmetic (synthesis) these span about 12 EV to 16-18 EV. All start with a fast shutter so light sources are not clipped, shoot RAW, fixed manual settings and a fisheye rotated in steps. They disagree on how many exposures the balls and chart get (3 vs 7) and where the chart sits. No vendor or standards document read gives numbers; the VES guide only lists HDRIs.
• articleWhat consistency and quality evaluations have the authors of HunyuanWorld 1.0, WonderWorld, WonderJourney and World Labs published, and can their numbers be compared?
  Corrected 2026-10-24 - see C3-B1039-01; the original statements below are kept for history and are superseded where the correction says so. Each source evaluates differently and none measures 3D geometric consistency directly. HunyuanWorld 1.0 reports no-reference image-quality metrics (BRISQUE, NIQE, Q-Align) and CLIP alignment on rendered views against baselines, with no ground truth; WonderWorld's only quantitative table is generation time (9.5 s vs 749.5 s and 798.1 s on an A6000) plus qualitative comparison and a stated failure mode; WonderJourney reports a human preference study (400 participants, binary choices on four axes). The World Labs pages read give examples and claims but no published metric; its TOS disclaims dimensional accuracy. The tables are not comparable across papers (different views, baselines, protocols).
• articleWhere should a narration or music stem go so it stays head-locked in a YouTube 360 upload, and why can't I ship a separate stereo track?
  Problem. Narration or music should not rotate with the viewer's head, but YouTube accepts one audio track. Conditions. YouTube Help spatial audio page with ?hl=en. Method. Mix tracks to be spatialised through the spatializer, keep head-locked tracks as stereo, export one 6-channel file laid out W, Y, Z, X, L, R at 48 kHz (PCM in MOV, or Opus in MP4 at minimum 768 kbps with mapping family 2), then run the metadata tool or equivalent. Failure modes. A separate stereo track alongside the spatial track is unsupported. Limitations. The page's routing sentence is ambiguous (see inference) and it describes the Facebook-era spatial workstation workflow. Version/date. Page copyright 2026, fetched 2026-10-24.
• articleIn the SA3D box, how can head-locked L/R channels sit anywhere in the track, and where is the spec's own byte-layout ambiguity for the head_locked_stereo flag?
  Problem. Writing or parsing SA3D by hand needs the channel_map rules and the flag layout. Conditions. Spatial Audio RFC in google/spatial-media docs. Method. Use ambisonic_channel_ordering 0 (ACN) and normalization 0 (SN3D); set ambisonic_order = sqrt(num ambisonic channels) - 1; list channel_map entries in file order, giving ACN indices 0-3 for W Y Z X and 4, 5 for L R, so L R can be stored before or after the ambisonic channels. Failure modes. The RFC syntax block shows an 8-bit ambisonic_type and omits head_locked_stereo, while the semantics call head_locked_stereo a 1-bit flag and ambisonic_type 7 bits; the bit position is not stated. Limitations. Only periphonic type 0 is defined. YouTube's own help page lists W, Y, Z, X, L, R, so the L, R, W, Y, Z, X ordering is an RFC example, not a YouTube-accepted order (not tested). Version/date. master as fetched 2026-10-24.
• articleWhat does Google's spatial-media injector do with a track that is not exactly one FOA stream: is a second-order or multi-track file accepted, and how does it decide FOA vs FOA plus head-locked stereo from the channel count?
  Problem. Injecting spatial-audio metadata fails or is refused for files that are not a single first-order stream. Conditions. Google spatial-media metadata_utils.py (master at fetch) used with --spatial-audio. Method. Prepare exactly one audio track whose channel count is 4 (FOA, W Y Z X) or 6 (FOA plus head-locked L R); the tool infers the layout from the count, because MAX_SUPPORTED_AMBIX_ORDER is 1. Failure modes. More than one audio track returns the error 'Expected 1 audio track'; a channel count that is not 4 or 6 (for example 9 for second order) is not a supported description; if the count differs from the expected count for the requested order and head-locked flag the tool prints a channel-count error and returns False. Limitations. Tool README says Python 2.7; I read code and docs only and did not run the tool. Version/date. master as fetched 2026-10-24.
• articleHow does Take Recorder's slate and take numbering turn a recording into a Level Sequence with subsequences?
  Problem. Keeping takes organised for shot-by-shot work. Conditions. Take Recorder panel open. Method. Set slate name, take number, description, fps and Record Speed; record via the red button, stop with Esc. The pending take is a Level Sequence; sources record into a subsequence (colour-coded per source); Takes Browser lists saved takes with metadata in column view; Review Last Recording opens the result; Root Take Save Dir and Take Save Dir use {take}/{slate} tokens; auto-save keeps sequences and subscenes. Failure modes. Reusing a take number triggers a warning (click to jump to next number); unsaved assets are lost. Limitations. How a take is placed into a Level Sequence with Shots is not shown in this page. Version/date. Current page as fetched.
• articleHow do Take Recorder timecode, clock source and Live Link 'Use Source Timecode' settings affect sync with mocap and other devices?
  Problem. Takes from different devices must line up later. Conditions. A timecode provider (defaults to UE's) and Live Link subjects. Method. Set Recording Clock Source (Audio, Relative Timecode, Timecode, Play Every Frame); enable Start at Current Timecode to begin at the current timecode instead of time 0; enable Record Timecode to write timecode metadata into track sections; on a Live Link source enable Use Source Timecode so the subject's timecode is used, and Discard Samples Before Start to drop earlier samples. Failure modes. With Use Source Timecode off, data is keyed on the Live Link thread using engine time and no timecode track is created, so source-to-sequence relation is lost. Limitations. Clock modes listed do not respond to pause states. Version/date. Current page as fetched.
• articleWhich sources can Unreal Take Recorder capture (actors, Live Link, microphone), and what must be true for a property to be recordable?
  Problem. Planning a capture session needs to know what Take Recorder can and cannot record. Conditions. Take Recorder plugin enabled (restart needed); Live Link plugin optional for mocap. Method. Window > Cinematics > Take Recorder; +Source adds Any Actor, Camera Cuts, Level Sequences, Live Link, microphones, nearby spawned actors, Player actor or World states; or drag an actor from the Outliner. Actor sources record as Spawnable or Possessable (project default, per-source override). Microphone source writes a sound asset named with {take}/{slate} tokens, with Audio Gain in dB. Failure modes. A property that cannot be keyframed cannot be recorded; spawnable recordings of unattached actors give global-space transforms. Limitations. Documentation page only; I ran nothing in the editor. Version/date. Current dev.epicgames.com page as fetched, version not stated in extract.
• articleHow do I record Unity AOV passes for compositing (multi-part EXR, unclamped linear, motion vectors) and what breaks with TAA?
  Problem. Handing a real-time Unity render to a compositor needs separate passes. Conditions. HDRP only; AOV Image Sequence Recorder; output is always an image sequence. Method. Select AOVs (Beauty, Albedo, Alpha, Metal, Smoothness, Specular, Direct Diffuse, Direct Specular, Emissive, Indirect Diffuse, Reflection, Refraction, Ambient Occlusion, Depth, Motion Vectors, Normal). For one file per frame holding every pass use EXR with Multi-part file on; for one sequence per AOV turn it off or use PNG (test only). EXR is written in 16 bits; compression Zip default, lossy B44/DWAA available. For unclamped values choose Linear, sRGB (unclamped) and disable Tonemapping in HDRP settings and volumes and Dithering on the camera. Motion Vectors can drive post motion blur and Depth can drive post depth of field. Failure modes. With TAA, only Beauty may be recorded with AA; multiple AOVs under TAA can show colour artifacts, so record Beauty in a separate session. ActiveCamera is unavailable, use M...
• articleWhat conditions must hold to record Unity Recorder Accumulation successfully, so a render does not silently fail or show a progress bar?
  Problem. Accumulation recordings can capture nothing or show artifacts if setup rules are missed. Conditions. Recorder 5.1.7. Method (checklist). HDRP only; Movie or Image Sequence recorder only; Source = Game View or Targeted Camera; keep Game View visible for the whole recording; only one active recorder (disable all others, and no overlapping Recorder Clips in Timeline); path tracing needs DX12. Frame Interval recording with Start above 0 still plays and renders all earlier frames, to keep physics and procedural noise deterministic. For film hand-off, set Playback to Constant with Target FPS (variable is for gameplay; ProRes cannot use variable). Failure modes. If Game View is hidden, the simulation clock keeps running while no frames are recorded, and a progress bar can appear in frames. Cannot run in -batchmode. Limitations. Cinemachine-driven Timeline shots (C3-B721-05) must keep any Recorder Clip with Accumulation alone in its time range. Version/date. Recorder 5.1.7 docs, fe...
• articleHow does Unity Recorder accumulate path-tracing samples, how do I get clean frames without motion blur, and why do frames come out overexposed?
  Problem. Path-traced HDRP frames are noisy until sub-samples converge. Conditions. HDRP with ray tracing set up and a path tracing override in the scene; path-tracing accumulation requires DX12 (Recorder 5.1.7 docs). Method. Samples is the number of sub-frames per frame and each sub-frame captures one path-tracing sample. With Shutter Interval above 0, samples are accumulated only inside the interval and the Shutter Profile weights them; with Interval 0 time does not advance, Shutter Profile is not applied, and all Samples converge one static moment (no blur). If noisy, raise Samples. Failure modes. With automatic Exposure and Adaptation set to Progressive, exposure is re-evaluated each sub-frame and noisy early sub-frames can overexpose the result; set Exposure Adaptation Mode to Fixed. A short Shutter Interval reduces path-tracing samples accumulated; the documented workaround is to disable path-tracing overrides on volumes. Limitations. HDRP path-tracing limitations also apply. V...
• articleHow do I set Unity Recorder Accumulation (Samples, Shutter Interval, Shutter Profile) to get film-style motion blur, and what must I switch off first?
  Problem. Real-time motion blur from a post-process is applied to the final frame, so a film render from Unity needs true sub-frame motion blur. Conditions. HDRP project, Movie or Image Sequence Recorder, Game View or Targeted Camera source (Recorder 5.1.7 docs). Method. Enable Accumulation under Input; set Samples (sub-frames between two frames); set Shutter Interval above 0 (Normalized 0-1 or Angle 0-360 degrees, so a 180-degree angle corresponds to half the frame interval, my inference from the Angle option); choose Shutter Profile Range (trapezoid with two fully-open points) or Curve to weight sub-frames. Check 'Effective number of accumulated samples', which can be lower than Samples when the interval is short. Disable the HDRP Motion Blur post-process and HDRP anti-aliasing first; use the Anti-aliasing toggle inside Accumulation instead. Failure modes. Leaving HDRP motion blur on stacks it over the accumulated blur. Limitations. Interval 0 turns motion-blur accumulation off. Th...
• articleWhat are Cinemachine Follow's binding modes, and which one emulates a human operator following a subject?
  Problem. A chase or follow camera either spins with the subject or ignores its turns. Conditions. Cinemachine 3.1 Follow Position Control behaviour. Method. Binding Mode sets the coordinate space of the Follow Offset and damping: World Space (camera ignores target rotation), Lock To Target (camera uses target local frame), Lock To Target With World Up (only yaw followed, tilt and roll 0), Lock To Target No Roll, Lock To Target On Assign (orientation captured at activation), and Lazy Follow (offset and damping in camera-local space, keeping distance and height with minimal movement). Position Damping per axis and Angular Damping (Euler per-axis or a single Quaternion value, which avoids gimbal lock) set the feel. Craft link (inference): Lazy Follow is the closest to a handheld operator, Lock To Target With World Up to a steadicam that ignores subject roll. Failure modes. Euler angular damping can gimbal-lock; Lock To Target will swing the view with every turn of a fast-rotating subje...
• articleHow does CameraCtrl II inject camera paths into a video diffusion transformer, how does it keep dynamic content, and how does it chain clips to explore a scene?
  Problem. Camera-conditioned video models trained on static-scene datasets lose scene dynamics, and single clips cover a small viewpoint range. Conditions. A pretrained DiT video model, clips with estimated camera parameters, and a user who specifies a camera path per clip. Method (CameraCtrl II). (1) Per-pixel Plucker embeddings from extrinsics and intrinsics are passed through an extra camera patchify layer at the model input and added element-wise to the visual features before the first DiT layer (reported to preserve dynamics better than encoder-injector designs). (2) A new RealCam dataset of dynamic videos with estimated camera parameters replaces static datasets such as RealEstate10K, ACID, DL3DV10K and Objaverse. (3) Joint training on camera-labelled and unlabelled video, using an all-zero dummy Plucker embedding for unlabelled data; this also enables classifier-free guidance on the camera signal. (4) Clip extension: tokens of the previous clip's last frames stay clean while t...
• articleWhich of the three nDisplay sync topologies (framelock only, genlock only, genlock plus framelock) does Epic recommend for an LED volume, and why?
  Problem. Cluster PCs drive LED processors and the camera must not capture different frames on different panels. Conditions. Multi-PC nDisplay cluster with NVIDIA Quadro GPUs and Sync II cards. Method. Epic describes three schemes. (1) Framelock only: daisy-chained sync cards, no external clock; Epic says it suits isolated displays but not a stage whose other devices share an external master clock. (2) Genlock only: each PC gets its own BNC feed from one generator; VSync is synced but NVIDIA barriers are unavailable, so Epic says presentation control at application level is imprecise. (3) Genlock plus framelock: the external clock enters the primary PC GPU and RJ45 daisy chain carries framelock to the render nodes, which allows NVIDIA barriers; Epic calls this the most desirable for virtual production. Failure modes. Genlock only gives unreliable frame presentation (Epic: not 100 percent reliable). Limitations. NVIDIA-specific; AMD FirePro S400 is mentioned only for Mosaic/Eyefinity ...
• articleCan I relight a Gaussian splat scene, and what does the PlayCanvas proxy-mesh method need and not handle?
  Problem. Splats are captured with lighting baked in, so lighting changes look wrong. Conditions. Real-time (PlayCanvas engine) viewing; not a general offline relight. Method. (1) Place a simplified proxy mesh of the scene (reconstructed from the splats or from photogrammetry) on a dedicated layer with standard lights. (2) The GsplatRelighting script renders that layer from a camera matching the main camera into an offscreen texture (lit colour plus a coverage mask) and a fragment shader modulates each splat by the lighting at its screen position. (3) Tune blend (0 original, 1 fully modulated), brightness (default compensates 0.5 grey albedo), and a background multiplier for uncovered splats such as sky. Failure modes. Where the proxy mesh silhouette diverges from the splat surface, lighting boundaries land in the wrong place; uncovered splats are left untinted unless scaled. Limitations. This modulates baked colour rather than recovering material or albedo; hence the baked shadows a...
• articleWhat numeric capture settings and photo counts does a splat vendor recommend (lens, aperture, shutter, ISO, overlap, photos per subject size)?
  Problem. Round-1 found no numeric photo count in the primary 3DGS and nerfstudio sources (C3-B572-02). PlayCanvas publishes explicit numbers. Conditions. Still or video capture of a static scene for splat training. Method (PlayCanvas guidance, not measured results). (1) Lens: 35-85mm equivalent, avoid ultra-wide under 24mm and telephoto over 135mm. (2) Aperture f/8-f/11, ISO 100-400 in bright light, manual focus, and identical exposure across the session (lock aperture, shutter, ISO). (3) Shutter at least 1/125s handheld. (4) Photos by subject size: small under 1 foot 50-100; medium 1-10 feet 100-200; large 10+ feet 200-500+. (5) Overlap 70-80% between adjacent photos in a ring, 60-70% between elevation rings; 15-30 degrees between viewpoints; multiple elevations. (6) Video: 4K minimum, 60fps+, locked exposure; extract every 2nd-5th frame and discard blurred frames. (7) Review images for sharpness and exposure consistency before training. Failure modes. Floaters, holes, flicker from...
• articleWhat camera parameters does glTF 2.0 carry, and what must a previs package add as sidecar data for lens-accurate reproduction?
  Problem. glTF is common for previews but its camera is minimal. Conditions. glTF 2.0 cameras. Method. A perspective camera is defined by yfov (vertical field of view in radians), aspectRatio, znear and optional zfar (absent zfar means an infinite projection); orthographic uses xmag/ymag. Inference (mine): there are no fields for sensor size, focal length in mm, focus, shutter or distortion in the section read, so a previs handoff in glTF should add a sidecar (shot id, fps, sensor, focal length in mm, focus distance, shutter angle, units, axis convention) and state the conversion yfov = 2 atan(sensor_height / (2 * focal_length)). Failure modes. Converting from mm lenses without sensor height gives wrong yfov. Limitations. Extensions not surveyed. Date. 2026-10-23.
• articleWhat does Blender's USD and FBX documentation say about camera round-tripping for a previs handoff?
  Problem. Previs cameras made in Blender must reach other tools intact. Conditions. Blender USD export/import, FBX add-on. Method. USD export: cameras supported are perspective only; Units option writes metersPerUnit; a Convert Orientation option maps forward/up axes (for Y-up apps use -Z forward, Y up). USD import brings in focal length, DOF distance, f-stop, clipping, sensor shift and size, but aperture-size animation import is limited because USD and Blender interpret sensor dimensions differently; shifts are animated to compensate. The FBX page I fetched documents scale, animation takes as Actions and leaf bones but contains no camera section, so FBX camera behaviour is undocumented there (absence only on that page). Failure modes. Orthographic cameras are dropped on USD export; animated aperture can change framing. Limitations. Manual 'latest' may differ from older Blender. Date. 2026-10-23.
• articleIn Unreal's PCG framework, what carries a seed and how are mesh variants weighted when spawning from sampled points?
  Problem. Level dressing generated by PCG must be repeatable and art-directable. Conditions. Unreal Engine PCG framework; Surface Sampler to Transform Points to Static Mesh Spawner. Method. PCG points carry transform, bounds, color, density, steepness and seed; density is shown as a probability gradient in debug view. Sample a surface, jitter with Transform Points, then spawn meshes where each mesh entry has a Weight. Failure modes. Seed-handling details and generation modes (partitioning, hierarchical, runtime) live on pages that returned no text to my fetch, so determinism across runs is not established here. Limitations. Overview page only; engine version not in extracted text. Date. 2026-10-23.
• articleWhat units and orientation does a USD camera use, and what breaks when focal length and aperture are authored in the wrong scene units?
  Problem. A previs camera exported to USD can render with the wrong field of view downstream. Conditions. UsdGeomCamera in any USD pipeline. Method. Lens and filmback properties (focalLength, horizontal/vertical aperture) are in tenths of a scene unit, so with the fallback metersPerUnit 0.01 (centimetres) they equal millimetres; clipping range and focus distance are in scene units. Cameras are always Y-up looking down -Z regardless of stage up-axis. The docs say if one property is authored in correct scene units they all must be. Failure modes. A stage with metersPerUnit other than 0.01 plus default millimetre values yields wrong absolute values (ratios still image correctly with focusing off). Limitations. Docs describe schema, not any exporter's behaviour. Date. 2026-10-23.
• articleWhich previs camera fields can USD carry beyond position and focal length (shutter, f-stop, focus, exposure, stereo role)?
  Problem. A VFX turnover needs more than a transform and a field of view. Conditions. USD previs file. Method. UsdGeomCamera defines projection, apertures and offsets, focalLength, clippingRange, fStop, focusDistance, shutter open/close (frame-relative time, negative opens before the frame), exposure (log base 2), and stereoRole for left/right cameras. Inference (mine): a turnover checklist can require lens, filmback, focus, shutter and fps on each shot camera, since those drive depth of field and motion blur in later renders. Failure modes. Optional attributes may simply be missing (fallbacks apply). Limitations. Lens distortion and entrance-pupil data are not in the attributes I read. Date. 2026-10-23.
• articleWhy is dialogue usually mixed to the centre even when the actor is off to one side, and what does that imply for placing generated dialogue and effects in stereo or surround?
  Problem: deciding where to pan AI-voiced or dubbed dialogue versus effects and music. Conditions: stereo or surround mixes with picture. Method (Murch's observation): in almost all stereo films of the previous 25 years dialogue is placed in the centre regardless of the actor's screen position, yet audiences and mixers still believe the voices come from the actors; effects such as car pass-bys get full stereo or multichannel treatment. He explains this by saying that while the brain is busy decoding language it lets the image 'steer' the apparent source, whereas the less linguistic a sound is, the more its spatial location matters. General rule he states: the warmer (more embodied) the sound the more it gets a stereo/multitrack treatment; the cooler (more encoded) the more it is placed in the centre. Early 1950s experiments moving dialogue around the screen were abandoned as 'artificial'. Use (inference): keep AI dialogue and dub lines centred (or head-locked in 360/VR, see the spati...
• articleWhat viewing-comfort practices does Apple's HIG give for video in visionOS?
  Problem. Immersive video can be uncomfortable when forced on viewers. Conditions. visionOS apps that play video they may not control. Method (HIG). Let people choose when playback starts; use a small playback window that people can resize; keep their surroundings visible during playback; in fully immersive experiences do not let virtual content obscure playback or transport controls; do not start a fully immersive video automatically; provide a thumbnail track (160 px wide thumbnails) for scrubbing; keep inline video 2D and do not expand it to fill a window. Failure modes. Auto-starting immersive playback; occluding controls. Limitations. These are app-level comfort practices, not disparity or convergence limits. Version/date. HIG documentation JSON fetched 2026-10-23.
• articleWhat are ARKit face tracking's device, range and mesh limits that affect capture for animation or AI characters?
  Problem. Phone face tracking is a common capture source but has conditions. Conditions. ARKit face tracking on iPhone/iPad. Method. (1) Faces are detected within 3 metres of the front camera. (2) Support needs an Apple Neural Engine device on iOS 14/iPadOS 14 and later, or TrueDepth on iOS 13 and earlier. (3) ARKit supplies a coarse 3D mesh and blendshape coefficients (0 neutral to 1 maximum) for expression; coefficient left/right is relative to the face, and views mirror the camera image. (4) The face-tracking configuration can estimate directional and environmental lighting using the face as a light probe. (5) Apps must include a privacy policy for face data. Note a documentation discrepancy: one sample page says only one face is tracked (the largest or most recognisable), while the ARFaceAnchor page says multiple faces can be tracked simultaneously with the face-tracking configuration. Failure modes (inference from the stated limits). Subjects beyond 3 m, multiple faces in frame,...
• articleWhat synchronisation and content-authoring constraints does Epic give for ICVFX (genlock, video playback, frame-rate target)?
  Problem. Multiple render nodes drive one wall and must show identical frames. Conditions. nDisplay cluster with camera, tracking and render nodes. Method. (1) Each device (camera, computers, tracking) has its own internal clock; without unification you get problems such as tearing, which genlocking with nDisplay prevents; engine timecode and frame generation must also match the camera. (2) Do not use video files as animated surfaces: video encoding gives no method to keep every node on the same frame; use texture flipbooks or an EXR sequence driven by a level sequence played simultaneously. (3) Performance: Epic's test content targeted 48-72 fps on artist workstations at 4K full screen as a benchmark, then profiled on machines matching the heaviest on-stage render node with a proper inner and outer frustum. (4) Avoid very large textures and dense meshes where not needed. Failure modes. Content that plays fine on one workstation but desyncs on the cluster. Limitations. The 48-72 fps ...
• articleOn an LED volume, what are the inner and outer frustums, which one moves with the camera, and what is the green-screen fallback?
  Problem. LED-volume shots mix a camera-tracked image with ambient lighting content. Conditions. In-camera VFX with Unreal nDisplay (Epic docs). Method. (1) The inner frustum is the part of the wall showing what the virtual equivalent of the physical camera should see, set by current lens focal length and tracked as the camera moves, which gives parallax from a full 3D world rather than a flat plate. (2) The outer frustum is everything displayed outside the camera's field of view; it turns the panels into a light and reflection source for the physical set and stays static when the camera moves, as real-world light does. (3) Each shot setup can be placed at a chosen location in the virtual environment to decide what the outer frustum emits. (4) For shots that cannot be in-camera finals, the inner frustum can be changed to green screen with tracking markers while the outer frustum keeps lighting the set, which also limits green spill. Failure modes. Reflections and light that do not ma...
• articleWhat are the camera-tracking options for virtual production and what does the virtual camera need to match?
  Problem. The wall image is only correct if the virtual camera matches the physical one. Conditions. In-camera VFX shoots. Method. (1) Tracking relays the physical camera position and movement to the engine so the correct perspective is rendered. (2) Common methods: optical (IR cameras tracking reflective or active markers), feature tracking (image patterns instead of markers), and inertial (IMU gyroscope and accelerometer, often combined with optical or feature tracking). (3) Epic recommends using multiple sources, such as optical plus inertial, to improve tracking data. (4) Live Link distributes tracked camera data, and with nDisplay the primary node replicates it to the cluster. (5) Calibration: the virtual camera's position and orientation must closely match the physical camera, and a Camera Calibration plugin generates data to align the cameras and model lens distortion for post-processing. Failure modes. Lens distortion or nodal offset not calibrated; unsynchronised tracking la...
• articleHow do I avoid moire when filming an LED wall, and which variables does Epic say control it?
  Problem. Visible interference patterns ruin LED-volume shots. Conditions. Camera pointed at an LED wall. Method. (1) Understand the cause: moire appears when display pixels and camera sensor pixels are slightly offset. (2) Distance from the screen, LED pixel pitch and camera sensor size together determine how far the subject must be from the wall to avoid visible artifacts. (3) Keep the camera focus plane in front of or behind the LED surface so the wall is slightly out of focus; moire can appear when the focus plane aligns with the panels. (4) Keep the camera perpendicular to the wall where possible, since severe angles make moire more likely. Failure modes. Focusing on the wall (for example a rack focus onto the background); steep angle shots. Limitations. Epic gives no numbers (no minimum distance or pixel-pitch table); those must come from stage test shots. Version/date. UE docs fetched 2026-10-23.
• articleWhat does Apple say about spatial metadata and disparity adjustment when converting side-by-side 3D to spatial video?
  Problem. Stereo files can be uncomfortable or treated as plain stereo. Conditions. Side-by-side stereo video converted to MV-HEVC for Apple Vision Pro. Method. (1) Convert by splitting each frame and writing left and right halves to the left- and right-eye layers. (2) Spatial metadata describes the left/right cameras (baseline, horizontal field of view, disparity adjustment). Adding it makes Apple platforms treat the file as spatial rather than just stereo and enables visual treatments that reduce common stereo discomfort. (3) Sample values: virtual cameras 64mm apart with 80 degree horizontal field of view; a disparity adjustment of +2% of image width gave a comfortable result in a window, placing the nearest object just behind the front of the window while keeping depth. Failure modes. Wrong baseline or field of view metadata for the content; nearest objects in front of the window plane. Limitations. The values belong to Apple's sample content; other content needs its own choices....
• articleIn spatial/360 audio, what changes when the listener's head moves: which parts rotate with the head, which stay fixed, and how many channels do the orders need?
  Problem: planning audio for 360/VR/head-tracked playback (e.g. a need about head movement). Conditions: ambisonic (scene-based) delivery decoded to binaural headphones. Method: ambisonic scenes are decoded and rendered binaurally, and the whole sound field is rotated by the head/camera orientation; Omnitone, Google's Web Audio decoder, applies a 3x3 or 4x4 rotation matrix each animation frame (it can be wired to a three.js camera or device orientation) to rotate the entire sound field. Channel counts by order are 4 (first order), 9 (second) and 16 (third) channels in that library. YouTube's spatial audio spec uses AmbiX (ACN ordering, SN3D normalisation), first order only, W,Y,Z,X at 48 kHz in one audio track, and it also supports a 6-channel FOA plus head-locked stereo (L,R) layout, where the stereo pair does not change when the viewer moves their head. Production consequences: put narration, dialogue-over-picture, music beds and UI sounds in the head-locked pair; place only source...
• articleWhat is Dolby Atmos 'binaural render mode' metadata (Off/Near/Mid/Far) and how does it relate to distance and room feel on headphones?
  Problem: control how each bed channel or object sounds on headphones (perceived distance/room). Conditions: Dolby Atmos masters with Dolby AC-4 immersive stereo; documented in the Dolby Atmos Renderer Guide v3.0 (2018, older software). Method: the Renderer supports binaural render mode metadata, a binaural renderer distance model, designed for content encoded as Dolby AC-4 immersive stereo. Per input (bed channel or object) you choose Off (no binaural virtualization), Near, Mid or Far. The metadata is written globally for the whole master, applies to headphone output during monitoring, recording and playback, and is not included with speaker processing. With multiple beds there is only one setting per bed channel (all left channels share a setting). Backwards-compatibility mode deletes bed settings and writes object-only metadata; full edit mode allows per-bed-channel settings but is not backwards compatible for non-AC-4 encodes. Use (inference): choose Near for dialogue-like, close...
• articleHow does head tracking work when monitoring a Dolby Atmos mix on AirPods in Logic Pro, and why does a bounced binaural file not keep it?
  Problem: judge a spatial mix with head movement, then deliver a headphone version. Conditions: Logic Pro with Dolby Atmos plug-in on a Mac; head-tracking-capable headphones (AirPods Pro/Max). Method: the Dolby Renderer and Apple Renderer monitoring formats each have a Head Tracking button; turning it on makes the sound field of the three-dimensional mix remain fixed in place when you turn your head. The button appears only when head-tracking-capable headphones are selected as the output device. Apple Renderer (Head Tracking) also requires a Mac with Apple silicon. For delivery to other devices you bounce a two-channel binaural file; Apple states that if you used an Apple Renderer (Head Tracking) monitoring format you will not hear head tracking in the bounced file, and that on AirPods the Spatial Audio / Spatialize Stereo setting should be turned off to play a binaural file (otherwise the headphones process it again). An ADM BWF file is the required format for submitting a Dolby Atm...
• articleWhat does a first-person crew account of a splat-on-LED job look like, and does the best one found involve a world model?
  Partially verified: the curator re-read none of the cited sources; S9, S10 rest on the producer's pinned reading. The only first-person crew account found (DOSENMUTTER, Filmakademie, 2026-07-08) uses a captured photogrammetric splat, not a generated world; AI appears only as denoising. It is useful as a template of what is missing from the generative cases: stated alternatives tested (plates vs splat), a stated reason, capture counts and named roles. Berlin (Volinga case, reported by Radiance Fields) is likewise capture-based. Neither is evidence about world models.
• articleWhich open tools compute MaxCLL/MaxFALL and which only pass the values through?
  Partially verified: the curator re-read none of the cited sources; S13, S12, S11, S14, S15 rest on the producer's pinned reading. In the source read, FFmpeg and libplacebo only carry MaxCLL/MaxFALL (struct fields, SEI parsing, forwarding to x265), libplacebo stores them, merges them when absent, and in the lines read uses MaxCLL only as a fallback for peak luminance, and dovi_tool copies the values from a madVR measurement file or its config into Dolby Vision L6 metadata. x265 takes the values from --max-cll but also accumulates statistics from luma plane sample values; hdr10plus_tool's plot command derives its MaxFALL and MaxCLL labels from per-frame HDR10+ metadata. Nothing read computes the H.265 D.3.35 per-pixel max(R,G,B) linear-light measurement.
• articleOn the Final Twist job, where in the pipeline did a generated Gaussian-splat world sit, what came in and out, and what outcome do the two accounts state?
  Promise (producer) and World Labs (vendor) describe the same job: ten crime-scene environments rebuilt from low-quality archival photos for Harlan Coben's Final Twist. Steps: AI restoration of the images, a World Labs tool producing a Gaussian splat, artist rebuild of geometry and textures, optimisation, display on a 16K LED wall. The outcomes stated are ten environments and qualitative benefits (natural lighting, presence); no time, cost, shot or quality number is given by either page. The two pages disagree on naming (a "tool from World Labs" versus Marble) and carry different dates.
• articleI have engine or simulator renders and want photoreal video through NVIDIA Cosmos-Transfer: what do I feed it, what comes out, and what do the control weights do?
  Cosmos-Transfer1-7B (paper, Mar-Apr 2025) and Cosmos-Transfer2.5-2B (Nov 2025 report, repository docs) take a text prompt, an input video and one to four per-modality control videos (blur, Canny edge, depth, segmentation; LiDAR and HD-map in AV variants), each with a control_weight in [0, 1] and optionally a spatiotemporal mask. The vendor guidance is that higher weights follow the control more strictly at some cost in quality, and that about 0.5 is a middle starting point. Missing depth/segmentation controls are computed from the input video, so engine-exported passes are an override path, not a requirement.
• articleWhat are the code, weights and dataset terms of the main 4D reconstruction and video-to-4D releases, and where do the texts conflict?
  Per-component record at pinned commits. Code: 4DGaussians (Apache text), Real-time 4DGS and DreamGaussian4D (MIT text), Consistent4D (Apache), Dynamic 3D Gaussians (MIT except Inria-licensed files) and SV4D inference code (MIT). Four repositories carry a conflict between the root licence and Inria non-commercial source headers or files (4DGaussians, Real-time 4DGS, DreamGaussian4D) or a stated split (Dynamic 3D Gaussians). Weights: SV4D 2.0 under the Stability AI Community License with a card that contradicts itself at exactly US $1,000,000 revenue; SV4D v1 card unreadable without login; Consistent4D and Dynamic 3D Gaussians advertise third-party or archive checkpoints without terms. Datasets: Neu3D is CC BY-NC 4.0; D-NeRF/HyperNeRF/Nerfies dataset terms are not stated in the READMEs read; DyCheck's iPhone dataset is Apache 2.0 per its README. No legal clearance is concluded.
• articleGiven a latitude, longitude, date and camera heading, how does an agent compute sun azimuth and elevation, light windows and the sun's bearing relative to the lens, and does a from-scratch calculation reproduce the published NREL example?
  SYNTHESIS with the worker's own arithmetic, not a source claim. Implementing the USNO approximate-solar-coordinates equations (S4) plus a standard GMST expression, the worker reproduced the NREL SPA Table A5.1 example (Golden, Colorado, 2003-10-17 19:30:30 UT) to 0.015 degrees in zenith, 0.002 degrees in azimuth, and sunrise, transit and sunset (UT-date convention) within 1 second (the script prints whole seconds). A worked shot-direction use: for a camera heading of 270 degrees (looking west) at the same site, the sun's bearing relative to the lens is -75.7 degrees at 19:30:30 UT and -24.7 degrees at 23:00 UT; with the golden-hour boundary taken at 6 degrees elevation (SunCalc's code) the window to sunset on the local evening of 17 Oct is 23:42:10 to 00:18:52 UT (about 37 minutes), and civil twilight ends at 00:46:05 UT. SPA lists rise/set for the UT calendar date, so its 'sunset 00:20:19 UT' is the previous local evening's sunset.
• articleHow do cinematographers and location people say they use sun-path plans on a scout and on set, and where do their terms differ from the algorithm sources?
  Three practitioner accounts describe sun planning. ASC's Jay Holben (2021) says to look up a location's orientation on a map before the scout, bring a compass, use a sun-tracking app (he names Chemical Wedding's Helios) to predict where the sun is on any day, and estimates the sun moves about a quarter degree per minute (a finger's width at arm's length is about 15 minutes). Cinematographer Todd Martin (Filmsupply, 2016) uses the Sun Seeker app on scouts and describes a sunrise shaft of light in a pool that would last about 10 minutes, so the crew arrived early to lay track and rehearse. A producer's tech-scout checklist (2020) says to know where the sun rises and sets and mentions Sun Seeker. Holben's article calls the sun's height 'azimuth', which conflicts with the algorithm sources where azimuth is the compass bearing.
• articleWhich primary algorithm sources let an agent compute sun position and rise/set times, what accuracy do they state, and what inputs and conventions do they require?
  Four primary or near-primary sources state different accuracies for different purposes. NOAA GML says its sunrise and sunset results are theoretically accurate to within a minute between +/-72 degrees latitude and within 10 minutes outside, assumes 0.833 degrees refraction, and warns the calculator is no longer actively supported and its data cannot be certified. The NREL SPA report (Reda and Andreas, revised January 2008) gives a step-by-step procedure with stated uncertainty of plus or minus 0.0003 degrees for zenith and azimuth over the years -2000 to 6000 and needs inputs such as delta T, pressure and temperature. USNO gives a simple solar-coordinates algorithm accurate to about 1 arcminute within two centuries of 2000 and says rise/set times may be in error by a minute or more even in ideal conditions. SunCalc's README claims about 0.08 degrees and 15 seconds against JPL Horizons and USNO data.
• articleWhich lens-metadata systems (Cooke /i, ZEISS eXtended Data, ARRI LDS) publicly document their fields, and which of those fields end up in recorded files?
  Cooke's /i FAQ lists per-frame lens fields (including entrance pupil position) recorded at up to 285 fps and says the extent recorded is the camera maker's choice; SMPTE RIS camdkit (0362321d) decodes entrance pupil and aperture from RED-recorded Cooke /i binary but leaves entrance pupil unmapped (TODO) in its ARRI CSV path.
• articleWhat numeric frame-time, refresh-rate and comfort budgets do Valve, Meta and Apple actually state, and what evidence stands behind them?
  For frame-time and comfort budgets, Valve's GDC 2015 talk (90 Hz = 11.11 ms, ~2 ms panel persistence, 2 ms running start from measured 1.5-2.0 ms bubbles, 24.22 ms prediction) and Meta's Quest page (Oct 2024: interactive apps at least 72 FPS, media apps may aim for 60; Rift S 80, Rift 90; ranges 'may vary') state numbers, while Apple's visionOS HIG comfort guidance read is qualitative.
• articleHow do MotionCtrl and CameraCtrl differ from text camera prompts: what do they condition on, what can be controlled independently, and which backbones are supported?
  Problem. Words like 'dolly in' give no exact trajectory. Pose-conditioned models take a numeric camera path. Conditions. Research checkpoints you run yourself (not hosted prompt UIs). Method. MotionCtrl: motion conditions are camera poses and object trajectories, treated as appearance-free; camera motion and object motion can be controlled independently or together; the repo script sets condtype to 'camera_motion', 'object_motion' or 'both'; released on VideoCrafter, SVD and AnimateDiff branches; extra test poses in dataset/camera_poses; object trajectories can be drawn with HandyTrajDrawer or extracted with ParticleSfM. CameraCtrl: a plug-and-play camera pose control module trained on top of a video diffusion model, leaving other base modules untouched; main branch is on AnimateDiff V3 with an svd branch; trajectories are per-frame camera poses (the README visualises each frame as a small tetrahedron for camera position and orientation); paper reports that training videos with dive...
• articleWhat capture-stage production conditions did a practice-based study find helpful for getting cartoon-style (principle-driven) movement out of motion-capture performers?
  Mohr (QUT, 2019) proposes four production conditions from four practice cycles: an 'animation performer' with movement training and animation knowledge; curated animated reference sent ahead and shown during capture; an optional pre-production capture of movement stylisations on a work-in-progress character; and gestural warm-ups with scaffolded actions. Supporting practices reported as helpful: overt movement, energetic actions first, goal-driven actions, a live projector view, and aesthetic movement rules per style. The thesis states the conditions have not yet been applied to a full production and that post-capture editing was not examined.
• articleIn OpenXR 1.1, what are the reference spaces and what conventions (axes, floor, recentering, tracking loss) must a spatial authoring pipeline assume?
  Corrected 2026-10-23 - see C3-B642-05; the original statements below are kept for history and are superseded where the correction says so. In the OpenXR 1.1 specification source (release-1.1.65), LOCAL_FLOOR is provided by XR_VERSION_1_1 and runtimes must support it; it is world-locked and gravity-aligned with +Y up, +X right and -Z forward, with its origin on the runtime's floor estimate, whereas STAGE is a floor-centred rectangle whose spaces a runtime may be unable to locate.
• articleIf I author a USD ParticleField3DGaussianSplat and render with hdPrman (RenderMan), does it read the sorting/projection hints or kernel type, and what does it draw?
  Corrected 2026-10-23 - see C3-B642-06; the original statements below are kept for history and are superseded where the correction says so. At OpenUSD v26.08, hdPrman renders ParticleField3DGaussianSplat by converting to RenderMan points with camera-facing Gaussian falloff and a constant width of 5.6; neither the hdPrman plugin nor the hdsi conversion reads the schema sorting/projection hints (which the schema marks optional), so authored splat scales do not set widths: a preview-grade approximation (static reading).
• articleWhich authored Gaussian-splat attributes carry through to a RenderMan render of USD, and which are lost?
  Corrected 2026-10-23 - see C3-B642-06; the original statements below are kept for history and are superseded where the correction says so. In OpenUSD (ee47c679) renderers without native particle-field support get splats converted to points: the generic hdsi conversion sets point width from the mean of the three scales and turns spherical-harmonic radiance into primvars, while the hdPrman plugin replaces width with a constant 5.6; orientation and kernel are not used in either file, so the RenderMan path is a preview of positions and colour, not a faithful Gaussian splat render.

More