Skip to main content

Filter by idea status

10000+ Ideas

Feature Request: Support for multiple Adobe IDs / Simultaneous account login on Creative Cloud Desktop | Pedido de Recurso: Suporte para múltiplos Adobe IDs / Login simultâneo de contas no Creative Cloud DesktopOpen for Voting

Good evening,Currently, the Creative Cloud Desktop application strictly enforces a single active login per operating system session. However, the workflow frequently requires managing and delivering projects across different client and studio accounts.Every time the user needs to switch from a personal account to a corporate or team account, the system forces a complete logout. This requires a new authentication (frequently involving two-step verification) and the mandatory restart of applications such as Lightroom Classic, Lightroom, and Premiere Pro. This process interrupts the production line and generates operational downtime throughout the day.A multi-profile management system within the Creative Cloud application, similar to the model used by platforms like Google Chrome, would be of great value. The goal is to allow the insertion of multiple Adobe IDs with simple switching between sessions, or the execution of Lightroom and Premiere Pro instances from distinct credentials simultaneously on the same machine and under the same Windows user.The consideration of a multi-account feature focused on advanced workflows that operate with diversified client ecosystems.Thank you!  --------------------------------------------------------------------------------------------------------------  Boa noite,Atualmente, o aplicativo Creative Cloud Desktop impõe estritamente um único login ativo por sessão do sistema operacional. No entanto, o fluxo de trabalho frequentemente exige o gerenciamento e a entrega de projetos através de diferentes contas de clientes e estúdios.Sempre que o usuário precisa alternar de uma conta pessoal para uma conta corporativa ou de equipe, o sistema força o logout completo. Isso exige uma nova autenticação (frequentemente com verificação em duas etapas) e a reinicialização obrigatória de aplicativos como Lightroom Classic, Lightroom e Premiere Pro. Esse processo interrompe a linha de produção e gera perda de tempo operacional ao longo do dia.Seria interessante um sistema de gerenciamento de múltiplos perfis dentro do aplicativo Creative Cloud, similar ao modelo utilizado por plataformas como Google Chrome. O objetivo é permitir a inserção de múltiplos Adobe IDs com alternância simples entre sesões, ou a execução de instâncias do Lightroom e Premiere Pro de credenciais distintas simultaneamente na mesma máquina e no mesmo usuário do Windows.A consideração de um recurso de multi-contas focado em fluxos de trabalho avançados que operam com ecossistemas de clientes diversificados.Obrigado!     

TROZANME
TROZANMEParticipating Frequently

Feature Request: Workflow & Customization Improvements for Adobe AuditionOpen for Voting

Hello Adobe Audition Team,On behalf of professional audio editors across post-production, broadcasting, animation, music, and podcasting, we request several key features that would make Adobe Audition more competitive and efficient for large-scale audio work.Audition is already a reliable DAW for editing, mixing, and restoration, but there are modern workflow tools present in other professional audio software that would significantly speed up production and organization for thousands of users.Requested FeaturesBins / Folder Structure in Files PanelCreate and manage folders (bins) in the Files panel to organize assets like Voice, SFX, Music.Drag-and-drop between bins, search inside bins, and filter by tags.Track Folders with FX InheritanceCollapsible folder tracks to group related tracks (e.g., all character voices, or all ambient SFX).Apply effects, automation, or routing at the folder level that affect all child tracks.Per-Clip / Per-Item EffectsApply effects directly to individual clips without affecting the entire track.Non-destructive and editable at any time.Advanced Delete Silence ToolAdjustable padding, RMS/LUFS-based detection, and the option to process multiple clips or tracks at once.Ability to visually preview silence detection before applying.Ripple Editing EnhancementsRipple edit across multiple selected tracks in the Multitrack Editor.Option to lock track sync groups so edits shift all related audio in sync.Custom Actions / MacrosAbility to record or build multi-step actions (macros) and apply them instantly.Include auto-apply effects chains to tracks in the Multitrack Editor as part of these actions.Render Queue & Batch ExportQueue multiple mixes or stems to export overnight.Save batch export presets for different delivery formats.Enhanced Bus & Mixer FeaturesReorder buses, hide/show specific buses in the mixer, and assign colors/icons.Multi-bus sends and pre/post-fader send options.Direct Video Export from AuditionExport video formats directly from Audition (like Premiere Pro) without needing Adobe Media Encoder.Saves memory and time, especially for quick review renders or short-form content.User Scripting & CustomizationSupport for user scripts to automate repetitive tasks.More customizable interface layouts to match different workflows (e.g., VO editing, multitrack mixing, restoration).Why This Matters:For professionals handling complex, multi-hour sessions — such as episodic animation, long-form interviews, and film post-production — these features would drastically improve editing speed, maintain cleaner projects, and reduce repetitive manual work.Many of these improvements already exist in other professional creative software — adding them to Audition would ensure it remains the preferred choice for editors who want both Adobe’s ecosystem and modern audio editing power.Thank you for considering these requests on behalf of the wider audio editing community. These features would make a meaningful difference to the daily workflow of thousands of professionals worldwide.Sincerely,Santosh MareddyThe Professional Audio Editing Community

agile_Heroab21Participating Frequently

Better Generations WindowOpen for Voting

Subject: Generation History is a mess. Fix it.I use Firefly for TV/film production. Generation history is where all my work lives, and it's nearly impossible to organize.Favorites is one bucket. One heart for everything. That isn't organization. Projects duplicate my files. Adding generations to a Project copies them, so I either pay for storage twice or delete originals and gamble that the copy worked. Frankly, it feels like a way to sell more cloud storage. Projects should reference originals, not copy them. No tags or labels. Lightroom and Bridge have had batch tagging and color labels for years. Generation history has nothing. I can't name my own shots. There's no way to give a generation a custom label like "Sc12_Tower_Wide_v3." Worse, the same file shows a different name depending on where I open it, whether Generation history, a Project, Your files or a download. I can't track a shot when its name keeps changing. No metadata after generation. To find anything later, I have to embed codewords in my prompts before I generate. That's a workaround for a feature that should already exist. Reuse means re-uploading. Anything I organize outside Firefly has to be uploaded again to use it. Adobe owns the cloud, the apps and the file system, and they still don't connect. Build a real project panel. Premiere Pro already has bins, sub-bins, list and thumbnail views, sortable columns (date, model, aspect ratio, resolution, prompt) and drag-and-drop. You've built it. Put it in Firefly and make it reference originals. Everything waits on the cloud. Every scroll, thumbnail and preview crawls. Browsing a few hundred generations shouldn't be a test of patience. Either this is bad design, or you've sold too many unlimited subscriptions without the server backbone to support them. Either way, I'm the one paying for it in lost time.Altogether, this is an incredibly frustrating experience. I'm paying for this, and I shouldn't have to fight it to find my own work.No need to reply. Don't send me a thank-you or a canned response. Just make it better. The only reply I want is from someone on your team who hates the Generation history window as much as I do and is going to fix it.