Questions

UPDATE 9-18-24:  This has been fixed in 25.1.0.17     As the subject says, the Lumetri GPU accelleration is completely broken, making playback fall entirely on the CPU. Also it is not possible for me to select the GPU accellerated Tetrahedral 3D Lut interpolation, as it is greyed out.   I updated to this new version this morning (I'm in Italy so you do the math), yesterday's version was working with GPU acceleration fine.    Needless to say, it made the software basically unusable and I can't revert to the stable release for the projects I'm working on.    Here's details on my system:   Asus ProArt Studiobook H7604J Intel Core i9-13980HX Nvidia GeForce RTX 4060 8GB Internal Nvidia GeForce RTX 4060Ti 16GB External (via Thunderbolt 3) 32GB DDR5 SODIMM System 1TB NVMe Gen4 Media 2TB NVME Gen3   EDIT: after checking further, it's safe to say the latest update completely broke CUDA integration. 

I'm finding Premiere Pro beta getting sluggish over a couple of hours of work. A quit and restart of the app seems to do wonders.

 This is awesome! I'm not seeeing a bunch of flickering when zooming in and out its a much more pleasant experience on the timeline! Kudos for this huge quality of life improvement.  I will say I was a little disappointed that this wasn't made apart of the update to the waveform code: https://community.adobe.com/t5/premiere-pro-ideas/display-waveforms-for-audio-clips-while-dragging/idc-p/14867803/page/2#M16595 Being able to see the waveform move while editing is a really basic and vital part of sound design that's always made it just that much hard to accomplish in Premiere Pro. Now that it draws so much faster, can we have dynamic waveform drawing pretty please.  

Is it my imagination or has save-in-background disappeared? I seem to be interrupted in my workflow more than ever with save progress bars. At first I was blaming it on how large my project was to save. But now I'm not so sure. Hmmmm...

Thank you!!      

if we could get properties reset by clicking on the property name it self without going to reset button or press ctrl+z.

Hi, I was doing some text-based editing and I was editing on the DYNAMIC transcription when I realized I couldnt export the transcription without naming the speakers. I wanted to change it to a STATIC transcription but I realized if I did that, Premiere would retranscribe my sequence (essentially making all my word/phrase edits null). For context, I had several interviews in the same sequence. So, is there any way to name my speakers on my DYNAMIC transcription? Or is there any way I can change from DYNAMIC to STATIC without losing all my word/phrase edits (meaning: all the times the transcription was wrong and put in a different phrase/word other than the correct one). Or is my workflow all wrong? Thanks!

I can't drag and drop (for example) the effects panel to another window.  Need tu "undock" first....  

Subject says it all, really; we just wanted to let everyone know that 25.0 is the MAX release. [Any changes in PPro beta 25.1 builds will NOT be part of the MAX release.]

I opened up premiere beta to use the enhance speech on a screen recording.  It sounds horrible, changing my voice into a robot. It seems to clip as well.  I don't think it happened before, but maybe it did. Is this a known issue, did something change?

Nikon released an update for the Z6 today that enabled metadata for WB and ISO in ProRes RAW. FCPX already has support for this but Premiere does not.When will this be coming?

Where did the PROPERTIES item in Adobe Premiere BETA go?

These should be blue colored too when activated.... or am i missing something...

With the latest update, the UI is almost broken. In the main window, I can't see panels name anymore - that space is blacked out which also means I can't change sequences at all but I always have to load them back again from the program tab.

I'm getting this pop up every few minutes "Premiere pro (Beta) would like to access data from other apps" Not horible but a little irritating. I get a simular message with Affter Effects. I'm running the latest Sequois Public Beta & the latest Premier/After Effetcs Beta. 

I just want it on record that Adobe should create a diagnostic tool that beta testers can install so that when we submit issues, Adobe can more efficiently troubleshoot rather than waste unecessary time going back and forth with the user reporting the issue, especially if Adobe can't replicate the issue on their end. For example, I have a case where Premiere Pro (Beta) crashes when I try to Browse for a LUT but Adobe can't reproduce it. Such a utility would contain all the user inputs and capture system behaviour and show what's happening when the program hangs. Is a utility like this in the works or has it been discussed?

After opening my project PP closes within 60 seconds without any error message. Happens again and again and I can't edit at all.  Edited for 6 hours last night before update and it worked just fine.

premier beta va de mal en peor, fallo todo el mes de agosto en mi pc y sigue igual, no se que pasa con esto, no funciona para nada y sigo pagando la mensualidad.

Hi Developers.In the BETA ii do not see the FEATHER for CROP.It is in the current version.Would be even best to be able to use FEATHER per SIDE. For example: Only feather top. Hope this will be implemented. Very usefull for designing and color correction. Works much quicker than drawing masks.Thanks a lot.Kind regards,Christiaan

Hi developers.I have an idea that can save us a lot of clicks.I use the remove atributes on more clips regularly when updating color changes for instance.Then I ONLY have to remove the lumetri effect. So I have to DESELECT all other boxes manually.At least 6 clicks when no other effects are used. Otherwise evenmore.It would be great to have a [Deselect All] Button.After that you can select what you want to remove.   

Hi, I feel like I didn't fully remember where this feature was before since I haven't used it that much, but there was a way to click on your first caption, make it into a style, and then say, "apply to all captions in this track". Or something like that. Did it move? Go away? I'm not seeing it in properties or graphic templates. It seems like it used to be in Essential Graphics maybe? Thanks!Tom

We're curious to learn more about how you use PPro's Reference Monitor.All detailed workflow descriptions appreciated!

Working away in PremierePro Beta on a project going on for months.Just about finished with it....Imported some rendered QT footage from Resolve.Put it in my timeline (as I've done hundreds of times)Clicked on a clip and ...crash.Weird. My system is very stable.Opened project,  clicked on same clip - crashOpened project,  clicked on different clip - crashOpened project,  clicked on same clip - crashOpened project,  deleted imported media, clicked on any clip - crash.Opened different project - all is fine.Opened auto-saved project,  clicked on any clip - crashTried to open project in non-Beta version - nope. Won't open.Uh oh.On an Intel Mac Pro 2019 and read the bug reports about enhanced audio.Deleted all enhanced audio audio, clicked on any clip - crashOpened project, got rid of all Resolve media, click on clip...ok!...until the last clip and then crash.Opened project, managed to delete last clip in timeline, removed all enhanced audio - now all clips are fine.

any way to switch back to squared off clips in the timeline? I've tried the bevelled settings, no change...  hating the bubble/bevelled clips design (it's so inaccurate, difficult to see synch, or holes in the timeline, lining up graphics is tough because the bevel makes it not a straight light to line up). Looks like think bubbles on my timeline! Help! 

Last month we had an issue rendering still images too dark. That's resolved now, but to deliver the project I had to apply Lumetri to about 50 clips. (Being a dummy,  I didn't think to use an adjustment layer.) So now if I lasso all the clips , there's no way to clear the effect of all. Is there a way to do this without going into each clip individually? System info    Application: Premiere Pro (Beta) v24.6.0.11    OS: Windows v10.0.22631, RAM: 63.83 GB GB, CPUs (logical): 16