Bug Reports

・Premiere Pro beta版（24.3）を使用。テキスト編集をしていると、編集できなくなることがあります。再起動すると直ります。修正お願いします。

I have been using text-based editing for a while. I have auto in and out set. However, when I attempt to do a ripple delete via the transcribe panel, nothing happens. It leaves the text and clips highlighted.  I opened the same project in 24.3.0 and highlighted the same section, and the ripple delete worked as expected. This is on Mac OS 14.4.1.

I've used text-based editing the past few weeks and had no problem, but today immediately after the latest update, it stopped working. I can see the text but if I highlight it, it doesn't let me delete it.

I recently updated to the latest Beta version, 24.4, and noticed that some essential features, such as text editing, cutting, deleting, and ripple delete, were not functioning properly. As a result, I downgraded to version 24.3, and now everything is working as expected. Upon checking, I found that the video segment is correctly marked, and the in-and-out points are working fine in the 24.4 version. 

ive realised something about premiere pro beta. For some reason when you Press alt. the top left of the screen opens up mode where the keyboard keys now effect the file, edit, clip, sequence, markers, graphics and titles, view, window and helpso alt and c will open the clip dropdownthis is good and all but in the newest version alt seems to toggle this feature rather than enable on down and disable on up. meaning if i press alt. im now stuck in this mode until i press alt again or click the mouse button.ive attached a video and in this video you can see when i let go of alt. the little lines under the tabs are still present

In version 22.2.1 and 24.3 beta (build 44), proxies made for Interpreted footage add a freeze frame after the original duration.  Both Windows and macOS.Example: 1. Import clips with frame rate 29.972. Interpret frame rate to 253. Create proxies Result: Proxies work fine up to the original clip length (they get longer after interpretation), but after that, they show just a freeze frame. Expected result is moving images, not freeze frame.This workflow has been working perfectly fine since version 22.6, but with the new proxy presets, it's broken. Please fix. 

Version Beta V 24.2.0 build 2In the lumetri panel setting options / in the sequence clip and for a Panasonic V-Log rush, the exposure value is not saved in the project.If, for example, I set this value to +1 when I reload the project, the value reverts to its default value: -0.3For your information, the time line is in REC 709 with automatic tone mapping. best regards Christian Goubier

Steps to reproduce:    1. Copy a segment of a video with preset audio adjustment     2. Paste Attribute to another segment linked with an audio (keep audio option unchecked) Result: Audio adjustment preset gets pasted onto the segment with audio linkedExpected: Audio Attributes should not be pasted onto the new segment due to the checkbox being unchecked System info    Application: Premiere Pro (Beta) v24.2.0.78    OS: Windows v10.0.22631, RAM: 31.93 GB GB, CPUs (logical): 12

Yes, I have the transcript window set to automatically choose the in and out points. And it's doing that. But pressing delete, or right-clicking and pulling up the menu to delete, etc. is doing nothing. I have to manually go to the automatically-set in and out-points to delete material. 

After update to 24.4.0. beta build 25: Audio waveforms are not showing up in the nested multitrack sequence (after opening the multitrack source in a sequence.) They were showing in build 24 or 23.  

NO EXPORT MY VIDEO

It should not be possible to accidentally link _proxy files as originals. I've seen quite a lot of users accidentally do this when relinking. They think Premiere Pro is asking for the original, when it's actually asking for the prtoxy file.  This creates a lot of unexpected behavior, relinking issues etc._proxy files should never accidentally be attached as originals. If people do this, it should be a very deliberate choice.  And it should definitely not be possible to attach the same file as both original and proxy at the same time. It seems that Premiere Pro will allow this - but only until we close the project and re-open it. Then it will ask us to relink.  Give us a warning and some guidance so we can avoid trouble!

Steps to reproduce:    1. Add video transitions to a few edit points    2. Select the edit points (Ctrl/Cmd-drag to select them)    3. Hit Delete, or right-click an edit point and and choose Clear Result: Clear will only delete one transition, not all the selected ones. Delete does nothingExpected: All transitions at the selected edit points should be deleted System info    Application: Premiere Pro (Beta) v24.4.0.32    OS: Windows v10.0.22631, RAM: 127,69 GB GB, CPUs (logical): 32

In Premiere Pro beta 24.4.0, build 32, the white corners that indicate Media Start (first frame of video) are there, but the white corners that indicate Media End (last frame of video) are missing.This seems to only happen when media and sequence frame rates are different. In practice, this means all the material with variable frame rate (which I seem to get a lot of these days) and all media shot at 29.97 in a 25 fps sequence are missing the end whiote corner.In a way it makes sense, since the media actually may have a few milliseconds more media, but it also makes it impossible to see at a glance what clips have been edited at the tail) and not. I liked it btter the way it was before. 

Do the developers read these?  Is there a better way to report minor bugs?  Or does anyone even want to know about them? Anyways, I have noticed a small bug (I think).  I have audio / video imported into a project and it will occasionally unlink itself.  I am not sure what causes this and its so minor that it doesnt particularly bother me, just wanted to report it.  I notice it when I use the ALT key to drag a copy of the clip to a second location in the timeline.  Perhaps it is actually a feature that I am not familiar with, but I put it here anyways.  Thank you!

Is anyone experiencing difficulty loading transcribed audio in Studio? Existing projects are continually loading and inaccessible, and if I re-upload the audio and re-transcribe it, the text conversion is successful, but I'm unable to play the audio. I'm using Chrome and .wav files.

I have noticed anomalous behavior in both the production and beta versions of Adobe Premiere Pro. The steps to recreate the behavior are as follows:I capture video on my iPhone 13 Pro Max running iOS version 17.4, but this has happened on every version of iOS that I've used with this phone.I uploaded the MOV file to my Windows 10 system using Google Drive.When I import and render using Premiere or Media Encoder, it fails with a failure to render at frame number XXXX error.The solution to this problem is to perform the following steps:Capture the video on the iPhone.Upload the video to my MacBook using AirDrop.Import the MOV and render using Premiere on the MacBook. This never produces the failure to render that I experience on Windows.Upload the MP4 file to my Windows 10 system using Google Drive and resume editing in Premiere Pro. The failure to render error does not happen.I don't understand why the MOV file can be rendered on the iOS version of the product but not on the Windows ver

Hi there, After today's beta update, playback is broken in the timeline unfortunately. It seems to be a factor 2x faster, but choppy.  More people experiencing this? Looking forward to a fix, can't work now unfortunately.   Thank you and kind regards, Matthijs

Premiere PRO Beta 24.4 (build 23) Mac M1 Pro When i open a project that i have been working on the day prior.  A random selection of files revert my cuts back to the the start of the timecode. loosing the in and out points. resulting in the timline with my two cameras getting out of sync. I am working on a two camera setup that has had files synced with a Tentycle Sync.  Not sure how to explain this better.  The files are linked, (no Missing media error) but the clips have a greyed out lines over them. I understand this is common with clips that have different frame rates.Which i know is not ideal but it happened in this instance. Trying to make the best of it.  And help or trouble shooting would be a great help.  the issue also effects when i try and export with Media Encoder. and the sync on all my files is off. If i export within Premiere Pro it works fine.  

I'm using a Macbook Pro Max 3 with 36gb RAM. Everytime I try to transcribe an interview clip (Sony .MXF from FX6 camera) the RAM usage jumps from 14gb to 65gb (not sure how that's possible, since I only have 36gb) and my Mac makes me Force Quit Premiere Beta without saving. I tried opening a new project file and only importing those interview clips, as soon as I try to transcribe them the same error happens. I then went to the non-beta version of Premiere Pro 24.2.1 and it works flawlessly with the same clips. No issues transcribing at all. My work-around right now is transcribing the source clip in 24.2.1 and importing that project into the beta version, since I'm very far along in the project already. This only started happening in the last 2 versions of Beta, it had been working on previous interviews shot on the same camera until the 24.4.0021 version of Beta. System:Mac OS Sonoma 14.2.1 - 14 inch Macbook Pro M3 Max 14 CorePremiere Pro Beta 24.4.0.021-22

Most current Beta Build 24, Mac Ventura on a Mac Studio. When I drag a bin in the project panel into another bin, it just duplicates the bin and adds a number at the end.

Tried to open Essential Graphics and it didn't work. So then I've tried to change to other workspace and it didn't have any effect.

Just updated Premiere Pro to 24.4.0 BETA (Build 21) And now suddenly all H.264 files are not displaying or rendering properly. They have a kind of purpulish hue and a lot of digital noise. ProRes and other file types look fine. Files play fine in VLC and Quicktime, rencoding to ProRes in Shutter encoder and importing into premiere is working as a workaround. MacOS 14 14.2.1iMac ProIntel Xeon W-2191B128 GB DDR4

Immediately upon clicking the "Transcribe" button the program crashes. And I mean IMMEDIATLY crashes with no option to report the crash. This is the ONLY reason I downloaded the Beta. 

I think maybe the classic colors disappeared in this update.