CS6 / AVCHD / Spanned Clip Bug / What Cameras And Media Types Are Affected?

[joe_bloe_premiere]

This known bug in CS6 has been well documented regarding the potential symptoms, known issues and transcoding workarounds.

Audio and Video glitches | AVCHD footage

It would also be very helpful for CS6 users to be able to specifically identify the problematic cameras and/or media types in order to make informed decisions when purchasing a camera, or when receiving media files with the intent of editing in Premiere CS6.

If there is a definitive list of specific camera manufacturers / models, and/or media types that are affected by this bug, I have not been able to find it.

Of course this bug has been resolved in the June 17th release of the Creative Cloud Subscription update. It remains to be seen if the fix will be back-ported to CS6.

Thanks.

Cameras confirmed as not exhibiting the bug:

Panasonic GH2

Sony HDR SR-12

Cameras confirmed that do have the bug:

Canon Vixia HF G10

[Steven L. Gotz]

Not really. No. I am lost. I may have to just drop this and let those with the problem deal with it without my help. I can't duplicate the problem so I will just butt out, I guess.

I have no reason to shoot AVCHD even though I could if I wanted to. I don't have a reason to want to, so "Thanks for all the fish." but I will get out of your way.

[Stan Jones]

I get that they are VERY upset. I just don't get why and I pride myself on understanding Premiere Pro and this is a hole in my knowledge that I would love to fill.

That is the topic for other threads. The bottom line is that it requires the affected users to transcode their AVCHD footage before it can be used without problems in PR. Event videographers very frequently have spanned clips.

[joe_bloe_premiere]

I see it also as a test as to whether the bug is really related to metadata or not. (I'm accepting the comment that the single file pulled without access to its metadata will not have it.)

Thank you Stan, that is exactly the point.

Jason's post #46:

"I can confirm that, with my source footage, the problem exists

with individual MTS files or the entire directory structure.

It doesn't appear to matter."

This seems to suggest the problem is not the metadata, but instead

the problem is the media file (or its length eg:spanned filesize limit).

If you remove the clips from any reference to the spanning metadata,

and they still demonstrate the same behavior depicted in post  #42,

then is the problem really a spanned clip bug?

Wouldn't that indicate the problem is the media itself?

So... I wonder

Does a single, short roll from the same camera that does not reach

the spanning filesize threshold play in CS6 without error...

with or without any associated metadata?

[excited_Genie16B8]

If you remove the clips from any reference to the spanning metadata, and they still demonstrate the [bug]

I had the same thought, Joe.  I wish I had some media to test with.

[joe_bloe_premiere]

Likewise.

I find it hard to imagine that Adobe guys didn't go through

this exact same excersise when developing CS6.

[excited_Genie16B8]

Well...if they had media that worked fine, like I do...

[joe_bloe_premiere]

True, but as a thorough tester I would have insisted

on trying multiple cameras and media types.

At least all of the cameras I knew were fully supported in CS5.

How many cameras would you think were tested before CS5 was

released with all of the brand new MainConcept decoders built in?

One would hope Adobe maintains media file databases from different

manufacturers on hand in the lab for testing, troubleshooting,

confirming bug fixes in the Creative Cloud Subscription release, etc.

[joe_bloe_premiere]

Hey, Jim.

Would you mind sharing your thoughts on a couple of questions?

Are you entirely confident that the AVCHD bug has truly been

resolved in the new Creative Cloud Subscription release?

Do you think Adobe tested multiple forms of possibly problematic

media types (spanned or not) in order to make this claim for CC?

If yes, then why would you think the same degree of testing

was apparently not performed prior to releasing CS6?

I would hate to speculate that such a seemingly negligent approach

to media testing for CS6 was in fact a deliberate effort to create an

artificial impetus for users to move to the CC Subscription model.

Thoughts?

[Steve_Hoeg]

If you have some problematic media that you would like us to double check has been fixed feel free to send me a PM.

[joe_bloe_premiere]

See posts #66 and #67...

Jim and I both wish we had problematic media to test with.

Maybe you can shed light on a question posed in post #69:

Does Adobe maintain media file databases from different

manufacturers on hand in the lab for testing, troubleshooting,

confirming bug fixes in the Creative Cloud Subscription release, etc.

[Steve_Hoeg]

Yes, we have sets of test media this reproduces with.

[joe_bloe_premiere]

So... what happened with CS6 testing?

How many cameras / media types were tested before CS5 was

released with all of the brand new MainConcept decoders built in?

Was the same degree of camera / media type testing employed

for the CS5 release performed prior to releasing CS6?

If not, why?

I would hate to speculate that such a seemingly negligent approach

to media testing for CS6 was in fact a deliberate effort to create an

artificial impetus for users to move to the CC Subscription model.

[Steve_Hoeg]

Verifying a piece of software as large as Premiere Pro is a complicated process, and here we made a mistake. We are sorry for any inconvenience this has caused and will let you know when we can share more details.

[joe_bloe_premiere]

Thanks for that, but...

You would think that testing media compatibility might be

at or near of the top of the testing list for an editing program.

I would hate to speculate that such a seemingly negligent approach

to media testing for CS6 was in fact a deliberate effort to create an

artificial impetus for users to move to the CC Subscription model.

[excited_Genie16B8]

Are you entirely confident that the AVCHD bug has truly been resolved in the new Creative Cloud Subscription release?

I haven't used it yet, so I only know what Adobe has said.

Do you think Adobe tested multiple forms of possibly problematic media types (spanned or not) in order to make this claim for CC?

I would assume they've made tests with the same media they used to verify the problem in CS6.

If yes, then why would you think the same degree of testing was apparently not performed prior to releasing CS6?

I have no idea how this bug slipped through.  Maybe they only tested shorter clips.  I mean, prior to CS6 there's never been a reason to suspect that longer clips would behave any differently than shorter ones.  I think it'd be unreasonable for Adobe to test every single possible combination of variables that can be accomplished with PP.  It'd take so long that the product would never get released.

I would hate to speculate that such a seemingly negligent approach to media testing for CS6 was in fact a deliberate effort to create an artificial impetus for users to move to the CC Subscription model.

Honestly, that smacks of paranoid conspiracy.  My suspicion is that Adobe made the decision to move to subscription only well after the release of CS6.  And I don't get the impression that the Premiere Pro development team is that unethical a bunch.

[joe_bloe_premiere]

Honestly, that smacks of paranoid conspiracy.

Thanks for the candid reply, Jim.

If it's an honest mistake, they should make good with a CS6 update.

Back to the topic of this thread...

Surely Adobe has developed a list of problematic cameras and/or

media types while in the process of reproducing the CS6 bug,

and while fixing it in the CC release.

It would be very helpful for CS6 users to be able to specifically

identify the problematic cameras and/or media types in order to make

informed decisions when purchasing a camera, or when receiving

media files with the intent of editing in Premiere CS6.

[excited_Genie16B8]

If it's an honest mistake, they should make good with a CS6 update.

I agree.  More so now that CS6 will be the last perpetual license you can buy.

[joe_bloe_premiere]

Jim Simon wrote:

If it's an honest mistake, they should make good with a CS6 update.

I agree.  More so now that CS6 will be the last perpetual license you can buy.

I'm glad we agree on something

(even if it isn't my presumed tendency toward paranoid conspiracies).

[Steven L. Gotz]

I don't think that there is any question that they should fix it in CS6. If they can.

If it is a problem deep inside the stacks of code that have been dramatically changed in CC, it might not even be possible. Otherwise Kevin may have already convinced them to do so.

Actually, since CS6 is the last software you can buy, a 6.1 release that fixes every bug they can possibly fix should not be out of the question.

[tfi_productions_44]

hello,  i am using the cs6 trial of PPRO windows with avchd spanned clip footage from a canon hfs20 camera

i loaded one take of 20gb (2 hours 25 minutes (high school graduation)) onto the timeline

everything plays smooth, scrubs smooth, conformed smoothly, etc.

playing in real time

the only glitch is right at the clip breaks

there is a glitch in the audio

sometimes there is a glitch in the video

i copied the entire folder structure from the hd of the camera onto a computer's hdd

however, i only imported the .mts files from within the 'stream' folder into PPRO

and everything is working properly except the glitches noted above...

j

[Stephen_Spider]

@ tfi productions 44

You did not import the clips normally. Spanned media should be imported with the media browser. A 2 hour and 25 minute take should come in as one clip with no breaks. (that is, if everything worked as it should).

I've had no issue with CS5x and Cannon AVCHD spanned media. Haven't used it with CS6 much.

[tfi_productions_44]

hello, @ Stephen_Spider:

ahhh,  that is really good to know

i've been tracking this whole spanned clip thing for a month

this is the first time i've ever used spanned clips

i will create a new project, import the correct way, and report back

thank you so much for clarifying, cheers, j

[joe_bloe_premiere]

ahhh,  that is really good to know

i will create a new project, import the correct way, and report back

This has been the entire point of this thread.

A bit of reading / comprehension before you post would've helped.

[tfi_productions_44]

hello,  @ joe bloe:

yeah  and to think i teach English to high school studentswith special needs

and get them to get Regents diplomas when they graduate...go figure...cheers, j

a bit of compassion and clarification goes a longer way don't you think?

[joe_bloe_premiere]

a bit of compassion and clarification goes a longer way don't you think?

I think I have shown you plenty of both in past threads.

http://forums.adobe.com/message/5350350#5350350