Premiere (Beta)

With the evolution of AI and ll these other products like TOPAZ i feel we pay enough monthly to get an in house feature like upscaling to 4K and 8KAobe should become a 1 stop shop 

Getting a crash on open with this on latest build.  Debug Assert failed!{expression: "false"hash: "dc3a8553-0e6a-b4c2-f8ed-78a100000030"message: "You tried to register the BetaFeature RemoveSyncSettings that is already registered, or with a duplicate JIRA ID DVAPR-4245935 that has already been registered."sourceFile: "D:\main\dva\shared\adobe\dvaappsupport\feature\src\BetaFeature.cpp"sourceFunction: "dvaappsupport::feature::BetaFeature::BetaFeature"sourceLine: "346"threadID: "31328"timestamp: "2023-08-30T17:25:35.0Z"} -------------- StackTrace --------------dvaappsupport::feature::BetaFeature::BetaFeature ( @ 0) (dvaappsupport.dll+0x0000000000138C4F)dvaappsupport::feature::BetaFeature::BetaFeature ( @ 0) (Frontend.dll+0x0000000000003F0F)initterm ( @ 0) (ucrtbase.dll+0x0000000000024EAD)FE::Run ( @ 0) (Frontend.dll+0x00000000004C8B2E)FE::Run ( @ 0) (Frontend.dll+0x00000000004C8CA4)RtlActivateActivationContextUnsafeFast ( @ 0) (ntdll.dll+0x000000000002868F)RtlEnumerateEntry

Version: Premiere Pro (Beta) v24.1.0.1 (2023-08-30)ACC Version: 5.11.0.522Computer: MacBook Pro 2023 M2 MaxDebug Assert failed! {expression: "false"hash: "dc3a8553-0e6a-b4c2-f8ed-78a100000030"lastError: "22"message: "You tried to register the BetaFeature RemoveSyncSettings that is already registered, or with a duplicate JIRA ID DVAPR-4245935 that has already been registered."sourceFile: "/Users/dvaeng/main/dva/shared/adobe/dvaappsupport/feature/src/BetaFeature.cpp"sourceFunction: "dvaappsupport::feature::BetaFeature::BetaFeature(const char *, dvaappsupport::feature::FeatureStage, dvacore::LocStringID, dvacore::LocStringID, const char *, dvaappsupport::feature::VisibilityInAllClientApps, dvaappsupport::feature::EnablementChanges, dvaappsupport::feature::DefaultEnablement)"sourceLine: "346"threadID: "148652"timestamp: "2023-08-31T02:58:47.0Z"}    dvaappsupport::feature::BetaFeature::BetaFeature(char const*, dvaappsupport::feature::FeatureStage, char const*, char

As a part of modernization and core updates, Adobe video products are moving to version 11.8 of the CUDA Toolkit in our upcoming beta releases. The rollout is intended to not have any impact on the plugin functionality, compatibility or performance.   The change is planned for the second week of September.   As we release this feature into our Beta builds, please take the time to install the builds and ensure that your plugins continue to function as expected.   We will also send additional communication and update our documentation on best practices to minimize impact on plugins, with any future CUDA SDK Updates.   Please let us know if you have concerns or encounter issues.

When we play a HDcamEX 35 PAL (420) MXF clip in a 1080i sequences we get random green flashes.These green flashes also export to output renders.This clip works fine in CC2023 and earlier.So something is broken in the MXF OP1a decoder....We don't see it with HDCAM 50 422 PAL 1080i stepsput a HDcamEX 35 PAL(420) 1080i in a matched sequence.playback MXF File details:Wrapper type: MXF OP1a (type: SingleItem SinglePackage MultiTrack Stream Internal)File generated by: Adobe Inc., Adobe Media Encoder (22.1.1)MPEG-2 420 MPHL 

Last night I updated my Premiere Pro Beta to v. 24.0. Everything worked fine for about one hour and after that when I was about to start exporting my project - which I've worked for months - the whole software crashed. After that I've tried to open the project but it only loads it to 69% and then nothing happens. I've tried to open different autosave files and importing the project to a different project as well but same thing. I guess the recent update has something to do with it and might have a bug.

NEW: Retain your custom export destinations for all clips and sequences in any project!    Previously, custom destinations were saved per sequence with no easy way to share them with other sequences and projects.    Now you can add and edit a single set of custom destinations in Export mode that are available globally. Simply open a sequence or clip In Export mode and set up multiple custom destinations – those will now be available globally.    Note: for sequences, presets assigned to custom destinations are unique to each sequence.  For clips, presets assigned to custom destinations are shared across all clips.    We want to know what you think.  Please join the conversation below.   

Could we get an option to auto tone map superwhites?Footage from Sony A7Siii (S-Cinetone, Cine4 etc) looks blown out on import and have to bring whites down on each clip. 

I've been using the new Auto Transcriptions Captions feature for all of our programs (and since MacCaption is EOL, why not move to some Adobe magic). However, I have a lot of painpoints. 1. Please add a way to save Captions formats/layouts to apply to different projects. Right now, I have to set this up each time. 2. Add a way to integrate Speaker Nmes into the caption workflow. Right now I have to manually type in ">PERSON NAME: " before the first word, and Premiere doesn't know that's introducing the person talking. It's a clunky workaround, especially since it can differentiate speakers. A checkbox enabling "insert speaker names into captions" would be great. 3. Many times the generated script includes a word at the end of a section which belongs to the next person's section. There's not a way to click in and say, move down or merge with below and there should. In face, the merge and split don't always work, and I wish they did—maybe they would fix some of these is

I am trying to edit a video from Kauai from last summer.  The issue with the beta that I have run into is with DJI Air 2S drone footage.  When I play it back it keeps glitching and does not play smoothly.  But before anyone starts asking, "Well, what computer are you using, graphics card, amount of RAM, and blah, blah, blah" I can play the same footage in the latest PP version and it plays back smoothly. Then this happened.  I was getting so mad at how slow and glitchy the playback was, I decided to render a portion of the video.  I set the In and Out, went to file, export, set the correct video format and pressed enter.  Now if I render the same footage in the latest PP version, it would take a few minutes.  However, when I went to render in the Beta it said it was rending 228 or 409 audio previews and it was going to take over 24 minutes.  The audio previews thing struck me as odd because there is only one audio track under the drone foota

With the latest update, we have fixed the existing LUT indexing issue due to which adding custom LUTs to the technical or creative folders would break the previous relationship between all clips and LUTs selected and users had to manually re-link the clips.   Now, users can add custom LUTs without any impact to existing projects and clips. The custom LUTs added to the ‘Creative’ or ‘Technical’ folders will show up in the LUT dropdown when users launches Premiere and creates a new project. This will not impact LUTs selected in existing clips.   This impacts the following workflows - Adding custom LUTs to a clip will not break existing LUT relationships linked to a clip across the project. Transferring the projects between systems with different sets of custom LUTs will work seamlessly. Team projects on systems with different set of LUTs can communicate any changes to the applied Lumetri LUTs without errors. Previously since these changes were based on LUT index in popup -