Skip to main content

Filter by idea status

10000+ Ideas

Stan Jones
Community Expert
Stan JonesCommunity Expert

Downgrading PR 2026 Projects to Earlier VersionOpen for Voting

Premiere 2026 projects cannot be downgraded for import to PR 2026 or earlier due to changes in the 2026 project data structure. Recent discussions about this have not yet been ported to the new forum. The primary previous feature request is here, but may be missing some interim posts. Also, it was primarily an explanation for how to use the non-Adobe methods for changing the project file version number. https://community.adobe.com/feature-requests-730/open-premiere-project-in-older-version-downgrade-project-version-1329162?postid=1329162#post1329162 At a minimum, there needs to be a method for downgraded a PR 2026 project to 2025. A longer term issue is the need, for years, for a more robust converter or for the After Effects procedure for doing a “save as” from a later PR version to some number of earlier versions. January 26, ​@hellopaul4 started a thread titled “Has version "2026" killed the ability to downgrade a project to a previous version?” The most important reply was by ​@Fergus H: “We are considering options for backwards compatibility, but we have nothing to announce at this time.We haven’t intentionally prevented downgrading tools from working with Premiere v26. As you likely know, those tools only change the internal version number without modifying the project data itself. However, in v26, the project data structure has changed significantly – largely due to the new Object Mask feature. Because of this, a v26.x file that has had its version number changed cannot be parsed correctly by v25.x or earlier, leading to the crashes or error messages you encountered.Fortunately, there is a simple remedy for your current situation: you can open the project created in the v26.x beta directly in the shipping version of v26.0. The file formats are identical, so you can move your work out of the Beta environment without needing to downgrade the file.” As Fergus says, The official Adobe recommendation for downgrading is XML export:https://helpx.adobe.com/premiere-pro/using/backward-compatibility.html However, when I tested, XML export/import was not working for me on Win 11. My reply in that thread included:“I tested this, and trying to open a PR 26.0.0 XML export in PR 25.6.4 crashes, as it does if creating a new project and importing it. It did import to a new project in 24.6.5, and, once saved there, I could open the PR 24 version in 25.6.4.”I have not retested this. Stan 

make it stop please! scroll wheel in program panel zooms in, super annoying & dumb new featureOpen for Voting

when I hover over the program panel to scroll through the timeline with my scroll wheel on my mouse the update apparently makes it zoom into the video instead of scrubbing through the timeline. This is extremely frustrating. Zooming into the frame is never a feature I wanted so it's completely useless. I need to be able to scrub the timeline with the cursor over the video in the program monitor for more than one reason. One, to fine tune my cuts which is the majority of what I do when I'm editing all day. So, I need this to not be a problem I have to constantly deal with all day every day. The way it suddenly is now there's a fine, unseen line between where I can scrub the timeline and where it zooms into the video and half the time I cross that line and zoom into the video. I then have to select "fit" until it happens again and knocks it out of "fit" into some percentage. Another time when I need the program panel to scrub with the cursor over the video is if I'm moving an object to create keyframes. In this case, which is fortunately not often, it would be excruciating to constantly have to move the cursor down below the fine line and back up again.In short, I need it so the program panel scrubs the timeline as it does when I use the scroll wheel in the lower part of the panel, but I need it to do this even when the cursor is over the video in that panel. This changed sometime last year I think where it use to work properly but instead of scrubbing it frame by frame it like it does at the bottom of the panel it jumped around all annoying. Now it zooms into the video. It's like Adobe keeps ruining features with updates, like they're charging for updates that I don't want and only make editing harder. 

Chris Spiegl
Community Expert
Chris SpieglCommunity Expert

Bug Report / API Defect: Scripted Export Queue Fails Silently with HEVC (H.265) PresetsOpen for Voting

There is a critical bug in the Premiere Pro / Media Encoder API (app.encoder) where attempting to programmatically queue a sequence using an HEVC (H.265) preset fails entirely. While the API seamlessly processes H.264, ProRes, and WAV presets, passing an HEVC preset results in a silent failure—Media Encoder simply drops the request without adding the item to the queue or returning an error code.Scope of ImpactThis is not an isolated plugin issue. This API defect completely breaks the core functionality of major industry-standard automation extensions, including: Excalibur (by Knights of the Editing Table) RenderSegments Blinkl.io Any workflow or custom JSX script utilizing the Adobe API to automate exports to HEVC is currently non-functional.The Inefficient WorkaroundCurrently, editors are forced to use a highly disruptive workaround: Trigger the scripted export using an H.264 or ProRes preset to successfully force the item into the Media Encoder queue. Manually select the queued items inside Media Encoder. Manually re-assign the desired HEVC preset to all items. For high-volume editors handling dozens of social media clips, localized versions, or review cuts daily, this manual intervention completely defeats the purpose of investing in automation tools.Steps to Reproduce (For Adobe Engineers) Create a custom export preset using the HEVC (H.265) format in Media Encoder. Use a CEP/ExtendScript workflow to programmatically queue an active sequence via app.encoder.encodeSequence(), passing the path of the HEVC preset. Observe Media Encoder: The application registers a command, but the queue remains empty. No error is thrown in the console. Repeat the exact same script using an H.264 preset path: The sequence queues instantly and perfectly. Requested ActionAdobe Engineering needs to investigate the backend handling of the encodeSequence method specifically when interfacing with the HEVC encoder wrapper. The API should treat HEVC presets with the exact same reliability as H.264 and ProRes.If you use automation extensions and have been frustrated by your HEVC queues failing, please upvote and comment with the extension you use to bring visibility to the Adobe API team!