# Rendertz Complete Technical Documentation Generated on: 2026-11-09T10:57:52.530Z Base URL: https://rendertz.com ---------------------------------------- --- title: Quickstart: Your First Cloud Render in 5 Minutes description: Learn how to connect your account, run a single-frame sanity test, and dispatch high-speed cloud renders on Rendertz. category: getting-started categoryLabel: Getting Started lastUpdated: 2026-10-08 order: 1 --- # Quickstart: Your First Cloud Render in 5 Minutes Welcome to **Rendertz**, the high-performance distributed cloud rendering platform designed for 3D artists, animators, and visual effects studios. This quickstart guide walks you through claiming your starter tokens, setting up your environment, rendering a single-frame test to verify camera angles and shaders, and submitting your full production animation. --- ## 1. Create Your Account & Claim Starter Tokens Every new studio registration receives **starter compute tokens** to benchmark render times risk-free. 1. Navigate to [rendertz.com/auth/register](/auth/register) and register with your studio email. 2. Confirm your verification email to activate your account. 3. If you have an onboarding voucher or promotional code: - Head to **Account Settings > Billing & Tokens**. - Enter your code into the **Redeem Voucher** box. - Your token balance will update immediately (1 Token = $0.01 USD anchor value). > [!TIP] > Rendertz meters strictly by active compute seconds. You are never billed for queue standby or file unpacking time. --- ## 2. Prepare Your Scene: Single-Frame Sanity Check Before dispatching an entire 600-frame sequence, **always run a single-frame sanity check**. A test frame validates shader compiling, texture paths, and lighting balance within 30–60 seconds, preventing wasted budget. ### Recommended Sanity Check Checklist - [ ] Select a complex hero frame (e.g., frame 45 or 120 where key lights, volumetrics, and characters are all in frame). - [ ] Ensure **Cycles** or **EEVEE Next** is selected in your render properties. - [ ] Check that samples and denoising algorithms (OptiX or OpenImageDenoise) are enabled. - [ ] Save your file before exporting or uploading. --- ## 3. Dispatching via Web Studio If you are not using our native Blender Addon, you can upload directly in your browser: 1. Open the [Rendertz Web Studio](/app/projects). 2. Drag and drop your `.blend` file (or a `.zip` archive containing your scene and `textures/` folder). 3. The **Automated Cloud Inspector** will parse your scene: - Detects saved camera and render resolution. - Analyzes frame bounds (e.g., frames 1 to 250). - Verifies whether external image textures are embedded. 4. Set **Target Frames** to **Specific Frame** and enter `1`. 5. Select **Pro GPU** (24GB VRAM) for accelerated OptiX ray tracing. 6. Click **Submit Test Render**. ```bash # Example Rendertz Scene Inspector Output Scene: hero_cinematic_v04.blend Engine: Blender Cycles (OptiX Accelerated) Resolution: 3840 x 2160 (4K UHD) Active Camera: Cam_Main_Rig Frame Range: 1 - 250 (Fps: 24) Textures Detected: 48 (All Relative / Packed) Estimated Test Frame Cost: ~3.0 Tokens ($0.03 USD) ``` --- ## 4. Live Telemetry & Inspecting Output Once submitted, your job transitions into the live telemetry dashboard: - **State Pipeline**: `Queued` → `Starting Node` → `Rendering` → `Completed`. - **Live Frame Inspector**: View rendered output in real time with high-dynamic-range image inspection. - **Burn Rate Counter**: Track exact seconds elapsed and tokens burned. When your sanity frame completes: 1. Zoom in to inspect fine geometry, displacement maps, and alpha fringes. 2. Verify that there are no untextured elements (no magenta or unlinked shaders). 3. Check memory telemetry to verify VRAM headroom. --- ## 5. Submitting the Full Animation Now that your sanity frame is verified: 1. Click **Duplicate Job & Adjust** or return to Web Studio. 2. Under **Target Frames**, select **Frame Range** (e.g. `1 - 250`) or enter a custom pattern such as `1-250x2` for half-framerate previews. 3. Select your hardware fleet: - **Pro GPU (24GB VRAM)**: Ideal for fast multi-frame production turns. - **Monster Multi-GPU (96GB VRAM)**: Uncompressed 8K textures, ultra-dense geometry, and heavy interior archviz. 4. Enable **Automated Deliverables**: - Check **Generate MP4 Preview** to automatically compile an H.264/H.265 daily reel upon sequence completion. - Check **Generate Master ZIP** for single-click archive retrieval. 5. Hit **Dispatch Production Fleet**. Sit back and monitor progress on your desktop or mobile browser while our cloud nodes render your frames in parallel. ---------------------------------------- --- title: Token Economics & Hardware Compute Tiers description: Understand Rendertz token pricing, per-minute burn rates across CPU and GPU hardware tiers, and our zero-queue-cost guarantee. category: getting-started categoryLabel: Getting Started lastUpdated: 2026-10-08 order: 2 --- # Token Economics & Hardware Compute Tiers Rendertz operates on a predictable, transparent, prepaid credit unit called the **Render Token**. Our pricing is engineered so studios and independent artists never face opaque surge pricing, surprise overages, or minimum monthly commitments. --- ## The Render Token Standard - **1 Token = $0.01 USD** (100 Tokens = $1.00 USD) - **Local Currency Support**: Top up seamlessly using East African mobile money (M-Pesa, Airtel Money, Tigo Pesa) or international debit and credit cards. - **Pay Only for Compute Seconds**: Metering starts strictly when rendering begins on a provisioned compute node and halts the instant the final output frame is written. ``` +--------------------------------------------------------------------------+ | Zero-Queue-Cost Guarantee | | | | Queue Waiting Time ---> $0.00 / 0 Tokens (100% Free Forever) | | Scene File Ingestion ---> $0.00 / 0 Tokens | | Automated Scene Probe ---> $0.00 / 0 Tokens | | Active Frame Compute ---> Metered per second at tier rate | | Frame Asset Retention ---> 7 Days Included with Every Render | +--------------------------------------------------------------------------+ ``` --- ## Hardware Compute Tiers Choose from purpose-built CPU clusters or enterprise NVIDIA GPU fleets tailored for Blender Cycles, EEVEE, Arnold, Corona, and V-Ray. | Tier Name | Specifications | Burn Rate (Tokens/min) | Effective Hourly Rate | Recommended Workload | | :--- | :--- | :--- | :--- | :--- | | **Studio CPU (16 Cores)** | 16 vCPUs, 32GB RAM | **2.25 Tokens/min** | **$1.35 / hr** | Physics sims, cloth, V-Ray/Corona CPU, high-RAM architectural stills | | **Studio CPU (32 Cores)** | 32 vCPUs, 64GB RAM | **4.25 Tokens/min** | **$2.55 / hr** | Heavy OpenVDB smoke/fire cache generation, multi-threaded CPU baking | | **Studio CPU (64 Cores)** | 64 vCPUs, 128GB RAM | **8.00 Tokens/min** | **$4.80 / hr** | Massive point clouds, raw photogrammetry, high-RAM lookdev | | **Pro GPU (24GB VRAM)** | 1x NVIDIA Discrete GPU, 24GB VRAM | **3.00 Tokens/min** | **$1.80 / hr** | **Most Popular:** Cycles OptiX ray tracing, motion design, 4K animation | | **Pro GPU Max (48GB VRAM)** | 1x NVIDIA High-Density GPU, 48GB VRAM | **5.50 Tokens/min** | **$3.30 / hr** | Cinematic production shots with 8K UDIM textures and complex hair curves | | **Monster GPU (96GB VRAM)** | 4x NVIDIA GPUs, 96GB Total VRAM | **11.50 Tokens/min** | **$6.90 / hr** | High-throughput multi-GPU film sequences, volumetric lighting | | **Colossus GPU (192GB VRAM)** | 8x NVIDIA GPUs, 192GB Total VRAM | **22.00 Tokens/min** | **$13.20 / hr** | Studio tentpole sequences requiring ultra-fast turnaround times | --- ## How Burn Rate is Calculated All jobs are metered to the exact second using high-resolution node timers. $$\text{Tokens Burned} = \left(\frac{\text{Active Compute Seconds}}{60}\right) \times \text{Tier Rate}$$ ### Real-World Example Suppose you dispatch a 120-frame animation on the **Pro GPU (24GB VRAM)** tier: - Each frame takes an average of **45 seconds** to render. - Total compute time = $120 \times 45 = 5{,}400 \text{ seconds}$ (90 minutes total). - Token Burn: $90 \text{ minutes} \times 3.00 \text{ Tokens/min} = \mathbf{270 \text{ Tokens}}$. - Total Cost: **$2.70 USD** (approximately 7,150 TZS). If your project spent 3 minutes in the queue while high-speed nodes were initialized, **0 tokens** are deducted for that queue time. --- ## Managing Your Balance & Auto-Top-Up 1. View real-time balance in the top studio navigation bar. 2. In-flight jobs will pause gracefully if your balance reaches zero, preserving all frames rendered up to that second. 3. Top up anytime using the [Pricing & Top-Up page](/pricing). ---------------------------------------- --- title: Scene Preparation & Asset Packing description: Best practices for packing textures, configuring relative asset paths, and baking simulation caches before submitting to Rendertz. category: scene-prep categoryLabel: Scene Preparation lastUpdated: 2026-10-08 order: 1 --- # Scene Preparation & Asset Packing Cloud render nodes operate in headless, high-throughput cloud environments. Because worker instances do not share your local workstation drive letters (such as `C:\Users\Artist\...` or `/Users/artist/Desktop/...`), your assets must either be **packed inside the `.blend` file** or bundled with **clean relative paths**. --- ## Method 1: Automatic Resource Packing (Recommended for Single `.blend` Files) For self-contained scenes under 2 GB, embedding all textures and external media directly into your `.blend` file ensures 100% texture fidelity. ### Step-by-Step Packing in Blender 1. In Blender, open your project. 2. Navigate to **File > External Data > Pack Resources**. 3. Blender will embed all referenced images, environment HDRIs, and fonts directly into the binary `.blend` file data blocks. 4. Enable **File > External Data > Automatically Pack Resources** to ensure any newly added textures stay packed when you press `Ctrl+S`. 5. Save your file. ``` Blender Menu: File └── External Data ├── Pack Resources [Click to embed immediately] └── Automatically Pack Resources [Check to persist on save] ``` > [!NOTE] > Video textures (e.g. `.mp4`, `.mov` image sequence planes) and physics caches (OpenVDB, Alembic) cannot be packed into `.blend` files. Use Method 2 below for scenes containing simulation caches or video footage. --- ## Method 2: Relative Directory Structure & ZIP Packaging For large projects, UDIM tiles, video planes, or external caches, organize your project folder using relative paths before compressing: ``` my_cinematic_project/ ├── my_scene.blend ├── textures/ │ ├── hero_diffuse.png │ ├── hero_roughness.exr │ └── hero_normal.png ├── hdri/ │ └── studio_sunset_4k.hdr └── cache/ └── fluid_sim/ ├── sim_frame_0001.vdb └── sim_frame_0002.vdb ``` ### Making Paths Relative in Blender 1. Open your `.blend` file. 2. Select **File > External Data > Make Paths Relative**. 3. Verify that your image paths in the Shader Editor start with `//` (for example: `//textures/hero_diffuse.png`). 4. Save your file. 5. Compress the root directory (`my_cinematic_project`) into a `.zip` file. 6. Upload the `.zip` archive via the **Web Studio** or let the **Rendertz Blender Addon** handle delta sync automatically. --- ## Baking Physics, Fluid & Particle Simulations Cloud rendering nodes render frames in parallel. If frame 50 depends on physics from frame 49 and the cache is unbaked, parallel nodes will produce mismatched or exploding simulations! ### 1. Mantaflow (Smoke, Fire & Liquids) - Go to the **Physics** tab of your Domain object. - Under **Cache**, change **Type** from `Replay` to `Modular` or `All`. - Click **Bake All** or **Bake Data**. - Save the VDB cache into a relative folder (`//cache/vdb/`). ### 2. Cloth & Soft Bodies - Select the cloth object. - Open **Physics > Cloth > Cache**. - Click **Bake** to generate frame-by-frame point displacement data. ### 3. Rigid Body Dynamics - Go to **Scene Properties > Rigid Body World > Cache**. - Click **Bake** to freeze keyframes. --- ## Pre-Flight Scene Checklist Before sending your file to the cloud, run through this 30-second checklist: - [ ] **Relative Paths**: No paths pointing to absolute local drives (`C:\`, `D:\`, or `/Users/...`). - [ ] **Missing Files Check**: Run **File > External Data > Report Missing Files** to ensure zero 404 warnings in Blender's info header. - [ ] **Active Camera**: Confirm an active camera is designated in **Scene Properties > Camera**. - [ ] **Output Format**: Set to `PNG` (16-bit) or `OpenEXR` for maximum compositing flexibility. - [ ] **Denoiser**: Ensure OptiX or OpenImageDenoise is enabled if using Cycles to save render time. ---------------------------------------- --- title: Blender Addon & N-Panel Walkthrough description: Complete guide to installing the Rendertz Blender Addon, authenticating with Personal Access Tokens, running pre-flight scans, and delta syncing. category: blender-addon categoryLabel: Blender Addon lastUpdated: 2026-10-08 order: 1 --- # Blender Addon & N-Panel Walkthrough The official **Rendertz Blender Addon** integrates distributed cloud rendering directly into your 3D Viewport sidebar (N-Panel). With the addon, you can audit missing textures, verify camera settings, sync only modified byte chunks over fast delta streams, and dispatch farm renders without ever leaving Blender. --- ## 1. Installation & Setup 1. Download the latest addon archive (`rendertz-blender-v0.1.0.zip`) from [rendertz.com/download](/download). 2. Open Blender (supports versions **3.6 LTS**, **4.0**, **4.1**, **4.2 LTS**, and **4.3+**). 3. Open **Edit > Preferences > Add-ons**. 4. Click **Install...** (or **Install from Disk** in Blender 4.2+). 5. Select the downloaded `.zip` file and check the box next to **Render: Rendertz Cloud Render Farm**. --- ## 2. Authentication with Personal Access Tokens (PAT) The addon communicates securely with our cloud API using fine-grained Personal Access Tokens. 1. In your web browser, navigate to [rendertz.com/app/settings/tokens](/app/settings/tokens). 2. Click **Create Access Token**. 3. Provide a label (e.g. `MacBook Pro Workstation` or `Studio Main Rig`). 4. Copy your secret token (prefixed with `rz_pat_live_...`). 5. Return to Blender, press `N` in the 3D Viewport to open the sidebar, and switch to the **Rendertz** tab. 6. Paste the token into the **Personal Access Token** field and click **Connect Account**. 7. Your account balance, active tier credentials, and studio name will appear instantly. ``` +-------------------------------------------------------+ | RENDERTZ CLOUD FARM | | Status: Connected [studio@renderhouse.com] | | Balance: 1,450 Tokens ($14.50 USD) | | Active Engine: Cycles (OptiX Enabled) | +-------------------------------------------------------+ ``` --- ## 3. The Viewport N-Panel Layout The Rendertz N-Panel is organized into three intuitive workflows: ### A. Pre-Flight Scene Scanner Click **Scan Scene** to trigger an automated local diagnostic: - **Missing Texture Audit**: Scans all `ShaderNodeTexImage` nodes. Any image marked pink or pointing to non-existent disk locations is flagged with line-item fixes. - **Path Inspector**: Verifies whether asset paths are properly converted to relative `//` format. - **Simulation Validation**: Checks if Mantaflow or Geometry Nodes simulations have baked cache files ready on disk. - **Camera & Resolution**: Displays current render resolution, aspect ratio, and designated active camera. ### B. Fleet & Compute Hardware Selector - Choose your compute tier: - **Studio CPU (16 Cores)**: Clean stills & physics caching. - **Pro GPU (24GB VRAM)**: Fast GPU ray tracing. - **Monster Multi-GPU (96GB VRAM)**: Demanding cinematics & 8K textures. - Set frame range: - **Sanity Frame**: Renders single test frame (e.g. current playhead frame). - **Animation Range**: Reads scene start/end frames or custom comma-separated sequences. ### C. Delta-Chunk Synchronization Engine Unlike traditional render farms that re-upload your entire multi-gigabyte `.blend` archive on every revision, Rendertz features **Block-Level Delta Sync**: 1. The addon divides your `.blend` file into 4MB cryptographic blocks. 2. It sends an inventory manifest of hashes to our cloud vault. 3. If you changed only a camera angle or tweaked a roughness shader, **only the modified 4MB chunks are uploaded**—saving up to 98% of upload bandwidth. --- ## 4. Submitting a Render Job 1. Once the Pre-Flight Scanner displays `All Checks Passed`, click **Dispatch Render**. 2. The addon syncs missing asset blocks to your private Project Vault. 3. The job is queued and automatically assigned to high-performance cloud hardware. 4. An inline telemetry card displays live progress percentage, elapsed render time, and token burn rate. 5. Click **Open in Web Studio** anytime to view multi-frame live previews or download completed EXR sequences. ---------------------------------------- --- title: Web Studio Upload Guide & Cloud Inspector description: Upload scenes through your web browser, review automated metadata probes, override render settings, and manage project retention. category: web-studio categoryLabel: Web Studio lastUpdated: 2026-10-08 order: 1 --- # Web Studio Upload Guide & Cloud Inspector The **Rendertz Web Studio** provides a full-featured browser interface for managing 3D projects, inspecting scene parameters, and launching render jobs from any computer, tablet, or mobile device. --- ## 1. Drag-and-Drop Browser Ingestion You can upload `.blend` scenes and zipped multi-file project archives directly from your browser: 1. Open [rendertz.com/app/projects](/app/projects). 2. Click **New Project** or drag your `.blend` or `.zip` file into the upload zone. 3. Supported formats include: - Standalone `.blend` files (with packed resources). - `.zip` or `.tar.gz` archives (containing `.blend` + relative `textures/`, `cache/`, `fonts/` directories). - Up to **50 GB** per project archive. ### Resumable Chunked Multipart Transfers For large files (over 50 MB), Web Studio automatically switches to high-speed multipart streaming: - Transfers are split into parallel 10 MB parts. - If your internet connection hiccups or drops momentarily, the upload pauses and resumes automatically without restarting from byte zero. --- ## 2. Automated Cloud Scene Probe The moment your file completes uploading, our serverless **Scene Inspector** safely parses your binary data blocks without executing untrusted scripts: - **Saved Cameras**: Lists all scene cameras (`Cam_Main`, `Cam_Closeup`, `Cam_Drone`) and notes the active camera. - **Frame Bounds**: Reads frame start, frame end, and FPS (e.g. frames `1` to `240` at `24 fps`). - **Render Engine**: Identifies Cycles, EEVEE Next, or workbench configurations. - **Resolution**: Extracts target width and height (e.g., `1920x1080` or `3840x2160`). - **Resource Verification**: Counts image texture data blocks and confirms whether external assets are packed. --- ## 3. Parameter Overrides You don't need to reopen your local 3D application just to change a camera or lower preview resolution. Web Studio gives you granular control over job execution: ### Available Overrides 1. **Target Camera**: Choose any camera detected by the probe. 2. **Resolution Scaling**: Render at 50%, 75%, 100%, or 200% resolution for quick draft turnarounds. 3. **Frame Selection**: - *Specific Single Frame*: Quick sanity test. - *Full Range*: Every frame in sequential order. - *Custom Frame Step*: Render every $N^{\text{th}}$ frame (e.g. `1-200x5` to render frames 1, 6, 11, 16...). 4. **Denoising & Sampling Overrides**: Force OptiX denoiser or adjust max samples for rapid turnaround. --- ## 4. The 7-Day Project Retention Shelf To keep cloud storage tidy and cost-free for artists, Rendertz includes a generous **7-Day Retention Window**: - Every project uploaded to your Project Vault remains available for **7 days** free of charge. - Completed render output frames and deliverables (EXR, PNG, MP4 previews) are also retained for 7 days. - A live countdown timer (`Days Remaining`) shows the exact expiration date on each project card. - **Extending Retention**: Need to keep an active client revision alive longer? Click **Extend Retention** to add 7 or 30 days of storage for a small token fee. - When an asset reaches expiration, it is purged cleanly from the cloud storage bucket to protect your intellectual property. ---------------------------------------- --- title: Troubleshooting Missing & Pink Textures description: Diagnose and resolve neon magenta shaders, absolute Windows drive paths, and Linux case-sensitivity issues on cloud render nodes. category: troubleshooting categoryLabel: Troubleshooting lastUpdated: 2026-10-08 order: 1 --- # Troubleshooting Missing & Pink Textures In Blender and modern 3D engines, when an object renders with a bright **neon magenta / pink** color, it indicates that the render engine cannot locate the referenced image texture file on disk. Since cloud render farm nodes execute on headless Linux instances, file paths must follow portable cross-platform conventions. --- ## Common Causes of Pink Textures ### 1. Absolute Windows Drive Paths If your image node is linked to `C:\Users\Artist\Downloads\wood_diffuse.jpg` or `D:\Assets\Textures\`, cloud nodes cannot find this directory because Linux nodes do not possess a `C:\` or `D:\` drive. ### 2. Linux Case-Sensitivity On Windows and macOS (APFS case-insensitive), `Texture.png` and `texture.PNG` refer to the same file. On Linux render nodes, **casing is strictly enforced**. If your shader expects `brick_diffuse.PNG` but the file on disk is named `brick_diffuse.png`, the shader will fail and display magenta. ### 3. Forgotten External Folders Uploading only the `.blend` file without packing resources or without including the sibling `textures/` directory. --- ## How to Fix Missing Textures ### Solution A: Pack All Resources (Fastest Fix) 1. In Blender on your workstation, open your project. 2. Select **File > External Data > Pack Resources**. 3. All textures are embedded directly into the `.blend` file. 4. Save the file and upload it again to Rendertz. ### Solution B: Convert to Relative Paths & Clean Case 1. Place all texture files into a folder named `textures` inside your project directory. 2. In Blender, select **File > External Data > Find Missing Files**. 3. Point the file browser to your local `textures/` folder. 4. Once Blender finds and links the images, select **File > External Data > Make Paths Relative**. 5. Check your Shader Editor: all file paths should begin with `//` (for example, `//textures/wood_diffuse.png`). 6. If uploading via Web Studio, compress the parent folder containing both the `.blend` and `textures/` directory into a `.zip` file before uploading. ### Solution C: Run the Rendertz Pre-Flight Scanner If you have the **Rendertz Blender Addon** installed: 1. Open the N-Panel and click **Scan Scene**. 2. The scanner will highlight any image textures with absolute drive letters or missing local targets. 3. Click **Auto-Fix: Relative Paths** to convert all paths in one click. ---------------------------------------- --- title: Fixing CUDA/OptiX VRAM Out-of-Memory (OOM) Errors description: Diagnose CUDA Out of Memory crashes in Cycles and resolve them using texture limits, geometry optimization, or High-RAM CPU fleet fallback. category: troubleshooting categoryLabel: Troubleshooting lastUpdated: 2026-10-08 order: 2 --- # Fixing CUDA/OptiX VRAM Out-of-Memory (OOM) Errors When rendering complex scenes with uncompressed 8K textures, heavy subdivision surfaces, or dense particle hair on GPU nodes, you may encounter an error message similar to: ``` CUDA error: Out of memory in cuMemAlloc(&device_pointer, size) OptiX error: CUDA_ERROR_OUT_OF_MEMORY Error: System is out of GPU memory ``` This error occurs when the combined geometry, BVH tree, and texture maps exceed the physical VRAM capacity of the graphics card (e.g. 24GB VRAM on Pro GPU). --- ## 1. Fast Fix: Upgrade Hardware Tier If your project requires full uncompromised fidelity and you cannot alter texture resolutions: 1. In the Web Studio or Blender Addon, change your hardware tier from **Pro GPU (24GB VRAM)** to: - **Pro GPU Max (48GB VRAM)**: Double the VRAM capacity for large scenes. - **Monster Multi-GPU (96GB VRAM)**: High-memory multi-GPU configuration for feature-film assets. 2. Re-submit your job. --- ## 2. Optimize Textures with Blender "Simplify" In many cases, background assets use unnecessarily high-resolution textures (such as 8K displacement or roughness maps on distant props). 1. In Blender, open **Render Properties > Simplify**. 2. Check the **Simplify** box. 3. Under **Viewport & Render > Texture Limit**, change `No Limit` to `2048` or `4096`. 4. Blender will dynamically downsample textures during render initialization, dramatically reducing VRAM footprint without touching your original asset files on disk. ``` Render Properties: └── Simplify [x] └── Render: ├── Max Subdivision: 2 └── Texture Limit: 2048 (or 4096) ``` --- ## 3. Optimize Geometry & Particle Hair - **Subdivision Surface Modifiers**: Verify that render levels for Subsurf modifiers are not set to extreme values (such as level 5 or 6). Level 2 or 3 is usually indistinguishable in final renders. - **Particle Hair**: Under **Render Properties > Curves**, select **Curves Info > Subdivision: 1** instead of higher levels to reduce BVH build memory. - **Adaptive Subdivision / Displacement**: If using Cycles Experimental feature set, set **Dicing Scale** in Render Properties to at least `2.0 px` or `3.0 px` rather than `0.5 px`. --- ## 4. Fallback to High-RAM CPU Fleet If your scene contains hundreds of millions of unique polygons, huge un-instanced CAD geometry, or massive fluid caches that exceed GPU memory limits, switch to our **High-RAM CPU Fleet**: - **Studio CPU (16 Cores)**: 32 GB System RAM - **Studio CPU (32 Cores)**: 64 GB System RAM - **Studio CPU (64 Cores)**: 128 GB System RAM CPU render nodes utilize system RAM rather than GPU VRAM. They can handle virtually unlimited scene complexity without crashing. In the Web Studio submission modal, select **Studio CPU** and dispatch your render. ---------------------------------------- --- title: Job Error Recovery & Diagnostic Logs description: How to inspect frame render logs, diagnose execution crashes, recover partial frames, and contact support. category: troubleshooting categoryLabel: Troubleshooting lastUpdated: 2026-10-08 order: 3 --- # Job Error Recovery & Diagnostic Logs If a render job fails or cancels unexpectedly, Rendertz provides full transparent logs and automated failure handling so you can diagnose issues quickly and protect your budget. --- ## 1. Inspecting Live Task Logs Every job in the Rendertz dashboard captures execution logs: 1. Navigate to [rendertz.com/app/jobs](/app/jobs) and click on your failed or flagged job. 2. Under the **Frame Breakdown** tab, click on any frame marked `Failed`. 3. Click **View Console Log** to open the raw standard output (`stdout`) and standard error (`stderr`) stream. 4. Search for keywords such as `Error`, `Traceback`, `CUDA_ERROR`, or `Fatal`. ``` Typical Diagnostic Log Excerpt: Fra:14 Mem:412.5M (Peak 450.2M) | Time:00:03.12 | Remaining:00:24.88 Error: Python script execution disabled in batch mode. Auto-run Python scripts is disabled for security. ``` --- ## 2. Common Error Scenarios & Instant Fixes ### A. Python Script Security Restrictions If your scene relies on custom Rigify rigs, drivers, or Python expressions: - In Blender, check **Edit > Preferences > Save & Load > Auto Run Python Scripts**. - In Rendertz Web Studio, toggle the setting **Allow Scene Drivers** if your rig uses custom Python expressions. ### B. Frame Timeouts If a single frame takes longer than the maximum allotted safety threshold (e.g. 2 hours): - Verify that your sample counts are not set to unreasonably high values (e.g. 4096 samples without adaptive sampling). - Enable **Adaptive Sampling** with a noise threshold of `0.01` or `0.02` to dramatically accelerate dark and uniform areas. ### C. Partial Animation Recovery If an animation job was interrupted or canceled midway: - Completed frames are safely stored in your project deliverables gallery. - You can submit a new job specifying only the remaining missing frame numbers (e.g. `120-250`) without re-rendering completed frames. --- ## 3. Filing a One-Click Diagnostic Support Ticket If a node crashes due to an infrastructure or hardware fault, Rendertz will automatically refund any burned tokens for the affected frames. 1. On the Job Detail page, click **Report Issue**. 2. Select the issue category (e.g., `Render Failure` or `Addon Error`). 3. The platform will automatically attach the sanitized task log, hardware tier, and scene parameters. 4. Our engineering support team will inspect the crash and credit compensation tokens to your balance. ---------------------------------------- --- title: Diagnostics, Privacy & Support Reference IDs description: How Rendertz handles client-side error reporting with in-memory logging, strict PII scrubbing, and Reference IDs (RPT-XXXXX). category: troubleshooting categoryLabel: Troubleshooting lastUpdated: 2026-10-17 order: 4 --- # Diagnostics, Privacy & Support Reference IDs When diagnosing issues across the **Rendertz After Effects Extension**, **Blender Addon**, or **Web Studio**, getting clear technical context without compromising studio privacy is critical. Rendertz features an enterprise client-side diagnostic system engineered around three core principles: 1. **Zero disk I/O overhead** through an in-memory rolling ring buffer. 2. **Automated client-side PII scrubbing** that strips passwords, secret access tokens, local operating system directory usernames, and email addresses *before* payload transmission. 3. **Traceable Reference IDs (`RPT-XXXXX`)** stored with a 30-day ephemeral cloud retention lifecycle for rapid engineering triage. --- ## 1. The 150-Line In-Memory Rolling Ring Buffer Client extensions and web tools capture real-time execution context in a circular, rolling memory buffer limited to **150 entries**: - **Zero Disk Drag**: Log entries are held strictly in process RAM. No heavy log files are continuously written to workstation SSDs. - **Auto-Rotation**: When log line 151 arrives, line 1 is discarded automatically. - **Captured Telemetry**: Records component initialization, ExtendScript communication bridges, asset hash verification milestones, chunk upload progress, and network response statuses. ``` +--------------------------------------------------------------------------+ | In-Memory 150-Line Ring Buffer (RAM) | | | | [DEBUG][Init] Extension host detected: Adobe After Effects 2025.1 | | [INFO] [Sync] Background .aep hash verified (2.0s debounce) | | [INFO] [Vault] 3 assets deduplicated, 1 delta chunk queued (4.2 MB) | | [WARN] [Queue] Item 2 has missing audio pass, auto-setting -sound OFF | | ... [Rolling 150 lines preserved for instant diagnostic bundle] ... | +--------------------------------------------------------------------------+ ``` --- ## 2. Automated PII & Credential Scrubbing Before any telemetry or user-submitted diagnostic snapshot is transmitted to the Rendertz Cloud, the client sanitization engine processes every string through strict regular expression filters: | Sensitive Pattern | Local Client Source | Sanitized Cloud Transmission | | :--- | :--- | :--- | | **Personal Access Tokens** | `rz_pat_live_8f3a9b21c4e7...` | `rz_pat_[REDACTED]` | | **Authorization Headers** | `Bearer eyJhbGciOiJIUzI1...` | `Bearer [REDACTED]` | | **Windows User Directory** | `C:\\Users\\SarahConnor\\Projects\\...` | `C:\\Users\\[USER]\\Projects\\...` | | **macOS User Directory** | `/Users/sarahconnor/Library/...` | `/Users/[USER]/Library/...` | | **Email Addresses** | `sarah@productionhouse.tv` | `[EMAIL]` | > [!IMPORTANT] > Sanitization happens **on your workstation** prior to HTTP serialization. Your secret Personal Access Tokens, local file system user account names, and private contact details never touch Rendertz servers in diagnostic reports. --- ## 3. Circuit Breaker & Crash Rate Limiting To prevent network congestion or loop flooding in the event of repeated host application errors (such as a malfunctioning third-party script or expression loop): - **Circuit Breaker Window**: The client enforces a maximum threshold of **5 automatic error reports per 10-minute sliding window**. - **Error Deduplication**: If an identical error message or stack trace occurs repeatedly within 60 seconds, subsequent occurrences are merged and dropped locally. - **Non-Blocking Operation**: Telemetry reporting executes asynchronously in the background. If a network timeout occurs, it fails silently without interrupting the artist's active timeline or displaying intrusive OS alert popups. --- ## 4. Ephemeral 30-Day Cloud Data Lifecycle All diagnostic snapshots sent to Rendertz Cloud Telemetry are governed by an automated, ephemeral **30-day Time-To-Live (TTL)**: - Every report is tagged with an immutable expiration timestamp ($t_{\text{now}} + 30 \text{ days}$). - Once the 30-day window elapses, the report and associated log buffers are **permanently and automatically purged** from our cloud databases. - Diagnostic data is utilized exclusively for troubleshooting and defect resolution—never for marketing, profiling, or third-party tracking. --- ## 5. Generating a Diagnostic Report from the Settings Tab If you encounter an unexpected issue—such as an asset failing to collect, a composition failing pre-flight inspection, or a network drop during submission—you can transmit a diagnostic snapshot directly to Rendertz engineering: 1. In After Effects, open the extension panel (**Window > Extensions > Rendertz Cloud Render**). 2. Switch to the **Settings** navigation tab. 3. Scroll down to the **Diagnostics & Technical Support** card. 4. *(Optional)* Enter a brief note in the text field describing the behavior (e.g., *"Render queue item 3 stalled during packaging"*). 5. Click **Send Diagnostic Report**. 6. The panel transmits the sanitized log buffer (up to 100 recent lines) alongside your operating system and host application version. ``` +--------------------------------------------------------------------------+ | Report Transmitted! | | Reference ID: RPT-74912 | | Share this Reference ID with support on WhatsApp or Email for tracking. | +--------------------------------------------------------------------------+ ``` ### Copying Sanitized Logs Manually If your workstation operates in an air-gapped or restricted firewall environment, click the **Copy Logs** button. This formats the sanitized 150-line buffer onto your system clipboard so you can paste it directly into an email or studio support ticket. --- ## 6. Sharing Reference IDs with Support Every generated diagnostic report produces a distinctive 5-digit Reference ID formatted as: $$\mathbf{RPT\text{-}XXXXX} \quad \text{(e.g., \texttt{RPT-48291})}$$ When reaching out to the Rendertz Concierge or engineering team: - **WhatsApp Support**: Message our 24/7 technical line and include your Reference ID. - **Email Support**: Include `[RPT-XXXXX]` in your email subject line. Our engineering team can instantly retrieve the sanitized diagnostic telemetry, correlate it with backend cloud compute logs, and identify the root cause within minutes without requesting access to your proprietary source files. ---------------------------------------- --- title: After Effects Extension Overview & Architecture description: Professional cloud rendering for Adobe After Effects 2022 through 2026 with native CEP integration. category: after-effects-extension categoryLabel: After Effects Extension lastUpdated: 2026-10-17 order: 1 --- # After Effects Extension Overview & Architecture The **Rendertz After Effects Extension** brings high-performance distributed cloud rendering directly into Adobe After Effects. Designed for motion designers, broadcast animators, and VFX compositors, the extension eliminates local workstation rendering freezes. It allows you to dispatch single still frames, focused work areas, custom frame ranges, or entire multi-composition render queues to high-speed cloud compute fleets while continuing to edit on your local timeline. --- ## 1. Adobe Ecosystem Integration & Architecture The extension is built on Adobe's **Common Extensibility Platform (CEP 11/12)**, seamlessly combining modern HTML5/TypeScript presentation with an embedded Node.js execution runtime and deep ExtendScript DOM access. ``` +-------------------------------------------------------------------------+ | Adobe After Effects Host Application | | | | +-----------------------------------------------------------------+ | | | Rendertz Extension UI Panel (Chromium / HTML5) | | | | - 3-Mode Time Span Control (Work Area, Still Frame, Custom) | | | | - Rendertz Multi-Shot Queue & Smart Frame-Range GPU Locking | | | | - Live Project Vault Sync Status & Token Balance Pill | | | +-----------------------------------------------------------------+ | | | | | +----------------------------v------------------------------------+ | | | Extension Client Runtime (Embedded Node.js) | | | | - 2.0-Second Debounced "Upload on Save" Watcher (Ctrl+S) | | | | - Persistent PAT Credential Store & Sequence Auto-Extractor | | | | - In-Memory Diagnostic Logger (150-Line Rolling Ring Buffer) | | | +-----------------------------------------------------------------+ | | | CSInterface Bridge | | +----------------------------v------------------------------------+ | | | Host Scripting Layer (ExtendScript / JSX) | | | | - Non-Destructive Project Staging & Relative Path Relinker | | | | - Layer & Pre-Comp Frame-Range GPU Effect Scanner | | | | - Smart Return Engine (Auto-Imports into "_Rendertz Renders") | | | +-----------------------------------------------------------------+ | +-------------------------------------------------------------------------+ | Secure HTTPS / REST API +--------------------------------v----------------------------------------+ | Rendertz Cloud Platform | | - Distributed Dispatch Orchestrator | | - Accelerated Cloud Vault (Zero-Reupload Hash Deduplication) | | - Dedicated Silicon Compute Fleets (GPU & CPU Clusters) | +-------------------------------------------------------------------------+ ``` ### Key Technical Pillars - **Decoupled Architecture**: Business logic is decoupled between the Node.js background worker and the ExtendScript host engine, ensuring zero UI freezing even during multi-gigabyte project packaging. - **Non-Destructive Staging**: Your active working `.aep` file is never modified on disk. Rendertz clones the composition into a temporary staging workspace, rewrites paths to relative formats, and packages assets cleanly. - **Fair-Billing Guarantee**: Metering operates strictly per active compute second on provisioned nodes. You are never billed for queue standby or asset transfer times. --- ## 2. System Requirements & Compatibility The Rendertz Extension is tested and validated for professional studio workstations across macOS and Windows: | Requirement | Minimum Specification | Recommended Production Spec | | :--- | :--- | :--- | | **Operating System** | Windows 10 (64-bit) or macOS 12 (Monterey) | Windows 11 (22H2+) or macOS 14/15 (Sonoma / Sequoia) | | **Processor Architecture** | Intel / AMD 64-bit x86 | Apple Silicon (M1/M2/M3/M4 Pro/Max/Ultra) or Intel Core i9 / AMD Ryzen 9 | | **Adobe After Effects** | After Effects 2022 (v22.0) | After Effects 2024 (v24.x), 2025 (v25.x), or 2026 (v26.x) | | **System RAM** | 16 GB | 32 GB – 64 GB for 4K / high-depth motion graphics | | **Network Uplink** | 10 Mbps broadband | 50+ Mbps fiber (accelerated by Rendertz block delta sync) | --- ## 3. Supported Render Engines & Deliverables Cloud compute nodes run headless instances of Adobe's native command-line rendering engine (`aerender`) configured specifically to prevent dialog freezes and ensure exact color fidelity. ### Native Output Formats & Codecs - **Apple ProRes**: ProRes 422, ProRes 422 HQ, and ProRes 4444 (with Straight Alpha transparency). - **MP4 / H.264 & H.265**: High-efficiency web deliverables with optimized bitrate profiles. - **Lossless Image Sequences**: 16-bit PNG, 16-bit TIFF with Alpha, and 16/32-bit Multi-Layer OpenEXR. - **Audio Integration**: Multi-channel AAC or uncompressed 24-bit 48kHz WAV audio multiplexed seamlessly upon completion. ### Multi-Frame Rendering (MFR) Cloud Optimization Rendertz cloud instances tune After Effects' Multi-Frame Rendering engine dynamically: - CPU thread allocations are capped at 85% to prevent OS thread thrashing and memory paging stalls. - Minimum RAM per thread is pinned to 3 GB, guaranteeing rock-solid stability even when rendering multi-layered 4K motion design comps. --- ## 4. Real Silicon GPU & CPU Fleets Select the optimal compute hardware for your specific project needs. Every fleet tier runs on real, high-performance dedicated silicon: | Hardware Tier | Compute Specs | Burn Rate | Best For | | :--- | :--- | :--- | :--- | | **Studio AE GPU (24GB VRAM)** | 1x NVIDIA Discrete GPU (24GB VRAM), 32 vCPUs, 128GB RAM | **5.50 Tokens/min** ($3.30/hr) | **3D Plugins & GPU Effects:** Video Copilot Element 3D, Optical Flares, Stardust, Trapcode Particular, Boris FX Sapphire | | **Studio CPU (16 Cores)** | 16 vCPUs (Intel Xeon), 32GB RAM | **2.25 Tokens/min** ($1.35/hr) | **Typography & 2D Motion:** Kinetic type, vector shape layers, lower thirds, UI mockups, and character rigging | | **Monster Multi-GPU (96GB VRAM)** | 4x NVIDIA Discrete GPUs (96GB VRAM), 48 vCPUs, 192GB RAM | **11.50 Tokens/min** ($6.90/hr) | **Cinematic Compositing:** Heavy 8K plates, complex multi-pass OpenEXR compositing, and intensive grain passes | > [!TIP] > Use our **Smart Bake Workflow** to isolate heavy 3D GPU layers (such as Element 3D titles) on the **Studio AE GPU** tier for just the few seconds they appear, then render the remaining master timeline on economical **Studio CPU (16 Cores)** for maximum budget efficiency. ---------------------------------------- --- title: Installation & 1-Click Setup description: Installing the extension on Windows and macOS with automatic update detection. category: after-effects-extension categoryLabel: After Effects Extension lastUpdated: 2026-10-17 order: 2 --- # Installation & 1-Click Setup The **Rendertz After Effects Extension** includes automated 1-click installers for both **Windows** and **macOS** that configure Adobe CEP extension permissions, verify directories, and deploy files in seconds. --- ## 1. Download the Universal Extension Package 1. Head to [rendertz.com/download](/download). 2. Select the **Adobe After Effects** tab. 3. Click **Download Extension Bundle** to download the latest universal package (`rendertz-ae-universal.zip`). 4. Extract the downloaded ZIP archive onto your workstation. The extracted folder contains: ``` rendertz-ae-universal/ ├── Install-Windows.bat # 1-Click automated installer for Windows 10/11 ├── Install-Mac.command # 1-Click automated installer for macOS (Apple Silicon & Intel) ├── com.rendertz.aftereffects/ # Extension core bundle (HTML5 panel, Node backend, JSX scripts) └── README.txt # Quick verification instructions ``` --- ## 2. Installing on Windows 1. Ensure **Adobe After Effects** is closed. 2. Open the extracted folder and double-click **`Install-Windows.bat`**. 3. If prompted by Windows SmartScreen, click *More info* → *Run anyway*. ### What the Windows Installer Does: - **Directory Verification**: Validates or creates `%APPDATA%\Adobe\CEP\extensions\`. - **Debug Mode Registry Configuration**: Enables `PlayerDebugMode = 1` across Adobe CSXS hives (`CSXS.9` through `CSXS.14`) in `HKCU\Software\Adobe\`. This allows After Effects to load unsigned production extensions smoothly. - **Clean Deployment**: Copies `com.rendertz.aftereffects` into the user's extensions folder. - **Success Prompt**: Displays a confirmation modal confirming readiness. --- ## 3. Installing on macOS 1. Ensure **Adobe After Effects** is closed. 2. Open the extracted folder and double-click **`Install-Mac.command`**. 3. *(If macOS Gatekeeper asks for confirmation, right-click the file and choose **Open**)*. ### What the macOS Installer Does: - **Directory Verification**: Verifies `~/Library/Application Support/Adobe/CEP/extensions/`. - **CEP Permissions**: Executes `defaults write com.adobe.CSXS. PlayerDebugMode 1` for versions 9 through 14. - **File Copy**: Deploys `com.rendertz.aftereffects` cleanly to the target extension folder. - **System Notification**: Triggers a native macOS notification confirming successful deployment. --- ## 4. Automatic Update Detection & In-Place Upgrades When a new version of the extension is released, upgrading is effortless: 1. Download the new release package from the download page. 2. Run the same installer (`Install-Windows.bat` or `Install-Mac.command`). 3. The installer detects your existing installation: ``` [1/3] Detecting Adobe CEP Extension environment... [UPDATE DETECTED] Existing Rendertz extension found. Upgrading to latest release... ``` 4. The script cleanly purges the old extension files and deploys the update. 5. **Zero Credential Loss**: Your Personal Access Token (PAT) and user preferences are safely preserved in your secure OS credential store and local storage. You do not need to re-authenticate after upgrading. --- ## 5. Configuring Your Personal Access Token (PAT) To connect the extension to your Rendertz token balance and cloud project vault: 1. In your browser, navigate to [rendertz.com/app/settings/tokens](/app/settings/tokens). 2. Click **Create Access Token**. 3. Label your token (e.g., `Motion Design Workstation` or `Studio AE Main`). 4. Copy your secret token (begins with `rz_pat_live_...`). 5. Open Adobe After Effects. 6. In the top application menu, open **Window > Extensions > Rendertz Cloud Render**. 7. In the extension panel, switch to the **Settings** tab. 8. Paste your token into the **Personal Access Token (PAT)** field and click **Verify & Save Token**. ``` +-------------------------------------------------------+ | RENDERTZ CLOUD RENDER | | Status: Connected [studio@motionlab.com] | | Token Wallet: 2,850 Tokens ($28.50 USD) | | Auto-Upload on Save: Active | +-------------------------------------------------------+ ``` Your live token balance, user profile, and active render fleets will populate immediately. You are now ready to dispatch your first cloud render! ---------------------------------------- --- title: Time Spans, Rendertz Queue & Smart GPU Detection description: Work Area, Still Frame, Custom Range, Rendertz Multi-Shot Queue batching, and Smart Frame-Range GPU locking. category: after-effects-extension categoryLabel: After Effects Extension lastUpdated: 2026-10-19 order: 3 --- # Time Spans, Rendertz Queue & Smart GPU Detection In professional motion design, you rarely need to render an entire 60-second composition from start to finish every time. You might need to verify a 2-second transition, export a single hero still frame, or stage multiple compositions and frame ranges to render simultaneously in the cloud. The **Rendertz After Effects Extension** keeps all queuing and scoping inside the extension panel—never touching or conflicting with After Effects' local Render Queue: ``` +--------------------------------------------------------------------------+ | Time Span: | | [ Work Area ] [ Still Frame ] [ Custom ] | | | | Actions: | | [ + Add to Queue ] [ ▶ Render Now ] | +--------------------------------------------------------------------------+ ``` --- ## 1. Time Span A: Work Area ("In - Out" Timeline Selection) The **Work Area** mode renders only the frames bounded by your timeline's Work Area Start (`B` key) and Work Area End (`N` key), matching After Effects' exact 0-based or custom `displayStartFrame` numbering. --- ## 2. Time Span B: Still Frame (Playhead / CTI) The **Still Frame** mode renders the exact single frame where your timeline playhead is currently positioned and switches Output Format to Still Image formats. --- ## 3. Time Span C: Custom Frame Range The **Custom** mode lets you specify any exact start and end frame range (for example `0-120` or `45-90`). --- ## 4. Smart Frame-Range GPU Effect Detection Rendertz scans the active composition and nested pre-comps to find the exact `[startFrame, endFrame]` range where each GPU-mandatory effect (`Element 3D`, `Optical Flares`, `Particular`, `Stardust`, `Plexus`, `Deep Glow`) is active, locking GPU only when your selected frame range overlaps those frames. --- ## 5. The Rendertz Multi-Shot Queue (`+ Add to Queue` & `▶ Render All`) Stage multiple compositions or frame slices with **`+ Add to Queue`**, then click **`▶ Render All`** in the **Queue** tab to upload once and render all items in parallel. --- ## 6. 100-Variation Snapshot Locking Engine (`v001..v100`) Freeze isolated snapshot bundles with **`+ Add to Queue`** up to 100 times. Modify text, swap photos, and change assets freely without project collisions, then dispatch all 100 variations to cloud compute simultaneously. ---------------------------------------- --- title: Automation & Production Safeguards description: Background upload on save (Ctrl+S), smart return auto-import, and straight alpha enforcement. category: after-effects-extension categoryLabel: After Effects Extension lastUpdated: 2026-10-19 order: 4 --- # Automation & Production Safeguards Rendering After Effects projects headlessly on remote cloud servers requires eliminating common traps: modal alert freezes, path mismatches, dark alpha edge fringing, and upload wait times. The **Rendertz After Effects Extension** solves these through automated background sync, intelligent asset ingestion, and strict production safeguards. --- ## 1. Background "Upload on Save" (`Ctrl+S`) Auto-Sync Waiting 5 to 10 minutes for your project to upload when you are ready to render breaks your creative momentum. Rendertz eliminates this with our **Background Sync Engine**: ``` +-------------------------------------------------------------------------+ | The "Zero-Wait" Submission Workflow | | | | Artist presses [Ctrl+S] / [Cmd+S] | | │ | | ▼ | | After Effects flushes .aep to disk | | │ | | ▼ | | Node.js background watcher detects file modification | | │ | | ▼ | | 2.0-Second Write Debounce (Ensures AE disk write is 100% complete) | | │ | | ▼ | | Calculates SHA-256 hash & queries Rendertz Cloud Vault | | │ | | ▼ | | Pushes project delta bytes silently in background (< 5s) | | │ | | ▼ | | Header Pill displays green: [Vault Synced] | | | | When ready to render: Click "Dispatch" -> Submits in < 1 Second! | +-------------------------------------------------------------------------+ ``` ### How It Works Under the Hood: 1. **File Watcher**: When the extension panel opens, an embedded Node.js thread initializes an `fs.watch` listener on the active project path (`app.project.file.fsName`). 2. **2.0-Second Debounce**: When you press `Ctrl+S`, After Effects writes out project binary blocks. The watcher waits 2.0 seconds after the last OS write event to guarantee the file is completely closed and uncorrupted. 3. **Block-Level Delta Sync**: Only modified bytes of the `.aep` are uploaded. Large footage files (video clips, image sequences, audio) that are already present in your private Cloud Vault are completely skipped. 4. **Instant Submission**: When you decide to click **Dispatch Render**, your project data is already residing in the cloud. The job queues instantly. --- ## 2. Smart Return & Automated Project Ingestion With traditional render farms, completed renders sit in a web browser download queue. Artists have to manually unpack the files, drag them into the After Effects project panel, create new folders, and position them onto the timeline. Rendertz automates the entire round-trip with **Smart Return**: ``` Project Panel (After Smart Return) └── 📁 _Rendertz Renders/ ├── 📁 2026-10-17_Hero_Comp_v03/ │ ├── Hero_Comp_v03_Full_ProRes.mov (Auto-Imported Master) │ └── Hero_Comp_LookDev_Frame_0142.png (Single Still) └── 📁 _Bakes/ └── Element3D_Title_Bake_Alpha.mov (Lossless Alpha Pass) ``` ### Automated Ingestion Steps: 1. **Cloud Completion Notification**: When cloud nodes complete rendering, a secure notification triggers the extension's local download manager. 2. **Dedicated Project Bins**: The extension calls ExtendScript to locate or automatically create a clean `_Rendertz Renders` folder in your active AE project. 3. **Metadata Tagging**: Deliverables are imported with job identifiers, render hardware tier, and timestamp tags. 4. **Quick Action Controls**: - 🔍 **Reveal in Explorer / Finder**: Opens the local asset directory on your workstation. - 📥 **Import to Project**: Re-imports the deliverable if you moved or deleted it. - 🎬 **Insert onto Timeline Playhead**: Places the rendered video directly on top of your active composition at the current playhead frame. - 📋 **Copy Cloud URL**: Generates a shareable high-speed link for immediate client or director review. --- ## 3. Strict Straight Alpha Enforcement (Zero Dark Fringing) One of the most common artifacts in motion graphics and VFX is **dark edge fringing** around transparent text, motion-blurred graphics, and particle overlays: ``` +--------------------------------------------------------------------------+ | The Alpha Channel Trap: | | | | Premultiplied with Black: RGB values multiplied by alpha value. | | Imported as Straight: Produces dark, muddy halos around edges! | | | | Rendertz Straight Alpha Guarantee: | | 1. Cloud Output Module locked to Straight Alpha (RZ_PRORES4444_STRAIGHT)| | 2. Smart Return sets footageItem.mainSource.alphaMode = STRAIGHT | | ==> 100% Crisp, Halo-Free Compositing | +--------------------------------------------------------------------------+ ``` ### How Rendertz Guarantees Clean Edges: - **Cloud Output Template**: Cloud worker nodes render alpha passes using our strict Straight Alpha output module template (`RZ_PRORES4444_STRAIGHT`). - **Import Interpretation Enforcement**: When Smart Return imports the footage into your project, ExtendScript inspects the source and forces Straight Alpha interpretation: ```javascript if (footageItem.mainSource.hasAlpha) { footageItem.mainSource.alphaMode = AlphaMode.STRAIGHT; } ``` - This completely eliminates dark halos and fringing when compositing renders over bright backgrounds or live footage. --- ## 4. Headless Cloud Safeguards Rendering headlessly on remote instances requires specialized operating system guards: ### A. Modal Dialog Suppression (`SuppressDialogs`) If an asset or font is missing, desktop After Effects opens a modal pop-up dialog (*"File not found, click OK to continue"*). In a headless cloud environment without a physical user, standard `aerender` hangs indefinitely waiting for a click that never comes, burning billable time. - Rendertz cloud compute nodes launch with Windows Server registry flag `SuppressDialogs = 1`. - All `aerender` execution commands pass `-suppressWarnings` to ensure zero headless stalls. - Our Pre-Flight Scanner audits all project dependencies before dispatch to catch missing files locally before upload. ### B. Headless GPU Virtual Display Driver Plugins such as **Video Copilot Element 3D**, **Optical Flares**, and **Boris FX Sapphire** require hardware OpenGL/DirectX acceleration. Headless server instances do not have physical monitors connected, which normally causes Windows to revert to software graphics emulation (resulting in Element 3D crashing or rendering 100% black frames). - Rendertz GPU nodes feature a hardware **Virtual Display Driver** (EDID monitor emulation). - This ensures the graphics driver reports an active 4K display, unlocking full GPU acceleration for third-party plugins in headless cloud sessions. ### C. Non-Destructive Path Relinking Workstation file paths (such as `C:\Users\Artist\Footage\clip.mov` or `/Users/artist/Footage/clip.mov`) do not exist on remote cloud compute nodes. - Before packaging, Rendertz creates a temporary project staging workspace. - All footage paths are converted into clean relative references (`./(Footage)/clip.mov`). - Your original workstation `.aep` file remains untouched. --- ## 5. Frame-Range-Aware Pre-Flight Sweep Evaluates whether missing footage, offline assets, or unbaked Dynamic Links actually fall inside your active render frame boundaries, suppressing false errors if outside the range. ---------------------------------------- --- title: Smart Delta Frame Cache & Partial Re-Assembly description: Recursive per-frame hash fingerprinting, 0 tokens for unchanged frames, motion blur padding, and automatic cloud stitch. category: after-effects-extension categoryLabel: After Effects Extension lastUpdated: 2026-10-19 order: 5 --- # Smart Delta Frame Cache & Partial Re-Assembly In animation, motion graphics, and VFX, artists frequently render a 2-second portion of a timeline for quick review, then later return to render the entire 10-second composition. Alternatively, after rendering a full commercial, the client might ask for a minor copy change in a 1-second lower third. Traditionally, re-rendering requires paying full compute costs and waiting through 100% of the timeline again. The **Rendertz Smart Delta Frame Cache** eliminates redundant cloud computation by calculating a recursive cryptographic fingerprint $H(f)$ for every frame in your composition. --- ## 1. The Core Innovation: "Portion First → Full Later" Consider this real-world production sequence: ``` Sequence A: Look-Dev / Client Check - Artist selects Work Area: Frames 0 – 30 (1 second) - Cloud renders 30 frames and caches each output in the Rendertz Cloud Vault. - Cost: 30 frames billed (~0.75 Tokens on Studio CPU). Sequence B: Full Final Delivery - Client approves look-dev. Artist selects Full Range: Frames 0 – 120 (4 seconds). - Rendertz inspects frame hashes H(f) across all 120 frames: * Frames 0 – 30: Hashes identical -> 100% CACHE HIT (0 Tokens!) * Frames 31 – 120: New frames -> Dispatched to cloud nodes (bypasses frames 0-30) - Cloud worker stitches cached frames 0–30 + newly rendered frames 31–120 into one unified MP4/MOV. - Cost: Artist pays ONLY for frames 31–120. Zero tokens burned for frames 0–30! ``` --- ## 2. Recursive Per-Frame Hash Fingerprinting $H(f)$ How does Rendertz determine whether frame $f$ has changed without rendering it? The extension's background engine computes a composite SHA-256 fingerprint $H(f)$ based on the active state of every layer and asset that influences that specific frame: $$H(f) = \text{SHA-256}\Big( \text{LayerTree}(f) \parallel \text{KeyframeValues}(f) \parallel \text{AssetHashes}(f) \parallel \text{EffectParams}(f) \parallel \text{CompSettings} \Big)$$ ### What the Hasher Evaluates: 1. **Layer Visibility & In/Out Bounds**: If a layer is inactive or trimmed outside frame $f$, changes to that layer do not alter $H(f)$. 2. **Interpolated Keyframe Values**: Evaluates property values (Position, Scale, Rotation, Opacity, Custom Effect Sliders) at exact time $t = f / \text{fps}$. 3. **Nested Pre-Compositions**: Recursively descends into nested comps to evaluate child layers affecting frame $f$. 4. **Linked Asset Hashes**: Incorporates the SHA-256 content hash of all footage files referenced on frame $f$. If $H(f)$ matches an entry stored in the artist's private Cloud Vault, the frame is marked **Hydrated (Cached)**. --- ## 3. Motion Blur & Temporal Physics Padding ($\pm 1$ Frame Guard) Temporal effects—such as Motion Blur, Timewarp, Echo, CC Force Motion Blur, and optical flow—sample adjacent frames to calculate pixel vectors: ``` Frame f-1 Frame f Frame f+1 [ Adjacent Frame ] ◀── [ Target Frame ] ──▶ [ Adjacent Frame ] ▲ ▲ └─────── Motion Blur Samples Vector ────────┘ ``` If the artist modifies a keyframe on frame 50, frame 50 changes. However, because motion blur on frame 49 samples forward into frame 50, and motion blur on frame 51 samples backward into frame 50, both adjacent frames also change visually. ### The $\pm 1$ Frame Padding Rule: - When a layer has **Motion Blur enabled** or contains temporal effects, Rendertz automatically expands the re-render boundary by $\pm 1$ frame around every modified range. - This prevents temporal edge seams and ensures smooth sub-frame vector transitions between cached and newly computed frames. --- ## 4. Zero-Token Pre-Stopwatch Hydration Under the **Fair-Billing Law**, artists are never charged for cache hydration: 1. When the cloud worker launches, it queries the Rendertz Cloud Vault for all cached frame hashes $H(f)$. 2. Cached frames are downloaded and verified into the worker scratch volume before `aerender` is invoked. 3. **The Billable Stopwatch Does NOT Run**: Cache hydration time is treated as infrastructure overhead and billed at **0 Tokens ($0.00 USD)**. 4. The billable stopwatch starts strictly when `aerender` executes the remaining delta frames. --- ## 5. Cloud Re-Assembly & Self-Healing Worker Fallback Once newly computed delta frames finish, how does the final video get delivered? - **Automated Video Stitching**: A lightweight cloud worker or Lambda function invokes FFmpeg to concatenate the cached and newly rendered frame sequences into the artist's chosen container (`MP4 H.264`, `ProRes 4444 with Alpha`, or image sequence) and muxes the uncompressed audio pass. - **Self-Healing Fallback**: If a cached frame fails checksum verification or is missing from storage, the worker automatically flags that frame for dynamic re-render without failing the overall job. The artist receives a complete deliverable every single time. ----------------------------------------