Questions

Help!The latest 2 versions of Premiere Pro Beta both send a Crash Report screen up with the message below.  If I ignore the warning, then after the project loads, the video monitors don't show any video, just the remains of the previous window without a redraw. --------------------------------------------------------------------------------------------------------------------------------------------------------------------Expression: insertResult.secondMultiple defined rules exist in sdm dictionaries for the following path (is this an incremental build?): ASSETMGMT|Capture|start|voiceover-recordingProcess: Adobe Premiere Pro (Beta).exeProcess ID: 35476Thread ID: 61380File: ..\..\analytics\src\SDMValidator.cppLine: 420Function: dvaappsupport::analytics::SDMValidator::LoadDirectoryLast Error: 0Assert Dialog Show:trueUnique Hash: 90bb545d-5707-b7b7-6ce9-010400000040-------------- StackTrace --------------dvaappsupport::analytics::SDMUsageLogger::SetOptOutdvaappsupport::analytics

On both Catalina (10.15.7) and Big Sur beta (11.3), I'm seeing stalling and not responding when Premiere & AME are first started after the apps are updated from previous builds.  Sometimes it requires a full computer reboot or just force quitting the apps and relaunching multiple times gets the apps to start up. This is happening on Premiere 15.0 build 27R & Media Encoder 15.0 build 30. Filed the folllowing bug (DVAPR-4229682) with spin dumps and sample process of when the apps freeze up. 

Hi, I currently use Premiere Pro Beta version as I was told a few months ago to use this app instead of the usual Premiere Pro due to bug issues. I have been creating my videos in Beta.  Now I am experiencing an issue when I select "effects" in Beta and the app is crashing / closing on me. I have uninstalled both Beta and the usual Prem Pro and reinstalled. All versions are currently up to date.  Now I am unable to open my Beta created videos in the usual Prem Pro - the error message says that the video was created in a newer version app and therefore cannot be opened in Prem Pro.

Hello,I update Premiere Pro Beta each day. And from yesterday update, I have this error window each time I open Premiere Pro Beta (here with Premiere Pro Beta v22.0.0.70) :  As there is no little cross on the error window, I restart my computer.Does an adobe employee has noticed the same problem ?

Hello,In Premiere Pro Beta project panel (modify tab), I have created 20 subclips.I would like export these 20 subclips, in 20 separate video files.How to do this ?  

Hey everyone, Possible to import a TXT file to use when Transcribing/Captioning a video in PP Beta?  I have some very long videos and fixing punctuation, capitalization, acronyms and so on is very time consuming.  I have done this in YouTube before.  Really hoping it's possible now or in the future with PP! Thanks!

Hi all,  The auto transcription feature is great, it was working well for 2 projects I have since completed. Suddenly out of the blue today it has stopped working. Once it gets to the following image belowI have: Restarted PCUpdated PremLogged out and into Creative Cloud This project I am needing to transcribe is due tomorrow so any quick hacks anyone might have to get this up and running again would be great, thank you!

Getting an Assert Error Dialog Box everytime Premier Pro Beta Starts. Bill Byrnes 

 

Steps to reproduce:    1. Quando abro o Premiere Beta já aparece a seguinte mensagem de erro:Expression: insertResult.secondMultiple defined rules exist in sdm dictionaries for the following path (is this an incremental build?): ASSETMGMT|Capture|start|voiceover-recordingProcess: Adobe Premiere Pro (Beta).exeProcess ID: 11620Thread ID: 18400File: ..\..\analytics\src\SDMValidator.cppLine: 420Function: dvaappsupport::analytics::SDMValidator::LoadDirectoryLast Error: 0Assert Dialog Show:trueUnique Hash: 90bb545d-5707-b7b7-6ce9-010400000040-------------- StackTrace --------------dvaappsupport::analytics::SDMUsageLogger::SetOptOutdvaappsupport::analytics::SDMTransport::LoadBundledDictionariesSyncboost::enable_shared_from_this<twisted::_ConcurrencyPrimitive>::~enable_shared_from_this<twisted::_ConcurrencyPrimitive>dvacore::test::Terminatedvacore::threads::CreateSubExecutorWithFunctionWrapperdvacore::threads::AdaptCurrentEventLoopAsExecutordvacore::threads::Get

Just updated to version 22.0.0 build 70 and now getting this error when starting Premiere:  Presseing Kill process crashes Premiere, pressing Ignore starts Premiere, but Mercury playback engine is software only. 

Hello friends. I was working on a project in Premiere pro Beta yesterday. I upgraded to the latest version 22 build70, and now whenever I turn on an error message and I can't see the video, everything goes black. Does anyone know what to do? Worse, I can't go back to 15 because the file doesn't open because it's newer.

after update the debug error starts

I got a "debug assert failed" screne and attempted to "file bug" when I got this message from Google "This server could not prove that it is jira.corp.adobe.com; its security certificate is not trusted by your computer's operating system. This may be caused by a misconfiguration or an attacker intercepting your connection."  What should I do? I need someone form Adobe to correct my program and not COMMUNITY ASSISTANCE, I pay a lot of money for this program and I need to use it the program. How can I get a really human being from Adobe to help me? 

Al intentar transcribir una pista de audio para generar los subtítulos, me aparece el botón TRANSCRIBIR inhabilitado, con la leyenda en hover "Respuesta de red lenta recibida", y no entiendo el tipo de error ni por qué no está funcionando esa característica.

Steps to reproduce:    1. Create a sequence from a file with a suitable audio track, open Captions Workspace, Click Transcribe, and accept the default.  Result: Nothing happens - Expected: The same sequence in 15.4.1 works perfectly This is the result after waiting 15 minutes. The activity monitor also shows Premiere Pro doing nothing but resting. System info    Application: Premiere Pro (Beta) v22.0.0.63    OS: macOS v11.5.2, RAM: 8.00 GB GB, CPUs (logical): 8

This is so incredibly frustrating. But for some reason, even though there are fields avaialable for camera make/model and lens even, selecting them to view is TOTALLY useless.   No data appears!   In this day and age, with so many heavily meta-based camera formats from RED, Arri, BlackMagic, Sony & Canon, we need to be able to sort and batch things by camera model!   We can't even search by camera model!   Please, please please, fix this immediately!   Sincerely, R. Neil Haugen

I scrub though tons of content in thumbnail view. Usually it takes a little bit for it to go through the "Media Pending" and then I can scrub through pretty quick. After this last update, it is now taking FOREVER to scrub over 1 clip. I'm going to have to switch off of Beta to continue editing because it's killing my speed so much.

How do I import new clips with the new import panel without making a new sequence in an existing project. Is this even possible, or am I missing something. I don't see a way to disable Create New Sequence.   BTW the beta does not draw very well on a 4K monitor W10.  

Same footage converted to prores no problem So guessing this is a codec issue? I have 4 projects with old dv footage: non of them show in the import window.

on IMacPro OSX 10.14.6 , premierePro 22.0 beta immediately crashes on startup, before showing anything ... no detailed error that could help investigating .. nothing...only the ..send report... what i did. What are the requirements for this version ? Did I miss something doing in advance ?

This effect was brought to my attention today, decided to check it out. Likely won't have to use it much myself, but I can see this being handy for tons of folks: A more expanded version of the TC generator, very nice! That said, one thing I recalled about the current TC generator isthat... it isn't very great at generating timecode, and I noticed this new beta effect still has the same issue. I specifically am referring to timecode conversions, and how it handles it (or the lack thereof). When selecting timebases other than the source timebase, it doesn't do any calculations or conversions, it just changes the target frame # at to which increment the seconds counter, resulting in differing real time values. (iex 00;00;10;15 in 29.97 DF is 00:00:13:03 in 23.976 as opposed to 00:00:10:12.). I guess it's just doing [Raw Frame #] / [Timebase Choice] = Timecode. Just figured I'd mention it, could be something useful for someone one day if corrected! Or maybe I'm missing some

Checked out the beta again, and things seem to be moving along well! Kudos to the team! I know the big focus on the new version is Import, Export, and Toolbar. My feedback below is just 1 specific thing from each category that I think needs addressing before it goes primetime. 1.) Import: Ingest SettingsThe Import workflow has a "Import settings" panel, and that's great! However I believe it is missing the best possible feature that can be leveraged here, and that are Ingest settings. Adding options for copy/transcode/create proxy/rename/etc. would be fantastic here. Currently, we'd have to import media the old way to take advantage of this, which bypasses the new workflow entirely. 2.)Export: Crop/Scale optionsWhile not the backbone of every export, I consider it to be a core part of the export environment. Being able to perform an on-export scale or crop is in my opinion, critical, despire how infrequently some may use it. There's plenty of UI space for it too! (above the p

Any updates and ETA on the Prores Raw White Balance and Tint settings?

I forced myself to update last week because my project files were crashing immediately as I opened them. When I updated it fixed that problem but introduced new ones that came with the new update. Before I already had this issue where if you export a sequence, while it's exporting/done it'll automatically take you back to the first sequence in the timeline rather than the one you just exported which is a minor annoyance but what I have noticed since the update is a bigger deal. Now there are glitches in exporting when it comes to video and audio. I have noticed that certain audio clips won't be clipping when I am editing in the timeline but when I export, those clips will now be clipping and will actually do weird things to the audio around it. Usually it will do it when I use "woosh" sound effects for special effect.  The other glitch I have noticed is that certain transitions like the cross zoom will change positions right before ending. Almost as if the transitio