I have a feature film with several open caption subtitle tracks. I want to turn off the subtitle tracks and export the movie along with a rolling credit at the end. Premiere 2020 will NOT do this. It simply refuses to export the the material. It hangs on export and tellingly the Encoding window does not respond to the cancel, but the cancel button on the main export window remains active. This does not happen in Premiere 2019, which works fine. Also, Premiere 2020 refuses to export a movie and an .srt sidecar file. The option is there, it simply doesn't work.

I'm using MacOS 10.13 on a iMac Pro with Vega 64. If I export to H.264 using hardware encoding the audio drifts out of sync for a longer sequence. By about 10 minutes the drift is noticeable. If I chose software In MacOS 10.13.6 on iMac Pro with Vega 64 GPU and lots of RAM. While encoding in the export window the audio stays in sync. In addition, Premiere Pro will hang when exporting H.264 randomly. Very frustrating, the other day I had to try small sections of the sequence to encode, I finally got this working. I feel it is the hardware / Metal interface. Maybe if I upgrade to MacOS 10.15 it may work better. What do you think? Overall performance while editing in 2020 is good, just the encoding part is really annoying

Autosave is incredibly disruptive and always cuts you off in the middle of something. It's really not okay for this to happen and can throw off your cutting groove. It's essential not to be interrupted, especially mid-edit. If the team is not capable of coding a non-interrupting autosave, please allow the option of an autosave warning, or countdown, letting us know the program is about to save and completely stop you from working. If we're deep into an edit and need to focus, we can hit a command/use a mouse click to stop the autosave before it kicks in. Removing all interruptions is imperative.

Also might be a good idea to ask to rate this software AFTER your project has opened, so someone doesn't open a huge project, leave a room for 5 minutes to let it load up, only to come back to see it's not open because Adobe wants to know if you'd recommend it Premiere to your friends.. Come on guys.

Ok…thoroughly confused about Project Management
as it relates to copying and CONSOLIDATING files.

Goal: take a sequence of video files, consolidate them
and export an AAF file for colour correction by a third party elsewhere.
Should be pretty straightforward, yes?

Previously I have had problems where I would get an error
the moment I tried to consolidate a sequence AND check “exclude unused clips”.
It would give me an error and then stop.
I attributed this to the weirdness of using Avid media on a system not yet blessed by Avid to use
and didn’t have Media Composer or its codecs installed by Avid.

So now I’d editing a brand new project.
All the media is straight from my source files.
I create a sequence with four clips of video (only).
The sequence does not refer to any proxy files.
The proxy file button is not turned on.
I go to project Manger and choose Consolidate and transcode
with exclude files checked ON and 24 frame for handles.
I click ok and it there are no errors!
Hooray!!!

But… rather than consolidating 4 files
it made a new clip of EVERY SINGLE PROXY CLIP in the project
and then placed each of the source clips in their ENTIRETY in that folder too.

Now, while I can probably just delete the proxies and hold onto the 4 non-proxies and send that over…
it certainly doesn’t seem to be consolidating or excluding anything.

Typically in Media composer an operation like this
with a sequence of four clips
would result in just four files
and would happen in a fraction of the time.

So…am I doing something wrong?
Or am I ASSUMING something wrong?
Is this what PP thinks consolidating means?
Are the proxies critical to the AAF somehow?

Help!

We have several users of BRAW Studio experiencing timeline shift after moving their projects between computers. Sometimes it even goes back to the first frame.

If this also happens to you please tell your story in Adobe Community Forums : https://community.adobe.com/t5/premiere-pro/cc-2020-timeline-clips-shifts-after-moving-project-relocating-relinking/m-p/10923880

Happens only with CC 2020 (both 14.0.0 and 14.0.1), both OSX and Windows, all framerate (23.96 fps and 25 fps for example).
Apparently happens with others formats than .braw : https://community.adobe.com/t5/premiere-pro/linking-media-losing-in-and-out-points/td-p/10922669 "I have this problem on every file type I have tried; R3D, BRAW and CRAW"
Attached is a zip with the two .prproj from a user editing with .braw and you can see what's changing inside <MediaFrameRate> and <TimecodeFormat>, also the timecode changes from 01:43:25:03 to 01:43:31:16000

Please investigate and fix this issue it is very annoying and preventing users to edit in good conditions with Premiere Pro it is quite urgent

Thanks,
Antoine

We have several users of BRAW Studio experiencing timeline shift after moving their projects between computers.
Happens only with CC 2020 (both 14.0.0 and 14.0.1), both OSX and Windows, all framerate (23.96 fps and 25 fps for example).
Apparently happens with others formats than .braw : https://community.adobe.com/t5/premiere-pro/linking-media-losing-in-and-out-points/td-p/10922669 "I have this problem on every file type I have tried; R3D, BRAW and CRAW"
Attached is a zip with the two .prproj from a user editing with .braw
We can see that this inside the .prproj XML :

<ClipLoggingInfo ObjectID="40" ClassID="77ab7fdd-dcdf-465d-9906-7a330ca1e738" Version="8">

    <ClipName>A005_01231137_C004.braw</ClipName>

    <MediaInPoint>1577778048000000</MediaInPoint>

    <MediaOutPoint>1621427734080000</MediaOutPoint>

    <MediaFrameRate>10594584000</MediaFrameRate>

    <TimecodeFormat>110</TimecodeFormat>

</ClipLoggingInfo>


is changed to this : 

    <ClipLoggingInfo ObjectID="40" ClassID="77ab7fdd-dcdf-465d-9906-7a330ca1e738" Version="8">

    <ClipName>A005_01231137_C004.braw</ClipName>

    <MediaInPoint>1577778048000000</MediaInPoint>

    <MediaOutPoint>1621427734080000</MediaOutPoint>

    <MediaFrameRate>5292000</MediaFrameRate>

    <TimecodeFormat>200</TimecodeFormat>

</ClipLoggingInfo>

Also, timecode when opening PPro project goes from 01:43:25:03 to 01:43:31:16000, the latter timecode coming from the project after relocation and this timecode doesn't make sense at all (16000 frames ?)

Please investigate and fix this issue it is very annoying and preventing users to edit in good conditions with Premiere Pro it is quite urgent

Thanks,
Antoine

We have several users of BRAW Studio experiencing timeline shift after moving their projects between computers.
Happens only with CC 2020 (both 14.0.0 and 14.0.1), both OSX and Windows, all framerate (23.96 fps and 25 fps for example).
Apparently happens with others formats than .braw : https://community.adobe.com/t5/premiere-pro/linking-media-losing-in-and-out-points/td-p/10922669 "I have this problem on every file type I have tried; R3D, BRAW and CRAW"
Attached is a zip with the two .prproj from a user editing with .braw
We can see that this inside the .prproj XML :

<ClipLoggingInfo ObjectID="40" ClassID="77ab7fdd-dcdf-465d-9906-7a330ca1e738" Version="8">

    <ClipName>A005_01231137_C004.braw</ClipName>

    <MediaInPoint>1577778048000000</MediaInPoint>

    <MediaOutPoint>1621427734080000</MediaOutPoint>

    <MediaFrameRate>10594584000</MediaFrameRate>

    <TimecodeFormat>110</TimecodeFormat>

</ClipLoggingInfo>


is changed to this : 

    <ClipLoggingInfo ObjectID="40" ClassID="77ab7fdd-dcdf-465d-9906-7a330ca1e738" Version="8">

    <ClipName>A005_01231137_C004.braw</ClipName>

    <MediaInPoint>1577778048000000</MediaInPoint>

    <MediaOutPoint>1621427734080000</MediaOutPoint>

    <MediaFrameRate>5292000</MediaFrameRate>

    <TimecodeFormat>200</TimecodeFormat>

</ClipLoggingInfo>

Also, timecode when opening PPro project goes from 01:43:25:03 to 01:43:31:16000, the latter timecode coming from the project after relocation and this timecode doesn't make sense at all (16000 frames ?)

Please investigate and fix this issue it is very annoying and preventing users to edit in good conditions with Premiere Pro it is quite urgent

Thanks,
Antoine

Steps to reproduce:

1. Throw any clip on your timeline


2. Add 3 Position keyframes. (The bug is more obvious if they're several seconds apart.) Confirm the position values for all are the default 960,540.


3. Change the position value for the 1st keyframe to 960,0


4. Change the position value for the 2nd keyframe to 950,540

Play and behold... between the 2nd and 3rd keyframe, the clip moves in the Y axis!
And yet the 2nd & 3rd keyframes are from 950,540 to 960,540. So instead of a slow movement to the right, it's adding a down&up movement (my Y value peaks at 579.9 before returning to 540).

• This has been in Premiere forever, and I just tested the same behavior in CC2018 and the latest CC2020.


• If you try to force a "fix", e.g. adding a 955,540 keyframe in between, Premiere will defy you, doing the same up&down maneuver twice now... so you can slice&dice it ad infinitum.


• I used to think it had to do with bezier algorithms I didn't understand, but as you can see, it has nothing to do with that and the behavior occurs with linear "dumb" keyframes.

IMO it's a high priority bug since such a fundamental feature is broken. For years I noticed that many pushes and "Ken Burns" moves behaved oddly, and I finally boiled it down to this basic problem. I also believe this user experienced the same issue, but it was poorly described: https://adobe-video.uservoice.com/forums/911233-premiere-pro/suggestions/36635713-keyframe-movement-that-actually-works

Since upgrading to the latest build of Premier Pro CC 2020, I get random glitchy one-frame lines in my renders from PP (see attached). They appear in different places with each new render, and aren't in the timeline if I go back and check the project... they only appear in the renders. I've tried H264 and ProRes 422 HQ... happens in both codecs. I'm trying to deliver a job today, but I have to re-render multiple times... and then comb through each 8 minute render to see if there's any glitches, which is unnecessarily time-consuming and frustrating. Please fix this! I've never had this problem with any of the earlier builds.

To be clear, this is all about working in a SINGLE project file.

1. Add a command in Window > Projects: New Project Window


2. "Go Back" command ("Up one level") will no longer go back all the way to a project's root level. Bring back this capability.

Since Premiere's UI has been about dockable pane workspace for ages, I don't just open new bins willy-nilly all over the screen (like the Avid way, until recently). I keep several windows/tabs docked and enjoy access to multiple bins as well as an organized workspace. Well, not anymore.

It's always been possible to have several bins (aka project windows) open, was just a bit of a 'hack': Cmd+click a bin, then do whatever you want with the new window. The little change in the "Go Back" button's functionality greatly hinders that basic workspace functionality.

This is one of those "I don't understand how come everyone else is not up in arms about this." :)