[Keith Moreau]

Thanks for the feedback Dan, those are exactly the symptoms I see, muted tracks where they were not muted before. I was able to get around it by doing a direct export from Premiere Pro rather than using Adobe Media encoder. Alas I was also hit by the multicam bug but I hear it is now fixed with 7.0.1.

Again, we’re not crazy!

[Keith Moreau]

By the way, have you tried actually editing the Clip-wrapped AVCHD .MOV files in Premiere Pro yet? When I did this (at least with 5.5) it was very sluggish and basically unusable for editing. I only did the wrapping so I could export the XML to use for Pluraleyes (I did find a better way later – render and replace audio). I think this has to do with how Premiere used a Apple quicktime engine to decode the AVCHD (which it does badly).

Anyway, just a FYI for you. I also have tons of footage with AVCHD but organize them by a unique parent directory and put the whole AVCHD structure in there. I would suggest you do that if your collaboration is with another Premiere Pro editor. Premiere Pro CC works well with AVCHD so far for me. So did 5.5 – 6 had a bug with spanned files so I skipped that version.

[Keith Moreau]

Thanks Paul, have you found the speed of CS6 on your Mac to be at least as fast as 5.5? And what Mac are you using, if I may ask?

[Keith Moreau]

Yep, been there, done that, have the T-Shirt. 🙂

Seriously though I and others have posted this exact same ‘essential feature’ deficiency in both the Adobe Premiere Pro Forums as well as using the bug form for literally years, it should not be new news to Adobe. I just wonder sometimes what they are thinking when simple yet vitally important features are just left out. For example, I’m positive that Kevin Monahan – the foremost ‘switcher’ and I believe current Adobe employee, knows about these holes since he used to be a stalwart FCP pro user before moving over to Adobe in the past couple of years. So I have to believe it’s common knowledge.

However, thanks for the links and I encourage people to use them, for whatever it’s worth. 🙂

[Keith Moreau]

I agree, Tom, it is strange how Premiere Pro has holes in it’s functionality in this way, and by evidence of how easy it is to change the XML indicates it would not be a big programming change. It is hard for me to believe that this hasn’t been a problem known by Adobe for quite some time.

In this area as well as finding items in the timeline by string matches are 2 items that really separates Premiere Pro as a pro NLE from even a 8 year old version of Final Cut Pro – that is the sad part. And obviously since the Premiere Pro file is just XML text, its really just an issue of doing a text search, it’s really easy from a programming point of view, it would probably take a very short time for an Adobe developer to address these issues and it would not change the interface in any way that would be difficult to understand or detrimental.

If the Adobe product managers read this forum, they really have to realize this is such an important area, especially for those ‘switchers’ from FCP, simply because switchers will notice these holes right away and it will be a big impediment to using Adobe for professional work.

[Keith Moreau]

If you are adept at using a text editor, you can open the original Premiere Pro file, which is just a big XML text file. In there you can search for the original path(s), and then replace it with the new path(s). Make sure you make a backup of the original file just in case. Not trivial but minutes instead of hours and less error prone.

Hope this helps.

[Keith Moreau]

Select all the clips you want to move, then do the command-drag.

[Keith Moreau]

Check the Adobe Premiere Pro forums I think there is somebody there experiencing your problem and a fix / workaround for it, It may require you create a new project file and import from the bloating one into the new one plus some other tweaks.

[Keith Moreau]

Actually I found it, it’s Page Up, previous edit point. Now I can map this to whatever I want. Thanks for responding so quickly.

[Keith Moreau]

I have that checked, I think it is a good idea to have that one checked. This means when you enter meta data for a clip into Premiere Pro it gets saved in the sidecar file as well as premiere pro project, I believe. I have it checked and have not seen adverse effects.