• Global community
    • Language:
      • Deutsch
      • English
      • Español
      • Français
      • Português
  • 日本語コミュニティ
    Dedicated community for Japanese speakers
  • 한국 커뮤니티
    Dedicated community for Korean speakers
Exit
2

P: Warp Stabilizer very slow when using Color Space Conversion

Community Beginner ,
May 24, 2024 May 24, 2024

Copy link to clipboard

Copied

Warp stabilizer analysis slows down massivly when using Color Space Conversion from Rec 2100 PQ. to Rec 709. By massively I mean at least 90% slower.  Tested with Canon 4k/25 HDR PQ (Rec. 2100 PQ) footage and compared to regular 4k/25 Rec. 709 footage. Lumetri color settings used are default, i.e. HDR Graphics white to 203 and tone mapping for Max RGB.

Reproduce:

  1. Create Rec. 709 sequence
  2. Add Rec. 2100 PQ footage
  3. Apply warp stabilzer

 

Environment:

Pr. version 24.3.0

Macbook Pro (M2 Pro) with 32gb ram

 

Bug Needs More Info
TOPICS
Color , Effects , Performance or Stability

Views

195

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines

correct answers 1 Correct answer

Adobe Employee , Jun 10, 2024 Jun 10, 2024

Hello Cogitare, 

 

This is a known issue with Warp Stabilizer when applying a Lumetri color space transform BEFORE running Warp Stabilizer. However, if you run Warp Stabilizer first, then apply the transformation, you won't get the slow down.

 

The order of operations is:

1. Drop Rec 2100 PQ (or HLG) clip on to timeline.

2. Set Timeline Working Color Space to Rec 2100 PQ (or HLG) -- just make sure it matches the clip.

3. Apply Warp Stabilizer (make your tweaks and final adjustments

4. Change Time

...

Votes

Translate

Translate

correct answers 1 Pinned Reply

Adobe Employee , May 24, 2024 May 24, 2024

Hi @Cogitare,

Thanks for writing in with the info you provided. I think the team may need more details: How do I write a bug report?

 

Knowing more about your footage and sequence settings might help them reproduce the issue. I hope the team or the community can assist you with this bug report.

 

Thanks,
Kevin

Status Needs More Info

Votes

Translate

Translate
5 Comments
Adobe Employee ,
May 24, 2024 May 24, 2024

Copy link to clipboard

Copied

Hi @Cogitare,

Thanks for writing in with the info you provided. I think the team may need more details: How do I write a bug report?

 

Knowing more about your footage and sequence settings might help them reproduce the issue. I hope the team or the community can assist you with this bug report.

 

Thanks,
Kevin

Status Needs More Info

Votes

Translate

Translate

Report

Report
Community Beginner ,
May 24, 2024 May 24, 2024

Copy link to clipboard

Copied

Hope this will be enough:

  • Issue - See above
  • Adobe Premiere Pro version number: 24.3.0 (Build 53)
  • Operating system - MacOS Sonoma 14.5
  • System Info: CPU, GPU, RAM, HD:
    • M2 Pro
    • 32GB RAM
    • 1TB SSD
  • Video format: 4K 25fps HEVC 10 bit 4:2:2, Rec 2100 PQ color space (Canon HDR PQ)
  • Workflow details: New basic sequence (4K/25) with Rec. 709 color space, with Auto Tone map media enabled. Preview format Apple ProRes LT.
  • Steps to reproduce - See above 
  • Expected result - Normal warp-stabilizer speed, somewhat comparable to native 8-bit Rec. 709 footage.
  • Actual result -  Considerably slower warp-stabilizer, only a few frames per second.

Votes

Translate

Translate

Report

Report
Community Beginner ,
May 25, 2024 May 25, 2024

Copy link to clipboard

Copied

Just realized it's regardless of using the Color Space Conversion or not. Dropping the footage on an empty native Rec. 2100 PQ sequence and applying the warp stabilizer is just as slow. Maybe the warp stabilizer just a really difficult time analyzing that format?

Votes

Translate

Translate

Report

Report
Engaged ,
Jun 10, 2024 Jun 10, 2024

Copy link to clipboard

Copied

I'm having the same problem, extremly slow when Color Space is active.

 

I tested without Color Space Convertion and now works as before.

Votes

Translate

Translate

Report

Report
Adobe Employee ,
Jun 10, 2024 Jun 10, 2024

Copy link to clipboard

Copied

LATEST

Hello Cogitare, 

 

This is a known issue with Warp Stabilizer when applying a Lumetri color space transform BEFORE running Warp Stabilizer. However, if you run Warp Stabilizer first, then apply the transformation, you won't get the slow down.

 

The order of operations is:

1. Drop Rec 2100 PQ (or HLG) clip on to timeline.

2. Set Timeline Working Color Space to Rec 2100 PQ (or HLG) -- just make sure it matches the clip.

3. Apply Warp Stabilizer (make your tweaks and final adjustments

4. Change Timeline Working Color Space to Rec 709, enable Auto Tone Map Media

 

Warp Stabilizer's analyze phase is CPU-only, while Lumetri's color transform is GPU-enabled. If the color transform is applied before Warp Stabilizer is run, then it pushes Lumetri on to the CPU which is why you're seeing the dramatic decrease in performance.

 

Please let me know if this helps, or if I can provide any more support here.

 

Eric

 

Votes

Translate

Translate

Report

Report