• Global community
    • Language:
      • Deutsch
      • English
      • Español
      • Français
      • Português
  • 日本語コミュニティ
    Dedicated community for Japanese speakers
  • 한국 커뮤니티
    Dedicated community for Korean speakers
Exit
2

Teams performance issues and bugs after 23.1 update

New Here ,
Dec 16, 2022 Dec 16, 2022

Copy link to clipboard

Copied

We updated to 23.1 a couple days ago and even though the new features and interface adjustments seem great, we are experiencing severe performance issues and bugs. We are all on M1 Macs, 2 Studios, and 1 MBPro. Running Ventura and Monteray OS. We are working on a 5TB promotional video, with roughly 1200 assets off 32 TB Thunderbolt 4 OWC drives. Everything was shot in 4K and 6K BRAW and was working much better in Premiere Pro 23.

 

Now we are having issues with the sequence render indicator being red upon opening the project, it will switch back to yellow after opening the teams project settings window, selecting "ok", then deleting preview files using the prompt that pops up. Seems that preview file indexed locations don't stay put now. This happens on every project open attempt.

 

Also, applying markers to specific clips in the sequence, whether attempting from the menu drop down, or hitting the keyboard, no longer works at all. 

 

Playback performance starts OK when first using the application, but as bouncing around the sequence and making adjustments gets more involved over a short period of time, play back becomes super laggy. Audio meters are delayed and choppy, and overall it just feels clunky and slower than before. Restart the application, re-open the project, and things improve for a short time. 

 

Another oddity that we are seeing, at least on the Mac Studio is that the internal hard drive space is getting eaten up when the project is open, even though all media cache and scratch disks are set to an external Thunderbolt 4 SSD. In my case it's almost 30GB. That space is returned to the internal hard drive after closing Premiere. 

 

Again, all of these issues are related to our use of Teams, which has generally been great prior to this update. Hoping we get fixes on all of this soon, it's really slowing down our progress. 

 

[Moderator note: moved to Team Projects forum for best assistance.]

TOPICS
Error or problem , Hardware or GPU , Performance

Views

432

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Adobe Employee ,
Dec 20, 2022 Dec 20, 2022

Copy link to clipboard

Copied

Hi,

Sorry for your troubles with Team Project, I'll try to address the various issues as best I can.

Render indicator issue: 
Where did you point your scratch-disk for Video-Previews to?

Add Marker not working:
I confirm this behavior and logged a bug for it – A user cannot add a Clip-Marker if the clip is being used in a locked sequence


Playback performance issue:

Do you mind converting the Team Project to a local Project and see if you notice a similar Playback performance degradation in this local project?


internal hard drive space

Are you referring to your machines RAM? We're investigating an issue where some users see memory usage spike on newer Mac machines.
As a possible workaround, it may help to reduce the number of sequences, especially duplicates for backup reasons. You could move these to a linked team project.


Best,
Udo

Udo Pawlik | Sr Software Product Quality Specialist | Adobe | upawlik@adobe.com

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Jan 04, 2023 Jan 04, 2023

Copy link to clipboard

Copied

Hey Udo, 

Thanks for reaching out. Apologies for just now getting back to you. I will respond to each note above individually. 

 

Render indicator issue: 
Where did you point your scratch-disk for Video-Previews to?

- We all typically set our media cache and scratch disks to our OWC external thunderbolt 4 SSDs. They are up to 2800 read/write, so there shouldn't be performance issues there. We have been using them for the past year on previous versions of Premiere and didn't have these performance issues. I also played with switching the cache and scratch to the internal Mac Studio HD, but the problems persist in teams. 

 

Add Marker not working:
I confirm this behavior and logged a bug for it – A user cannot add a Clip-Marker if the clip is being used in a locked sequence. 

- Thanks for doing that. Another bug that we have recently encountered is when you select the edge of a clip in a sequence and "Option" frame left or right, using the arrow keys to extend or trim the edit point, the selection of the edge actually de-selects after a single frame move. So you have to re-select the edge, move one frame, it un-selects, then re-select, etc. It is pretty frustrating and makes it tough to be precise. It didn't function that way previously

 

Playback performance issue:
Do you mind converting the Team Project to a local Project and see if you notice a similar Playback performance degradation in this local project?

- So interestingly enough, the day that I posted this originally, I did convert the team project to an offline "non-team" standard project. I was thinking that it would solve the issues, and improve performance. Unfortunately it didn't help that much. The only thing that seemed to stop happening was the red bar render indicator on the sequence showing up when opening the project. It stayed yellow for each project open, and we didn't have to go through the process of deleting preview files through the menu and prompt window that I noted in my original post. Performance though, was still super laggy, choppy, and got worse the longer the project stayed open. I had to close the project every 30-45 minutes and reopen to gain back some level of efficiency. It feels like something under the hood of Premiere was changed in a massive way with regard to how it handles footage and playback. Now, this was exclusively for BRAW footage as I noted, so I don't have a good basis for other formats at this point. Maybe it's better with RED? MXF? But I don't trust it right now. Our upcoming projects will be done in Premiere 23 until 23.1 gets the kinks worked out.

 

internal hard drive space
Are you referring to your machines RAM? We're investigating an issue where some users see memory usage spike on newer Mac machines.
As a possible workaround, it may help to reduce the number of sequences, especially duplicates for backup reasons. You could move these to a linked team project.

- No, it is actually the physical HD space. I have a stock internal Apple 500GB SSD in my Mac Studio, and it is sitting around 180 GB free right now. When I open this project, whether in team, or non-team format, that 180GB drops to 155GB free. As I continue working in the project, that trickles down to around 150GB free. At that point, the performance gets so bad in Premiere that I use the 150GB mark as an indicator to save and close the project, then re-open. This was my standard repeating process to get this project complete prior to our holiday break. Lots of wasted time.

 

Premiere is the only application that does this to the available HD space. I'm not sure if it's some kind of VRAM overflow or what, but Premiere just eats up what it needs, unchecked, and requires me to monitor my available space. If I wasn't more careful to ensure I had enough free space, I could see this causing serious issues and potential system/application crashes.

 

All in all, Premiere 23 performed far superior to 23.1, whether in teams or not for our M1 Macs.

 

I would be willing to be more involved with testing, reporting, and just helping to work through these challenges if that need arises. We really lean heavily on Premiere and have some long-tenured clients that we've built multiple products for in the application over the years. Our team members are absolutely power users of this software and it is, in a lot of ways, our livelihood. We need to be able to depend on it, and so we are game to get it in a more stable, high-performing condition. 

 

Thanks for taking the time, Udo. Let me know if I can provide more feedback.  

 

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Jan 06, 2023 Jan 06, 2023

Copy link to clipboard

Copied

Just chiming in to say we are experience the exact same issue with 23.1 and braw files, on multiple computers. Initially the issue was also with a complex Teams project, but as with Mobes here, it's not really any better on a private project. You can manually re-render everything that's red on opening, but it will be gone again on next open, and playback remains sluggish. We've had to revert to 23.0 to continue our work – playback functions absolutely fine in this version. Using 2 x M1 Ultra Mac Studios and an M2 Macbook Air.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Engaged ,
Feb 01, 2023 Feb 01, 2023

Copy link to clipboard

Copied

Hello,

Which plugin are you using for BRAW files ? The Blackmagic RAW plugin or BRAW Studio (Autokroma) ? 
If you are using the first one, note that you can test our BRAW Studio third party plugin even if you started your work with the Blackmagic RAW plugin. For that you need to convert the project with the conversion tool inside the BRAW Studio Panel. BRAW Studio has a Free Mode which has the same features than the Blackmagic RAW plugin, so you should not have to pay for anything. 

We didn't experience any change with BRAW playback between 23.0 and 23.1. 
Note : I also know for sure that your Sequence Settings : Preview File Format could be source of bad playback performance ! (Even if previews are not generated : green line above timeline).  You should try to set it as Quicktime ProRes.

Best,

Nicolas from Autokroma

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Mar 14, 2023 Mar 14, 2023

Copy link to clipboard

Copied

LATEST

Thanks Nicolas - we're using Blackmagic at the moment, and _right_ at the end of a feature project, so not really wanting to make a transition at this immediate moment. But we'll definitely check it out when spinning up the next project (and also try upgrading to 23.2 to see if it helps at all...)

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines