This is a bad/misleading response. You can't Chromecast to a Fire TV (obviously).  Adobe arrogantly refuses to allow/develop a Fire TV app (corporate rivalry). ... View more

This is a great example of so-called "Community Experts" (in this case, Gary and Hess) constantly and insecurely dishing out bad information that's totally unresponsive to what's actually being discussed, and what started this topic in the first place.  We already know that deleting from a collection doesn't necessary delete from the disk; we're demanding a simple feature to delete from the disk while inside the collection instead of going to All Photographs or gigantic folders that are unorganized.  @dj_paige provided the answer that should be marked "correct" and Adobe should give us the ability to downvote/kill bad advice like that from @JP Hess and @gary_sc  ... View more

You note that when using the F6 as an audio interface, 32-bit float recording works in Adobe apps.  Thus it's especially reprehensible that lazy Zoom after nearly two years has failed/refused to simply make this product work properly in Adobe apps. ... View more

I agree with everybody that eliminating the scroll bars -- even just as an option to toggle back on -- was incredibly stupid of Adobe.   The hand tool doesn't even behave productively like it does in Adobe's own Photoshop!  There's no way to temporarily scroll around in the program monitor by holding down something like the spacebar in Photoshop - forcing us to change pointer modes back and forth is hilariously counterproductive.  (I refuse to reassign my scroll wheel button just for Adobe.) ... View more

If NVIDIA graphics, make sure to use a Studio Driver from NVIDIA (NOT the Game Driver), but not the latest version - it has issues with Premiere Pro. Go here to download: https://www.nvidia.com/en-us/geforce/drivers/results/218115/ By @Peru Bob   You've made an extremely vague diagnosis that the latest two versions after the January version of the NVIDIA Studio Driver are causing problems.  I reverted to a clean installation of the January version and it had zero effect on the lag problem, along with all the other usual steps that you cite.   What is the basis for your claim that the latest two Studio drivers are causing problems?  I see nothing at these forums after ten minutes of scrubbing its poor navigation tools. ... View more

I'm shocked at the lack of evidence for interest in this critical feature. After all, Google saw fit to make it a central part of YouTube's first-in-class transcription platform, and MANY people use it.  A great example (something I work with frequently) is: when you have existing works of poetry or drama that readers/actors are reciting word-for-word, sans improv.  This should be relevant to most scripted dramas too.  When the text can easily be imported in perfect grammar and punctuation and spelling, hours are saved in post. ... View more

Adobe: seriously, this is one of the easiest fixes imaginable. Just do it. ... View more

Adobe has totally ignored this and it should be filed as a bug report. There's no excuse for preventing us from exporting captions related to a nested sequence that is clearly showing the captions. The Captions category at export, for any nested sequence, remains greyed out. Stupid. ... View more

What is the status of this gigantic, affects-nearly-everyone, cripples-Premiere bug?  I am not updating to the "latest" version despite the nags from the Creative Cloud app, until Adobe finally acknowledges and addresses this (instead of blaming Nvidia even though their latest drivers worked with the immediately preceding Premiere version). ... View more

The triggering action that caused Premiere to melt down, was entirely Adobe's fault.  This is an easy logical deduction because of the fact that all prior and current Nvidia drivers work perfectly fine with the very recent 2023 update of Premiere.  When Adobe compiled the 23.1 update, it was Adobe itself who committed this failure that didn't exist in 23.0, regardless of current/prior GPU drivers installed.   Instead of taking ten seconds or so to boot up Premiere on an Nvidia system to see if it works, Adobe just sorta went "meh" as usual and published the broken update. ... View more

Hey @Kevin-Monahan (Adobe employee):   Your "advice" to roll back our GPU drivers, is not what any of us should be expected to do. You released a totally non-functioning version given a stable GPU driver in the especially stable Studio strand of udpates. And the prior major update of Premiere 2023 worked just fine.   The solution is of course for us all to uninstall the latest Premiere version that Adobe sloppily released, and to revert to the prior version, until Adobe admits its error and corrects it ASAP with their own new update. Do not wait for Nvidia to make a move (unless that's secretly a pay-to-play universe of hidden negotiations).  And maybe for once, apologize? ... View more

Adobe: this is a years-long problem that you've consciously known about, but totally ignored. It's another reason everyone's bailing on your Creative Cloud for better horizons like Da Vinci. Do you care? ... View more

i'll try to be clear so , i had my multicam edited timeline and two of my trhee angles were black. i went back to the original timeline from the nest multicam file, like if you want to modify something on one of the camera. there you right-click the enable option on the missing files , then you right-click once again the enable option and it cancels that bug, when you go back to your multicam work you can see all your angles. if my english is not good enough, i'll explain once more. tell me if it worked for you! By @sandra.lederer   I think this is a potential patch for now, even though Adobe needs to finally spend a few seconds with competent coders to fix this problem that they know about, but refuse to fix after half a decade or more.  However, the working explanation is (as the author kindly notes) not in clear English, so to clarify:   Open the Multicam source in the same Timeline panel and move the current playback time to the spot where you got the blank screen after switching angles (even though it's now visible in this Multicam source). Right-click on that clip on the track that was blank, and un-check Enable, then re-check Enable.  When you go back to the final sequence with that nested Multicam source, the bug will be (temporarily) fixed. ... View more

This worked for me: Right-click the program monitor and check your multicam settings. I turned all of them off and then enabled "show multi-cam preview monitor". Brought everything back for me.  By @InaCl   This is absolutely not a solution.  It literally does not work. Adobe knows about this bug but refuses to fix it.  They only make a move if they have to.  There is surprisingly little traffic at https://adobe-video.uservoice.com/forums/911233-premiere-pro/suggestions/35348485-multi-camera-toggle-track-output-bug.  Everyone, please log your complaint/upvote/description there.  Meantime, Adobe needs to be frightened about everybody giving up and moving along to DaVinci Resolve. ... View more

Hilariously stubborn that Adobe has invested 0% into compatibility with HEIF. Except, when you consider that the world's richest and most notorious lobbyist The Apple Corporation frequently locks down secret deals for exclusive compatibility, as part of its basic playbook.  If you're wondering why after all these years, the now-baseline HEIF image standard is ONLY supported from iOS devices, wake up and smell the coffee (and then, call out Adobe publicly on this). ... View more

Such a hilarious joke that Adobe knows about this, and willfully refuses to fix it. Any competent coder at the multibillion-dollar Adobe Corporation could fix this bug in a matter of minutes. ... View more

It's irrelevant that you have the Pocket 6K, gerikp. dluksa has the Pocket 6K Pro which has Gen. 5 color science and is incompatible with the latest BRAW plug-ins.  However, I just successfully loaded 6K Pro footage into Premiere using the beta version and it works fine for now:   https://www.autokroma.com/blog/BETA-For-URSA-12K-Color-Science-V5 ... View more

This is actually the solution, though it's another bug (if Adobe eventually admits it). Paused full resolution is otherwise not a mandatory requirement for being able to see Lumetri results. ... View more

Hey there Adobe employee, you marked your own bad advice as the "Correct answer" but you linked to a thread that's not only moralistic about NEVER EVER EVER EVER deleting RAW files, but admits that there is absolutely no way to do this.  Adobe has failed at offering the simple feature. ... View more

Disgusting as usual that Adobe has gotten the clear message on this, but after a decade simply refuses to care or even justify its decision to lock down our choices.  We get it, tsk tsk tsk, should have done it in the Project panel.  If you tell us we're in the penalty box, in truth you have no authority over us:  we'll just keep jumping ship to DaVinci.  Your call, "ref."   Or maybe, these Bay Area slackers will finally look up from their lattes and fix this damn obvious problem.  If you took a vote among Premiere power users, 99% would bolt their hand in the air and say YES.   I'm so tired of this guy and others like him handicapping Premiere...   "Adobe Jesus" Jason Levine   ... View more

Completely disgusted/amazed that this has resulted in the usual pattern:  Adobe ignores this bug/oversight, while compensated Adobe evangelists volley back with "I don't see the problem" responses.   There is NO conceivable reason for the program to force merged clips with stereo content into separate mono audio tracks, besides the typical Adobe entitled Bay Area slacker reason that we know all too well:  they skimmed the feature when coding, and don't want to spend any time fixing it (or their egoes are getting in the way.   This is especially true when selecting the feature to discard of the AV audio clip's content, keeping the content only from a merged stereo audio file.   All that's left is to simply fix this.  It's another bug among thousands that's ruining Adobe brand loyalty (and sending users to the hills for better alternatives). ... View more

This has been going on forever. Adobe knows about it. Adobe has done nothing to address it. ... View more

Here we are, on the day of the latest release (14.0.2) and stubborn Adobe has refused to address this widely known bug.  It would be extremely easy to fix.  Probably the Adobe defendants seen in this thread got emotional, refusing to facilitate any fix... ... View more

Adobe's modus operandi is to read stuff like this, try it on their in-house system, and only take action if it happens to be a problem at the moment when they try.  Thus they reply back almost always saying, "we can't replicate this but let us know the next time it happens, telling us your system specs."  It's an endlesss loop, with no accumulation of productive data, and they still think their customers won't leave Premiere after years of neglect.  That is changing fast. ... View more

Adobe totally doesn't care.  Many have reported this directly to them, and over at UserVoice, and here, where you can see an Adobe employee marked the topic as answered and resolved.   I think Adobe is passively encouraging us to use competing software.  Their profit margins went through the roof after moving to a subscription model, and currently they don't feel any need to compete.  That is changing. ... View more

That has absolutely nothing to do with it, Adobe Employee (but sure, I just checked).   Instead of sending questions back to us, perhaps finally do something? ... View more

Adobe:  this is a well-known bug, evidence provided here, and totally ignored for years.  Why? This thread absolutely should not have been marked "resolved." ... View more