Adobe Community: AVCHD Workflow help

Currently Being Moderated

40. ExactImage,

May 24, 2012 11:38 AM in reply to ZachRosing

Report

Well, I hope you and EVERYONE who has this problem has filled out the bug report because we need to make sure it's super high priority for them and not something that gets put on the back burner because other people are screaming louder about something else.

|

Mark as:

Currently Being Moderated

41. SimonHy,

May 24, 2012 4:46 PM in reply to Jim Simon

Report

Jim Simon wrote:

Why wouldn't you do it? It's just re-wrapped

Because QuickTime is still a 32 bit application, and Premiere Pro needs a 'band-aid' to work with MOV files.

Keep them native. There are plenty of media players than can play the .mts streams directly, including VLC, which is one of the best media players on the planet and available for Windows, Mac and Linux, so pretty much anyone can install and use it.

Thanks, that makes sense. There's a lot involved in changing everything in the company over to a new workflow, and we have a lot of media that's already been wrapped, so will probably still be dealing with .movs for some time to come, but at least I can start heading the ship in the right direction. And all those wrapped files played fine in CS5.5, so I'm still hoping they do get it working better.

|

Mark as:

Currently Being Moderated

42. ACT.onn,

May 30, 2012 12:32 AM in reply to Reg Santo Tomas

Report

Hello All

Add me to the list.

In addition to the problems mentioned above, all of which I have with a project in which I have 1 set of MOV files and 2 sets of AVCHD files (3 cameras at a wedding), I am getting a clip that shows green frames whenever and wherever I stop scrubbing on that clip. I think the green frame = media pending but I haven't seen premiere do that before. This clip plays fine in all the media players I have installed, but premiere garbles it. The other clips from the same camera are fine. The clips from the other 2 cameras are fine. And I have tried copying the offending clip 3 times each to a different hard drive and loaded it into my project. Each attempt failed to change anything.

I was going to recode the footage to make it more palatable for premiere, but I am not sure what to use. Anyone have suggestions? And Jim I did try the UT AVI file format you mentioned, the resulting file was twice the size! Is there a way to get it to stay around the same size as the original and keep the quality?

|

Mark as:

Currently Being Moderated

43. ExactImage,

May 30, 2012 1:11 AM in reply to ACT.onn

Report

We're currently transcoding AVCHD fotage to either Prores or DNxHD, but you could equally well transcode to a high bitrate MPEG2 or H264 and it still work, as long as it's a single file!

|

Mark as:

Currently Being Moderated

44. Jim Simon,

May 30, 2012 9:16 AM in reply to ACT.onn

Report

Is there a way to get it to stay around the same size as the original and keep the quality?

No. Anything that small will require lossy compression. You'll have to decide between quality and size. You can't have both.

|

Mark as:

Currently Being Moderated

45. jrobba3,

May 30, 2012 9:21 AM in reply to ExactImage

Report

Keyword here: transcoding. The whole selling point behind premiere is that you can edit natively. Transcoding to ProRes is not only time consuming but makes the file sizes about 3 times bigger. Obviously a work around, but then what makes Premiere different from FCP7? This issue needs to be fixed.

|

Mark as:

Currently Being Moderated

46. Blind Monk,

May 30, 2012 11:14 AM in reply to ACT.onn

Report

Hey ACT.onn,

ACT.onn wrote:

In addition to the problems mentioned above, all of which I have with a project in which I have 1 set of MOV files and 2 sets of AVCHD files (3 cameras at a wedding), I am getting a clip that shows green frames whenever and wherever I stop scrubbing on that clip. I think the green frame = media pending but I haven't seen premiere do that before.

Curious on a few things:

1) What cameras are you are using?

2) What are you using to wrap the AVCHD files?

Reason I ask is that I'm getting the same green frames & green preview files in the timeline. I actually got the green preview frames in CS5.5, which was odd. Green frame is not media pending, and simply removing that clip from your project then re-importing it should do the trick -it worked for me.

|

Mark as:

Currently Being Moderated

47. Blind Monk,

May 30, 2012 11:15 AM in reply to Blind Monk

Report

My story:

I'm currently immersed in 300gb of clips I'm working with from both A55 cams & a NEX-FS100 that were all wrapped by ClipWrap. This mass of work spans over a 30 day shoot, and was wrapped into MOV so we'd have metadata/cataloging capabilities -which is crucial with over 3500 clips. Transcoding after cataloging is not an option -this would set us back tremendously. The only real option is to use CS5.5 until Adobe sorts out the issues introduced into CS6.

|

Mark as:

Currently Being Moderated

48. ACT.onn,

May 30, 2012 8:52 PM in reply to Jim Simon

Report

Jim Simon wrote:
No. Anything that small will require lossy compression. You'll have to decide between quality and size. You can't have both.

Jim, I should have said that I only transcoded 30 seconds worth and it was twice the size of a 4 minute clip. That kind of ballooning is not going to be possible with my current drive setup. I understand that the footage is HD and all, but isnt there a way to change it enough to get it near same quality and near same size? Is the "wrapper" the problem? Should I encode to MOV instead of AVI?

Thanks for you help in this, I really appreciate every response.

|

Mark as:

Currently Being Moderated

49. ACT.onn,

May 30, 2012 8:51 PM in reply to jrobba3

Report

jrobba3 wrote:

This issue needs to be fixed.

Agreed.

|

Mark as:

Currently Being Moderated

50. ACT.onn,

May 30, 2012 10:03 PM in reply to Blind Monk

Report

Blind Monk wrote:

1) What cameras are you are using?
2) What are you using to wrap the AVCHD files?

Reason I ask is that I'm getting the same green frames & green preview files in the timeline. I actually got the green preview frames in CS5.5, which was odd. Green frame is not media pending, and simply removing that clip from your project then re-importing it should do the trick -it worked for me.

1) I had a Sony HDR XR150, all its' footage is fine. I also used a Canon Vixia HFS20 and T3i. The Vixia and the Sony are both AVCHD format.

2) I am not sure what you mean, but here is the the Properties of the offending clip:

File Path: L:\McGregor Wedding\Canon Vixia HFS20\Vixia1.MTS

Type: MPEG Movie

File Size: 1.9 GB

Image Size: 1920 x 1080

Frame Rate: 29.97

Source Audio Format: 48000 Hz - compressed - Stereo

Project Audio Format: 48000 Hz - 32 bit floating point - Stereo

Total Duration: 00:11:26:15

Pixel Aspect Ratio: 1.0

Now I also noticed that when I select the clip in the project pane it says:

Movie, 1920 x 1080 (1.0), video used 1 time

00:04:03:12, 29.97i UFF (This is the most interesting line)

48000Hz - Compressed - Stereo, audio used 1 time

What is 29.97i UFF? I understand that is frame rate and I am guessing i is for interlaced, is UFF for Upper Field First or something else?

So I decided to try removing the clip and reimporting it. I also tried deleting it, using the project manager to move just the clips and the project to a new drive, then copied the offending file to the new project folder and then reimporting it. Still the same result. I feel like the file is the offender, that it is some how corrupt in only a way that Premiere can see.

The other possiblity that I saw posted about somewhere is that I am mixing footage types with a sequence format that is different. My Project settings are from top to bottom of the dialog:

Render: Mercury Playback Engine GPU Acceleration. Now I have a CUDA card but it is not on Adobe's list, so I found information on the internet on how to enable it and did so. I hope this isnt the problem.

Video Display format: Timecode.

Audio Display format: Audio Samples

Capture Format: HDV

I dont think the safe areas have anything to do with this problem.

My Sequence Settings are:

Editing Mode: AVCHD 1080p square pixel

Timebase: 29.97 frames/second

Video

Frame Size: 1920 horizontal 1080 vertical 16:9

Pixel Aspect Ratio: square pixels (1.0)

Fields: No Fields (progressive scan) - I haven't tried a new sequence with UFF (if that means Upper Field First)

Display Format: 30fps Drop-Frame Timecode

Audio

Sample rate: 48000 Hz

Display Format: Audio Samples

Video Previews

Preview File Format: I-Frame Only MPEG

Codec: MPEG I-Frame

Width: 1920

Hieght: 1080

Maximum Bit Depth and Maximum Render Quality are unchecked.

I remember trying to create a new sequence by dropping the file on the new item button, to see if that would create a sequence that didn't have the green frame problem. Unfortunately it didnt help. I also did a Rolling Edit and moved the cut I have between this camera angle that this clip provides and another to see if it was where I started using the clip in terms of its duration. That didn't help.

Then I thought maybe it was just the preview, maybe if I rendered it out that the resulting video file would be fine. So I put on the transition I wanted and made my work area bar large enought to cover some of the clip before, the transition and a lot of the offending clip and rendered that out at high quality settings. the result was a good start where the non offending clip was, a transition that turned into pixelated red squares in places mixed with freeze frame pixelated footage and then fine video from the offending clip.

I am not sure about what you mean to wrap the AVCHD files.

I have been hoping that every update Adobe does will have one for premiere and that it will fix this problem. I am at a stand still on this Wedding DVD project because of this problem and cannot see how to get around this without using a previous version which I no longer have access to without downloading it illegally. I used to use Production Suite that had been purchased by a Non Profit organization that I volunteered for, but that version and software is no longer mine to use. So I subscribed thinking that I could start using the latest greatest and have all the tools I could ever dreamed of. Well my first project is a total crapfest at this point and I don't see an end in sight.

Is anyone from Adobe working on this? Is there any idea as to what could be the problem? Is there a way to send my project to the techs to see if they can figure it out?

I am so frustrated, bummed and hopeless. I told my customer 2 weeks and I would have the DVDs done. I emailed in the second week and told her that I was going to be late on that delivery. It is now 3 weeks and will probably be 4 by the time I get an answer to this problem. What do I tell my customer? What do I tell her father, who is a friend and coworker in my day job, who suggested me in the first place?!?

|

Mark as:

Currently Being Moderated

51. Blind Monk,

May 30, 2012 11:09 PM in reply to ACT.onn

Report

ACT.onn wrote:
The other possiblity that I saw posted about somewhere is that I am mixing footage types with a sequence format that is different.

One of the huge main points of using Premiere Pro is that you can work with different filetypes at different frame rates, so I just cannot see how this would be the case... Your sequence settings jive well.

ACT.onn wrote:
2) I am not sure what you mean, but here is the the Properties of the offending clip:
File Path: L:\McGregor Wedding\Canon Vixia HFS20\Vixia1.MTS
Type: MPEG Movie......

ACT.onn then continued:
........I feel like the file is the offender, that it is some how corrupt in only a way that Premiere can see.

Can you not transcode the offending clip into some other format to see if that works?

I take it this one particular clip has some super important stuff onnit?

Do you have access to Adobe Media Encoder?

Mac or PC?

Move it to some other format (I'll get flamed for sure) like ProRes LT or anything other than what it's currently in... See if this works. Doing this should be simple and (provided you have the tools) should take a very short time. I've had clips that don't work in Premiere which work in Final Cut, and vice versa -I then transcoded them, and they worked....

What do I tell my customer? What do I tell her father, who is a friend and coworker in my day job, who suggested me in the first place?!?

Before telling them anything, take a deep breath or seven, and remember that you gave them the deadline of two weeks -I'm sure in the future you'll leave yourself with a good cushion on time until you fully trust your workflow. You say the footage plays just fine on other media players, so seems to me like you need to transcode that offender footage into some other format and see what happens.

For now keep busting tail to make that important piece of footage usable. Spending time worrying about problems does not get them solved. Only allow yourself to feel let down by Adobe AFTER you deliver to your customer!

|

Mark as:

Currently Being Moderated

52. Jim Simon,

May 31, 2012 7:24 AM in reply to ACT.onn

Report

isnt there a way to change it enough to get it near same quality and near same size?

Not really, no. Getting it anywhere near that size will require heavy compression. The 'wrapper' makes little difference here. It's the codec that does.

If you need more hard drive space, go ahead and get some. Better that than compromise on quality, I say.

|

Mark as:

Currently Being Moderated

53. Jim Simon,

May 31, 2012 7:26 AM in reply to ACT.onn

Report

is UFF for Upper Field First

It is.

|

Mark as:

Currently Being Moderated

54. Blind Monk,

May 31, 2012 9:19 PM in reply to Jim Simon

Report

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

Link for bug report. Please do fill out!

|

Mark as:

Currently Being Moderated

55. ACT.onn,

May 31, 2012 10:41 PM in reply to Blind Monk

Report

Blind Monk wrote:

Can you not transcode the offending clip into some other format to see if that works?
I take it this one particular clip has some super important stuff onnit?
Do you have access to Adobe Media Encoder?
Mac or PC?

Move it to some other format (I'll get flamed for sure) like ProRes LT or anything other than what it's currently in... See if this works. Doing this should be simple and (provided you have the tools) should take a very short time. I've had clips that don't work in Premiere which work in Final Cut, and vice versa -I then transcoded them, and they worked....

Thanks for the encouragement.

I can transcode it to anything I want, as long as I have hard drive space to store it. I was thinking of simply uncompressing it entirely to an avi or something. All of the footage I have is important as it is someone’s wedding. Eventually I will trim it to just what I use, but right now I need all of it so I can do fine edits of the ceremony. In fact all this started after my initial rough cut of the footage. Everything was fine until then.

I am a subscriber to creative cloud. I have everything. I used media encoder to change it to a MPEG avi. Basically changed the "wrapper". I pumped up the quality and made sure that everything was set the same as the AVCHD file. It actually looks really good and is about the same file size. I have imported it and I haven’t gotten any green frames. I do however have stuttering over the same section that I was getting green frames. I was going to do a render of the section that I did before to see if it comes out ok.

The project is 32 minutes long and this problem is in the first 38 seconds. I have got a lot of other edits to fine tune and I am hoping that this will be the only problem I encounter for the rest of the premiere portion of the project. Not that I am ok with having any more problems with any of the DVD creation process I have left to do.

I should have posted my specs before, sorry.

Windows 7 SP1 64bit

AMD Phenom II X4 965e @3400MHz

8192MB DDR2 SDRAM

NVIDIA GeForce GTS 450

Asus M3N72-D Mainboard

nVidia nForce 740a SLI chipset

I have been keeping all the adobe software and my OS up to date and I have no viruses or pirated software on my computer.

I don’t understand why premiere is behaving so badly...

|

Mark as:

Currently Being Moderated

56. ACT.onn,

May 31, 2012 10:52 PM in reply to Jim Simon

Report

Jim Simon wrote:

isnt there a way to change it enough to get it near same quality and near same size?

Not really, no. Getting it anywhere near that size will require heavy compression. The 'wrapper' makes little difference here. It's the codec that does.

If you need more hard drive space, go ahead and get some. Better that than compromise on quality, I say.

I agree, but at the same time I already have a few TB drives. I have some old projects that are waiting to be done. The problem is everytime I add a new drive I find something to fill it up to at least 1/2 if not 3/4 full. Each drive I add or think about adding causes my stomach to turn.

Why? Because I have no good backup solution. If my house were to catch fire I would be doing my best to get my family out first and then saving my computer tower and the 3 external TB drives worth of footage because if they go I have nothing.

I am thinking and working out a solution to this, but right now my main concern is the project. And yes, I have copied the files around so if a drive were to fail I wouldn't loose the footage. I actually had that happen to 1 of those old projects I mentioned. $700 and 3 weeks later I got a working replacement drive with all my data back.

Anyways... I was thinking if this file is the only offender then I could just transcode to a large file and different format to see if that helps.

Question: If I were to uncompress the footage to a large file size, high quality format, would that cause problems with playback in premiere or would that make it easier to work with? If the processor doesnt have to "interpret" the frames because it is basically an image sequence on the drive in an AVI wrapper does that cause slowness in playback or would it speed up and only the drive speed would be a problem? I hope you understand what I am asking...

|

Mark as:

Currently Being Moderated

57. ACT.onn,

May 31, 2012 11:17 PM in reply to Blind Monk

Report

Done.

ACT.onn's Bug Report:

"Premiere Pro is showing green frames in a clip that resides on a multicamera final sequence. The sequence is set to AVCHD and the footage on it is AVCHD files in MTS file format.

The offending footage plays fine in any media player tried but Premiere loads the project and the clip and in every timeline the clip appears it is green.

Create a project.

Create a sequence.

Import Clips.

Clips are organized into separate folders on hard drive and in the project based on the camera that recorded the video.

Place the clips on a video track using 1 track for 1 camera. Stack the footage from another camera on a new track on the second track. Repeat with the footage from the third camera.

Using audio visual clues find points where you can match up the clips from each camera and synchronize the footage. Repeat this until all 3 tracks and all clips are matched and in sync.

Create a new multicamera sequence based on the synchronized footage sequence.

Using the multicamera monitor create edits. Save the project and come back the next day. Find green frames in the first use of the second tracks first clip at the first 38 seconds of the 32 minute project. Cry.

Expected results were that the clip would not turn green like the Hulk and you could continue to fine tune edits and eventually dynamically link the sequence to an Encore DVD project where you would create menus and chapters and publish a Wedding DVD for the client.

Currently working to see if a different encoding of the offending clip would allow Premiere to handle the clip so as to allow fine tuning of the multicamera edit.

Praying that the remaining clips from 2 of the cameras used, both create AVCHD MTS files, will not have the same problem or this user will end up having to buy a few more Terabyte drives to store all the footage in an uncompressed file format.

If there is anything more you need to know please email"

|

Mark as:

Currently Being Moderated

58. Jim Simon,

Jun 1, 2012 8:21 AM in reply to ACT.onn

Report

I used media encoder to change it to a MPEG avi. Basically changed the "wrapper".

Couple of things.

First, I don't believe AME is capable of creating an AVI file using the MPEG codec. And second, pretty much everything AME does will transcode the footage. It's not really capable of just rewrapping it to a new container without transcoding.

|

Mark as:

Currently Being Moderated

59. Jim Simon,

Jun 1, 2012 8:26 AM in reply to ACT.onn

Report

would it speed up and only the drive speed would be a problem?

Yes, that. AVCHD is heavily compressed and requires a lot of CPU horsepower to work with efficiently. Uncompressed (or lossless compression like UT) is easier on the CPU, but it is a larger file and so is more stressful on the hard drive. A fully Uncompressed HD file may give you issues. A UT version (using YUV420 mode) should play just fine from a single, modern drive even at HD resolution.

|

Mark as:

Currently Being Moderated

60. chesterr_mizik,

Jun 1, 2012 12:17 PM in reply to ACT.onn

Report

I would suggest contacting Adobe Phone Support as well to report the issue !

|

Mark as:

Currently Being Moderated

61. ACT.onn,

Jun 1, 2012 10:23 PM in reply to Jim Simon

Report

Jim Simon wrote:

Couple of things.

First, I don't believe AME is capable of creating an AVI file using the MPEG codec. And second, pretty much everything AME does will transcode the footage. It's not really capable of just rewrapping it to a new container without transcoding.

Hmmm... that is strange...

Here is a screen of gspot reading the AVI file I made from the MTS file giving me trouble.

I don't know what else to say...

I should say that this worked. When I used encoder to transcode the file to an AVI the problem went away. The new file works in the project in place of the original.

Here is a screen shot of the new video file playing in a media player.

|

Mark as:

Currently Being Moderated

62. ACT.onn,

Jun 1, 2012 10:25 PM in reply to chesterr_mizik

Report

chesterr_mizik wrote:

I would suggest contacting Adobe Phone Support as well to report the issue !

I think I have actually put in 2 bug reports about this problem. I am hoping for an update soon to fix this problem, even though I have a work around.

|

Mark as:

Currently Being Moderated

63. Jim Simon,

Jun 1, 2012 10:59 PM in reply to ACT.onn

Report

screen of gspot reading the AVI file

Ah, Xvid.

That's not a native format available to Adobe Media Encoder. It's something you added.

|

Mark as:

Currently Being Moderated

64. Blind Monk,

Jun 2, 2012 10:26 AM in reply to chesterr_mizik

Report

Adobe has been in touch with me and I'm sending them "offender" files today to help the process along.

Will post any updates here.

|

Mark as:

Currently Being Moderated

65. Rohlstusk,

Jun 8, 2012 9:18 AM in reply to Blind Monk

Report

Have there been any updates from Adobe?

|

Mark as:

Currently Being Moderated

66. Jim Simon,

Jun 8, 2012 4:19 PM in reply to Rohlstusk

Report

Yes, but this issue still exists.

|

Mark as:

Currently Being Moderated

67. ACT.onn,

Jun 9, 2012 10:00 AM in reply to Blind Monk

Report

Have you had any helpful contact with Adobe?

|

Mark as:

Currently Being Moderated

68. Blind Monk,

Jun 9, 2012 2:52 PM in reply to ACT.onn

Report

No word back on anything at the moment -I FTPed a trimmed project and some files last week, so we shall see. I can say that they are working on it.

|

Mark as:

Currently Being Moderated

69. randymcwilson2012,

Jun 10, 2012 4:06 PM in reply to Blind Monk

Report

Still not resolved. PLEASE, everyone with this issue go to:

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

(This is Adobe's bug report page)

and send Adobe something like "Long/spanned MTS files cause hanging/freezing"

also, most are also complaining about "Audio RE-conforming" each time one of these projects opens, maybe send that too.

They respond to volume, so let's "turn up" the volume.

|

Mark as:

Currently Being Moderated

70. ACT.onn,

Jun 10, 2012 11:29 PM in reply to randymcwilson2012

Report

I have hit the same problem I have described earlier again in the same project. This time it is another clip from the same Canon Vixia HFS20 that the other offending clip is from. This is unbearable. 2 out of the 4 clips necessary to complete this wedding DVD are being garbled by Premiere.

Here are the specific problems:

Green Frames on the specific clip when scrubbing over it the main timeline or the multicamera window.

If I export a section where it transitions from a Sony camera clip to the Canon Vixia camera's clip with a simple dissolve transition it turns out with pixilated video with red squares all over.

When premiere needs to update the preview windows, the main time line and the multicamera windows are about 10 seconds sluggish, at least.

Clearing the media cache doesn't help.

Deleting all preview files doesn't help.

My work around was to use media encoder to transform the offending file into an MPEG AVI. The first clip that did this has not been a problem in Premiere again and I have been able to work. Until now.

One other thing I did was to use the project manager to move the entire project to another drive.

Between those 2 things I was able to get some work done. But here we go again. I have lost a full month because of this problem. I know because I received an e-mail from Adobe telling me they took my money. I lost 2 weeks trying to find a solution in the forums and from Adobe support's site.

Adobe I have work to do, please fix this problem. Oh and here comes another bug report.

|

Mark as:

Currently Being Moderated

71. Reg Santo Tomas,

Jun 11, 2012 8:02 AM in reply to ACT.onn

Report

I just wanted to chime in to let others know that we are still tracking all these issues.

The spanned clip issue seems to be only reproducible with some Canon clips. We have checked a number of other spanned clips from different manufacturers. Even with the Canon files, it doesn't occur on all spanned clips.

Also, there seems to be some related but slightly different issues in this growing thread. It may be useful to address or discuss them in separate threads as it may become to unwieldly to track a variety of issues on a single thread. This thread has already moved away from the original issue.

We have received the bugs reported and continue to look at them. A lack of direct correspondence does not equate to a lack of interest or concern.

Thank you all for all your support.

|

Mark as:

Currently Being Moderated

72. usartdude,

Jun 11, 2012 8:29 AM in reply to Prof-McAlexander

Report

I am having a similar problem. I cannot edit AVCHD (MTS) files in Premiere Pro CS6. The same files work fine in Premiere Pro CS5. If I knew this beforehand, I would have skipped the upgrade...i can't use the new version.

|

Mark as:

Currently Being Moderated

73. ACT.onn,

Jun 11, 2012 7:06 PM in reply to Reg Santo Tomas

Report

First, thanks for letting us know you are working on the problem. Maybe at this point you can shed some light on a few issues.

What is meant by "spanned" AVCHD files?

Reg Santo Tomas wrote:

The spanned clip issue seems to be only reproducible with some Canon clips. We have checked a number of other spanned clips from different manufacturers. Even with the Canon files, it doesn't occur on all spanned clips.

What Canon cameras seem to be affected? Which other Camera Manufacturers cameras? Has the problem occurred in previous versions of Premiere? Are there any other HD file types that have the same problem?

I know that this may be jumping the gun and that you might not be able to answer some of the following questions but maybe you can give us a temporary solution.

Do you have a "solid" work around? Is there something we can do without a full reencoding of the files that would fix the problem?

Also, there seems to be some related but slightly different issues in this growing thread. It may be useful to address or discuss them in separate threads as it may become to unwieldly to track a variety of issues on a single thread. This thread has already moved away from the original issue.

Sorry. I don't understand how this happened. I thought was replying to this Thread. I must have replied by clicking one of the links in my email and thought was on the other thread.

Is there an easy way to move the posts around?

|

Mark as:

Currently Being Moderated

74. ExactImage,

Jun 12, 2012 12:44 AM in reply to Reg Santo Tomas

Report

Thanks for the feedback Reg. Do the engineers have any idea what's causing this yet and have worked out a possible fix (to come in future updates) or are we still in the data collection phase?

I'm trying to figure out if we should continue using CS6 and suffer transcoding from this one camera or roll back to CS5.5 where were didn't have the problem. There are things in CS6 I'd rather not give up (like the skimming).

Do we have *any* idea of a timeframe to a fix being released?

|

Mark as:

Currently Being Moderated

75. Trent Happel,

Jun 14, 2012 2:54 PM in reply to ACT.onn

Report

For those that are having poor playback with .mov wrapped AVCHD files, could you try something? After you import your file(s), could you quit Premiere, then launch again and select a new Project and import the file(s) again. At this point, does the file now play back without dropping frames? We have seen some cases where when we first import .mov wrapped AVCHD files that we are importing via QuickTime, which results in performance issues. Once it's been imported, it gets stamped with xmp which when imported again on a relaunch of Premiere will allow us to import via MPEG and produce much better performance.

|

Mark as:

Currently Being Moderated

76. ACT.onn,

Jun 14, 2012 9:23 PM in reply to Trent Happel

Report

Trent Happel wrote:

For those that are having poor playback with .mov wrapped AVCHD files, could you try something?

And for those of us with poor performance with MTS files?

|

Mark as:

Currently Being Moderated

77. Blind Monk,

Jun 15, 2012 11:08 AM in reply to Trent Happel

Report

Trent Happel wrote:

For those that are having poor playback with .mov wrapped AVCHD files, could you try something? After you import your file(s), could you quit Premiere, then launch again and select a new Project and import the file(s) again.

I'm working on testing this now.

1) Wait for peak files to be generated I assume?

2) Also, just for my own knowledge, is the XMP data you're talking about being written to the MOV wrapped AVCHD file or a sidecar?

EDIT:

Just tested and this doesn't seem to help or hurt the cause for my test subjects - status quo. Back to CS5.5 for now.

Message was edited by: Blind Monk

|

Mark as:

Currently Being Moderated

78. Trent Happel,

Jun 15, 2012 1:20 PM in reply to Blind Monk

Report

Blind Monk wrote:

Trent Happel wrote:

For those that are having poor playback with .mov wrapped AVCHD files, could you try something? After you import your file(s), could you quit Premiere, then launch again and select a new Project and import the file(s) again.
I'm working on testing this now.

1) Wait for peak files to be generated I assume?
2) Also, just for my own knowledge, is the XMP data you're talking about being written to the MOV wrapped AVCHD file or a sidecar?

EDIT:
Just tested and this doesn't seem to help or hurt the cause for my test subjects - status quo. Back to CS5.5 for now.

Message was edited by: Blind Monk

Darn it. I was hoping we had a wpossible workaround. Thank you for trying this out.

|

Mark as:

Currently Being Moderated

79. HeatherJSheard,

Jun 19, 2012 1:17 AM in reply to Reg Santo Tomas

Report

I am having the same issue with footage from Panasonic AG-AC160 and AG-AC130 so I don't think it only Canon files that are affected.

|

Mark as:

Premiere Pro

More Like This

Incoming Links

Bookmarked By (2)

Answers + Points = Status

Premiere Pro

AVCHD Workflow help

May 14, 2012 8:45 AM

More Like This

Incoming Links

Bookmarked By (2)

Answers + Points = Status