Questions

In Premiere Pro Beta version 23.1, build 40 or later, you will find new magnification (zoom) factors of 800% and 1600% have been added to the Source and Program Monitors. These new options can be useful for creating intricate masks or inspecting small details in your footage.        You will see these new options in the magnification menus in the source and program monitor window, the context menu, and the application View Menu   Note: Custom Keyboard Shortcuts can be assigned to the Program Monitor to make it easier and faster to zoom in, zoom out and zoom to fit.  The Program Monitor needs to be in focus for these shortcuts to work.  These functions do not have a shortcut mapped by default, but you can map your own. Zoom Monitor In Zoom Monitor Out Zoom Monitor To Fit   We want to know what you think.  Please join the conversation below.                

Hello, We are on PC's. Z840 -64Gig Ram, 10Gbps connection to storage.We. are on 22.4. but been testing the beta's too. We have with bigger project the issue that SEND TO AME not works. It gets stuck on 75% of the program bar. If we go to AME settings and deselect : import sequence native . It seems to work, the project loads into AME. Downside. we can not activate that he not encodes with offline media. And second one, we had some project who had a 5h render time. (instead of 10min).  A direct export out of Adobe Always works. And is fast 10-13min on these projects, what is good.   When i put that project and media on a local SSD. And try the SEND TO AME again( from the local media) it works perfect, no need to change preferences on AME, all works fine and fast . So fast conclusion... it is an network issue. Because we see on the network scans that AME is scanning for all the files.. but never seems to stop scanning. We let it open for 2H, but still stuck

Just wanted to report that I'm seeing a tremendous improvement in stability and performance using Beta 23.x on our new M1 macs. On 22.x we were seeing constant hangs and crashes. So much so it was severly impacting our work output. We are a team of 5 editors and artists and had thought upgrading to the latest M1 systems would only be a positive thing. (Based on the reviews and experiences we read before hand.) NOPE! It was so much pain! However, 23.x appears to be addressed those issues and our team is looking forward to updating to 23 when it releases. (I, for one, will be working on Beta 23 until then.) Cheers!

 This message keeps appearing on my timeline and audio stops.  I stop playback and then it's fine but keeps appearing.SPECS (ATTACHED)I am running an AMD 24 core threadripper3960 (3.8ghz)  and Nvidia GeForce RTX3070 graphics card, TRX40 Aurus Pro WIfi.  32mb of RAM so a pretty powerful computer. Sound harware: C4RG9x (NVIDIA)SPDIF Interface, Realtek USB2.I have searched forums but not seen any resolution for this issue.

HiI am having an issue with this Beta release where some of the functions of my Loupedeck CT are not working. Specifically, I am not able to use the dials for position keyframing, for scale adjustments, crop, rotation, opacityBestAlex

I wish we could change the color of the wireframe in the Program monitor. When working in high resolution and blue images the wireframe is very hard to find and view. E.g points in 4 color gradient, ramp, mask.   https://adobe-video.uservoice.com/forums/911233-premiere-pro/suggestions/45760513-change-color-wireframe-program-monitor  

Premiere Beta runs out of memory on my Mac Mini M1 (16GB RAM). To be specific, the window that pops up is from Mac OS, and Premiere seems to be OK but I save and close to be safe. The weird thing is, the popup claims Premiere Beta is using 70GB memory. But I have it configured to optimize for "Memory" (not "Performance") and to use 8GB memory max. The project has over 100 raw media footage files in it, each 2-3 minutes long. They're not all in use in the open Sequences, but they're imported in the project. Is Premiere Beta loading all of those clips in RAM, even if not used in any open sequences?

Premiere still uses the old FCP7 XML format, right?   I keep getting hammered by colorists/finishers that for the love of all that's Holy, could the Premiere team please freaking update the XML used.   Resolve/FCP/Avid all can use a newer format that works quite well between apps, and the Premiere process ... is a slog of conforming in comparison.   Neil

I am trying to find the most fluid workflow for various language editions of a video using the new caption features in Premiere Pro Beta. I have been accepted to the testing program and see that the trascription feature works well. However I would like to import a trascript already done professionally and see that the "import transcript" feature is greyed out. Will this be available in the future? 

I imported 4k HDR video files from my IPhone 12 Pro Max and the beta converted these to Rec.709. I went to drop them on my HDR time line and theycame out as Rec.709. The video quality was terrible until I went back and Modified the clipt to interpret the footage as Rec.2100 HLG to match my time line. This brought the clip back to life. A previoius video I put out, where I did not notice this, looks poorer quality than on the original content and it already out so that I cannot change it.  The IPhone is recording HDR video. Although I know Premier has had problems with video clips being treated at Rec.709 in the past this is wrong and for people looking to create HDR video which is now supported on YouTube and Facebook more and more people like me are putting out HDR content to deliver better quality. This was clearly a temporary hack to solve another problem. Please correct this and make people aware that it is up to the author to properly represent the timeline and not for A

See this thread in the regular forum.: https://community.adobe.com/t5/premiere-pro-discussions/work-area-bar-color-invisible-after-22-6-1-update/td-p/13184070   Show work area. Set work area. The "bar" area that is active no longer shows a color indication.   System info    Application: Premiere Pro (Beta) v23.1.0.5    OS: Windows v10.0.19043, RAM: 63.80 GB GB, CPUs (logical): 16

Steps to reproduce:    1. Open media browser where 12 bit Prores RAW files are located Result:  Getting error "Frame substitution recursion attempt aborting after multiple attempts on file:" then it shows the file path. All the files are 12 bit Prores RAW. The thumbnails also do not display in media browser. These files work fine in Premiere 14.5Expected: I should be able to see the thumbnail previews and import files. After I bring files into premiere via media browser, none of the files can be played back. It's just a black screen on the Program monitor System info    Application: Premiere Pro (Beta) v15.2.0.8    OS: Windows v10.0.19041, RAM: 127.91 GB, CPUs (logical): 32

Hi!Finaly you nailed it, and Hebrew captions (RTL) worked perfectley. but since the last Beta update (Feb 13th), the captions are reversed again! in graphic preference panel its set to  South Asian and Middle Eastern and in text pannel its seems fine, but in the program monitor it is still reversed.please fix it for us Hebrew users! ThanksAmi

Hello..i have updated adobe premiere but i can't see the( remix tool).

I know this effect is no longer supported but your software does not show the fast color corrector in the effects so that I can remove it and use an alternative technique to replace it. So, I constanntly get the error. During testing of version 23 of the media encoder this caused it to blow up on mac silicon. If you are not going to support something give us the chance to remove it. It is not even visible in the effects to delete it. What other non-supported effects do you have this problem with and what are the ramifications on Apple silicon of not being able to remove it? Please fix this

Fergus, I am using the beta PP and I am not given the option on where to save the project. The option to select a location to save the project is not available. Editing with a 13 " M1 Mac Book Pro, 16 GB memory. The option to save the project of course is available on PP 2021 and 2022. Thanks for any info you can provide.  

I've reinstalled the public beta several times.   I can't get it to download and actually apply my CC settings. I can't get it to actually OPEN a project created in a 2023 created Production. At least, as far as say ... showing ANY panels.   I get a blank screen. As in ... I can't get the workspaces to actually do anything from the menu, they're grayed out.   I can't get it to 'see' any of my prefs or keyboard shortcuts, my 7 custom workspaces, zilch. I do get a panel that opens on another monitor with the Production panel on it.   If I click a project in that Production panel, I get a cascade of panels across that screen ... Timeline, Program Monitor, Source, and ECP panels. All in a cascade of separate panels.   This is totally unworkable.   Win 10, Ryzen 3960X 24 core, 128GB of RAM, 2080Ti, and every other version back to Pr2019 operating perfectly on this machine.   Neil  

Just found out today when updating the beta that future versions will require Mac OS 11 Big Sur going forward. A heads up would've been appreciated if that was the route things were going. Luckily I have a home computer with Monterey but I'll have to wait to try out any future beta builds going forward

any guys happened? any help? just back to the 22.5 for safe so far.......

 There are no choices even in the drop down.Beta 23.0.0 b16 

I think it would be very cool if Adobe filmed and posted a tutorial showing in depth on how to get the most out of posting to Instagram. 

Can we please have some folder structure in the Preset Manager. The list is too long and a b..... to search.

Macbook Air, M1 processor, 8 core CPU and 8 core GPU. With right mouse click i can choose scopes from the menu, but they won't show up. Panel stays black.I use the up-to-date version of Premiere on june 16th. Maybe that's the problem?It worked without any problems until Premiere update and/or Mac OS update (Bof Sur).Both updates around the same time.  

Ok ok I know you're not supposed to overwrite files that are in a live project, but I confess I do it all the time because it means I'm always using the right version of clips. I work a lot with After Effects, so a typical edit in Premiere will be a string of AE renders. Of course, Premiere has never particularly liked this because the media temporarily dissapears, but recently it causes a full freeze, vs what happens in After Effects, where you get an offline warning and app remains stable. I think it should be fully robust and have a way of dealing with offline events like this.  Side bar: I also like in AE where you can reload, vs open the cumbersome dialogue to re-browse for clips. Thanks!

@Fergus Kousha @mattchristensen et al ...   Why is it so freaking impossible to get Premiere Pro to simply apply my prefences to a new version?   I can have my prefs upload-synced in the previous version. Then tell the new version to download sync my prefs.   It says it does.   But not a D*&M thing comes through!   What the hay, folks?!   Do I have to MANUALLY find all the files, and copy them to a new location, AGAIN?????   A bit miffed here, as might be noted ...