Via the media browser, just like you're supposed to

Also, there is a related bug in Media Encoder.  Drop this (30 min spanned) file on to a sequence in 5.5 and export via media encoder and it takes around 80 mins to export to H264.   Media Encoder CS6 starts off saying about 80 mins, then it goes up, and up, and up, and up and TBH I gave up at 9+ hours and only 30% encoded.

The problem appears to be that it's reparsing the entire file all the time and this can be seen in the Windows resources monitor (where you can see the files than an App has open and how much it's reading).   Hopefully they figure this one out soon because it's causing me major problems.  

Yes, I've submitted a bug report complete with a sample project demonstrating the problem.

I'm not the only one.  See other topics that mention problems playing back multiple video tracks and multicam.

It makes sense that multicam is the one place it showed up first because that's where you tend to have the longest clips.

And....it's not just one computer.  We have the same problem on 3 PCs here, and a Mac Pro and another editor off site - same problem - repeatable every time.   That's why I sent Adobe a sample project complete with source media.   They grabbed it late Friday so hopefully some one will have recreated the problem in house by now.

Well Jim,  I'm happy for you to download the sample project and see if you have the same problem..... it's only 5GB, but I don't want to post a public link here.....

Sent.

Thank you Sir!   My sanity is restored!

Jim Simon wrote:

 

Yeah, this one is definitely a show stopper.  CS6 is just completely unusable in this current state.

 

I'm kind of glad I don't (yet?) work with AVCHD.

Yes indeed.  That's why I felt compelled to put that sample project together and send to Adobe.  I can't beleive they missed this in beta testing....

Wow.  Just got an email from Adobe acknowledging the problem and it's been passed to engineering.   Let's hope for some quick progress and a fix sooooooon

I just checked on the Mac too and no difference there either.

I just tried to use PP6 with AVCHD for the first time and had no luck.   Clips play for a few seconds and then get completely stuck.   This is video from a Canon HF G10.    Prelude had the same issues, too.

Niels.

I can see that this is an existing problem that is being looked at by Adobe, but thought I'd chime in that it's effecting me too, so they can see it's wide spread. FS100 footage wrapped to .mov, media pending for ages every time you go to a new clip, and then when it does play it will often only play the video.

First edit after moving our company to Adobe to avoid all the transcoding we've been having to do to work in FCP, and I find myself having to transcode most of my footage! Foolishly did all my testing in 5.5, which is now uninstalled. Bit of a shame, hopefully Adobe will get it sorted soon.

Because we're coming from a Final Cut based workflow where it was essential. Also it means anyone can view the files, so helpful for directors and other people other than our editors with Premiere installed. Why wouldn't you do it? It's just re-wrapped, not transcoded. Anyway, the media plays back just as badly when imported directly as .mts files.

I do the same thing, and have run into the exact same issues with MOV wrapped FS100 footage as SimonHy. This was no problem in CS5.5.

Jim Simon wrote:

 

FS100 footage wrapped to .mov

 

Why on earth would you do that?

FYI- One reason that we wrap the footage is beacuse as it stands, there is no good way to catalog and add/manage metadata with AVCHD files- sidecars, ugh. Using Clipwrap to "wrap" the AVCHD files in MOV wrappers provides an extremely fast solution for adding inclusive metadata capabilities to each clip. It takes about the same ammount of time to transfer from card to disk, as it does to "wrap" AVCHD while transferring from card to disk.

I don't see any advantage to keeping MTS files native for working in any NLE.

Harm Millaard wrote:

 

I don't see any advantage to keeping MTS files native for working in any NLE.

 

If you insist on turning the 64 bit nature of PR back into the past and to 32 bit only, you are correct. But why then did you upgrade to a version over CS4? That was 32 bit.

Wait, I'm confused... Are you saying that MTS files are the only type supported in 64bit realm? Because if that were the case, then I'd eat my words.

Perhaps you read me wrong; I merely said that I see no advantages in keeping MTS files native. I did not say that I only see advantages in keeping MOV files.

Anyhow, back to what this thread is really about: AVCHD does not play well in Premiere Pro CS6, regardless of opinions or how it's brought in.