Skip to main content
InovativeWorks
Participant
April 24, 2026

"Create Multiple Compositions" renders black — preview normal, render silent black (CC2024 & CC2026)

  • April 24, 2026
  • 1 reply
  • 21 views

# Adobe Community Forum Bug Report (Form Format)

## Title:

“Create Multiple Compositions” produces comps that render completely black — silent failure, no error

-----

## Issue:

Compositions created by dragging multiple MOV files onto the New Composition icon in the Project panel (“Create Multiple Compositions”) render as completely black output. Preview plays back normally. The render completes with a success status and no error message, making this a silent failure.

## Steps to reproduce:

1. Import multiple MOV files into the Project panel
1. Select the MOV files and drag them onto the “New Composition” icon (film strip icon at the bottom of the Project panel)
1. AE creates one composition per MOV via “Create Multiple Compositions”
1. RAM Preview any of the created comps — video plays normally
1. Add the comp to the Render Queue
1. Render using any format (ProRes 4444, PNG sequence, etc.)
1. Check the output — completely black

## Expected result:

Rendered output matches the preview with visible video content.

## Actual result:

Rendered output is completely black. No error message is displayed. The render queue shows success.

## Application version:

- After Effects CC2024
- After Effects CC2026 (v26.x)
- Both versions reproduce this issue

## Operating system:

- Windows 11

## GPU driver version:

- (Not GPU-related — issue persists regardless of GPU settings)

## Comparative context:

- Does it affect all projects? — Yes, reproducible in any new project
- Does it affect new projects? — Yes
- When did the problem begin? — Unknown, discovered April 2026. Confirmed on both CC2024 and CC2026

## What I’ve ruled out:

- Color management settings — no effect
- Bit depth (8/16/32bpc) — no effect
- Footage interpretation — no effect
- Re-encoding source MOVs via Media Encoder — no effect
- aerender (command line) — same black output
- PNG sequence output — same black output

## Suspected cause:

The “Create Multiple Compositions” workflow inherits the source footage’s internal timecode into the comp’s displayStartTime (e.g., source TC 1:00:59:05 → comp displayStartTime 1:00:59:05). This appears to corrupt the comp’s internal state so that RGB data does not reach the render pipeline. Manually resetting displayStartTime to 0 after creation does not fix the issue.

## Workaround:

Create compositions manually (Ctrl+N / Cmd+N), then drag footage into the comp. Manually created comps render normally.

## Why this is critical:

The render completes without any error or warning. Users have no indication that the output is broken, which creates a high risk of delivering black frames to clients.

-----

(Screen recording can be provided upon request)

Kazuki Inoshita / InovativeWorks
AE plugin developer — aescripts.com/authors/inovativeworks/

    1 reply

    Nishu Kushwaha
    Community Manager
    Community Manager
    April 24, 2026

    That's not ideal. Sorry to hear about the issue. I tested it on my end. I didn't encounter the issue. If possible, can you share a screen recording of the issue? Are there any third-party plugins/effects involved? Are there any third-party plug-ins installed? Can you try exporting using Media Encoder and see if the issue persists?

    Let me know.


    Thanks,

    Nishu

    InovativeWorks
    Participant
    April 24, 2026

    Hi Nishu,

    Thank you for testing. Here are the additional details:

    **Third-party plugins:** None involved. The issue occurs with raw source footage only — no effects applied, no expressions, just the MOV placed in the comp.

    **Media Encoder:** Same result — black output.

    **Source footage details:**

    - Format: ProRes 422 HQ MOV
    - Resolution: 1920x1080
    - The footage has embedded timecode starting at 1:00:59:05 (not 00:00:00:00)

    **Exact reproduction steps (more specific):**

    1. Import multiple MOV files that have non-zero embedded timecode (e.g., starting at 1:00:59:05)
    1. Select all MOVs in the Project panel
    1. Drag them onto the “New Composition” icon (film strip icon at the bottom of the Project panel)
    1. AE creates one comp per MOV via “Create Multiple Compositions”
    1. Notice: the created comp inherits the source’s timecode as its displayStartTime
    1. RAM Preview — plays normally
    1. Render (Render Queue or Media Encoder) — output is completely black

    **Key finding:** The issue appears to be specifically related to source footage with non-zero embedded timecode. When “Create Multiple Compositions” copies this timecode into the comp’s displayStartTime, something breaks in the render pipeline. Manually resetting displayStartTime to 0 does not fix it.

    **Workaround confirmed:** Creating a comp manually (Ctrl+N) and dropping the same footage in renders correctly.

    I can provide a screen recording and a short sample MOV with embedded timecode if that would help reproduce the issue. Let me know.

    Thanks,
    Kazuki / InovativeWorks

    InovativeWorks
    Participant
    April 25, 2026

    additional note:

     

    All 5 files are ProRes (10-bit yuv422p10le) from free:

    |#                               |File                              |Result |Profile        |Resolution|FPS|Color Transfer     |
    |--------------------------------|----------------------------------|-------|---------------|----------|---|-------------------|
    |1                               |406568_Splashing_Droplets_…_HD.mov|BLACK ❌|ProRes Standard|1920x1080 |25 |bt709              |
    |2                               |461919_Casserole_Phantom_…_4K.mov |OK ✅   |ProRes HQ      |3840x2160 |30 |unknown (no tag)   |
    |3                               |556278_Bubbles_Liquid_…_4K.mov    |BLACK ❌|ProRes HQ      |3840x2160 |25 |iec61966-2-1 (sRGB)|
    |4                               |6041240_Oar_Remo_Tour_…_4K.mov    |BLACK ❌|ProRes Standard|3840x2160 |25 |bt709              |
    |5                               |6084959_Pottery_Process_…_4K.mov  |OK ✅   |ProRes HQ      |3840x2160 |24 |bt2020-10          |
    |Common attributes (all 5 files):|                                  |       |               |          |   |                   |

        •    Codec: prores (10-bit yuv422p10le)
        •    Color primaries: bt709
        •    Source: Artlist stock footage (.mov container)
    Pattern observed:
        •    All 3 failures are 25fps; both successes are 30fps / 24fps
        •    Failures have explicit color transfer tags (bt709 / sRGB);
    successes have either no tag or bt2020-10
        •    However, neither fps nor color tag is the root cause —
    the same files render correctly when dropped into a manually
    created composition (Ctrl+N), bypassing “Create Multiple Compositions”.