As a Loupedeck user, I want to add tracks to timeline without causing Premiere to crash.

Steps to reproduce:
Open Premiere Pro 14.6 or 14.7 on Win or Mac (bug is not reproduced with older versions)
Add Loupedeck as control surface
Add a track (audio, submix or video) in the timeline sequence

Expected result:
The track is added, Premiere Pro application is running

Actual result:
The track is not added, Premiere Pro application hangs up

Note:
The behavior is the same when adding tracks with mouse through the UI of Premiere (with LD added as control surface)
Adding tracks works fine when LD is removed as control surface.

It'd be nice if Premiere and After Effects would have some way to let the user isolate and disable/delete plug-ins that cause the programs to crash on start-up (my biggest issue with new updates) or ideally even when it causes older project files not to work correctly. I hardly use plug-ins (for this reason) and even so a few times I've found myself scrutinizing the application load screen trying to catch exactly where the application crashes and then digging through the hard drive to find and delete the plug-in I think is crashing it. Maybe there's an easy way to do this that I don't know about but if not, I'd certainly appreciate one!

Currently, there is no way for a CEP panel to know if "Scale to Frame Size" is enabled, which means that it's missing crucial information about clip transformations that is highly relevant if the panel needs to adjust position or scale or, indeed, know anything about the dimensions of the clip.

Per a discussion on the forums, it is unlikely this will be added before UXP. This is a request to be sure to add this capability to UXP, but also, that it should be considered a critical enough omission in the Extendscript/CEP architecture that it be added there as well.

See this discussion on the forums: https://community.adobe.com/t5/premiere-pro/how-to-find-out-if-a-clip-was-quot-scaled-to-frame-size-quot-in-a-cep-extension/td-p/11781911

Understandably, Adobe work on making integration between their various software packages within the Adobe family as smooth functioning as possible and it works fairly well to this end. However, Premiere can be a real nightmare to work with when your intention is to use 3rd party software for parts of your post production process, or when you want to collaborate and have other creatives working on different aspects of project, even if they themselves may use Adobe products.

There are many separate reasons why this is problematic, but my request is a little more general and overarching. Premiere has a collection of various functions some of which are designed to facilitate transfer of timelines and media from Premiere to someone or something else, and also some functions that aren't designed for that but can be co-opted for that. Examples include the AAF export tool for sending timelines out mostly to Avid products but also some others than can read AAFs too, or the media management tool that can be used to archive a project but as a side effect can theoretically be used as a means of sending projects or parts of projects out to other people/ software packages, render and replace can function similarly if you set it up so that conditions are as ideal as possible for it work, it also has XML and EDL export for sending timeline data around between packages without media, OMF too.

The issue is that these tools each have a LOT of problems and quirks, way more than you'd expect to the point where you need a book of workarounds to make them function as intended, also if you throw proxy files in to the mix then all bets are off because Adobe evidently didn't envisage that scenario when they designed those tools early on and didn't update them to accommodate the proxy feature after it was introduced.

All these tools, aside from their faults, are also, different, silo'd islands of functionality that all revolve around the same concept but which you have to know about separately to operate. They each seem designed for some theoretical, unlikely form of editing with little to no effects, one or as few as possible tracks, no proxies, no nesting, no multicamera, no merged clips etc, etc, etc. and the issues that affect one tool and require workarounds aren't the same for another. You have to invest a great deal of time trying to create this theoretical ideal circumstance to try and coax them in to doing what you need and even then it only really works about 50% of the time or less.

Aside from all the various glitches being fixed, I want there to be a single point of access for managing all the various scenarios you might encounter in the process of archiving a project or packaging elements of it up for use by other people/software -- what I call "interchange". Just as there is a single 'Export' window that you could use to create all possible forms of media that the Adobe Media Encoder engine can create, you'd use the interchange window to access all tools, features and settings related to this goal.

My idea is that in the file menu there'd be something called 'interchange/archive' and that this will open up a window that houses all those tools with an interface that makes the function of each very clear so that if you don't for example know what an AAF is, but do know you need to send your timeline to someone who uses Avid Media Composer, then this will be made clear to you. Additionally, this should hopefully integrate functions of existing tools that are often co-opted by Premiere users to approximate dedicated functions, in to something built for purpose. Thus, XML would be one of the options here in the interchange menu, but there'd be additional options such as transcoding the sequence media to a mezzanine codec packaged alongside the XML, not just exporting the timeline data, or consolidating the media in its current form so you can collect all the media associated just with the one sequence and send it off in its camera original form on a hard drive. Or consolidating in camera original codec, but also trimming with handles. These functions all theoretically exist in the media management tool, but for a start, they almost NEVER work but even if they did, it's not immediately obvious to someone who wants to send a timeline off to another package/person that they should use the archiving tool as a way of doing that, it's counterintuitive.

There's all kinds of ways I could suggest presenting this interface but really the important thing is that the options presented are all about different ways of delivering media and data about projects or parts of projects to different software and different people (who might even be using Adobe software but aren't on the same machine). With that end goal in mind, any single point of access to the different relevant settings would be an improvement. Same goes for archiving as well which has similar purposes in mind. Arguably Premiere has archiving sorted out in the form of the media management tool, but aside from the glitches, the tool is pretty rudimentary and could be folded in to this proposed single interchange tool which itself would hopefully have many levels of complexity to suit the level of control needed, much like exporting media does.

While development on this issue can help people to use tools other than Adobe tools, it's still in Adobe's interests since the 'Pro' part of Premiere Pro is always going to mean operating in circumstances that involve collaboration and that's going to mean different, facilities, different people, different storage, different machines let alone different software and the ability to manage that effectively drives a lot of the decision making on what editing software to use.

As a Loupedeck user, I want to add tracks to timeline without causing Premiere to crash.

Steps to reproduce:
Open Premiere Pro 14.6 or 14.7 on Win or Mac (bug is not reproduced with older versions)
Add Loupedeck as control surface
Add a track (audio, submix or video) in the timeline sequence

Expected result:
The track is added, Premiere Pro application is running

Actual result:
The track is not added, Premiere Pro application hangs up

Note:
The behavior is the same when adding tracks with mouse through the UI of Premiere (with LD added as control surface)
Adding tracks works fine when LD is removed as control surface.

I have been working with scripting repetitive tasks in Premiere. Many of our projects require making many iterations of the same idea. The scripts add graphics as needed. A given project might have 30+ sequences which we then need to go back through and apply transitions to these graphics. This seems like a no brainer. Loop through all the items on a specific track and apply the default transition. But it's not available. I can script opacity handles which works quite well, but in many cases, it would be easier to use the default transition as there's a visual indicator to the editor why something is happening to the video.

Scripting example:
app.project.sequences[index].videoTracks[index].clips[index].setDefaultTransition
app.project.sequences[index].audioTracks[index].clips[index].setDefaultTransition

Scripting is not an option in the feature request dropdown. Please pass this on to the people who handle user-sided scripting for Premiere. Thanks.

For the folks who like writing scripts for Premiere, please add the ability to lock a particular video track within a sequence. Personal Use situation: I have written a script that duplicates a template timeline, then adds graphics at specific places needed in every video in the project (generally 30 duplicated sequences per project). Video is later added meaning I need to go through and lock all the tracks that these script added items live on so they stay put when inserting the video segments. While I don't currently need it, if you do implement this, please do this for audio tracks as well.

script example...
app.project.sequences[index].audioTracks[index].setLocked(1)
app.project.sequences[index].videoTracks[index].setLocked(1)