Personal View site logo
GH3 user reviews and opinions
  • 1089 Replies sorted by
  • @uzland

    Make more of such videos :-)

  • “Cinematography is more than a camera, whether that camera is a Red an Alexa or a Bolex. There is a little more to it that resolution, colour depth, latitude, grain structure, lens aberration etc. etc. etc. The lenses use for ‘Citizen Kane’ were in no way as good as a Primo or a Master Prime and the grain structure in that film is, frankly, all over the place. But the cinematography? Well, you tell me.”

  • @filmiwilliam i.resolution mode whilst recording video automatically switches to LOW setting. Still doing the tests to see if there is any gain.

  • If anyone takes that Will Crockett guy seriously, I need to punch myself in the dick. If you're going to promote yourself as some sort of camera expert and blog guy, AT LEAST USE A F*$KING BOOM MIC OR SOMETHING!!!!!! Good god. I heard 5 seconds and off it went. And as for the frame rate stuff he said, yeah, that should tell ya enough!

  • Great forum!!

    Are anyone using the i.dynamic and i.resolution options in any way? Will they give you a flater profile or whats the deal with them?

    I´m going to film some documentary work on Wednesday and I´m still trying to figure out the settings for the camera. The project I´m filming will continue for at least one or two years and It would be nice to start filming in the most correct way possible =)

    Are everybody saying that the 50mbit mov codec is the best one? Better then the 72 all i? How do you grade your material? Sharpness, noise reduction, contrast etc - What do you ad and how?

  • @windcharger: I see a lot of micro stuttering of moving objects - e.g. the adult slide at 0:18 and the child sliding to the left at 0:24. Is this from the camera or from the pcpx?

  • So what is a footage converted to 300 mb/s worth? Transcoded from 72 to 300. Any difference other than the latter is heavier?

  • slowmo test with FCP X 10.03

  • @hay

    Just read that article, thanks but I'm not sure what it has to do with my issues? This may be my first MFT camera but I've used a Canon 7Ds & 5Ds on productions with the 17-55mm EF-S and some very sharp primes and the pans at the same frame rates and shutter speeds had a smooth film-like quality. This staccato, stuttering motion on my GH3 is weird and totally disappointing. I do not profess to be an expert, I've simply followed this rule and normally had great success: http://tylerginter.com/post/11480534977/180-degree-shutter-learn-it-live-it-love-it.

    Just tried an old Canon lens and it is the same if not worse. If anyone can give me some other way of testing to see if its just a problem with my particular camera, I'd be very grateful. The way it is now, this is unacceptable.

  • @Tenjin, good luck, I am interested in results, but currently I am disappointed with GH3 iq? if Panasonic have moved to Sony for the sake of 1ev dr, its a big mistake.

  • @ conundrum

    ive encountered problems in the past panning with the newer panny lenses optimized for micro 4/3. try using old nikkor, olympus or canon glass with an adapter. the results often look smoother as these lenses resolve less detail (lp/mm).

    http://www.luminous-landscape.com/tutorials/resolution.shtml

  • Sorry for a longish first post, this is a great and informative forum!

    @FilmingArt, the trouble with the stock picture profiles on many if not most of these cameras is that they are overly saturated with too much contrast, sharpening and noise reduction "baked in". Therefore the dynamic range is somewhat compressed and there's a loss of information especially in the shadows. The goal of the Canon picture profiles, for example, that are used on the 7D and 5D, like Cinestyle or Marvel, is to get the most neutral image possible and retain as much tonal and detail information as possible. The value of "flat" or "log" is that it gives much greater latitude for grading in post. Even with a 4.2.0 codec. I'm hoping that someone here will be able to develop a series of "cinestyle" profiles for this camera that will give a truly neutral image (without the magenta push).

    I have now had the GH3 for 3 days and have begun to play around with it. My initial impressions are positive BUT I am finding that there is a lot of strobe effect and aliasing on slow pans. I've tried to get slow, smooth "strobe free" pans in MOV-50mps & 72mps-24p @ both 30 and 50 shutter speeds and MOV-50mps & 72mps-30p @ 30 and 60 shutter speeds, but I am finding there is a lot of staccato motion, kind of a repetitive delay in the panning motion. I am using the 12-35 lens. I've been seeing this on a lot of the Vimeo and Youtube clips as well but I thought it was just compression problems. I'm seeing it in the raw footage. Seems much more pronounced than on the Canons. Has anyone else noticed this?

    The other issue I'm finding is that there is a brightness shift when zooming with the 12-35mm. Its almost as if the aperture pumps slightly mid-zoom even if its a fixed aperture lens.

    I really want to hang on to this camera but these issues have me doubting that I will. Could others please let me know if you have these issues? It may just be a problem with this particular specimen.

    thanks

  • @adventsam the points you mentioned are also my concern. But as I said I used standard setting -4 -3 -3 -3 so that may be one of the reason for soft and mushy... Also I learned by these tests to NOT use 72mbps at low iso (i have to compare with more shots at high iso).

    Most people said were happy the green tone went away with GH3, but as you said i think now we have a more magenta-like dominance. The tighter crop may be a problem or an avantage depending on the situation but I would say that x1.8 was already enough...

    I really tried to do some run&gun shooting without having mastered the camera so I wasnt looking for the "pretty picture". It seems that some people could achieve that already in some videos posted in this topic. This week I'll try using the camera to get the most beautiful image possible (by my standard of course) and see how it goes.

  • @FilmingArt FCP X, Premiere Pro CS6, Vegas Pro 12, Smoke 2013, are all 32bit

    per VK's wishes a new thread to discuss this in http://www.personal-view.com/talks/discussion/5439/8bit-nonsense

  • Tenjin, what you show is that;

    1. GH3 has a funny pinkiness/readiness to its images
    2. GH3 has a tighter crop than a GH2
    3. GH3 image is soft
    4. GH2 has better detail and is a cleaner, purer rendition c/w GH3 which is mushy.

    Basically the GH3 looks horrible and soft like 5dmk2/nex/dslr etc. The more I see the pink/soft/mushy image the more I dislike this camera, in fact its horrible.

  • rolleyes... back to the topic though! eyeroll not directed @Vitaliy_Kiselev .:)

  • @FilmingArt
    @shian

    It is wrong topic for discussion. Use existing in grading or make new one.

    I also remember that Chris showed that it is really not good idea to go flat most of the times.

  • @shian

    I currently edit in FCP7 where 32bit does not exist. Please direct me to a NLE that does 32bit so I can look it up and run some tests. Also to @rockroadpix it's not about baking an image in, it's about retaining information. If you shoot super flat no matter what you do in post your not going to bring those colors back as if you would have just recorded it normal.

    Leaving settings at 0 across the board is not baking anything in. These cameras do not shoot raw nor have the quality you see in more expensive setups. Just by shooting flat and trying to bring colors and contrast back introduces noise and all other kind of problems. Regardless let me see what this 32but workflow is about.

    Thanks

  • Now that the GH3 has improved the hookup, monitoring and playback of audio, I am looking to simplify my working setup. The absence of plug-in power limits my choice of microphones unless I want to use a Beachtek, etc. Is there a compact, in-line, battery powered source of 48V phantom power?

  • Yeah fellas, bake that contrast/saturation image right in!

  • It's not about adding, it's about NOT LOSING. You are correct about not being able to add. If you work with 8bit in 8bit the image falls apart. If you work with 8 bit in 32 bit, it doesn't. Just look me up, and my work, and you'll see what everybody is talking about. In brief, I spent enough time working in the professional image processing field to know what I'm talking about.

  • Who's wasting time? I'm here to see footage and what's being done. My post I said prior was to simply be careful shooting ultra flat. You can actually lose information doing that. I shoot and edit so I'm speaking from experience.

    Also I would really like to see how 32bit from 8bit is being done. I want to see how there is benefit and it being proven. No way in the world can you just magically add something that does not exist.

    Regardless no need to derail this thread, carry on peace

  • @FilmingArt Obviously you haven't seen the works by @shian. It's the art of squeezing into 8bit. It's doable. It starts before you click the shutter button. Also if you don't trust 8bit codec, why are you wasting your time on this thread?

  • @shian and @ FilmingArt Don´t really want to join your shootout, but both of you have their point on this topic. shian is absolutely right, claiming that a 32bit workflow helps keeping data intact while grading. It´s simply the math of keeping the level of precise calculations in the biggest possible colorspace. FilmingArt is right claiming that you can´t generate 12bit or more out of the recorded 8bits. His statement that keeping the image flat is always wrong doesn´t apply. It´s right if your histogram doesn´t stretch from left to right (in other words is narrower than the full range) it´s better to try not going flat, cause you are using less than the 8bits. If your histograms uses more than the available headroom, its quite useful to go flater. But there is no absolute rule for this, it depends and you have to know your tools. If you are always going for a flat image there is a big chance that you often use less than 8 bits. Just my 5 cents. Sorry for interrupting (and my rusty english) Holger