Also impossible to understand, just strange.
How they can be hardcoded then we change them and it works?
Try to read my posts in last pages.
GOP is an arbitrary number. It may define a length of I/P frames in a group but it does NOT define the quality, type or actual quantity of the frames in that group.
Therefore some other process MUST be determining the quality/quantity and makeup of the GOP.
Being able to define how many I or P frames and their quality/compression would be more beneficial than defining how long the GOP is and letting the subroutines do their best to try to accommodate.
That's why I think people are having issues with writing to the cards, because adjusting the GOP might bring any routine that defines the quality/size and or number of I/P frames outside of it's coded boundaries and therefor confuse any other routines that might happen later in the processing chain.
EDIT:
I suppose what I'm saying is that more research needs to be done on the processes involved and we need to focus less on just changing GOP numbers and seeing what happens.. We are on to something with changing the GOP but we need to investigate the lower level stuff first due to the fact that we are seeing the GOP changes cause issues and not actually "fixing" anything.