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

[excited_Genie16B8]

Joe,

I've edited your original post to include the two cameras I know for certain do not exhibit the bug.  I will continue to update that as (and if) other people upload their media for testing.

[Stan Jones]

I've edited [Joe's] original post ....

What post number is the edited list?

[excited_Genie16B8]

The original, first post that started this thread.

[Stan Jones]

Duh. I conjured up that you were editing one of his long lists of reports.

[GAPmedia]

Warning:

To those of you who have been waiting months to a year to use Adobe Premiere to its full potential...   If you don't already know...

Adobe CC introduced another major bug! 

I have been following this thread for months so I felt an obligation to inform the community members I have suffered alongside.

I am also trying to inform you because Adobe won't.  Yet again, they are disastrously failing to inform customers of avoidable problems. 

If you upgraded to Premiere CC to fix the AVHCD problem, you could be out of the frying pan and into the fire like I was. 

The new bug is described in this thread.  http://forums.adobe.com/message/5490602#5490602

Bug Overview:

After saving multicam edits, and reopening a project, multicam edits may loose their link to the location in a clip.  The result is that every angle switch restarts at the beginning of a clip.  Many of us have lost hours of work like this.  The problem may ocurr at any point and ruin work performed prior upon saving and re-opening. 

There is a work around described on the thread above to prevent the problem from occurring, but once it does, a project is lost and can only revert to a backup.

I hope this spares some of you the trouble and loss of being struck by the second bug in a row like I was. 

I also hope to enlist the help of some of you who would like to join me in demanding that Adobe communicate more openly with their customers. 

Again, many people have also been hurt by Adobe's failure to inform customers of a huge problem that they knew about prior to the release of Premiere CC. 

Like the AVHCD bug, so many of us could have been spared weeks to months of lost wages and clients if Adobe simply informed Premiere users that there were some issues with the update.  As people could have stayed with CS5 for a while to avoid the AVHCD bug, users on this thread could have stayed with CS6 for a while until the Multicam bug was fixed, if they needed that feature. 

On that thread, I posted the request I quoted below.  Please join us in demanding greater responsibility for communication from Adobe.

please join me in making a feature request:

That Adobe add notifications about important software issues, updates and work-arounds...

1. to the start pages of applications
2. and to the Application manager (so that users may make informed decisions about weather or not an update may introduce issues into their workflows prior to installing.)
   

If they can use those platforms to provide tips and adds, they should also be effective for informing their customers.

Feature requests can be entered at the link below and are prioritized by the number of requests for a certain feature.

https://www.adobe.com/cfusion/mmform/index.cfm?name=wishform

[Stan Jones]

Adobe CC introduced another major bug!

I hear your pain, but please don't trash all these threads by posting so much content. "New bug" and "file request" and "here's a link" should work as well as anything.

[GAPmedia]

Please understand, the three threads regarding the AVHCD bug do not by any means include all the same people. 
These two problems have cost me dearly financially and in time and credibility.  If someone could have saved me this trouble, my gratitude would be beyond words. 

So, That's all I hope to accomplish. 

True, I am very frustrated and disappointed, but I'm trying hard to turn frustration toward advocating positive solutions. 
Do you think we can encourage some positive change here?

[excited_Genie16B8]

I'm afraid I can't join you in your feature request.  Adding notifications in that way I would consider intrusive and unwanted.  The much better option is a Known Issues page or section on the Adobe web site, easy to find for current customers, categorized by program, version and OS, and actually required reading before purchase for new customers (or at least a required click through).

At a bare minimum, there should be a readme for every program that pops up immediately after a successful install and before running the program.  Many software programs do this already.

[GAPmedia]

That's a good suggestion and could be a better idea.  All the programs have different welcome screens or none at all.  I don't know if you use Dreamweaver or Flash, but it they are unique in that they have always had sort of a bulletin board in their welcome screen.  These change frequently and advertise features, add-ons, and resources. 

I was thinking that would be a good place for notices as well, but I could see where someone could find these intrusive.

See the screenshots below.

I just realized that those are the only ones like that.  I wonder if that is a holdover from the Macromedia days?

[Alan_Craven]

I like this ReadMe or Release notes concept.  I would much prefer that to the inevitably far briefer start page notifications.

The much reviled Matrox provide Release Notes with a complete list of known issues, as well as a list of corrected problems, plus possible work-arounds for problems, with each driver release.

Of course this does not help if the publisher is unaware of the issue.  It would seem that better beta testing is the order of the day there.

[Guest]

I'm afraid you chose the least efficient way to communicate your idea:
- hardly any Forum user would expect an information about either bugs or feature requests unrelated to the topic. Yet smaller amount of Forum users would read all comments in a lengthy thread just for the sake of being aware of everything;
- most participant, who replied in this thread, already unsubscribed from e-mail notifications and will certainly miss your input, while those who are still monitoring comments here are fully aware of the new bug in CC multicam;
- hijacking a thread is not a best practice in general.

Therefore, please
- start a brand new thread so as to propose your feature request regard to notifications on Welcome screens;
- be stick to the subject and provide a spanned AVCHD sample from your camera if you really want to give a hand on that matter.

[GAPmedia]

You are absolutely correct about starting a new thread.  Which I did here:  Requesting a Means of Notification about bugs & issues from Adobe

If there are any further responces on this topic please post them there.

In reply to your earlier request:  The link below is to one .mts segment of a spanned AVHCD video.  The footage is from a brand new Canon XA10.  It was the first sequence I tried to play from this shoot immediatly choking Premiere CS6.

https://docs.google.com/file/d/0Bz1DaLFk8wbFOG5IWW1aY1c0blk/edit?usp=sharing

To make the problem identically reproducable, I think I would have to send the whole intact file structure of one of my SD cards.  Those are about 40GB each.  The segments wouldn't play on their own either though.

Please note I am not having any problems with the AVHCD bug since the release of CC.  Just that I still cant edit them because of that multicam bug.  But as I am writing this I hear the fix was released.  So that one only lasted about a month.  Thank goodness.

[excited_Genie16B8]

To make the problem identically reproducable, I think I would have to send the whole intact file structure of one of my SD cards.

Yup.  You can always shoot some junk footage for upload.  Just make sure it's over 20 minutes.

[Stan Jones]

See Fuzzy's method at post

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

He used 7z compression, not because it saved much size, but to keep the folder structure intact. He just shot traffic - there's constant movement and sound, so easy to monitor. His 7z was just over 7 gig.

While the promised fix for CS6 makes this less of an issue, the fix is only promised, and I'm curious! So far, we don't have a sample of a "bad" file/camera.

[ExactImage]

Stan Jones wrote:

See Fuzzy's method at post

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

He used 7z compression, not because it saved much size, but to keep the folder structure intact. He just shot traffic - there's constant movement and sound, so easy to monitor. His 7z was just over 7 gig.

While the promised fix for CS6 makes this less of an issue, the fix is only promised, and I'm curious! So far, we don't have a sample of a "bad" file/camera.

I first reported this problem on May 10th last year !!!!   http://forums.adobe.com/message/4395645#4395645

I made a 4GB or 5GB project available to Adobe shortly after and they downloaded it and confirmed they could repeate the problem. 

This contained footage from a Canon HF-G10 that showed the problem in a CS6 project.  

[Guest]

As I mentioned in one of my previous comments, the purpose of this thread and public samples library in particular is different from giving files to Adobe so that they can reproduce the bug. Rather we ourselves need these samples so that we can test Adobe software and make context-aware decision if not while choosing a camera, then while deciding on upgrade. Shooting a sample and uploading it to Google Drive takes not so much time...

[ExactImage]

Appologies.  I will create a similar file (using a slate) within a day or so.

[Edit] It's recording right now.

[ExactImage]

Ok - I have a 42 min avchd clip captured, copied as the entire card, verified it exhibits the problem in CS6 and is now uploading to Google Drive.   It's 7.45GB so it's going to take a while, probably overnight.   I'll post a link when it's there (probably in the morning).

[Stan Jones]

Excellent. Look forward to testing.

[John T Smith]

No date given, but 'the fix is in' for this bug http://forums.adobe.com/message/5493187#5493187

[ExactImage]

Ok - here we go.  42 minutes of slate shot on a Canon HF G10.  Play a few frames from the start then try to move the play head to 30 mins and see what happens

The ZIP file has a single folder in it called AVCHD Test.  Inside there is a full card copy.   Note I'm in a Pal area so this is 25p footage.

https://docs.google.com/file/d/0B-0vO4a8_of4V3d0VVdNYUJGV0k/edit?usp=sharing

[Guest]

Sounds like I can't extract files from this ZIP: Windows reports the zipped folder as invalid; 7z can open the file, but reports dozen of 'Unsupported compression method' errors and just hangs after a while. I re-downloaded ZIP file a couple of times to ensure there are no download errors. The check sums calculated by 7z are:

[ExactImage]

Hmmm..... this was a simple right click and compress to ZIP on a Mac

I just copied the file to our Windows7 system and opened using WinRar no problem.  It's possible the file on Google is corrupt, so if you can try with WinRar (free) and it still doesn't work then let me know and I'll re-upload it. 

[Guest]

The issue is not I can't open the ZIP, the issue is I can't extract files from the ZIP. WinRAR (which is not by the way quite free) also reports an error:

I tried to repair the archive with no avail so far. So, please check whether you can actually extract files from your archive and if so, reupload the file on Google Drive.

[ExactImage]

How big is the file you are downloading (as it sits on your HDD) ?   I just tried downloading this and it appeared to termiate normally buy was only 1.7GB, which would explain a lot.

SHA1 should be f65b552876706721eda4d4557cde64a663e9395f