Adobe Community: Premiere Pro CS6 and AVCHD

Premiere Pro CS6 and AVCHD - Should I upgrade or wait?

Jun 3, 2012 9:16 AM

Latest reply: BlueScarecrow, May 20, 2013 3:23 PM

Replies

Currently Being Moderated

15. Jim Simon,

Jun 26, 2012 9:18 AM in reply to Nancy\'sWorld

Report

That would depend on the filter.

|
Mark as:
$Nancy\'sWorld$

Currently Being Moderated

16. Nancy\'sWorld,

Jun 26, 2012 9:32 AM in reply to Jim Simon

Report

Mainly RedGiant Looks, which I could use in PP, I just prefer some text options in AE more.

|
Mark as:
Currently Being Moderated

17. Jim Simon,

Jun 26, 2012 10:04 AM in reply to Nancy\'sWorld

Report

Well, the grain option of that effect would cause a loss of quality, but then that would be the desired outcome of using it.

|
Mark as:
$Nancy\'sWorld$

Currently Being Moderated

18. Nancy\'sWorld,

Jun 26, 2012 11:54 AM in reply to Jim Simon

Report

Thanks, Jim. No grain used. Just basic exposure/gamma/color contrast etc. Anyways, going to try out UT codec today. Thanks again for all the help!

|
Mark as:
Currently Being Moderated

19. BlueScarecrow,

Jan 11, 2013 11:35 AM in reply to Nancy\'sWorld

Report

AVCHD files will never be supported by Adobe until it becomes profitable. Until then they will spin and dance and tell you your computer processor is too slow, or you don't have enough ram or you have the wrong operating system or you have to transcode or buy some more software or hardware... Just like Avid.

I lost thousands of dollars with Avid and wound up throwing my Avid Media Composer in the garbage. Funny... there it seemed to fit fine.

Complacency and greed killed Avid and now it looks like complacency and greed have their sights on Adobe.

Remember: There is a season for all things.

|
Mark as:
Currently Being Moderated

20. Kevin Monahan,

Jan 11, 2013 11:51 AM in reply to BlueScarecrow

Report

BlueScarecrow wrote:

AVCHD files will never be supported by Adobe until it becomes profitable. Until then they will spin and dance and tell you your computer processor is too slow, or you don't have enough ram or you have the wrong operating system or you have to transcode or buy some more software or hardware... Just like Avid.

I lost thousands of dollars with Avid and wound up throwing my Avid Media Composer in the garbage. Funny... there it seemed to fit fine.

Complacency and greed killed Avid and now it looks like complacency and greed have their sights on Adobe.

Remember: There is a season for all things.

I wish you could see how hard we are working on this problem. When there are issues affecting a lot of our customers, we definitely know about it. If that issue is taking a long time to fix, know that there are often times other parties holding up the show. On behalf of Adobe, I apologize that this problem is persisting. We hope to find a fix as soon as possible.

|
Mark as:
Currently Being Moderated

21. Keith Moreau,

Jan 11, 2013 12:22 PM in reply to Kevin Monahan

Report

Kevin, thanks for your post. Wow, I posted this 7 months ago and the spanned AVCHD problem still isn't fixed in CS 6? That's incredible. Tell me I'm misinterpreting your answer.

Thanks much!

-Keith

|
Mark as:
Currently Being Moderated

22. John T Smith,

Jan 11, 2013 12:36 PM in reply to BlueScarecrow

Report

>AVCHD files will never be supported by Adobe

I use PPro 5.0.3 to edit AVCHD from a Canon Vixia HFS100 with zero problems... of course, I am a home hobbyist shooting short family clips that I combine on the timeline, so I currently have no experience with >4Gig "spanned" clips

A program bug is not the same thing as "will never be supported"

I do not work for Adobe so I have NO idea what source code changes were made between CS5-CS5.5-CS6 but my understanding is that CS6 added new features, and new codec support, so finding a bug is very likely going to take time

|
Mark as:
Currently Being Moderated

23. BlueScarecrow,

Jan 11, 2013 12:47 PM in reply to Kevin Monahan

Report

Hope? Hmmmm.

I was hoping to make a career for myself in video production. I invested 10 years and thousands of dollars in Avid and got the same runaround that's evident on this forum. Everytime the software crashed Avid told me to buy something else; that same thread is evident here also.

For a huge conglomerate like Adobe, with all of it's resources, to sit back and hope to find, wish to discover or stumble across a solution is absolutely unconscionable.

The thousands of people that have invested in Adobe need a little better treatment than that.

Ps.

Along time ago I wished out loud in front of my Grandmother.

My Grandmother told me... "Wish in one hand and spit in the other; and see which one fills up the fastest.

God... I love forums.

|
Mark as:
Currently Being Moderated

24. Kevin Monahan,

Jan 11, 2013 4:38 PM in reply to Keith Moreau

Report

Keith Moreau wrote:

Kevin, thanks for your post. Wow, I posted this 7 months ago and the spanned AVCHD problem still isn't fixed in CS 6? That's incredible. Tell me I'm misinterpreting your answer.

Thanks much!

-Keith

Hi Keith,
As an editor that came into the world of software engineering, yes, it is incredible how long things take to fix, change, or upgrade. As I mentioned, sometimes there are road blocks that we have no control over, so that takes more time. This is on my Top Issues list, meaning that it is a top priority for the community. Again, I'm sorry this issue is affecting so many of our users.

|
Mark as:
Currently Being Moderated

25. Kevin Monahan,

Jan 11, 2013 4:43 PM in reply to BlueScarecrow

Report

BlueScarecrow wrote:

Hope? Hmmmm.

I was hoping to make a career for myself in video production. I invested 10 years and thousands of dollars in Avid and got the same runaround that's evident on this forum. Everytime the software crashed Avid told me to buy something else; that same thread is evident here also.

For a huge conglomerate like Adobe, with all of it's resources, to sit back and hope to find, wish to discover or stumble across a solution is absolutely unconscionable.

Pardon me, I didn't mean to say we hope to find a fix. We have a fix. We are just waiting for third-parties to fix their stuff, so we can fix our stuff. Let's hope it gets into an update or CS Next. In the mean time, yep, file a bug report: http://www.adobe.com/go/wish

|
Mark as:
Currently Being Moderated

26. BlueScarecrow,

May 19, 2013 4:00 PM in reply to Kevin Monahan

Report

Dear Kevin,

Over 4 months has passed since my post on Adobe AVCHD issues. You wrote that Adobe has a fix regarding AVCHD files. Please tell me where it is.

Thanks!

Mike

|
Mark as:
Currently Being Moderated

27. Jim Simon,

May 19, 2013 4:06 PM in reply to BlueScarecrow

Report

The fix has been implemented for the new Premiere Pro CC version due out June 17th.

It may or may not get back-ported into CS6.

|
Mark as:
Currently Being Moderated

28. BlueScarecrow,

May 19, 2013 4:08 PM in reply to Jim Simon

Report

Thank you.

|
Mark as:
Currently Being Moderated

29. rmartin215,

May 20, 2013 6:56 AM in reply to Jim Simon

Report

Where do you get your info?

|
Mark as:
Currently Being Moderated

30. tfi productions 44,

May 20, 2013 11:24 AM in reply to rmartin215

Report

hello @ John T Smith

i use 5.03 currently on a win 7 machine
with canon vixia hfs20 camaeras
i have only shot a few times with spanned clips
and didn't edit them, so i don't know if i have the avchd problem or not

have you updated to cs6 PPRO? what are your thoughts please?

i don't think it is fair when adobe staff say earlier in this post in january that there is a fix
for cs6, yet it will only be released via the new PPRO version (and the problem originated
in cs6)

i love PPRO 5.03, but want to use Encore64 bit, and x264pro...

would love to hear from you

cheers, j

|
Mark as:
Currently Being Moderated

31. Kevin Monahan,

May 20, 2013 12:10 PM in reply to rmartin215

Report

rmartin215 wrote:

Where do you get your info?

Hi martin215,
We announced it in another thread.

Thanks,
Kevin

|
Mark as:
Currently Being Moderated

32. Kevin Monahan,

May 20, 2013 12:15 PM in reply to tfi productions 44

Report

tfi productions 44 wrote:

i don't think it is fair when adobe staff say earlier in this post in january that there is a fix
for cs6, yet it will only be released via the new PPRO version (and the problem originated
in cs6)

Hi tfi productions 44,
The fix is in Premiere Pro CC, it's not in Premiere Pro CS6. As I've explained in another post, there was a major architectural change that had to take place to get the fix in, so a fix for CS6 is not trivial, it's extremely complex. That said, please create a feature request to add your voice to those wanting a fix in a Premiere Pro CS6 update: http://www.adobe.com/go/wish

Thanks,
Kevin

|
Mark as:
Currently Being Moderated

33. tfi productions 44,

May 20, 2013 12:30 PM in reply to Kevin Monahan

Report

hello,

et tu, brute? et tu, adobe?

j

|
Mark as:
Currently Being Moderated

34. Kevin Monahan,

May 20, 2013 12:56 PM in reply to tfi productions 44

Report

tfi productions 44,
Only the messenger here: Just trying to get you the latest info is all. The few Adobe employees that are in these forums are in support, quality engineering, etc. We have no control or influence over pricing or subscription models.

Thanks,
Kevin

|
Mark as:
Currently Being Moderated

35. tfi productions 44,

May 20, 2013 1:03 PM in reply to Kevin Monahan

Report

hello,

i am on my best behavior but wanted to say something...

by definition: a fix is for when something is that was not broken breaks

how the adobe godhead sleeps at night is beyond me

hopefully all will be well in the state of denmark...

is there a list of cameras that have/have not issues with the avchd spanned clips?

i use canon hfs20 vixias

thanks, j

ps the serenity prayer comes in handy a lot now

|
Mark as:
Currently Being Moderated

36. BlueScarecrow,

May 20, 2013 3:23 PM in reply to tfi productions 44

Report

The Adobe GodHead (CEO) sleeps very well at night. takes home a wonderful
salary. and takes many a vacation thanks to all of us suckers that buy into
Adobe's buggy software.

A forum is a place to let it out not hold it in. This doesn't mean foul
language, but it does mean telling it like it is.

I've heard that the AVCHD fix is due 17 June of this year; only in the CC
version.

This means that there will be a constant fire under your but to make that
monthly payment; if not. you're out; and if you had any files in the cloud,
you'll have to re-up to get em out. Ouch!

I went through all of this with Avid for a decade and in the end I was the
loser and the CEO was the winner.

Don't buy anything until you see it work.

Mike

|
Mark as: