AdminFrancis Crossman
(Product Manager, Adobe DVA)
My feedback
-
395 votes
An error occurred while saving the comment -
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.
-
592 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. -
14 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.
-
43 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.
-
6 votes
An error occurred while saving the comment Sorry to hear you are having problems with the mask tracker. Can you please provide more information about the footage you are trying to track? It's useful to know the resolution and framerate, but most importantly - what's going on in the scene. Mask tracking technology does not do well with fast-moving objects (lots of motion blur), when the object goes off screen, or when the object is occluded (some other object passes in front). Mask tracking can also be thrown off by wildly changing lighting. Do any of these situations describe the footage you are trying to track? Remember that at its core, mask tracking is trying to lock onto a pattern of pixels (usually several patterns) and find that same exact pattern from frame to frame. If the pattern is hard to find (motion blur, lighting) or disappears altogether (occlusion, goes off screen) then the tracker will likely fail.
-
5 votes
An error occurred while saving the comment We have Identified a problem with the Black and also White sliders in Lumetri and we are working on a fix that we hope to make available soon.
-
6 votes
An error occurred while saving the comment Josh, sorry to hear about the frustrating problems you are running into. I am on the color team that maintains Lumetri and I'd like to help you get to the bottom of this, but I will need more info. Can you tell me if there are any error messages and what they say? Are you failing with GPU acceleration, software rendering, both? Are you sending the job to AME or exporting directly from PPro - any difference there? Did you render the timeline first and are you using previews during export? Does it successfully render the timeline or does that fail too? Have you tried using codecs such as Prores / DNxHD / Cineform rather than H264/AVC codecs - any difference? What Nvidia driver are you running? GH5 . . . I assume you are cutting in 4K, any difference on regular HD projects? I'm here to help you are still in a jam.
-
3 votes
An error occurred while saving the comment Just summarizing the specific problem here - you have a dual monitor setup with one above the other and menus in the Lumetri panel expand upwards and can get lost. This is a known issue that we are looking into. Some workarounds are to configure your monitor arrangement a bit staggered so that the menu doesn't have any desktop real estate directly above it. The other workaround is to configure your Mac system preferences - Mission Control "displays have separate spaces". I hope this helps until we resolve this issue.
-
9 votes
An error occurred while saving the comment We are looking into this issue and taking it very seriously. If you can supply us with a detailed description of your system and PPro version it will be very helpful in narrowing down the problem.
-
3 votes
An error occurred while saving the comment Can you please supply some details about your system and Premiere version?
-
39 votes
An error occurred while saving the comment Adding your own LUTs to the Premiere Pro application package is not recommended or supported and is the cause of your current problems. Yes, your assumption is correct, the default LUTs that come installed by default with Premiere Pro are indeed indexed by item number in the folder rather than by name. It's done this way because users are not meant to alter the files in this folder.
If you are using several custom LUTs and want them to show up in the Lumetri dropdown menus we have a solution which is newly available in a recent update (2018 - version 12.1). You can install your LUTs into a specific folder in your OS user library and Lumetri will scan them in.
Here are the instructions to install and use custom LUTs:
Like to read: https://helpx.adobe.com/premiere-pro/using/whats-new.html
Like to watch: https://www.youtube.com/watch?v=dnJQj09GDfMLUTs that are stored in these folders will get embedded into the project file when you use them. So you can share the project with a colleague and all the LUTs will be present and be functioning for them even if they don't have the specific LUTs installed. It will not install these LUTs onto the other person's system for them to use on additional clips, however. It is therefore recommended that you send them the LUT with instructions on how to install it onto their system. Hope this helps.
-
8 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. 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 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 is newly available in the most recent update (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 the instructions to install and use custom LUTs:
Like to read: https://helpx.adobe.com/premiere-pro/using/whats-new.html
Like to watch: https://www.youtube.com/watch?v=dnJQj09GDfM
LUTs that are stored in these folders will get embedded into the project file when you use them. So you can share the project with a colleague and all the LUTs will be present and be functioning for them even if they don't have the specific LUTs installed. It will not install these LUTs onto the other person's system for them to use on additional clips, however. It is therefore recommended that you send them the LUT with instructions on how to install it onto their system. Hope this helps. -
4 votes
An error occurred while saving the comment I am looking into this and so far cannot reproduce this bug. Can you please add some more detail? OS, CPU, GPU, Media type, Media Encoder version number, really the more detail the better. Are you using any LUTs? If so, where are they stored? When you say "will not export sequences", what precisely do you mean? Is there an error message, a crash, it just doesn't look like what you expected, something else? We are here to help, we just need some more information.
-
21 votes
An error occurred while saving the comment I'm looking into this problem but so far have not been able to reproduce the results. Can you please provide some more details about your system (Exact PPro version, CPU, GPU, displays, which scopes configuration, CUDA / OpenCL / Software rendering). The more detail the better - thanks.
This is a really good and simple idea. Also, I can answer the question of why cyan is in the middle. Hue is measured in degrees. We start with Red at 0° then go on around the circle (Red, Yellow, Green, Cyan, Blue, Magenta, Red) we end with Red again at 360°. Cyan is in the middle at 180°. That's the only reason it's in the center on the curves. But the problem you mention of adjusting skin tone most often is exactly why we put the horizontal scroll bar in there – so you can recenter the scale to wherever you'd like. Skin-tone is actually more orange, not red but I think we could simply set the default horizontal scroll to a value that places red in the center.