NVIDIA hardware encoding issue

Subject: Urgent: Unacceptable Performance Drop, Ignored Feedback, & Missing NVIDIA Hardware Encoding Support Since v25.2 (v25.2 through v27 Beta)

System info
Application: Adobe Media Encoder (Beta) v27.0.0.23
CPU : AMD 7900x3D
RAM : 64GB
SSD : 4TB, 4TB, 2TB
GPU : RTX 4070 Ti (NVIDIA Studio driver : 581.57)

OS: Windows v10.0.19045, RAM: 63.65GB GB, CPUs (logical): 24

Feedback Summary & Key Requests

• Severe Performance Regression: Smooth playback and editing workflows possible in legacy versions are now broken from v25.2 onward.

• Missing CUDA/NVENC Support: Both Premiere Pro and Adobe Media Encoder (v25.2+ through CC 2027 Beta) completely fail to utilize NVIDIA Hardware Acceleration for HEVC/H.265.

• Ignored User Reports & Account Churn Warning: Multiple submitted feedback reports have received no response or resolution, forcing us to consider switching away from Adobe after this year.

Detailed Feedback Content

1. Severe Playback & Timeline Performance Degradation Since v25.2

• Prior to version 25.2, identical editing workflows ran smoothly on the exact same hardware configuration.

• Ever since the v25.2 update, performance has degraded so drastically that editing without proxy generation has become virtually impossible. The system is currently too slow and unstable for actual professional use.

2. Broken HEVC (H.265) Hardware Encoding Across Premiere Pro & Media Encoder (v25.2 – CC 2027 Beta)

• H.265 export speed in recent releases has plummeted compared to legacy builds.

• Both Premiere Pro and Adobe Media Encoder starting from CC 2025 (v25.2 through v25.5) up to the current CC 2027 Beta fail to engage NVIDIA Hardware Acceleration (CUDA/NVENC) for HEVC/H.265 encoding.

• While CC 2023 and early CC 2025 releases (v25.0, v25.1) operated properly, every release from v25.2 onward across both applications falls back to software/CPU encoding or fails to utilize GPU hardware pipelines.

• Leaving a critical hardware regression unaddressed across major software updates for nearly 1 to 2 years—and allowing it to persist into the 2027 Beta—is completely unacceptable.

3. Feature Request: Standalone Proxy Presets in Adobe Media Encoder

• Creating proper proxies with correct metadata currently forces users to open Premiere Pro first.

• Dedicated, built-in Proxy Encoding Presets must be made available directly within Media Encoder for independent batch-rendering.

Demands & Final Warning

As monthly paying subscribers, we should not be forced to deal with a broken product that ruins daily productivity.

I have submitted feedback regarding this critical issue multiple times, yet there has been absolutely no response, update, or acknowledgment from Adobe. This silence is extremely frustrating.

This problem is so severe that I am actively considering canceling my subscription after this year and switching to alternative editing software.

If Adobe cannot immediately resolve this hardware encoding defect and restore normal timeline performance, you must at least allow subscribers to download and run earlier working legacy versions indefinitely until a proper fix is deployed. Please address this critical regression with the utmost urgency.