Premiere Pro
ANNOUNCEMENT - This forum is moving
151 results found
-
DO NOT retire Legacy Title!
DO NOT retire Legacy Title! 90% of my titles are simple, one-off titles and I don't require templates or special FX. Just let it be and give us options like Legacy Title to create as we see fit! Please don't change for the sake of change.
3 votes -
Add the Premiere version number to the title bar, since I need to report bugs so often.
I'm posting frequently on forums about issues I'm having and it would save a lot of time to just keep the version number displayed in the Windows Title bar atop the screen, rather than have to to to Help - About Premiere Pro
2 votes -
M1 Premiere pro incompatible with Waves Clarity Vx Pro plug-in
Not sure how many of you are using Clarity Vx from Waves. On Apple M1 processor, it only produces a loud buzzing on the M1 Native version of Premiere Pro. Works fine on Rosetta. Workflow for now is loading Intel (Rosetta) version to do audio processing or offloading audio to another audio app. Anyone else have the problem?
4 votes -
accept .DV footage so I can edit my archival footage from Mini DV tapes.
Please add support for .DV format. its a must for anyone editing archival footage or still shooting on these cameras. likely switching to FCP because of this.
1 voteDeclined ·
AdminFergus Hammond
(Product Manager, Video & Audio Cloud Workflows, Adobe DVA)
responded
Hi Matthew,
We do support DV footage in the AVI, QuickTime and MXF containers. However, we have not supported .DV files since at least version 12 of Premiere Pro and we do not plan on doing so in the future.
Regards,
Fergus
-
Loudness Radar for Mac M1
I switch from windows to apple device with M1 chip and for my surprise Loudness radar is no longuer available. There is Loudnes meter, but not really useful compared with the radar. I would like to have this tool added for people using M apple chips as is an essential tool for high end sound production process in my case. Many thanks
1 voteThe Loudness Radar will not be available in the Apple Silicon version of Premiere Pro.
-
Be able to change Source Filenames of clips within the Project Window
I would like to be able to change Source Filenames of the clips within the Project Window without leaving Premiere (individually, batches, sequences).
At present I can delete the source file of a clip from there but I need to go to Windows Explorer to rename the file AND then "replace footage" to relink it.
Takes too long/cumbersome.
1 voteDeclined ·AdminFergus Hammond
(Product Manager, Video & Audio Cloud Workflows, Adobe DVA)
responded
Hi Ronald,
Our approach is to never modify the original footage on disk. That includes not changing the original file name. We do not plan on changing that because we believe what we do today is the safest way to protect your footage.
Regards,
Fergus
-
Bring back Loudness Radar for Mac M1
Please bring back the loudness radar for Mac M1
9 votes -
Adobe Premiere must embrace USB Capture devices
FireWire is dead. New apple computers and MacOS wont support/recognize firewire video capture devices, like Canopus advc100.
Bought a generic HDMI capture device that plugs in to a USB-c Port.
Works perfectly with QuickTime capture, unfortunately QuickTime has very limited options on how to capture, in particular no frame rate option.
Adobe should develop enabling capture from USB capture devices; they are an easy and affordable way to capture footage from any analog devices Betamax, VHS, Video8, Hi8, DV, HDV, anything with RCA or SCART outputs via another cheap analog to HDMI conversor. They are also used by YouTubers and…1 vote -
Feature request: option to revert to legacy screens for new project and export.
The new interface for creating projects and exporting seems dumbed down and requires more clicks to achieve the same goal as on previous versions.
I feel this is targeted towards new editors at the expense of experienced editors.
3 votesIt would be helpful to know exactly what you don't like about the new workflow so we can improve and move forward. We will not be going back to the old designs. One tip I'd like to share is that you are not required to import media when you create a project. You can just enter a name and location and hit create. This will create an empty project like before and then you can import in all the ways you are used to (drag from finder, media browser, File>import). This is exactly the same number of clicks as the old method.
-
Put the workspace tabs back where they were by default.
the new system of having them hidden in that dropdown panel by default is inconvenient. any system where you add clicks to get to something that used to be a one click option is objectively worse. and the new method of showing the tabs is much less clear/readable because it's in all caps with no dividers between each tab name AND they can only show a few at a time. I dont understand how anyone thought making it less convenient to switch between workspaces was a good idea.
2 votesYou can enable this option in the workspace dropdown "show workspace tabs". This puts the workspaces across the top again. This provides a way to change workspaces with one click like before. We are sympathetic to changes in muscle memory, but we won't be going back to the old UI.
-
11,405 votesDeclined ·
AdminPatrick Palmer
(Director of Product Management, Pro Video and Motion Design, Adobe DVA)
responded
Hello everyone,
after looking into both technical viability and current market needs, it’s unfortunately become obvious that we’re not going to be able to act on this request in the near future.
I wanted thank everyone for the considerate and passionate discussion on this thread. This has been a great example of a meaningful conversation over a controversial subject that I don’t take for granted.
Cheers,
Patrick -
Productions - See and Open Contents of Projects in the Productions Window
I find the current Productions workflow to be very cumbersome having to juggle multiple project windows, especially when using a single monitor. Projects within a Production should show their contents with a twirl down and allow you to use them without having to open a project window.
1 vote[my team created Productions]
We understand that things get crowded on a single screen.
The Project panel has special powers, unavailable in the Productions panel. Since those special powers are already available to users, the engineering effort to turn the Productions panel into a superset of the Project panel’s feature set, will be better spent improving Productions workflows.
Potentially helpful: Soon after introducing Productions, we also added to a “Close all other Projects” item to the Project panel context menu.
-
Update API to allow 3rd party software to assign shortcuts to transition presets
In case you haven't heard yet, the Excalibur plug-in (https://knightsoftheeditingtable.com/) is revolutionizing editing in Pr! While it can do many things, over a dozen of which are in response to FR users have been requesting for years, one of the things it cannot do is assign keyboard shortcuts to transition presets, due to a limitation in Pr's API.
It would be wonderful if the API could be updated to allow this, given that it already allows 3rd party plug-ins such as Excalibur to assign shortcuts to any effect, effect preset or transition.
Thank you!
10 votesWe know (and love) the Knights, thanks!
For consistency, PPro maintains control of its keyboard shortcuts, letting panels override them only when active; this is unlikely to change.
-
Bring back support for OpenCL until Apple stops selling OpenCL capable computers.
Metal performance is vastly INFERIOR to OpenCL. Please don't tell us the dropping support for OpenCL is an advantage. It's not.
Here's the data from the Premiere 14.9 Console of playback of the same sequence with Metal vs. OpenCL:
Metal:
<123145370017792> <Dump Playback Queue> <0> =============================== Queue Dump (2936) ===============================
<123145370017792> <UpdatePlaybackStatusInfo> <0> Frames dropped during playback: 1045 / 2733, Preroll(ms): 2007.75
<123145370017792> <UpdatePlaybackStatusInfo> <0> Avg Prefetch(ms): 3430.04, Avg Render(ms): 60.636, Avg Display FPS: 14.8163Open CL:
<123145370017792> <Dump Playback Queue> <0> =============================== Queue Dump (1776) ===============================
<123145370017792> <UpdatePlaybackStatusInfo> <0> Frames dropped during playback: 88 / 1574, Preroll(ms): 242.077
<123145370017792>…1 voteWe have no plans to go back.
-
1 vote
Happily, Newtek already provides the ability to stream PPro’s output, via their Transmit plugin.
https://www.newtek.com/software/adobe-creative-cloud/
While capturing from such streams isn’t in our near-term plans, PPro’s APIs make it possible for third parties to write Record plugins to capture streamed output, into media files.
-
1 vote
Apple’s guidelines for application behavior require that we request access to all three locations.
-
Enable "Import Settings" for Productions
This one should be easy, enable the "Import Settings" for Productions. it is already there, just don't grey it out so we have the option to use it.
In a newsroom or university environment we need to be able to set global settings for import codecs and locations. It is easy for us to use UNC paths to ensure each computer on our network can properly find the shared storage location regardless of the drive letter.
If this is too complex for some reason, create an "ingest" function in Productions which allows for transcoding in the background and moving files…
1 voteWe’re glad you’re using Productions!
We understand why that sounds like a good idea; here’s why we don’t do that:
Ingest settings are disabled in the Production Settings dialog because they are designed to apply to a single computer at a time. To use Ingest Settings first close your Production and create a standalone project that is saved outside of the Production folder. Set your desired Ingest Settings and import your media. After all ingest operations have finished, save your project and close it. Open your Production and use the Add Project command to bring the project file into your Production. From there you can use the ingested clips normally.
-
Render via spare processing capacity of ipad and/or iphone
Create an App that allows you touse the spare capacity of your iphone or ipad whilst working in Premiere and After Effects
1 voteIt’s a lovely idea, but the work necessary to get media onto another platform, process it, and get it back, would obviate any performance “gains” made by enabling rendering on other devices.
We are pursuing other ways to distribute renders…
-
For low income, general public, a return to one off purchases of your software, may bring back like minded people. Not everyone can afford l
As the strain on finances continues due to COVID 19 t, people on low income - I am 62, cannot afford a lifetime subscription and in the past, have saved up hard for a private / residential software, that should last them years. Your upgrade service was absolutely brilliant and made purchasing more affordable. I appreciated this going to fall on death ears, but have heart, not all of us can afford lifetime deductions from your bank account, with shrinking monthly finances at present. Besides, you may win back many people in the same boat as me
1 vote -
multicamera
Please redesign the multicamera interface to work the way it did in Premiere CS 5.5. In 5.5, if you paused the video, and then pressed a camera number, a cut would be made in the timeline and the clip from that point forward would be the new camera. In the current version of Premiere, if you pause the video and press a camera number, it merely changes the entire clip to the new camera. One has to manually make a cut first, and then switch the camera. It's a much more cumbersome way of working.
1 voteWe’re glad you’ve been using PPro so long!
That behavior was changed because of multiple requests, and is unlikely to change back.
As you rightly describe, if you paused and pressed a camera number, you’d get an edit. If you selected the wrong camera (a frequent occurrence, based on the feedback we received), you’d need to undo the edit.
The “new” (vintage 2013) behavior provides more “audition several cameras” flexibility, before the user intentionally makes the edit.
[I wonder whether creative re-designation of keyboard shortcuts, might not let you put together behavior closer to what you’re looking for…]
- Don't see your idea?