Build better products with our product team
Still having the massive problem of having to select EDIT CAMERAS for every single edit in the timeline to turn on cameras in the group that were added after the first edit pass has been made. This has to be applicable to all the edits in the timeline, not just the one you have selected. It takes ages to go through a 90 minute concert cut turning on the late additition camera angles and really needs to be fixed please!! Am I missing something, is there a way of affecting every edit in the timeline or is oversight still in v25 after all this time . . . ?
Now on Premiere Pro, right click menu at timeline panel with under 1200px height display, it shows as compact size mode I think. and I usually wants full size mode.(it works with over 1200px height) 1080px height default(compact size mode) full size mode I wantPhotoshop has both mode and it's switchable option.
Missing Feature of green overlay within pro mode and manually focussing in Lightroom mobile app for android users. Does this feature exists? If not will you develop it?
Much like every other program ever on Windows, add a right-click menu to the system tray icon to allow Creative Cloud to be completely exited.
🔍 Problem Currently, new masks in Lightroom are generated based on the already edited image, which includes all global adjustments such as exposure, contrast, and color changes. This causes issues like: Lost dynamic range: Blown-out highlights or clipped shadows are impossible to isolate cleanly. Limited slider headroom: Mask adjustments are relative to the modified state—not the untouched RAW—so fine tuning the sky or subject becomes tricky after global edits. Unpredictable behavior in layered workflows: Subsequent global changes can affect earlier masks in unexpected ways. 💡 Proposed Solution Introduce an optional toggle in the mask settings: “Base this mask on original RAW image” (✔️ default off) What it does: Makes mask previews and initial slider neutral positions refer to the unedited RAW. Allows sliders (exposure, contrast, whites, etc.) to operate using the full dynamic range available in the RAW. Ensures consistent and predictable mask behavior, regardless of global edits made after mask creation. 🛠️️ Interface Design Within the Mask panel (accessible via the ⋯ menu in the mask thumbnail): ☐ Base mask on original RAW (pre-globals)ⓘ This mask will ignore current global edits and use the untouched RAW data as its baseline. Benefits Enables precise local adjustments on bright skies or deep shadows, even after bold global changes. Supports a more robust non-destructive workflow. Greatly reduces the need for workaround steps like layer duplications or complex adjustment orders. Aligns with Lightroom’s ethos of being both nondestructive and flexible.
Hey! I have started exloring Firefly and I need to say it is more amazing than I was expectting. 🙂 For sure I will be from now on a day-to-day user of those features. When checking the Fonts styliation I got this idea - Fireflay can create concept of material/style of a font, so ideally the next step could be to create layered effect in PSD based on the concept. User could donwload the PSD version of the font and when editing the PSD file he could add any shape/vector within a smart object and apply the effect to anything that he wants without any additional effort. This would be really cool and useful!
Dear Adobe team, you must see there is a growing demand for big file use in Photoshop. It is nice, that we have the possibility to save as PSB, but most other tools which i have to work with do not support PSB nor PSD. While Photoshop can read, open and edit BigTiff files, it is unable to save them. We are almost at the and of 2020, please make this a possibility. There are tools out there, that can do math operations Photoshop can not. Aswell as there is Photoshop, that can do things the other tools are unable to. Please connect this by allowing to save with the BigTiff file format. It would certainly expand the possibilities of what we can do with your software. http://bigtiff.org/
It would be super helpful if we could add a crop feature to the moodboard. Sometimes, I have to take a screenshot from the moodboard, crop it, and then paste it back, which can be a bit time-consuming.
LR displays the capture times for video from many cameras in UTC, rather than in local time of where the video was shot, which is obviously less useful to users. Though the original sin was a poorly written Quicktime/MP4 standard that is inconsistently obeyed by cameras, LR could handle the situation much better with a small amount of effort. The De Jure and De Facto Standards The Quicktime/MP4 standard specifies that the time in the Quicktime:CreateDate field is in UTC, not local time, and the standard doesn't provide for a time-zone field as EXIF does. However, prior to smart phones and GPS-connected devices, most cameras recorded local time in Quicktime:CreateDate, not UTC, and many cameras still do. But now, more cameras (but far from all) are following the standard. They fall into these categories: 1. Smart devices that connect and sync time with the Internet. These devices know both UTC and the local time zone. Apple devices obey the standard, writing UTC in Quicktime:CreateDate but also writing local time and a time zone in the non-standard field Quicktime:CreationDate (sic): [QuickTime] Creation Date : 2021:11:08 06:45:07-05:00 At least some Android devices (e.g. Samsung S23 Ultra and Nexus 5) obey the standard, but I don't know if some of them record the time zone somewhere (the Nexus 5 doesn't). 2. GPS-connected devices that sync time with the satellites. GPS doesn't provide them with a time zone, though some of them may allow the user to set a time zone manually. At least some DJI drones write UTC in Quicktime:CreateDate. 3. Cameras requiring the user to set date/time and time zone manually. Most (all?) Canons obey the standard, writing UTC in Quicktime:CreateDate, but they also write local time in EXIF:DateTimeOriginal, using the time zone set by the user. Older Nikons (e.g. the D850) write local time in Quicktime:CreateDate, while the Z series writes UTC in Quicktime:CreateDate and local time in a Makernotes field, using the time zone set by the user. Newer D cameras write UTC in Quicktime:CreateDate and local time with a time zone in XMP:CreateDate. Newer Sonys (e.g. the RX100M7) write UTC in Quicktime:CreateDate and local time with a time zone in XML:CreationDateValue, where XML is a Quicktime Meta tag. 4. Cameras requiring the user to set date/time manually but don't allow time zone to be set. Older cameras, including older Sonys are in this category. These cameras write local time in Quicktime:CreateDate.Lightroom's Current Rules For Handling Video Capture Time LR currently uses the following rules to display video capture time: 1. If the video was created by an Apple IOS device, LR displays Quicktime:CreationDate, the Apple-specific nonstandard field containing local time plus a time zone. Thus, LR displays local time for Apple devices. 2. If the video contains EXIF:DateTimeOriginal, LR uses that. This correctly handles Canons. At least one camera, the Fujifilm X-T4, writes the same time into both EXIF:DateTimeOriginal and Quicktime:CreateDate, but I don’t know if that's UTC or local time. 3. Otherwise, LR uses Quicktime:CreateDate. This causes UTC rather than local time to be displayed for many cameras, including many Nikons and DJI drones. For Sonys and other cameras that write local time to Quicktime:CreateDate, their capture times are displayed correctly. Making Lightroom Better With a small amount of effort, LR could do a much better job of handling this industry mess: 1. a. For Nikon cameras, use local time from Makernotes:DateTimeOriginal if it exists, otherwise XMP:CreateDate if it exists and has a time zone. The Z series has Makernotes:DateTimeOriginal, while at least some of the newer D series has XMP:CreateDate with a time zone. LR already uses this general approach for Apple devices, reading a non-standard metadata field. Since Adobe already has legal agreements with Nikon to read Makernotes for raw processing, perhaps they would apply to reading Makernotes:DateTimeOriginal (XMP:CreateDate is an industry standard field, not Nikon-specific). But if Adobe needs a modified legal agreement, a small number of overpriced lawyer hours is surely worth the benefit to users, putting Nikons on an equal footing with Canons. 1.b. For Sony cameras, use local time from XML:CreationDateValue if it exists, otherwise use Quicktime:CreateDate. LR already uses this general approach for Apple devices, reading a non-standard metadata field. 2. Provide an option in Import > File Handling: Shift Video Capture Time By Current Time Zone. This would only be applied to those videos that don't have an explicit rule for recognizing local time (e.g. Apple devices). The option could be saved in import presets. This option would work correctly when the video was taken in the same time zone as the computer running LR. It wouldn't work when the video was taken in a different time zone. But it's still much better than the current situation, in which the capture time is always wrong. 3. Provide a user-editable text configuration file that lists camera makes and models for which the video capture time should be automatically shifted to the current time zone. Adobe could optionally pre-populate it with known cameras that record UTC in Quicktime:CreateDate. As with the previous option, this would still get wrong the capture times of videos taken in a time zone different than the computer running LR, but it's much better than the current situation in which capture times are always wrong. 4. If GPS coordinates are available and no other rule applies, use open-source libraries to map the coordinates to the time-zone offset of the capture time or use the Google Maps API (which Adobe has already licensed for LR). Shift Quicktime:CreateDate by the offset. This would be useful for the large number of Android phones and drones that obey the Quicktime standard. Updated 8/28/23 for newer Sony cameras.
I often have to move multiple layers of clips or still images and keep their position relative to each other. In AE and in PS I can select multiple layers and drag their position around freely, but in Premiere Pro, I can only drag one layer at a time. Bouncing to AE is not a solution for me because everything I work with needs to be timed with multiple layers of audio at all times. Nesting is not a solution for me because I need to be able to adjust each layer independently as well. This is a feature I would use (and did use in FCP) dozens of times every day! I really need this. Any chance it's coming in a future update?
Instead of using the slip tool to retime a clip in the middle of a sequence, I like to double clip the clip and slide the in/out region to another part of the source footage - the problem is that when I double click to open the clip in the source monitor it doesn't match if the scaling is different; e.g. if the source footage is 4k in a 1080 timeline then the source monitor will show a punched in version that is neither how it looks in the timeline OR how it looks if you press F or go to the source through the project panel.It would be good to have an option to change the default behaviour to show the clip as it looks in the program monitor in the source monitor
Please modernize the Vegas plugin.It's essential for live unified strokes in 2D rigging workflows (RubberHose/Joysticks + Sliders, Duik Angela/etc). It's killing performance!
Ich würde mir eine Messenger-Lösung für die Creative Cloud wünschen, die wie Messengerdienste wie Slack oder Notion fungieren - mit dem Twist, dass man sie sowohl aus der CC App ansteuern kann als auch direkt als Panel bspw. in After Effects oder Photoshop etc. geöffnet haben kann und so in-App mit Team-Mitgliedern zu chatten, Calls zu führen, Termine und Projekte zu planen und milestones im Projekt abhaken zu können. Das würde die Teamarbeit in der CC noch mal erweitern und den All-in-One-Charakter von Adobe unterstreichen.
Description: Add a Sequence > Apply Default Transition to All Sequences command to apply the default transition (e.g., 6-frame Cross Dissolve) to all clip junctions across all sequences in a project in one click. Benefit: Saves up to 18.7 minutes per project for 50 clips, streamlining storytelling workflows.
I’ve been testing out Lightroom CC for a bit. I am considering a switch from Apple Photos. Is there a reason you cannot support Live Photo’s? Google Photos does on apple device, so I know its not a totally closed down format. Even if you could only view them on apple devices it would still be nice. Sometimes the Live Photo feature captures really special moments. I’m not sure I could give them up.
Just wondering (and maybe possible It exists and I don't know how to do this) - but why can you not do a render and replace using media encoder? I'm running into use cases where the CPU and GPU are not busy, and a render and replace running within Premier doesn't allow me to use premier, leaving tons of capacity in the system to do the render and replace as a background task. I would LOVE to see more ways to use ME to background process things like render and replace and any other suitable processes. hopefully other feel having this option would allow more work to get done when premier can remain usable while a background task runs. For example, here is how much CPU and resoures are beign used when I an doing a render and replace and a export to ProRES HQ at the same time of a 12 min clip. My system doesnt even feel this rendering... it would be really nice to have the option to render and replace with Media Encoder also (in addition to within premier) like the export project process works.
There are often times when I have a product box, and for the sake of composition, it would look much better if the box was facing left, but the photography I have points to the right. It would be easy to just flip the box horizontally and improve the composition 100x, excep there's a bunch of writing and graphics on it, and it takes time to change the perspective of every single graphic, piece of text, or other detail that would make it obvious the box was flipped. It would be very helpful if Photoshop had a smart flip that would flip the object, but detect the graphics/text (or even give an opportunity to select the elements that can't be reversed) and keep those elements facing the correct direction, but change the perspective/angles to match the newly flipped object.
Hola, me gustaría sugerir que integren una función nativa en Lightroom para poder filtrar fácilmente las fotos que he marcado como "me gusta", o que permita ver una lista de mis favoritos personales sin tener que usar banderas o estrellas. Sería útil tener un botón tipo "❤️" como en otras apps, para hacer este proceso más rápido y visual. ¡Gracias!
I have been using stamps very frequently and whenver i am layering them, i dont have individual control on levels on them or to be able to erase a projection without create a layer to erase, which globally erases from all the layers beneath it
Already have an account? Login
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.