Skip to main content

Filter by idea status

10000+ Ideas

Enhancing Source Patching & Track Targeting with Keyboard ShortcutsOpen for Voting

I currently utilize the keyboard shortcut to move all video targets up or down in Adobe Premiere, which is a valuable feature for copying clips across tracks. However, I propose adding a similar or new keyboard shortcut to move source patching up or down. This would significantly streamline the workflow when inserting or overriding clips from the source monitor, as it would eliminate the need to manually adjust source patching.Benefits:Increased efficiency: By automating the process of moving source patching, users can save time and focus on creative tasks.Improved workflow: A dedicated keyboard shortcut would provide a more intuitive and streamlined experience for editing and post-production.Enhanced productivity: By reducing manual steps, users can potentially increase their overall productivity.Possible Solutions:New keyboard shortcut: Assign a unique keyboard combination to move source patching up or down.Option within existing shortcut: Add an option to the existing "Move All Video Targets Up/Down" shortcut to toggle between moving targets and source patching.Contextual menu: Implement a contextual menu that appears when a clip is selected in the source monitor,allowing users to quickly move source patching up or down.I believe that this enhancement would greatly benefit Adobe Premiere users and contribute to a more efficient and enjoyable editing experience.

Don't force Content CredentialsOpen for Voting

I applaud that Adobe wishes to promote transparency around the use of AI in imagery.However, forcing the addition of Content Credentials (CCs) is a bad move for several reasons:The whole point of the AI debate is that humans should be in control, not computers. Forcing CCs is exactly the opposite of this. The chain of trust must always begin and end with humans, not software. That's the whole point.Minor use of AI to touch up a photo is basically equivalent to Content-Aware Fill or Healing Brush, or traditional airbrushing.It is actually less transparent. Adobe does not make it clear if there is a threshold for the amount of AI usage that triggers the forced addition of CCs. Clarifying this threshold doesn't help. No threshold can truly reflect usage of AI that is deceptive vs benign.People already know that images – even before the age of AI – can't always be trusted. CCs don't really add anything to this, in fact they create a false sense of security when CCs are absent.It is trivial to remove CCs from an image for anyone who actually wants to deceive. This further emphasises the problem of a false sense of secuity.The current implementation often erroneously forces CCs when no, or extremely minimal, AI was present. This can occur for instance if a file was loaded that previously used AI, but all trace of the AI has actually since been removed. This isn't a bug that needs to be fixed. It illustrates the fundamental problem with a system where the software decides.CCs don't make any difference if the end medium isn't digital, or isn't able to display the CCs.I would put it to Adobe that Content Credentials is an excellent initiative, but it is a feature that must be in the user's control.It is up to me to decide whether it's important to disclose that AI has been used. If I removed a few dust marks in the background, no one cares. If I'm trying to sway an election, let my conscience be my judge. If I've made a satirical image and I want people to laugh, but not get the wrong idea, I certainly would choose to include CCs.A forced digital watermark is not, and cannot, be a magic solution to the moral questions that surround the manipulation of images.

SSO (SAML / OIDC / LTI) authentication attribute mappingOpen for Voting

Currently, Adobe's SSO mechanisms do not allow you to customize which IdP attributes map to which Adobe profile fields. You are restricted to using the "default" attributes dictated by Adobe: https://helpx.adobe.com/enterprise/using/automatic-account-creation.html#attribute-mappings Adobe support states that the attribute release should be handled/customized on the IdP end and that this feature is not offered by Adobe.  In a lot of SAML and LTI implementations, it is against best practice to override standard attributes with new values on the IdP end. Instead, you are able to release additional custom attributes, and the SP or Tool Provider (Adobe, in this case) should be able to map those to Adobe's profile fields. For example - the Canvas LMS, does not allow you to override attributes at all. You can only add new attributes per-tool, that are prefixed with "custom_". This causes an issue with Canvas, specifically, because Canvas allows users to change their default email address. What most Canvas admins do to circumvent issues, is release an additional attribute like "upn" or "eppn" which contains the user's official school email address. Much like other apps, Adobe's user mapping, is done through email address. But other apps, allow you to say, "use the UPN attribute for email address".  Given these limitations, the Adobe LTI for Canvas, cannot be used properly in our environment in it's current state, as Adobe cannot properly match up users who have modified their Canvas emails.