HI I know it is an old thread but I wondered does this mean it is recording in 422 in MJPEG mode? And also how do I get it to shoot in 25fps instead of 30fps?
Thanks.
is manual exposure available in VGA mode??
good Day! is there any way or patch that i can play mpeg in my gh1?
Are you sure @vadimvadimman ? I thought frame rate changes in MJPEG mode weren't true frame rates, they're dropped frames. Also I thought the GH2 didn't have 4:2:2 color vs the GH1 does have 4:2:2 in it's MJPEG, though the GH2 does allow higher resolution.
I've only done one shoot in MJPEG but the lack of spanning and resolution limits kept me from doing more. I do agree that in low light/low iso the MJPEG blacks are much nicer, deeper, vs AVCHD, but in high/iso low light the AVCHD has much less noise/FPN.
Today I did tests using Driftwood Cluster X between AVCHD and MJPEG and found out that AVCHD gives me only 8bit footage while MJPEG 16bit with much higher bitrate. One more reason for me to use MJPEG over AVCHD.
By the way you can change frame rate of MJPEG mode.
Do i just load both firmwares (Flowmotion and the anamorphic hack) into ptool and "load" both versions, than save the new firmware? Is that enough?
"Flow Motion v2 comes with the non-anamorphic version of my 100Mbps MJPEG patch. You can replace that with the anamorphic 100Mbps MJPEG patch without disturbing any of the AVCHD settings. Using PTool, simply replace all FM2 settings found under the "MJPEG Movie Mode" header with the anamorphic settings, and save a new firmware file to disk."
// edit: i just edited the ini file guess it works now. Thanks anyway.
Could one adjust the distance of the 3D lens to cover more of the sensor?
@lpowell thanks for the explanation. by the way, do you plan to release any new patch settings? i recall reading something was potentially "in the works" in another thread (though perhaps a reference at the time to fm2.02)...
@hay When you set the camera to MJPEG HD mode, the clip duration is estimated by the amount of video that can fit into MJPEG's 2GB file size limit. It does not indicate how much space you have left on the SD card until you're down to less than 2GB.
@lpowell i loaded fm2.02 via 3.66d ptool. when using manual movie mode/motion jpeg/HD, my gh2 display indicates (at all times, regardless of the number of clips shot) that only 2:39 remains, regardless of what sd card is inserted - 64gb sdxc or 16gb sdhc. ive tried reinstalling the patch and reformatting, etc, to no avail. should i be using an older version of ptools? have you seen this issue before? i like the mjpeg image, but would like accurate remaining time on the camera display. maybe this was mentioned before but i missed something...thx for the help
@eminogrande Flow Motion v2 comes with the non-anamorphic version of my 100Mbps MJPEG patch. You can replace that with the anamorphic 100Mbps MJPEG patch without disturbing any of the AVCHD settings. Using PTool, simply replace all FM2 settings found under the "MJPEG Movie Mode" header with the anamorphic settings, and save a new firmware file to disk.
I did some tests and it seems that Gh2 use for .mov files rec601 (SD) not rec709 (HD) color profile. I heve not tested vimeo but I not think they use rec601. The computers and I think the new plasma, led and lcd tv with HD uses rec709. Rec 601 is standard for < 720p , Rec 709 is for > 720p. So this is a bug in GH2 camera. (Is possible in post-production to convert from one to another.) Maybe we will see a hack which has MJPEG 4:4:4 and Rec 709.
@LPowell is there a flow motion patch including the anamorphic 1.33 so i can play around with 24p and mjpeg 30p mode - both with peak 100mbps?
Thanks a lot @LPowell - i guess i "just" trust you in that. I basically get both points. I will try to use 800 ISO or less for my next shots and post the result here.
best regards emin
@eminogrande At ISO 3200 on either the GH1 or GH2, MJPEG is definitely going to be noisy. With an anamorphic adapter, I'd recommend shooting at ISO 800 or less.
MJPEG 1.33x anamorphic mode has two advantages over post-processing 24p anamorphic footage:
Convenience - the camera does the 1.33x horizontal stretch, producing square pixels natively.
Compression quality - the camera stretches the frame before it's encoded into MJPEG format. The drawback of stretching the frame in post is that you're working with compressed 8-bit color data.
Hey,
i've a question. I use a 1.33x adapter and your anamorphic patch. For me, it seams like the image is much noisier than before.
I read somewhere, that this is "normal" and i have to reduce the noice later with my editing program (i just have premiere pro). Is that right or wrong? Sorry if im asking stupid questions.
Please check my video:
Also, i dont 100% the advantage of using MJPEG instead of AHVCD 24p mode (which is much more cinematic) - is there an easy explanation why i should use MJPEG?
Isnt it better to do the post processing (in example exporting the image in 1080p, 1.33 PAR via Adobe Premiere Pro) than let it be done by the camera (cropping the picture to 1920x810).
Hope this is the right place to ask this kind of questions.
Best regards Emin
Fantastic, thanks for all of your help!
@csync Yes, and these same 100Mbps MJPEG settings are included in Flow Motion v1.1
Are these settings compatible with 1.1 and v3.64d?
Its quite straightforward, but yes a wiki from the testers will probably appear soon. Take a look at Lpowells low light setting which are good or my higher bitrate/quality mjpeg settings in some of the Quantum patches (dont forget to put it back to 720 width/height =1920 x 1080 and 480 width and height =1280 x 720). Basically you have four tables for Quality (bitrate) and four tables for, well, Quantisation.
My hunch has been that E1/F1 pushes Q chrominance and E4/F4 pushes Q luminance. Lessen the table values for better Quantisation (closer to 0 is better quality low compression but requires more bitrate in Quality setting, higher table values = higher compression, poorer quality but uses less bitrate).
Judge allocating bitrate in the quality settings according to how low your tables go. Too high on the Quality bitrate/low on the tables will hinder recordings/stop them prematurely.
Use jpegsnoop (search google for downloadable proggie) to look at the jpegs produced by the GH2 (when you hit record in mjpeg mode a first frame snapshot is produced - analyse this jpeg with jpegsnoop to see the quality/quant info).
If your recording never gets past the snapshot youre using too low a table setting/too high a Quality setting! Good luck!
It is possible to create in the wiki a GH2 Hacking FAQ for the Mjpeg? A setting scheme like it exist for the AVCHD will be for the newbies of the Ptool like me very usefull. (I decided to wayt for the 1.1 version before playing around). Would be nice to have the timelapse settings too.
Second this! If you have RAW, why not shoot RAW? Compared to high-rate video, the space needed is still small…
No, the MJPEG patch settings are completely separate from the camera's still photo JPEG settings. I recommend shooting stills in RAW mode.
@LPowell Thank you for the explanation! Oh, does this MJPEG tunning also improve the photo JPEG quality? Or is there a way to do this? Because many people complaining that the camera JPEG is not too good.
It looks like you're new here. If you want to get involved, click one of these buttons!