Premiere (Beta)

See this bug post in regular forum: https://community.adobe.com/t5/premiere-pro-bugs/issues-creating-new-text-overlay-in-premiere-beta/idi-p/14849710   From my post there:   Build 7 is now up. When I update, I start with Shift+open PR, and reset preferences and cache. And I create a new project.   The text tool is not working: Click and type or Click+drag and type. The keystrokes execute as shortcuts. The Properties panel does not adjust to be the text item. The history panel shows no text creation - just whatever shortcut (e.g. typing I adds an in-point in the sequence).   Clicking the Text tool or hitting T does select the text tool, and it shows in the Program monitor. Click+drag does create a bounding box. Typing anything immediately executes a shortcut.   System info    Application: Premiere Pro (Beta) v25.1.0.7    OS: Windows v10.0.19045, RAM: 63.80 GB GB, CPUs (logical): 16

Steps to reproduce:    1. ... Result: ...Expected: ... System info    Application: Premiere Pro (Beta) v25.1.0.8    OS: macOS v15.0.0, RAM: 16.00 GB GB, CPUs (logical): 12

With the latest update of Adobe Premiere Pro BetaMy templates in the Graphics Templates area do not appear in the timeline area.

Every time I switch workspaces the project window will go to icon view and doesn't retain the folders I have open in list view. I have the workspace saved with the project window in list view but this has no effect on it.

If I have a panel open, eg. a Properties panel, if I scroll down the panel using my mouse's scroll wheel, it is possible to inadvertently change things in pop-up menus in the panel if I happen to scroll on them. This can happen quitre easily:1. Move your mouse to an empty part of the properties panel2. Scroll the scroll wheel to move up (or down)3. See how if a menu scrolls into position under the mouse pointer, you'll change the values I suggest this behaviour is fixed so that it's possible to NOT have pop-up menu values changeable with the mouse wheel unless the user has clicked on that value, or some intelligence is coded in to the scrolling process that maybe checks if the window has been scrolled in the past, say 1 second, and during this 1 second disables the mouse-menu-value-changing behaviour.

I have after starting up Premiere Pro Beta a error message of the Debug Event.The bug log is:Debug Assert failed!{expression (StringValue): "!dvacore::string::StringEndsWith(inPath, DVA_STR("\\"))"hash (Guid): "2eab9b5d-191e-0a26-871a-94a90000005f"lastError (std::uint64_t): "5"sourceFile (StringValue): "D:\main\dva\Drover\dvacore\filesupport\file\win\FileHelper.cpp"sourceFunction (StringValue): "dvacore::filesupport::`anonymous-namespace'::AssertNoTrailingSlash"sourceLine (std::uint64_t): "75"threadID (std::uint64_t): "26892"threadName (StringValue): "main"timestamp (StringValue): "2024-09-18T08:59:39.0Z"} -------------- StackTrace --------------dvacore::debug::DoSimpleAssert ( @ 0) (dvacore.dll+0x00000000001C5D6E)dvacore::filesupport::IteratorHelper::IteratorHelper ( @ 0) (dvacore.dll+0x00000000003774F4)dvacore::filesupport::DirHelper::SystemDir ( @ 0) (dvacore.dll+0x000000000037C88E)dvacore::filesupport::Dir::UserDocsDir ( @ 0) (dvacore.dll+0x0000000000224097)dvacore::filesuppor

This is to confirm an email from @Nicolas from Autokroma re: licensed BRAW Studio being unusable in rather 25.x builds of Premiere Pro. Even though I'm fully updated in my license data, and fully functional in all previous release versions, no 25.x build allow the use of any control in the BRAW panel. I'm hoping this is solved before final release which is coming very soon now.

There is a dramatic color and level shift when selecting the Lumetri controls. Difference is visible on the scopes as well as the monitorFootage is ProRes422 shot on a BlackMagic PCC6KPro film profile, but issue is exhibited with other footage as well. Opening a project in Non beta does not exhibit the problem.

I cannot select the type tool now and be able to type text on screen on Beta version of Premiere

I've noticed that only the project panel can't be dragged out. Has to right click-Undock panel to move to a different place. It's annoying because the saved workspace still bugged. Never saves the position of the project window. I need to replace it manually everytime i make a new project.

Steps to reproduce:    1. Editing clips in the timeline. Result: Audio wave forms are not updating, visually out of sync.Expected: Wave forms to reflect and update based on the edit.Solution: Jumping between Sqeuences seems to refresh the wave forms. System info:    Application: Premiere Pro (Beta) v25.1.0.8    OS: Windows v10.0.19045, RAM: 127.80 GB GB, CPUs (logical): 24

Clips in sequences randomly get a cross-hatch texture on them (see attachment).And audio waveform display is randomly incorrect.

PT_BRBom diaBug reportAs ondas de audio não acompanham quando se dá ripple delete, elas ficam desalinhadas___________________________________________________EN_USGood morningBug reportThe audio waves do not stay in sync when ripple delete is applied; they become misaligned. 

As I use ripple delete, the audio from the next clip doesn't visually update. The audio displays what was previously trimmed off and only readjusts if the clip is moved.

Found a bug in Premiere Beta (25.1). Trying to expand or shrink clip on timeline becomes laggy if this clip is the last on the track. Then, if I drop something on the track in the right of that clip, lag is gone