Skip to main content

Filter by idea status

10000+ Ideas

athletic_fact6385Known Participant

Filtering in project panelOpen for Voting

Hi, I know we got the fancy new search panel but as I see, it’s lacking basic filter functionality based on folder structure.Often I get folder structures with selects, shootings dates, color labels and to put that into context, I need to see the location of those files, best by seeing the folder structure.(Sure, if all was logged into metadata it would be nice but that is not always possible and to be honest, showing a few metadata panels more in the project panel hits the performance a lot and often leads to UI bugs like input fields getting stuck while scrolling and such things).So what do I want to do?The situation is following:A structure like-Day 1--Scene 1--Scene 2-Day 2--Scene 3In each “Scene” folder, there are numerous files, color coded to be selected or to be excluded.Now I want to filter for specific labels but unfortunately the search doesn’t allow for something like Label:Green or Label=Green.A search like “Green” isn’t working either, despite this search/filter is also picking up on other metadata columns (e.g. I could search for 1920 to only show 1920x1080 clips… working more or less).So, what’s really missing here as far as I can see is a basic filtering “language” allowing for stuff like:Label=”Dark Green” AND Resolution=”1920x1080” OR Resolution=”3840:2160” AND Date<=”19.02.2020”Again this is for filtering inside of the project panel with folder structure as a base which isn’t possible with the search panel, nor search folders as they flatten the results to only files.Is there anything like this possible at the moment or is this something that would be entirely new to filtering inside of Premiere?I know you can hide files and toggle them but that wouldn’t help with finding specific files fast (relative to their structure)

amanda_8187Participant

Report inaccuracy or allow ratings/reviews on Adobe Stock assetsOpen for Voting

I’ve been extremely frustrated by misleading Adobe Stock graphic descriptions. This probably just applies to vectors. The platform is starting to be OVERRUN with AI-generated graphics claiming not to be AI. These typically look great on the preview, but once you download them, zoom in, and try to edit them it’s extremely obvious that they’re AI. Mostly because they’re always put together in a sloppy way that’s hard to edit, and don’t look nearly as good close up. I have on numerous occasions downloaded 20+ assets before I could find one that wasn’t AI, despite having the “exclude generative AI” filter on. Additionally, I’ve downloaded a ton of icons that claim to have editable strokes but don’t, and various graphics claiming to have editable text that don’t. I can’t even imagine how frustrating this must be for people who buy download packs rather than having a subscription. I understand that your team probably doesn’t have time to review every asset that gets posted, but it seems that stock artists are using that to their advantage to get downloads from people who wouldn’t actually want to use the asset. I always want to report these inaccurate descriptions, but you can only report copyright infringement. The assets I’m referring to do not need to be removed from the site, just labeled correctly. I imagine that adding a report option for “inaccurate description” would be the easiest way to handle this, but alternatively I think allowing reviews and/or ratings could also help with this issue.

Joost van der Hoeven
Community Expert
Joost van der HoevenCommunity Expert

Preserve source clip's native frame rate when reconnecting high-res in a proxy-first workflow with mismatched frame ratesOpen for Voting

In a proxy-first or proxy-only ingest workflow, when a 25i high-resolution source is later connected to a pre-existing 50p proxy, Premiere Pro incorrectly inherits the proxy's interpreted frame rate (50fps) and applies it to the 25i source, causing it to play back at double speed.Importantly, this issue does not occur in the reverse workflow: when a 25i source is ingested first and a 50p proxy is generated from it, toggling between proxy and high-res works correctly. The problem is exclusive to the proxy-first path.Context:This is a real and growing workflow challenge for broadcasters and post-production facilities transitioning from interlaced (25i) to progressive (50p) acquisition. Archive footage shot in 25i must regularly be cut alongside new 50p material. Using 50p proxies for archive 25i clips is desirable because: All 50 fields per second are represented as individual frames, enabling frame-accurate editing Progressive proxies play back more efficiently on laptops and office workstations It creates a uniform editing environment across 25i archive and new 50p acquisition The high-res source must remain native 25i for broadcast delivery and archival integrity — re-interpreting it as 50fps is not acceptable.Request:When reconnecting high-res media to a proxy in a proxy-first workflow, add an option to preserve the native frame rate of the source file rather than inheriting the proxy's interpreted frame rate. This could be implemented as: A per-clip option in the Attach/Reconnect Full Resolution Media dialog A project-level preference: "On reconnect, use source file's native frame rate" An automatic fallback when the source file's container frame rate differs from the proxy's interpreted rate Expected behavior: Toggle to proxy → clip plays at 50p (proxy rate) Toggle to high-res → clip plays at native 25i (source file rate), without speed distortion and without requiring manual Interpret Footage correction on every clip

ali1424like
ali1424likeParticipant

Make Premiere Mobile for Androids like Node video pleaseOpen for Voting

Interesting talk with Gemini :  Me: would it be as good as the pc version in the future ?  like is there any conversation the company was taking about dreaming about a pc level editing for the future... you know? Gemini:  Adobe’s vision isn’t necessarily to make the mobile app an exact "clone" of the PC version, but rather to make them partners in a single, professional workflow. While they aren't "dreaming" of putting the full, heavy Premiere Pro interface on a 6-inch screen, they are working toward PC-level quality through a few key strategies: ## 1. The "Edit Anywhere" Philosophy Adobe’s current goal is for you to be able to start a project on your phone and finish it on your PC without losing any quality. [1, 2]  * Seamless Sync: Projects from the new [Premiere on iPhone](https://www.adobe.com/products/premiere/app.html) (and the upcoming Android version) can be directly imported into Premiere Pro on desktop. * Unified Engine: The new mobile app is powered by the same high-quality rendering engine as the PC version, ensuring your mobile exports look just as professional. [3, 4, 5, 6]  ## 2. AI as the "Great Equalizer" Adobe is betting on AI (Adobe Firefly) to bring "pro-level" results to mobile without needing complex PC menus. [7, 8]  * One-Tap Pro Tools: Features like "Enhance Speech" (which makes phone mic audio sound like studio recording) and "Auto Reframe" are being ported directly from PC to mobile. * Generative Power: They are adding tools that allow you to generate sound effects, expand backgrounds, and remove objects with text prompts—things that used to take hours on a PC. [7, 9, 10]  ## 3. Will it ever be "as good" as PC? In terms of power, yes; in terms of control, probably not. * Mobile's Strength: Speed, AI-driven automation, and social media integration. * PC's Strength: Complex color grading, advanced visual effects (VFX), and managing massive multi-track projects with hundreds of clips. [7, 11, 12, 13]  ## Summary of Differences | Feature [7, 13, 14, 15] | Premiere Mobile (Future Android) | Premiere Pro (PC) | |---|---|---| | Speed | ⚡ Fast (AI-heavy) | 🐢 Slower (Manual) | | Control | 🤏 Simplified (Touch) | ⌨️ Precise (Keyboards/Shortcuts) | | Project Size | 📱 Short-form/Social | 🎬 Full Films/Long-form | | VFX/Color | ✨ Presets/AI Looks | 🎨 Deep, Manual Tools | Adobe’s "dream" is that you shouldn't have to choose between them—you use the phone for the quick, smart stuff and the PC for the heavy lifting. [2, 6]  Since the Android version is still in development, are you planning to use it for professional work or more for social media content? Me: dude; why can't they ; don't they know that there is an app called node video and is basical an Adobe after effects for mobile!  I believe they should be able to do something like this if they wanted! Gemini:  You're spot on—Node Video proves that high-end, "After Effects-style" editing is technically possible on a phone, even featuring a node-based interface, 3D camera tracking, and complex keyframing. [1, 2, 3, 4] If a smaller studio like Shallway can do it, Adobe definitely can—but their current business strategy is different. Here is why Adobe hasn't "cloned" Node Video's approach yet: ## 1. Different Target Audience * Node Video is built for "power users" and VFX enthusiasts who are willing to deal with a steep learning curve and complex menus to get professional results on mobile. * Adobe's Goal is to capture the massive social media creator market. They want an app that is fast and "uncluttered," where AI does the heavy lifting (like auto-captioning and noise removal) so users can post high-quality content quickly. [1, 5, 6]  ## 2. Guarding the "Desktop Crown" Adobe makes a huge portion of its revenue from Creative Cloud subscriptions. If they put 100% of Premiere Pro or After Effects on a phone for $5 a month, many professionals might stop paying the $50+/month for the desktop suite. They prefer a "Mobile + Desktop" hybrid where: [7]  * The mobile app is for the rough cut and quick AI fixes. * The desktop app remains the only place for deep VFX and professional color grading. [5, 8, 9]  ## 3. Stability vs. Features Node Video is powerful, but it has very high hardware requirements and can crash or disable features on many mid-range Android devices. Adobe is a massive corporation that prioritizes stability and compatibility across millions of devices. They would rather release a "simpler" app that works for everyone than a "pro" app that only works on high-end flagships. [10, 11]  ## 4. The Shift to AI Instead of giving you manual "After Effects" sliders, Adobe is betting on Adobe Firefly. Their "dream" is that you won't need to manually animate a mask or track a camera—the AI will just do it for you based on a text prompt. [6, 8]  The Bottom Line: Adobe isn't trying to beat Node Video at its own game; they are trying to change the game entirely by making mobile editing as automated as possible. [5]  Since you're a fan of those pro-level tools, are you mostly using them for complex motion graphics or just for better color and precision than basic apps offer? Proactive Follow-up: Would you like to see a list of the best After Effects-like features currently available in the Premiere Mobile beta? Me:  Don't be fool, they can make it easy and stable for quick edit using AI or whatever; but also include pro heavy features for the people who want to use them! Gemini:  You’re right—technically, there is nothing stopping a multi-billion dollar company like Adobe from building a "Pro Mode" into their mobile app. Apps like Node Video, LumaFusion, and even DaVinci Resolve on iPad prove that you can have a "simple" interface for quick edits and a "beast" mode for professionals under the same hood. If Adobe actually listened to power users like you, here is how they would likely build that "Dream App": ## 1. The "Switchable" Interface Instead of two different apps, they could have a Simple/Pro Toggle: * Simple Mode: Big buttons, AI-automated captions, and one-tap filters (for the TikTok/Reels crowd). * Pro Mode: Unlocks the timeline, keyframe graphs (like After Effects), 3D space, and Lumetri color wheels. ## 2. External Hardware Support For "Pro" features to be stable, Adobe would need to optimize for: * Thunderbolt/USB-C SSDs: Allowing you to edit 4K footage directly from a drive instead of filling up your phone's storage. * External Monitors: Using Samsung DeX or iPads to give you a full desktop-sized UI while the phone does the processing. ##3. Why they haven't done it (yet) It likely comes down to Corporate Strategy, not technical ability: * The "Subscription" Trap: Adobe wants you to need the PC version. If the mobile app is too good, their $50/month Creative Cloud sub looks less "essential" to some people. * Cloud Processing: Adobe is moving toward "Cloud-First." They’d rather have their massive servers do the heavy rendering (AI) than your phone’s battery-draining processor. ## 4. The Competition Pressure The only thing that will force Adobe to make a "Pro" Android app is competition. * If Blackmagic brings DaVinci Resolve to Android flagships (like they did for iPad), Adobe will be forced to match those pro features or lose the market. * Node Video is already eating their lunch in the VFX mobile space. Adobe is definitely capable; they just seem to be playing it "safe" to keep their desktop business protected. Since you know your way around high-end apps like Node Video, what’s the one "must-have" feature from After Effects that you think Adobe is crazy for leaving out of mobile? So what do you think Adobe? Can you do that or your scared to fail 🥲?!