@rawmeyn best player I've found for MTS files on mac is Movist. Toast Video Player (inside the Toast 10 app package) works smoothly too (licensed from Elgato and unfortunately replaced with a crappy in-house player in Toast 11). Also, the Panasonic "AVCCAM Importer" QuickTime plug-in for OSX plays MTS files smoothly when handled by QuickView (as opposed to QuickTime Player X). Just my personal experience. Hope this helps.

@rapsoe good to see we are on the "same page" ; )

p.s.amazingly the toast player I use is "old" - from 2008 (toast video player 3.0 licensed by elgato)!it can do a anamorphic crop(not stretching but really cropping the video) The only thing i miss there is a playlist.

Thanks for the movist suggestion!Finally a playlist player ; )

@peternap real fast and detailed action sport (motor bikes)....
Example http://speedy.sh/Vg6q4/00018.MTS its just a 28 mb download, its not sharp, filming didn't give probs, it happens when i stop filming, then it freezes, if it does not, it take many many seconds to save the file,

but flowmotion 2 give incredible images, if all go's well ...........

The ones with skies are normally a banding nightmare but in this test with FM v2.0 i don't have this issue. the ETC one is not so sharp but i would imagine it is mostly due to a hand held shot at around 200mm(58mm x crop factor x etc) manual lens no OIS ; )

24p standard -2,-2,-1,-2 iso160 (the moon-iso400'ish, maybe?)

side note: the player is movist and i used the command shift 3 to capture the images(mac) so that i can have the file info too.

@luxis I Didn't know about mediainfo. thanks!

@LPowell I did some short tests with FM2. My concern was noise, as I loved FM1.1 but had switched back to all-intras as I couldn't stand the noise rendition difference between I frames and B frames in FM1.1. In FM2 I can't tell the difference. That's amazing. And FM2 scales so well too! You really did an amazing job with FM2. It'll probably be my new patch of choice. Thanks so much for all your hard work!

@LPowell I can wait for the fix I think. Most of my shots are 10-30 seconds. Otherwise...this is mighty nice so far!

@rawmeyn Splash Lite works well for high bitrate files also. You do have to go to the paid version for a frame grab though.

@LPowell Yes thats it "shooting brightly lit, high-detail subjects"
Just did some test to reproduce that problem.
If i follow a fast moving object, in my case a dirtbike, and it gos from a "dark" background, to a over exposed one (think on a big jump), and back to the dark background, where the camera does a refocus, there it go's wrong when i stop the recording..

I must say your scaling tables and deblocking ones are just briljant.
i did merge them with my own patch, and now the DC in the Elementry Stream Encoder is not 2 anymore, but 6

@LPowell. Lee, just did a quick test of FM2 with Panasonic 14-140mm lens using Sandisk Extreme 32GB 30mb/s and Transcend SDXC 64GB class 10 cards. 24H,L and HBR worked fine with great quality on both cards. FH and H modes worked fine too. The only problem is with SH and FSH which stops with write errors. I really need the 720p60 SH specially for slow motion. It seems like when bitrate for FSH/SH reaches mid to high 50s then stops with write errors. Bitrates below 50 works fine. Will reducing the top end of the SH/FSH bitrate from 99 to a lower value help with this situation without any noticeable compromise? Thanks for all your hard work After refreshing my browser I noticed your comment on further testing on 720p60 and a possible fix.

@mozes Thanks for confirming my test results. As you've discovered, the GH2 has a tendency to overreact to rapidly changing exposure and detail levels when you start a recording with a blank scene. The AVCHD encoder appears to use the first P-frame in the initial GOP to predict the bitrate requirements of the subsequent video frames. While that works very well for typical shots with static scenery, it can confuse the encoder when the exposure shifts dramatically a few seconds after the recording starts. Since Flow Motion v2 does not use P-frames in its 1080 modes, I was able to take advantage of this P-frame calibration mechanism in the design of its Scaling Tables, using it to manipulate the encoder's rate control at high bitrates.

Unfortunately, I wasn't able to employ this technique in 720p60 mode, since its 6-frame GOP uses P-frames as well as B-frames. I actually put about a week into an attempt to perfect a GOP-3 720p patch, but its image quality wasn't as consistent as the 6-frame GOP used in FM2. To make it even more challenging, I was able to produce reliable and highly optimized results in PAL 720p50 mode that I'm reluctant to compromise with heavy stability adjustments to 720p60 mode,

Meanwhile, I reviewed all 1080p recordings I took from the "moving tree leaves in the sun". Here is what I found:

The results for 24H have an average bit rate of 113MBit/s (without ETC) and 118MBit/s (with ETC), and they look very, very good - visibly better than the GOLGOP3 setting I used before (which was also producing very good results at ~80MBit/s). I spotted only very faint compression artifacts where in the lower midtones of a very fast changing area, horizontal borders between different colored areas became visible for a few frames - not something that would come to the viewers attention at normal playback speed.

The results for VMM 80% have an average bit rate of 105MBit/s, and they, too, look very very good, not visibly different from the 24H results. But there was one glitch in ~15 minutes recorded, where some (ffmpeg based) players report the following error message, and 5 frames show damaged blocks (see attached screenshot):

[h264 @ 0xfd6920]negative number of zero coeffs at 104 36 [h264 @ 0xfd6920]error while decoding MB 104 36 [h264 @ 0xfd6920]concealing 3785 DC, 3785 AC, 3785 MV errors

The strange thing about this glitch is that it resembles a similar glitch I experienced when testing GOP3ZILLA, which also had some damaged blocks in the lower third of the screen - and which also was ignored (and decoded with no visible damage) by other players. Maybe this is not at all setting related (and it is only the second time ever I have seen such a glitch).

Last but not least, I tried the HBR (NTSC) mode, and there I experienced a bad surprise: The average bit rate of the HBR 30p recording was only ~50MBit/s, and thus not too surprising, it exhibited serious compression artifacts - see attached screen shot. The quality of the HBR recording is low for the whole "moving leaves" recording, not just in a few frames of it.

Bottom line for me so far: Thanks a lot for what is probably the best 24fps GOP3 setting today - the quality is really awesome.

I hope the HRB/NTSC quirk can be fixed.

Next I will try to do some 720p60 recordings.

@Karl. Nice report. I would be interested in your 720p60 test results. I am having write errors at bitrates above 55MB.

I did some lowlight shots in a big room with just a small lightsource in a corner. The cam shut down once in HBR (Pal) mode after 1.50min at iso 320 with the 20mm pancake at f1.7 (Smooth -2 -2 0 -1). All other HBR shots came out just fine. I did tests from ISO 160 up to 2500, all shots were between 2 & 3 minutes long. The average bit rate was around 55MBit/s for all clips. Then I gave 24H a try (but I need 25fps so bad(!)) at ISO2500 and it looked just great. The bit rate was higher at around 100MBit/s. I was using a SanDisk Extreme 30MB/s Class10 8GB Card. Cheers!

re PAL / HBR25p:

write speed error after a few seconds shooting a static death chart (black&white/high contrast) on both SanDisk 30MB/s (16GB) and SanDisk 95MB/s (32GB). What a pity!