Patches for testers>AVCHD movie mode>AVCHD research>Encoder setting 1 1080i/p when value changed from Original 3 to Modified 4 there is a silent crash with no recording, camera becomes unresponsive and needs to be rebooted by taking battery out.

Patches for testers>AVCHD movie mode>AVCHD research>Encoder setting 4 1080p when value changed from Original 8 to Modified 4 average video bit rate in a 24H file drops to 8k and only I and P frames recorded with motion, b frames recorded without motion so it looks like an 8 frames a second film.

Very nice dkitsov.

Mmm- ES4 1080i is 17.. I wonder

0n 'encoder setting' 2 and 3, 1080i is double that of 1080p, and on ES4, 1080i is double 1080p, +1

1080p and 1080i both have the same value for ES1

Maybe so... but I thought the similarities were curious, like the leap to a larger value at ES4, and a rise in values from ES1-4 across the 3 resolutions.

So it's probably a good idea to give a testing structure.

My first thought is that we should ask for someone to test each encoder setting under each resolution and set up the camera to produce identical video files of 10 seconds on each and then run Streameye and Streamparser on each file. We can then easily compare what is different.

However, the camera needs to take video of exactly the same subject with the same lighting, etc, every time so that there is no introduction of change to the file from external influence, so that we can only see what the encoder setting changes.

My camera is out on loan until next week. If nobody can do this sooner, I'll do it when I get it back.

I am going to try to do the bit rate tests tonight with the test charts on a tripod. I have a spreadsheet setup to keep track of every change. I will change one parameter at a time. Hopefully I can post some files tomorrow. I just did a quick test with half of the original GOP and bit rate set at 40 mb/sec for each resolution. The first 2 seconds of a tree blowing in the wind showed almost no compression artifacts just like the GH13. Then you can actually see the macro blocking suddenly start after 2 seconds. If we can get the whole video to look like the first 2 seconds everyone will be VERY HAPPY.

We will just keep testing away and see if we can find the magic setting. Those first two seconds look really good though.

@mpgxsvcd
Btw, I think that errors must be less frequent with new release.
We also need mode data and more systematic testing.

Look at second post of this topic.
I just need complete chart. Plus numbers.
Also advise to use any MTS loseless cutter and cut first 2 seconds to get numbers for them separately.

>after the 2 sec reset, the average bitrate seems to be lower than if the bitrate was not manipulated..

I know.
But again. Please use full report form.
You words are and ideas are fine, but they won't provide necessary data.