Skip to main content

Filter by idea status

10000+ Ideas

Philéas
PhiléasKnown Participant

Better "Timeline in Source Panel" workflow - "Toggle Source/Record" from Avid.Open for Voting

Hello ! Context :I've been a Premiere editor for a long time. But my recent jobs have forced me to work on Avid Media Composer. This has required me to completely rethink the way I edit: Premiere being more suited to drag-and-drop workflows and Avid more keyboard In/Out workflows. On Avid, you tend to create multiple sequences for your selects. Then, use those sequences in your Source Monitor, and use the "Toggle Source/Record" function to show the source timeline, and integrate clips on your sequence. Now that I'm back to using Premiere as my main editing program, I wanted to bring this method to the way I edit. But doing it on Premiere is kind of frustrating on specific points. I think this kind of workflow has a lot of benefits compared to pancaked timelines: you can edit more precisely, as you can anticipate the exact start and end frames you're going to insert. You are also working more efficiently because of the keyboard centric approach and using two monitors at the same time. Here are the problems when we try to apply this way of working on Premiere, and how we could make it better : Bringing a nested sequence rather than UN-nested clipsEvery time you bring a clip in your final timeline, Premiere defaults to bring a nested sequence rather than the clip's themselves.So if you want your original clips flattened, you have to use, on every clip you bring from the source sequence, the "Multicam" option (see attached video). But then, the source audio/video are not linked anymore, which means that you need to relink them one by one.It would be great to have an option to directly bring the clips from the source sequence to the working sequence using the selected patching. Rather than a nested sequence, which is more complicated to work with.Update : As @WellToldFilmCo commented, there is in fact a button to allow this. Thanks for the sharing, I'm now using it every day ! Complicated shortcutsIf you want to use this workflow, you have to use multiple shortcuts on Premiere :"Panels : Open Sequence" to open the current selected sequence in the source monitor on a timeline"Application : Source Monitor" when you want to select the source sequence as your active working panel"Application : Program Monitor" when you want to work on your final sequence."Application : Sequences" when you want to switch from your opened monitor sequence and your working sequence.Update : You also have "Toggle Source/Program Monitor Focus" which is very convenient !All theses different shortcut are a pain to work with. I think it would be better to have a simplified shortcut which does it all : open the sequence which is on your monitor, on a timeline, and switch to this timeline in the sequence panel. And when you click it again, do the opposite : go back to the sequence which is not in the source monitor.Update : Resolve also now have a button in the UI which is convenient instead of going into the wheel every time. Annoying UX frustrations and bugsIf you try to open a sequence from the Source Monitor already opened in one of your timelines. Premiere will bug you out, and close your original source, sometimes destroying your layout. I've created a separated topic for this here.Premiere will not restore your Sources Timelines when reopening your project - while it does it for sequences opened from the Program Monitor. So you have to re-open your sources sequences every time you reopen your project. I've also created a separated topic for this here.An Adobe's employee replied that that would be a good idea to implement.Sometimes, the in/out point of your Source are different from the in/out points of your opened source's timeline.Sometimes, when you open the Source timeline, it will be blank. You have to click on the panel multiples timeline so the UI of the timelines shows. If you are an editor, here's the best way I've found to implement an Avid's like workflow.Define "Toggle Source/Program Monitor Focus" shortcut to an easily reachable key, let's say @Define "Panels : Open Sequence" shortcut to an easily reachable key, let's say MAJ + @Drag a sequence into the Source Monitor, place the panel above your existing sequence.Click on MAJ + @ to open it as a sequence.Click on @ to continue working on your Program Sequence.You have a video explaining that just below.

tarang_6679
tarang_6679Participant

Bring "Quick Apply" from After Effects to Premiere ProOpen for Voting

I would love to see the Quick Apply feature from After Effects implemented in Adobe Premiere Pro.In After Effects, Quick Apply lets users instantly search and apply effects, animation presets, and menu commands by simply pressing Ctrl + Enter (Windows) or Cmd + Return (macOS). Instead of navigating through multiple panels and menus, users can type the name of an effect or command and press Enter to apply it immediately.A similar feature in Premiere Pro would significantly improve editing speed and workflow efficiency.Suggested Workflow Press Ctrl + Enter (Windows) or Cmd + Return (macOS) to open a Quick Apply dialog. Search for: Video Effects Audio Effects Transitions Essential Graphics presets Effects Presets Menu Commands Keyboard Commands Press Enter to instantly apply the selected effect or execute the command. Show recently used and frequently used items at the top of the search results. Why this would be valuable Eliminates constant navigation through the Effects panel. Speeds up professional editing workflows. Makes Premiere Pro more keyboard-driven and efficient. Creates consistency with After Effects, making it easier for users who work across both applications. Saves time, especially for editors who repeatedly use the same effects and commands throughout the day. This feature would be a major productivity improvement for content creators, YouTubers, filmmakers, and professional editors who rely on fast, efficient workflows.

MagicalSakuraParticipant

It would be nice if Photoshop wasn't bloatware.Open for Voting

I'm incredibly frustrated with Adobe. I've been using Photoshop CC 2018 since likely 2018 and recently Adobe made it so I could no longer use the software despite my subscription. Instead of opening the app, it gives me the option for a trial version of Photoshop CC 2018. Adobe support told me there was nothing they could do to fix this aside from updating the software or pirating it. The person I spoke to literally told me I should try pirating the software when I asked if that was the only way to use an older version of the software. I'm extremely frustrated because the latest version of Photoshop has ridiculous spec requirements. Photoshop 2018 only needed a minimum of 2gigs of RAM and recommended 8 gigs of RAM. The latest version of Photoshop needs a minimum of 8 gigs of RAM but recommends 16 gigs of RAM. This is getting ridiculous. I primarily used Photoshop for editing, color balance, and text. I do not need any of the new features nor do I want any of the generative AI crap.  I have not and will never use Adobe Cloud storage as Photoshop is too bloated to use on anything but my desktop pc. I don't need or want any of the updates. I primarily use the latest version Clip Studio Paint for my creative work and it has basically the same spec requirements of Photoshop 2018. Clip Studio Paint is frankly a better program for digital painting, but I still liked Photoshop for editing and preparing print files. I don't understand why photoshop is so ridiculously bloated. I also don't understand why I can't continue to use Photoshop 2018 when I don't use any of the cloud features. I don't understand why the programs are so bloated despite the fact people are, or were, paying a subscription. Why can't photoshop be smaller and run more smoothly with all that people are paying you'd think they'd make a lighter program that doesn't eat 50gig of space just by being open. 

thomas5CEDInspiring

P: Custom Whitepoint adaption when changing Camera ProfilesOpen for Voting

When switching Camera profiles in LrC and “As Shot” white balance is selected, LrC will change the Temperature/Tint so the visual result is the same before and after the profile switch. Yet, when the whitepoint is set to “Custom” the numbers are not changed so the visual result is different. Since this is hard to explain here is a small screencast: notice that Temperature changes when white blaance is “As Shot” (“Wie Aufnahme”, sorry for German), but does not change when it is set to “Custom” (“Benutzerdefiniert” in German).  The user effect is the follows:With as shot white balance: the image is visually kept identical (apart from the different camera profile), with the same temperature and tint even though numbers change With custom white balance: the image visually changes, the perceived temperature and tint is different in addition to the different camera profile When using the white balance picker tool a neutral gray patch that was selected with one profile is not neutral gray with another profile This sounds clearly unexpected to the user.Now I can understand this decision: with custom white balance the user gave us exact numbers, so they are never changed. With “As shot” the user doesn’t care about the numbers, but the photo should look the same as shot, so updating the numbers is okay. Yet, I’d argue that even with custom WB, the user is more interested in keeping the photo visually similar with the same visual tint and temperature and not numerical. This is a feature request to change the behavior and always adapt white balance to the color profile and not only for “As shot”. Technical details, this is just my understanding of DNG/DCP, you can skip the rest if not interested.  I worked with DNG/DCP profiles before, So I understand what is happening. “As shot” white balance is usually encoded in camera space (in AsShotNeutral) whereas temperature/tint give xy color space (camera independent) numbers. The conversion from camera color space to xyz is basically the camera profile. White balance always happens in camera color space. SoAs shot always does: AsShotNeutral is already camera color space, so it can be directly used for WB correction For display we need temperature/tint, so we do: AsShotNeutral → xy → temperature/tint when the camera profile changes, the xy conversion changes, so numbers change Yet, AsShotNeutral DOES NOT change, so the actual WB does not change With custom WB:  We ignore AsShotNetural for Whitebalance instead we do  temperature/tint → xy → whitepoint in camera space we use this white point for correction Since the xy → camera space conversion changes with the profile, the WB correction is now different, even though numbers are the same What this feature request technically asks to do is to adapt the xy white point on profile change. Let’s say we change from profile A to profile B. Then the white point is updated such that we do old WP xy → profile_A → WP in camera space → profile B → new WP xySo to make sure that the white point correct in camera color space stays the same, we transform the custom whitepoint to camera color space and back.

touchbParticipant

P: (Masking) - Sync on faces, not person numbersOpen for Voting

Hello,   TLDR: I wish the Ai was more clever when syncing subject masks, syncing faces rather than 'Person numbers'    While editing I often create Ai subject masks for one or two people in an image. Let's say it's the bride & groom walking down the aisle for example... I've then got a big sequence of these images that I would like to sync.  But when you sync, the Ai more often than not decides to choose 2 random people sitting off to the side, instead of the first image where I've selected the bride & groom.    Looking into it deeper, it seems it always syncs the 'person number(s)' rather than the actual intended target. So after correcting the mask to the correct people - some shots of the bride & groom could be labelled differently... 'Person 2 & Person 3' while the next shot could be 'Person 3 & Person 4' or if it's getting it really wrong 'Person 5 & Person 6' ....even though the shot is only marginally different from the first.    It would be good if there was some rhyme or reason to it, but it seems it's just random as to how Adobe and the Ai software are numbering each 'Person' in the shot. It then takes a great deal of time to delete the incorrect mask and reselect the correct person every time for each shot.   It already recognizes each face, why can't it sync on the face rather than the person numbering system? There's probably a reason but would be a brilliant improvement and a massive time saver!  I surely can't be the only one.    Thanks for listening.   Cheers.

llealloo
lleallooKnown Participant

Better text/typography data from sourceRectAtTimeOpen for Voting

With the advent of MOGRT, Essential Graphics and templated AE tools, there is a need to have more data exposed surrounding AE's "Point text" and "Box text" layers that the current sourceRectAtTime does not provide. Having more typographic bound data exposed would be extremely useful for procedurally aligning type. The main issue that one might encounter is ascenders and descenders influencing the sourceRectAtTime dimensions, which is a typographic no-no if using these properties to align type to just about anything. Currently, sourceRectAtTime only has an option "includeExtents" which returns a Box text's (paragraph) bounding box. This is a good start, but there are some other things that would be extremely helpful! Additional optional parameters for sourceRectAtTime might be: 1) typeBounds (Bool) (optional)- sourceRectAtTime.top and sourceRectAtTime.height would be calculated from the topmost capheight to the bottommost baseline. The key is ignoring ascenders and descenders that currently influence the height & position of the rectangle.- sourceRectAtTime.left and sourceRectAtTime.width would be calculated differently as well depending on the type layer's "Left align text" or "Right align text" settings. For type aligned left, sourceRectAtTime.left would return the character's typographic left x position (i.e. it would be 0 without left margin indent for left aligned) and width would give us all the way to the rightmost visual edge. For type aligned right, sourceRectAtTime.left and sourceRectAtTime.width would behave much the same but mirrored. 2) ignoreTextAnimators (Bool) (optional)- This option simply serves to get the type layer's rectangle data before or after any text animators have been applied. Much needed for aligning several type layers with text animators. Additionally, it would be very helpful to expose the properties of a paragraph/box text layer's bounds on the type layer itself as:sourceText.paragraphBox.sizesourceText.paragraphBox.position Thanks for your consideration! For the time being I have been able to get around these issues with some very silly and overly complex expressions, but it would be much appreciated to have these data points built in / more readily accessible. I am certain that designers & animators would find it extremely helpful when building MOGRTs / using Essential Graphics for procedural template design.