@Lpowell: True, the AVCHD settings do seem to have too much interplay between modes. ATM it's either a long GOP (like 13) to get timelapses going without spending or if going modular, it's got to be in the lines of the MJPEG set I attached. Thanks for the expert opinion, it's very much appreciated.
P.S. Oh, and thanks for the warning!
@LPowell Scary ... even if i have to sacrifice Time lapse thing :((
@Chhatrapal : If you really need the lenght that only AVCHD can give you, I've got this (somehow old by today's standards) mix of 24P settings by bkmcwd and cbrandin 44M_32M which I believe I changed for GOP 12(13?) and gave me good if not stellar results for regular video and near 4h timelapses on 16GB.
I used above @mickos tweaked Quantum 100 ... It worked out to be fine. @LPowell @driftwood I just wanted to ask if changing settings of MPEG Mode on Quantum 100 is safe? Are MPEG and AVCHD streams are separate? And i don't intend to use 1080i. Even if the things are grey i don't want to take risk rather i will look for separate timelapse patch.
@Chhatrapal Yes, MJPEG and AVCHD settings are completely separate and do not have any effect on each other.
@LPowell Even if you don't fully understand what caused your near disaster, I hope you will share what you do know. Bricking a camera is the last thing any of us want to happen.
@Ralph_B I was experimenting with using B-frames in 720p60 mode at the time. Although I'm not 100% sure that was what caused the near-fatal incident, I've since abandoned that approach for other reasons. I'd advise anyone to proceed with caution when making changes to GOP structure.
Let's keep it simple. Complete settings in a file. No modular approach. Actually PTool already has the basic sequantial setting file loading which I do not prefer either.
One last modular question: 720p settings are independent from 1080i/p or are there any shared ones that you know about? Thanks again.
can anyone tell me if 30p is working yet with the hack?
@duartix Beware, 720p is intricately entangled with 1080i settings. Beyond here lie dragons.
Thanks @LPowell. I'm getting the point...
Here is the latest LPowell Flowmotion 100Mbps patch with just one small change - the MJPEG framerate changed to 2fps for use in timelapser. Not very efficient; only about 41mins on a 32Gb card due to the MJPEG compression table values, and a bit of a waste of the patch MJPEG settings, but might be useful.
GH2 v1.0E 100Mbps Flow Motion Patch Executive Summary:
100Mbps AVCHD in 1080p24, 1080i50/60 & 720p50/60 at 8-12 keyframes/sec.
50Mbps AVCHD file-spanning in 24L and FH video modes; 30Mbps in H mode.
100Mbps MJPEG 1080p Patch maintains high bitrates regardless of light levels.
Optimizes quantizer tables to produce P and B-frames that match I-frame quality.
Efficiently combines maximum I-frame size with compact, short-GOP file size.
Compatible with all NTSC and PAL video modes, 80% Slo-mo, and ETC mode.
Works reliably on standard Class 10 SD cards, with in-camera playback in all modes.
V1.1 will feature customized quantizer tables combined with 25p HBR support!
Have you seen this? http://www.personal-view.com/talks/discussion/2111/gh2-mjpeg-resolution-findings-and-myth-busting/p1
BTW, as you said, there is no point in maintaining the same quantization/tables when recording length is the other main objective beyond IQ. A better balance is in order.
Yeah, too true, though I'm happy at this (exciting) stage of patch production to sacrifice the length just to have that option in-camera, as I'm mostly using 24p modes and I'm liking the new interlaced modes in the FlowMotion too. I just grab a timelapse if an opportunity arises, but I'm looking forward to a specialist timelapse card. Very interesting discussion at gh2-mjpeg-resolution...!
@Ralph_B Toying with the encoder settings is most probable. It shouldnt brick it, just go bonkers/green, etc... if you put an unworkable value in encoder. The encoders are still fairly mysterious. No one absolutely knows what they do, but Ive done many different tests using an array of different values. Take a look at the defaults, spot trends. For example;-
We do know that encoder Settings 1 effect frame types and stability ie 720p encoder1 = 3 gives B frames, encoder setting 1080p/i set to 2 or 1 I found gives i frames only in GOP1 - ie no 2nd frame p slice).
In the past some people suggested they could be related to the default factory scaling factors for quantisation tables (Emul on July 27 2011) and that a factor of 3 could be being used throughout(3×17=51 for example). Another interesting trend to spot is that all the 1080i settings seem to be an 'addition' setting of 720p + 1080p [e.g. 720p Setting 4 (9) + 1080p Setting 4 (8) = Setting 4 1080i(17)] and that changes effecting one set may have to be carried through using this 'additional' factor. Settings 1 could purport to i frames, setting 2 to P frames, setting 3 could be for B frames, and setting 4 some kind of fallback/ initialiser. Equally setting 1- 4 could relate to the Quantiser Scalers/ related to Panasonic's own alogorithms for Quantisation.
I have experimented with different settings in some of the Quantum BETA patches and seen that lowering or enlarging these encoder settings is possible without destabilising the camera by using this additional factor. Whether or not this improves Q or is necessary for stable higher bitrates or to help widen other parameters remains to be proven. So, if things get stabilised by adjusting any of these settings we still don't know why and what they are doing.
@mickos Where do I get the latest Quantum 100 from?
Someone please let me know the link.
It looks like you're new here. If you want to get involved, click one of these buttons!