Editing native .MTS files in Premiere CS6 - WHAT KIND OF ARTIFACTS IS THAT?

Tim_

Member
Hi guys!

Hope somebody can elaborate on this: .zip sample of 1080p artifacts (33mb) - the file are from Panasonic GH2 and they always fine and good if you open them BEFORE putting them in CS6... So Premiere opens them with some artifact issues (see sample) and then export them too (in final version)

It looks like raining of noise in top left corner - very subtle , but still very visible.

Any ideas why it's there and what to do about it?... I mean without the need of convert them before premiere into ProRes or something. I really need workflow that will be fastest as possible...
 
Is this the original footage? I see the artifacts before I open them in Premiere. OR can you upload some original footage so I can see if I can reproduce the problem?
 
No, it's after-premiere...

hmmm... the original footage is 4gb... I'll try to re-shot something very short tomorrow and upload it... Thanx for helping!
 
Is this a hacked version of a GH2? Apparently those do have some issues with artifacts. Also make sure the resolution is set at full when viewing in the Source or Program monitor. If you google GH2 artifacts in Premiere Pro you get quite a lot of hits.
 
I don't see anything wrong with the included file, either outside or inside of PP. What exactly am I looking for?
 
Look on the left side of the image. It looks like faint slashing rain with low opacity. It is more pronounced higher in the image. I see it in windows media player and PP. That is why I would like to see some original footage and see if I can find the same problem.
 
Is this the original footage? I see the artifacts before I open them in Premiere. OR can you upload some original footage so I can see if I can reproduce the problem?

U P D A T E :

Here is a scientific proof of that this is Premiere's "fault":

(I've tried to make those files as tiny as possible - just 3-4 seconds...)

ORIGINAL .MTS from GH2 (no artifacts)

AFTER (and inside editing pane) Premiere CS6 (Has all new updates, btw) (you will clearly see one-directional noise-rains constantly dancing around darkest areas)

Side note: My Panasonic GH2 is NOT HACKED... Firmware version 1.0 (asian version, no recording limit)... 24H cinema mode

I don't need HACKED crazy bitrate, but definitely want to do something with this artifact issues.... I don't now if updating to ver. 1.1 will give any benefits since there is only Europian version available as far as I know so I will lost time-limitless recording (and I have doubts about that will solve Premiere artifacts problem)

Maybe any of you own GH2 and work succesfully in CS6 with native .MTS? Or you just have any clue what's going on here ? :)

This problem appears with all my lenses.

Any ideas / directions I will highly appreciate...
 
I see the difference in your footage. I also the see the difference between them on the Premiere timeline, so Premiere itself isn't doing anything to the raw footage.

I'd guess it has more to do with your MPG render.
 
I see the difference in your footage. I also the see the difference between them on the Premiere timeline, so Premiere itself isn't doing anything to the raw footage.

I'd guess it has more to do with your MPG render.

So what could one do about that? ...Is there any way to fix that somehow?
 
OK, I just checked out the original footage in PP (board-original.MTS) and I now see the issue. It looks like it's snowing.

Problem is, it's in the original footage, as I also see it when playing outside of PP using VLC.
 
This is a playback decoding issue, most likely the result of an underpowered computer. I suggest you play your clips back on a different computer with more horsepower.
 
This is a playback decoding issue, most likely the result of an underpowered computer. I suggest you play your clips back on a different computer with more horsepower.

I have this issue on my 2012 non-retina Macbook Pro, with latest i7 processor, 1 gb Geforce GT 650M and 8 gb RAM and firewire800 external drive
 
OK, scratch that one. But, seriously, try playing the clips in question on different machines. The first step in troubleshooting is to isolate where the problem is occuring. If you have access to a decent PC, play the clips there and see what they look like.
 
Back
Top