@matt_gh2 no mystery, just 5DtoRGB and I use the same settings also suggested by @shian in either the 5DtoRGB thread or perhaps his ColorGHear thread (or both).

5DtoRGB solves all woes currently encountered with MTS, that aren't simply facts of life from shooting such highly compressed images in the first place.

Folks investigating alternate patches in an attempt to avoid this artifact, which is not an artifact introduced by patching, instead of exploring various patches for their often signature aesthetic and qualitative aspects, are just being pitifully ironic.

@DrDave I'm rain-free with Apoc Now Boom v1 and edit in Prem Pro CS6. But you should be able to use any setting you want, but in some cases transcoding the footage is necessary. @BurnetRhoades seems to have a pretty good handle on this and has posted his transcoding solutions, so maybe check his posts.

Anything over GOP3 coupled with unequal shutter speeds (iA modes does this too) for the frame rate produces unbalanced b frames on the GH2 and could be one of the reasons responsible for digital rain where certain decoders cannot decode the mts file correctly.

Long gop seems more prone to these problems.

Strangely, anything which does show unequal b framesis where odd shutter value ratios to frame rate are employed (see graph example attached) and these often play as rain in VLC and CS6 (Sony Vegas too I believe) whilst Elecard products, ffdshow (libavcodec codec plugins), Windows Media Player / Classic and a few others play things without problems.

However, since it appears to be happening to some GOP3 stuff the investigation continues...

I was not able to get rid of the rain with GOP3. Did you try it on Flowmotion? Maybe I am changing the wrong setting.

I invited the cineform support to read this topic so maybe they can find a improvement to the neoscene decoder to handle the gop6 and gop12 and other long gops

by now if you use cineform transcoding to avi i recomend you to work with gop3

@apefos

Only viable testing is changing ONE parameter, not whole settings.

Most probably your decoder issue is related to custom matrixes, not to GOP.

hack settings 48 / 24 Mbps Gop3. problem solved for 1080p 24p and for 720p 60p in 48 and in 24 Mbps. Gop3 was the solution.

hack settings: 48 / 24 Mbps Gop6. problem still there in 1080 and 720, 48 or 24 Mbps. changing datarate does not affect the problem at all. it seems lowering the gop to 6 the problem is a little more subtle, but not sure about that. will try new settings.

interesting: the problem does not show in sunlight shoots, just inside home at less light.

My workflow to do denoising is: 1-convert original mts to cineform avi using neoscene. 2-denoise with neatvideo using cineform neoscene codec to save the denoised file as cineform avi. 3-convert the denoised cineform avi to the format i need, for example h264 or mp4 to upload to web or mpeg2 to output to dvd.

I did some new tests to compare denoising in two ways and i found no significant difference in image quality: 1- original mts to denoised h264 2- original mts to cineform avi to denoised cineform avi to h264 so it seems you do not need to use the intermediate codec to get good denoise if your output is H264.

But, if your output is a DCP (digital cinema package) using cineform codec is a must because the denoised cineform avi file is much much better than the h264 denoised video. The difference is more noticeable in the shadows, in low light, in gradients, near the blacks and no light areas. the h264 compression hurts the video quality a lot.

the neatvideo tutorial is here (read the video description on vimeo for important updated informations):

See if you can get ffdshow-tryout to work in MPC-HC. Neoscene might be able to use ffdshow-tryout also.

Ah - ditched VLC after my computer rebuild and that might explain why I haven't seen the phenomenon since.

here is the jpg files from videolan and windows media player, videolan shows the problem.