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

Warp Stabilizer extremely slow when "Auto Detect Log Video Color Space" is enabled

Community Beginner ,
Apr 01, 2024 Apr 01, 2024

Copy link to clipboard

Copied

In Premiere Pro 24.3, the Warp Stabilizer effect is extremely slow when processing log footage with the "Auto Detect Log Video Color Space" option (ADVLCS) enabled in the Lumetro Color > Settings panel. I'm defining slow as 1/12 the speed observed when applying a fresh instance of Warp Stabilizer to the same clip with ADVLCS disabled. The log footage was shot on a Panasonic S5ii (4:2:2 10-bit LongGOP, 150Mbps) and I am actively using Quicktime ProRes proxy files (quarter frame size) when applying the Warp Stabilizer effect in both scenarios.

 

A few quick computer specs in case they are relevant: 

  • Primary drive is 512GB SSD
  • Project and source footage drive is external SSD connected through Thunderbolt 3 port (Crucial X9 Pro, 4TB)
  • Cache files stored on secondary SATA platter HD
  • Intel(R) Core(TM) i7-7820X CPU @ 3.60GHz 3.60 GHz
  • RAM: 32.0 GB (I know... more would be good!)
  • Windows 10 Pro Education, Version 22H2 (OS build 19045.4046)
    Experience Windows Feature Experience Pack 1000.19053.1000.0
Bug Investigating
TOPICS
Color , Performance or Stability

Views

360

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 Pinned Reply

Adobe Employee , Apr 03, 2024 Apr 03, 2024

@Enumcluck I've sent you an email to get more information. 

 

Thanks for your very clear problem description!

Votes

Translate

Translate
8 Comments
Adobe Employee ,
Apr 02, 2024 Apr 02, 2024

Copy link to clipboard

Copied

@Enumcluck Thanks for reporting this, we're investigating what's going on.

Votes

Translate

Translate

Report

Report
Adobe Employee ,
Apr 03, 2024 Apr 03, 2024

Copy link to clipboard

Copied

@Enumcluck I've sent you an email to get more information. 

 

Thanks for your very clear problem description!

Votes

Translate

Translate

Report

Report
Community Beginner ,
Apr 03, 2024 Apr 03, 2024

Copy link to clipboard

Copied

Thanks, Fergus! I responded to your email with a sample project. Hopefully it helps your team isolate the issue. 

Votes

Translate

Translate

Report

Report
Adobe Employee ,
Aug 15, 2024 Aug 15, 2024

Copy link to clipboard

Copied

The status of this bug report has been updated.

Kevin Monahan - Sr. Community & Engagement Strategist – Pro Video and Audio
Status Investigating

Votes

Translate

Translate

Report

Report
New Here ,
Nov 05, 2024 Nov 05, 2024

Copy link to clipboard

Copied

Hello there! i have the exact same issue on Premiere Pro 25.0. Did you mange to find any solution??

Votes

Translate

Translate

Report

Report
Community Beginner ,
Nov 05, 2024 Nov 05, 2024

Copy link to clipboard

Copied

I haven't received any updates from Adobe to say if they are making progress on this. For now, I just gave up on "Auto Detect Log Video Color Space" and went back to using LUTs on an adjustment layer to avoid GPU processing conflicts for Warp Stabilizer. Until Adobe can address conflicts with commonly-used effects, I can't afford the slower workflow. 

Votes

Translate

Translate

Report

Report
New Here ,
Nov 05, 2024 Nov 05, 2024

Copy link to clipboard

Copied

Thank you for the immediate response! I will also stick with the adjustment layer solution. However, it seems strange to me that no one else seems to be facing this issue. I mean, no one using the ADLVCS function with the Warp Stabilizer?? That sould be widely known to the community but i didnt find any other relevant thread.

Votes

Translate

Translate

Report

Report
Community Beginner ,
Nov 05, 2024 Nov 05, 2024

Copy link to clipboard

Copied

LATEST

To be fair, my understanding is that Adobe Premiere Pro has an effects pipeline that tries using the GPU, but if one of those effects runs into an issue and needs to default back to the CPU, it affects all downstream effects in the que. Drivers and GPU hardware all play a part.

 

I've since moved to a newer machine with an NVIDIA GeForce RTX 4070 and should retry ADLVCS but haven't had time with several back-to-back work deadlines. Once those are behind me — crossing fingers for next week! — I'll have to rety with the test project I sent to Adobe and see if it behaves any differently between the new hardware and Premiere 25.0. 

Votes

Translate

Translate

Report

Report