Maya Sequence QA: Find Missing and Broken Redshift Frames Before Delivery
A long batch can finish with gaps you only find in comp. Check these before you deliver:
- Log file: Render.exe -log saves standard output and errors to a file (Windows)
- Frame range: -s, -e and -b set start, end and step
- Redshift log: the latest session is in the Log.Latest.0 folder
- Missing frames: compare the range with the files on disk
- Broken frames: flag 0 KB files and files far below a good frame
A batch render that reports it finished is not the same as a complete sequence. Frames can be missing because a batch stopped early, empty because a frame was cut off while writing, or written under another name in another folder. These problems usually surface in compositing, after the render machine has been shut down.
This guide shows how to start a Maya and Redshift batch from the command line with a log file, where Redshift keeps its own log, how to scan the output folder for missing, empty and suspiciously small frames, and how to re-render only the frames that need it. To catch problems before the batch, use the Maya and Redshift pre-flight checklist.
Checked against Autodesk’s Maya command line renderer documentation and Maxon’s Redshift log documentation, November 2026.
1. Why a finished batch can still have broken frames
A batch writes one file per frame. If the batch stops, everything after that frame is missing. If a frame is interrupted while it is being written, the file can exist with no data in it. If the output flags differ from the scene, frames land in another folder or under another name and look missing. The diagram shows how a short check turns those cases into a re-render list.
The check only needs the frame range, the output folder and the file name prefix. It does not open the images, so it runs in seconds even on long sequences; open any frame it flags before deciding to re-render.
2. How to render a Maya sequence from the command line with a log
Autodesk documents the command line renderer as Render -r <renderer> <options> <filename>, and on Windows it must be called with its full path (Autodesk: Render from the command line). Among the common flags, -s, -e and -b set start, end and step, -rd and -im set the folder and file name, -pad sets frame number digits, and -log saves standard output and error information to a file, a flag Autodesk lists as Windows only (Autodesk: Common flags for the command line renderer).
Redshift also keeps its own log. Maxon’s support article points to C:\ProgramData\Redshift\Log, where the most recent session is in Log.Latest.0 (Maxon: Finding your Redshift log file). Maxon notes that log folders can conflict when several Maya instances render at the same time, so keep a separate -log file per instance (Maxon: Log Files).
3. How to find missing and broken frames (step by step)
The script below lists missing frames, 0 KB files and files smaller than a limit you set from one good frame of the shot. It expects names in the form prefix.1001.exr; change the pattern if your render settings use another naming convention.
Settings checklist (copy or follow line by line):
4. Reading the result and fixing the sequence
Each pattern in the report points to a different cause. Use the table to decide whether to re-render a range, read the log at one frame, or fix the output flags first.
What a broken sequence usually means
Start from what the check script reports.
| What the check finds | Likely cause | What to do |
|---|---|---|
| A run of missing frames at the end | The batch stopped or the machine was shut down before the range finished | Re-render from the first missing frame with -s and -e |
| Single missing frames in the middle | A frame failed and the batch moved on, or the step (-b) skips frames | Read the log at that frame; check -b is 1 |
| 0 KB files | The frame was opened for writing but never finished | Delete and re-render those frames |
| Files far smaller than the rest | Partly written frame, or a pass that rendered black | Open the frame; re-render if it is incomplete |
| Frames in the wrong folder or with another name | -rd, -im or project settings differ from the scene | Fix the flags and keep one naming pattern per pass |
| Errors from two renders mixed in one log | Two Maya instances wrote logs at the same time | Give each instance its own -log file and frame range |
Keep the batch file, the log and the check report together in the project’s logs folder. When a shot comes back with notes, you can see which frames were re-rendered and with which command.
5. SaaS or IaaS render farm for checking long sequences?
Who checks the sequence on each farm type
Both farm types return frames; the difference is who runs the check and who re-renders.
| Situation | Usually a better fit | Why |
|---|---|---|
| You want frames delivered and checked by the farm | SaaS | The farm’s job manager tracks failed frames |
| You run your own checks and re-renders | IaaS | You run the script and Render.exe on the render machine |
| Many shots with different frame ranges | IaaS | One batch file per shot with its own log |
| Studio pipeline with its own submit tools | Either | Pick the farm that supports your submit workflow |
Rule of thumb: check the sequence before you stop paying for the machine that rendered it.
Checking a Maya sequence on an iRender server
An iRender server is a full Windows machine with 32 GB RTX 5090 or 24 GB RTX 4090 GPUs:
- Upload the project to iRender Drive before you start a server; uploading is free and does not use rental time.
- Start a server, install your Maya version and the matching Redshift build once; they stay in your image. Setup details are in Redshift for Maya on a multi-GPU render server.
- Render with Render.exe and a -log file, then run the check script on the output folder.
- Re-render the listed frames, run the check again, then shut down. Multi-GPU servers bill per minute; 1-GPU servers have a one-hour minimum.
Sequence QA checklist
Tick each item before you deliver the sequence.
Frequently asked questions
1. How do I save a log of a Maya batch render?
Add -log with a file path to the Render.exe command. Autodesk describes it as saving standard output and standard error information to a file and lists the flag as Windows only.
2. Where is the Redshift log file?
Maxon’s support article points to C:\ProgramData\Redshift\Log on Windows. The latest session is in the Log.Latest.0 folder; older sessions have date and time in the folder name.
3. How do I find missing frames in a rendered sequence?
Compare the frame range with the files in the output folder. A short Python script can list every frame number without a file, plus 0 KB files and files much smaller than a good frame.
4. Why are some rendered frames 0 KB?
The file was created but the frame did not finish writing, for example because the batch stopped. Delete those files and re-render the frames.
5. How do I re-render only some frames in Maya?
Run Render.exe again with -s and -e set to the first and last frame of each gap, with the same output flags as the original batch.
6. Why are my frames in a different folder or with another name?
The command line flags override render settings. Check -rd, -im, -pad and the project path so every batch writes the same pattern.
7. Can I run two Maya renders at once on one machine?
You can, but Maxon notes that Redshift log folders can conflict when several Maya instances render simultaneously. Give each instance its own frame range and -log file.
8. Can I check and re-render sequences on iRender?
Yes. An iRender server is a full Windows machine where you install Maya and Redshift once, run Render.exe with a log, check the output and re-render frames before shutting down.
Render your Maya and Redshift projects on iRender
iRender is an IaaS GPU render farm: you rent a bare-metal server with 1, 2, 4 or 8 NVIDIA RTX 4090 (24 GB) or RTX 5090 (32 GB) GPUs, an AMD Ryzen™ Threadripper™ PRO CPU, 256 GB ECC RAM and a 2 TB NVMe SSD, connect by remote desktop and work on it like your own workstation, with full administrator access. Your server image is saved between sessions, so your plugins and settings stay installed. Maya is not pre-installed: you install the Maya version your scene uses with your own Autodesk license, and it stays in your image. Prime accounts get Redshift licenses pre-activated on every server.
Multi-GPU servers are billed per minute (1-GPU servers have a one-hour minimum), and sessions of 3 hours or more get 10% off. Our 4-GPU and 8-GPU servers are liquid-cooled; in our own measurements the GPUs hold 60–70°C under sustained render load. Elite support is available 7 days a week by hotline, live chat, Skype, WhatsApp and email.
This quick start shows how to start a server and connect to it:
A full Maya and Redshift session we recorded on an 8x RTX 4090 server:
New users get a 100% bonus on the first top-up (minimum $50). See plans on the Maya render farm for Redshift page or download the iRender GPU app.
Sources: Autodesk: Render from the command line · Autodesk: Common flags for the command line renderer · Maxon: Redshift Log Files · Maxon Support: Finding your Redshift log file. Checked November 2026.



