AdminFrancis Crossman
(Sr. Product Manager, Adobe DVA)
My feedback
-
1 vote
An error occurred while saving the comment -
1 vote
An error occurred while saving the comment Just confirming that you did set the spell check language to UK English? And just for your information we are using the OS dictionary supplied by MacOS or Windows. You should find that Premiere Pro will correct words in the same way as the rest of the system.
-
1 vote
An error occurred while saving the comment You can do this in Audition. https://helpx.adobe.com/audition/using/text-to-speeech.html
FWIW I always just record my own scratch VO. Since it's just a scratch track you can just use the voice memo app on your phone or whatever is convenient.
But this is a good request for additional functionality in PPro.
-
2 votes
An error occurred while saving the comment Sorry for the frustration. 10min to wait for a file to import is awful. We have actually fixed this issue in version 22.1.2 (the December '21 release). We'll now import embedded captions asynchronously. This means that we'll import the file immediately and you can even start editing but the caption stream will get decoded in the background. You will still have to wait for the captions to get decoded but this is way better than the import process being blocked.
The preference for importing captions does indeed speed up import time of media with closed captions. I'm surprised it's not working for you.
There is one other control you should be aware of:
- Option to restore captions onto the timeline from a piece of media (Right-click on clip in timeline > Restore Captions from Source Clip)I hope this helps
-
2 votes
An error occurred while saving the comment We do this by default. When you drag the .srt onto the timeline you should see the "New caption track" dialog. Make sure you have the source timecode option selected (the default). If it's still not working as you expect, double check that the sequence has the expected timecode. Right-click on the sequence tab and choose "start time". Premiere Pro sequences start at 00:00:00:00 by default. Possibly you need to change that to match the start time of the media. Another thing to check is the timing that is actually in the .srt. Open the file in a regular text editor. Hopefully that helps.
-
1 vote
An error occurred while saving the comment You will need to import the saved style into each project presently. But your suggestion of having those styles available across all your projects is very valid. In the mean time this is how you can get it done.
1. Save the track style in the essential graphics panel
2. The style gets saved in your Project Panel
3. Right click on the style in the project panel and choose "Export Text Style"
4. Import that file into subsequent projects before creating captions
5. Choose the stlye in the Create Captions dialog -
1 vote
Thanks Garrick! We’re tracking this as DVAPR-4235518, and will keep you informed of our progress.
An error occurred while saving the comment We have narrowed down this bug and unfortunately it shipped in the 22.1.1 release that just went live a few days ago on December 13th. This affects other plugin developers too (Red Giant, Boris, etc.) Here is are some more details. https://community.adobe.com/t5/premiere-pro-discussions/plugin-issue-with-premiere-pro-v22-1-1/m-p/12599673/thread-id/384685
We're actively working on a fix to be rolled out ASAP.
-
3 votes
An error occurred while saving the comment Eric – I recommend clearing your media cache and checking the system compatibility report for GPU driver issues.
System compatibility report:
https://helpx.adobe.com/premiere-pro/using/system-compatibility-report.htmlOther Troubleshooting steps:
https://helpx.adobe.com/premiere-pro/kb/troubleshoot_playback_performance.html
-
1 vote
An error occurred while saving the comment Yes, this is certainly in the plan. Thanks for the feedback. You can follow the discussion on import happening over on the beta forum https://community.adobe.com/t5/premiere-pro-beta/discuss-new-import-workflow/td-p/12130677
-
1 vote
An error occurred while saving the comment Thanks for the suggestions. We are certainly looking into 1 and 2. I'm not sure I understand what you want with 3. Are you talking about syncing clips together - like in multi-cam shoots? You can follow the discussion for import mode happening over on the beta forum - https://community.adobe.com/t5/premiere-pro-beta/discuss-new-import-workflow/td-p/12130677
-
9 votesAdminFrancis Crossman
(Sr. Product Manager, Adobe DVA)
supported this idea
·
-
2 votes
An error occurred while saving the comment This could be a related to display color management, the QuickTime gamma shift issue, or both. Here is a link that explains the problem and how to solve it.
-
1 vote
An error occurred while saving the comment You can accomplish this in After Effects using the puppet warp tool. Right-click on the clip in question in your timeline and select "Replace with After Effects composition". This will create a dynamic link and open the clip is AE. Any change you make in AE will automatically be updated in PPRo. Hope this helps
-
1 vote
An error occurred while saving the comment This is a very interesting idea, but for the proposed use case adjustment layers would do the trick.
-
4 votes
An error occurred while saving the comment A little info on Display Color Management might help troubleshoot this problem. DCM uses the ICC profile of the display to transform your colors to display accurately on your particular display. It requires GPU acceleration to work. Switching to the software renderer will disable DCM. I'd recommend checking your display color profile settings to make sure you don't have something odd chosen. You should most likely see a profile that is named after the model of your display. Here is some more info on the topic
- https://helpx.adobe.com/premiere-pro/kb/color-management.html
- https://premierepro.net/color-management-premiere-pro/It is also worth mentioning that DCM has no effect on the actual exported file, it only affects the colors that get displayed on your monitor.
-
657 votes
Thanks for the suggestion(s).
An error occurred while saving the comment Thank you for the request, Joel. This is certainly a great idea that we are interested in implementing. Here are a couple of workflow suggestions in the meantime.
- Enable "Selection follows playhead" in the sequence menu. The lumetri color panel turns this on by default, but you are free to turn it on yourself at any point.
- Selecting multiple clips will allow you to add effects, including effects presets, to all at once.
- Label colors are a good way to keep things organized (A-Cam = Blue, B-Cam = Green, B-Roll = Purple, etc.). You can select all clips with the same label and apply an effect. Right-click on a clip in the timeline > Label > Select Label group.
- Master clip effects are a good way to apply an effect to every instance of the media throughout your project. -
18 votes
An error occurred while saving the comment There are a couple of problems we have in this area that we are working to resolve.
1) In the Effects Tab in the Export Settings, the Lumetri Look/LUT effect only shows Looks/LUTs that are in the Creative section of Lumetri. It does not show LUTs that are in the Technical section or LUTs that you install into the custom LUT folders.
2) Choosing Select allows you to navigate to a LUT anywhere on disk, but once you select it, the dropdown menu shows Applied: None. This is a bug. The LUT actually has been applied, however. Ignore what the menu says and see that the LUT has indeed been applied.You can save an encoding preset with the V-Log-to-Rec709 LUT applied and use it for a dailies process. Cube LUT files are supported, but you may have downloaded ones that are intended for Davinci Resolve which are incompatible with Adobe products. Look for ones intended for Premiere / Speedgrade.
We are aware of these limitations and are working to resolve them. We totally understand the frustration some user have around this area.
-
46 votes
An error occurred while saving the comment Totally agree! We are looking to modernize our LUT workflow. Others, please post your LUT workflow ideas - we are listening.
-
5 votes
An error occurred while saving the comment The problems you are experiencing are caused by tampering with the LUTs within the application package - please do not do this - it's not a recommended or supported workflow. I know there are a lot of very official looking tutorials out there that tell you to do this, but that information is wrong. The safest way to proceed at this point is to completely reinstall PPro and AME so the LUT directories are restored to their default state as intended by our engineers. You should then install your custom LUTs according to the directions below. You will then need to remove all LUTs from your project and reapply them. I know this is inconvenient, but it really is the safest way to make certain your project will render as intended.
If you are using several custom LUTs and want them to show up in the Lumetri dropdown menus we have a solution which was introduced earlier this year (2018 - version 12.1). You can install your LUTs into a specific folder in your user library and Lumetri will scan them in. Here are steps to set that up.
Mac
From the finder, use the Go menu to navigate to this directory: ~/Library/Application Support/Adobe/Common/
- Create a folder named LUTs
- Create two more folders inside the LUTs folder: Technical and Creative
- Copy technical conversion LUTs (often called camera LUTs) such as LOG to Rec709 into the Technical folder
- Copy creative LUTs such as day-for-night, B&W, or anything that is just a stylistic look into the Creative folder
- Restart PPro/AME
- Technical LUTs show up in the Input LUT dropdown inside the Basic section in Lumetri
- Creative LUTs show up in the Look dropdown inside the Creative section in Lumetri
Windows equivalent directories:
~\AppData\Roaming\Adobe\Common\LUTs\Technical
~\AppData\Roaming\Adobe\Common\LUTs\Creative
This is a convenient and easy way to add as many LUTs as you like to the Lumetri dropdown menus and this will persist through updates - unless of course you delete or change this directory.
-
15 votes
An error occurred while saving the comment This sounds like a huge headache, and I'm very sorry for the trouble you are experiencing. It sounds like there are 3 individual problems, lets tackle them 1 by 1.
1) Color correction is hugely different from 2018 to 2019
I assume that the actual slider values have not changed - correct? Are you using any LUTs? Have you ever installed custom LUTs by opening up the application package/program files and installing them alongside the default LUTs that ship with PPro? If yes, this is what is causing your problem and I can work with you to resolve it.2) Curves points are un-editable
In order to diagnose this one, I will need to know exactly which curves you are talking about. Lumetri RGB curve? Hue vs Sat donut? RGB curves standalone effect? The new curves in 13.0? Please describe the precise behavior you are experiencing.3) Low-level exception
This is the most elusive of the bunch. A low-level exception simply means something went wrong, but we don't know what. If you are able to provide precisely repeatable steps that lead to a low-level exception warning then we can begin to try to diagnose what is going wrong. Think about this from the point of view of starting a brand new fresh project - exactly what do you need to do to get the warning - does it happen with all media, specific media?Hopefully, we can help to resolve these issues.
Are you running Premiere Pro version 22.3? How long is your timeline? If it is longer than 34min you might be running into this issue. https://community.adobe.com/t5/premiere-pro-discussions/fixed-issue-premiere-pro-stops-playback-at-around-34-46-fixed-in-22-3-1/td-p/12896356
It is fixed by updating to 22.3.1
Update to