Build better products with our product team
Is this overly convoluted. I have a sequence with a stereo audio track in the timeline. Left track is clip mic, right is ambient. I want to mix this. What I have done is. Open the Audio track mixer. Toggle the track mixer effect pannel open, navigate through two drop down menus to apply channel mix effect, double click to open the effect - another mixer! Adjust left channel, tab to right channel control, adjust faders. So streamlined. Seriously, is this the only way to do this? How about a pair of ganged faders in the main audio track mixer. Am I missing something?
It'd be very useful to know exactly where a mask ends once you start playing with its feather value. And since there's already a dotted line that shows up when using the feather pen tool, perhaps that same one can appear when modifying the regular feather value?This would be great to avoid "ghost elements" left by mistake when animating out of a mask, by failing to reach the absolute end of the feather gradient (I keep adding a black solid underneath and ramping up the preview exposure just to check if all elements are out of the mask's feather range!) Incidentally, here's a secondary request... How about an editable feather value for shape layers? Adding "Fast box blur" to achieve this seems like extra calculations that could be easily avoided...
After Effects currently allows running scripts at Startup and Shutdown,but there is no way to automatically run a script when saving a project.If this were possible, it would greatly expand automation possibilities, for example:Before saving: validate the project (e.g., detect missing footage, enforce naming conventions)After saving: write logs or export metadata for pipeline integration(This would work like a Git pre-commit hook, but for After Effects projects.)I fully understand that executing scripts at such a critical timing carriesimplementation risks and potential stability issues.However, for large studios and power users, this feature could be extremely usefulto maintain clean, pipeline-ready projects and reduce manual steps.Thanks!
When you export unmodified RAW images from MacOS Photos app and ingest them into lightroom, the GPS data isn't handled correctly. This seems to be due to an Apple bug/feature where the XMP contains incorrect GPSLongitudeRef (perhaps always set to E). It would be nice if LRC detected the mismatch, the fact that it is an Apple image and then just use the image GPS data, not the XMP GPS data. I have a bash script that uses exiftool to do this for me and it solves the problem but I doubt most people would be happy running a bash script.All the files here have this issue. They were talken in Colombia so GPSLongitudeRef is "W" https://www.dropbox.com/scl/fo/aa2qr4ls17ovyxfandg3y/AAdsvTLGd4_DTdejeuimp_0?rlkey=kmxhbc8uzom032dazxx5a91pn&e=2&st=9sfobv0b&dl=0Note I'll remove the above files within a month so I hope the Lightroom team collects the samples before then.
An important feature for all editing programs regardless of what they're editing (text, video, graphics) is for undo/redo to make it clear what is being undone/redone. Text editors do this by moving the cursor to where insert/delete is happening. NLEs like Avid, FCP7, and FCPX do it by moving the playhead to where the action happened - and bringing the playhead into view if the move hides it. As far as I can tell, Premiere has no way of showing you what's being undone/redone unless you already know where to look. Please enlighten me if I'm wrong. If I'm not I hope you add this oh so important feature!
It can especially be useful for certain compositing effects, specifically in an HDR project. For example, if you have something that is at the full 10,000 nit brightness, and you set that at 50% opacity against a black background, you should expect 5000 nits. Instead, you get 92 nits because it's working in the original PQ space for those transformations.Working in the PQ space can be useful for plenty of workflows, but for some specific needs, being able to do color calculations in linear space can be very helpful. There used to be an old "Composite in linear color" setting, but it doesn't seem to do anything anymore when I tried it in SDR, and it's completely greyed out in HDR.
I want to suggest the following feature for Adobe Firefly. As we know, every JPEG file can contain a vector path inside it. This path can be loaded as a selection in Fairlight. This will help people make precise selections.
Dear Adobe would it be possible for ae to remember recent open/save dialog settings per project? our usual workflow involves switching between different projects, each in its folder and when you try to render, save project or open new project ae opens the file dialog with the last open directory which causes a lot of chaos when people are in a hurry and renders get saved to different project render folders, project files get saved to different folders than intended because of this.If each project had some way to remember its recent file dialog paths it would help a lot.
Je ne comprends pas qu'un effet tel COLOR METAMORPHOSIS ait été retiré de la liste. Il était tellement simple d'utilisation. Je souhaite son retour et vous ?
What the title says. Sometimes I have shape layers in a precomp and I want them to be nice and sharp, and also don't want it to completely destroy the layout work I've done when working in 3d. This is just an example - I'm not looking for a workaround for this specific point.
The camera tracker is a little long in the tooth, and there are three big improvements I would suggest: 1) the ability to use an alpha/mask so it doesn't consider parts of the image when tracking (perhaps this exists, I've just yet to find out how to do it);2) the ability to, after a track, automatically reject/delete points based on their error (i.e. all points above a tracking error of 1 (or whatever is chosen) are deleted across the entire track;3) A button so that the camera only re-solves on command rather than every time tracking points are deleted, so points can be deleted across the entire track without having to wait for the solve every time.
wir arbeiten in unserem Archiv mit über 250.000 Fotos, im Bereich der darstellenden Kunst. In unserem Katalog sind oft Fotoserien (+20 Bilder) mit ähnlichem/gleichen Bildausschnitt, und teils 15-20 abgebildeten Personen pro Bild. Lightroom Classic bietet leider keine Möglichkeit, die z.B. einmal für alle 20 Personen gesetzten Auswahlrahmen (Gesichtsregionen) auf alle anderen Bilder (eine beliebige Bildauswahl) mit zu übertragen. Obwohl Personen-Keywords synchronisiert oder kopiert werden können. Es würde sehr viel Zeitersparnis bedeuten, diese Facetagging-Rahmen kopieren zu können, da bei gewissen Fotosets oftmals bishin zu mehreren Stunden die selbe Information immer wieder neu eingetragen werden muss. (gerade weil bei körnigen SW-Bildern die automatische Gesichtserkennung weitestgehend scheitert)
If Premiere Pro had an Auto Sequence feature like Avid Media Composer, it would save me hours and hours of syncing video and audio. What I need is a function that lays all the video from each individual camera on a timeline by the timecode and have that sequence match the timecode of the clips so I can "Auto Sequence" each camera's clip by the timecode. When trying to perform a similar function in Premiere (multicam multiple clips by timecode), it trys to put each individual clip on a seperate layer, and that costs me even more time to move the clips on one layer. This should be a basic function and I'm surprised it doesn't exist. I am working with 10+ cameras that are multicamed with over 12 layers of audio, so I need a way of quickly placing the clips on the timeline by timecode to sync them all which should be a simple thing to do. Something that takes me just a few minutes in Media Composer winds up taking me a whole day in Premiere Pro.
The "Line" tool. You can adjust the line "weight".You can use options to add an arrow at the start or end of the line (or both).You can adjust the length and the width of the arrow.It would be nice to have a "lock ratio" option for the arrow, so that once you adjust the length and width of the arrow, if you engage the "lock ratio" for the arrow, then if you resize the line weight, the arrow dimensions would also change. Like if your line weight was "10", and you set up the arrow to be 5x5, and then changed the line weight to "20", the arrow would become 10x10, if scale lock was engaged. Thank you for consideration.
I really struggle to see keyframes under this grey highlight. All we really need is the blue line, not the grey outline that's nearly the same colour as the keyframes underneath
"Hello, I have a request for Lightroom Mobile. I lack precision when editing the tone curve due to the small screen. Could you consider adding the option to manually enter numerical values for the curve points? It would greatly improve the workflow and provide more control, similar to the desktop version. Thank you for your hard work.
PLEASE add a feature that creates a stringout with gaps based on source timecode (similar to AutoSequence feature in Avid). So many times with lower budget work, I've been given 100+ shots I had to try to sync when timecode doesn't match, the cameras have no scratch audio (they just record 8 dead channels for no reason), and there is no clapper. If I'm able to sync one thing, I'd be able to create a sync map, which can save me tons of time.
Request for change. In the crete masks/Landscape, add at least one inverse mask, in this case, Invert Sky. This to allow a quick special mask where a user can apply edits such as the curve, Clarity, and several possible contrast edits to everything except the sky.
Currently in each export template there is a setting, that existing files should be overwritten without warning.This works fine. However, if multiple export templates are selected, this option is ignored and instead copies with a suffix are saved. Please allow for an option to also allow overwriting existing files in Multi-Batch-Export.
Request to allow us to import ogg files into Premiere Pro. I just finished organizing tons of ogg files in different folders for a project not knowing premiere doesn't support it. The only third party "plugin" I could find was an unfinshed beta made over 10 years ago. So now I'm going through the nightmare of converting them all to wav or mp3 and reorganize all the converted files.
Request for change. In the Landscape Mask selections, in addition to the Sky, add selections for Sky Blue and Sky Not Blue. First one would select AI Sky, but would be intersected to the color Blue (as such the mask would not include clouds), and the other would invert the intersect to the color Blue (as such the mask would only include clouds, i.e., not blue)
Stitching panos is especially problematic when there's a clear blue or otherwise featureless sky. Often, in fact virtually always, LrC chops off corners of the sky that were in the original captures. It's also nearly impossible to shoot a 3x3 with the horizon perfectly centered, which is normally desirable to maintain verticals. LrC will essentially chop off the entire top of the sky and screw up the perspective of the remainder. The only workaround is to center the captures slightly below the horizon so the top row has some ground included at the bottom. Oh, and a large expanse of water in the lower portion of the pano can also be problematic. Before LrC added the pano feature, I had been using PanoramaStudio Pro (I'm currently using v4.xx), which has an option in its initial Align dialog to "place non-aligned images using metadata." This evidently reads gimbal position metadata from the files, and I don't believe I've ever had it fail. But using that app involves a much slower, more complex workflow - export from Lr, set alignment, view initial result and tweak adjustments if necessary, render the full-res pano, export a perspective projection from it (usually), then manually import that image to LrC as a TIFF for final processing. I'd really love it if LrC had the ability to read that gimbal metadata in the same fashion. Here's one example of what LrC often generates. That top right corner wasn't missing, LrC just mangled it. Like I said, it happens virtually 100% of the time when the sky is relatively featureless. The second image is the same 9 exposures stitched with PS4Pro using the metadata feature. And you might also notice that it automatically corrected the horizon position, which was actually above-center in the original captures, so I don't have to use a transform to fix the verticals. PS4Pro will always render multiple row panos using a spherical projection, but then allows numerous other projections to be generated and exported from it. Anyway, I'd love it if LrC had the ability to read that gimbal metadata and stitch all my drone panos flawlessly, not just the ones with cloudy skies and no large expanses of water.
Already have an account? Login
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.