Mac version 23.3.0   When I match frame any clip or audio, it sets the In point correctly, but not the Out point. So when I cut it back into the sequence, it is wrong and annoying to fix. Mutliple clips and multiple projects.   Is anyone else experiencing this issue? ... View more

Hi, So I am working on a Mac Pro with the newest version of Premiere (12.0 Build 224) with Proxies. I'm also working with another Editor. When she sent me her project file, I opened it, reconnected the her media with mine and copied her sequences in my timeline. When I opened the project again, her audio files and proxies regenerated in my project. So now I have duplicate media in my project. This seems to be a common Premiere problem that they cannot solve no matter how many times I ask about it. But here's where it starts getting weird and might be a new bug. I started working on my MB Pro laptop. And all of a sudden, Premiere must have generated duplicate files for both the Proxies and Audio files (Refer to screenshots). It basically put (_1 - _4) at the end of every file. They are small (less than 50 KB) and cannot be imported into Premiere (unsupported or damaged file). So now I have thousands of these files on my drive and no idea why. Any ideas? Anyone know a quick way to delete these useless files? Thanks, Tom ... View more

Let's talk about the giant elephant in the room. Premiere is a great product. When Apple put their head in their a** and ruined FCP, Adobe stepped up and was huge at taking over the reigns and making Premiere an awesome successor for small projects. However, it still has a major, major flaw. It is absolutely awful in a team environment. It would be a giant mistake to use this software on a networked project. Here's the issue. A company creates a project and gives it to 2 Editors, call them A and B. Same starting point, same media, same nests, same location for media, etc... A works on a sequence Called S1. B works on a sequence called S2. A finishes S1 and tells B to import it. B tries importing S1 and everything seems fine. Joke's on B. If you right-click on the media in S1 and hit "Reveal in Project," nothing happens. B is in for a giant surprise. When B closes project and reopens it, all of the media in S1 has now been re-imported and cloned. B now has a nightmare of a project where there is duplicate media, audio, nests, galore. There is no way to tell the media in S1 to refer to the media that was in B's project. Now, with a few clips and a sequence or two, it is not a huge deal. But imagine this process being repeated by dozens of editors on a project with thousands of clips. Logistically, it might be easier to figure out financial systems than understand what is going on in the project window. Why does this happen and can/will Adobe do anything about it? My best guess is it has to do with a fundamental flaw in how Premiere processes audio. In the preference pane, you specify how you want to deal with audio. So, if you like specifying stereo clips as mono or whatever, and someone likes something different, Premiere cannot process these as the same clip. So, for instance, A likes using stereo because it takes up less tracks. B is more professional and likes using mono for the control. Premiere then cannot process these clips as being the same thing. It, for some ridiculously odd reason wants to think these clips are somehow fundamentally different. Therefore it thinks it needs to re-import these clips to create the nightmare in the project pane. Can B just delete the duplicate? Absolutely not because Premiere wants to keep them both. What you end up with is a giant logistical nightmare. And heaven help A if A was foolish enough to upgrade Premiere before B was ready. So, for example, Adobe launches an update and A clicks mindlessly to update the software, taking a chance that there is not a bad bug in the update. B decides to hold off for a couple of days. However, when B tries to import A's sequences, Premiere cannot read them. There is absolutely no backwards compatibility between, not only different releases, but the updates as well. So between the inability for Premiere to read projects created with different versions of the software and wanting to re-import the same media over and over again, Premiere is terrible software on networked environments. So, for small little projects with one Editor, the software is incredible. But, for large projects with lots of media and lots of Editors, I think Premiere has too many problems. Are there workarounds? Sometimes, I try to get everyone to get Premiere to interpret audio the same way. It works sometimes, but not others. No rhyme or reason. Sometimes opening someone else's project on your computer works. Sometimes not. No rhyme or reason. Has anyone else experienced these issues? What do people think? -- Tom ... View more

I am getting this error trying to attach proxies I made from Premiere 2017 on a Mac. The 4K footage was shot 24P, 4 mono channels on C300 Mark 2. I have tried making the proxies Quicktime with ProRes 1280x720 and GoPro Cineform 1280x720. Besides bigger frame sizes, those are the only 2 options (I also tried the larger QT ProRes setting, same result). The proxies get created just fine and, like the source, they have 4 channels of mono audio. However, nothing shows up in the Proxy tab in the Project window. When I try to attach manually, I get this error: "Proxy Media and Full Resolution Media must have matching audio channels." I don't know what else to do. Any ideas? Thanks, Tom ... View more