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.
5
Replies
AdChoices