Hacked GH1 and Canon 60D shoot. My impressions of the cameras.

Lucas Adamson

Well-known member
I don't want to start a new Canon vs. Lumix thread, as I'm a good boy and I know it's verboten, and rightly so, but I have just spent the weekend doing a shoot of a circus/physical theatre piece in a converted church (Circomedia in Bristol UK) with a hacked GH1 and a Canon 60D and there have been issues I feel I ought to report with both as I didn't know some of this stuff before (in spite of endless reading.)

1. Images from both cameras at 1080p25 match up very well. I turned NR and sharpening off on both.

2. The 60D overheated 3 times and caused error warnings. We didn't lose a shot over it, as it recorded the image to disc, but it did stop recording. The GH1 didn't at all.

3. The 60D had a max 12 minute record time. The GH1 had none.

4. The 60D produces file sizes 3 times the size of the GH1 (hacked to lpowell reliable settings) That's 16Gb to 5.5Gb as I remember it. Go figure! They're both full HD H.264 but in different wrappers - AVCHD vs. Quicktime.

5. Canon Quicktime files have consecutive unique numbering making file management during editing easy. Panasonic AVCHD files reset to 00000 each time you delete the card, making file management a freaking nightmare I still haven't resolved. Premiere CS5 supposedly edits native AVCHD, but it's rubbish. I wish I'd stayed with and upgraded FCS now, as I'm going to have to transcode anyway, to keep my files in check as much as anything. I'm using XDCam HD422 50Mbps, which is good, but not perfect - there is a slight degradation, but it has to be worth it, because native AVCHD is horrible. This is the BIG downside with Panasonic's AVCHD, in my opinion - nasty file management - impossible almost. The editing of AVCHD I can't complain about, as a faster computer with a CUDA card would eat it up I'm sure.

6. I am shocked to report that I used the 14-140mm lens exclusively for 2 days solid. I have Zeiss manual primes that I've had from the Canon 5D days, and I love them. Not only that but historically I've always said that I hate autofocus and zoom lenses, being a purist manual focus primes man. But on this shoot, I started off with the 14-140 as I needed a wide, and I just loved it. I didn't need short depth of field as the background was blacked out, creating highly focussed subjects anyway. Great lens. It did go hunting now and then, but I my friend Adam on the 60D fared worse focussing manually. I shot at 140mm a lot too - really great lens.

7. My GH1 image is very clean at iso800, which I shot at for most of the shoot. The 60D shot at similarly high iso settings, and I've seen more coloured pattern noise on his images than mine.

8. The Canon is much better built and the ergonomics are good, and there was a definite sense that I had a toy and Adam a real pro camera. The images tell a different story though.
 
Last edited:
I edited native AVCHD in Premiere Pro CS5 and had NO problem without a CUDA enabled video card. Not sure why you call it rubbish. Worked great. (However, the file structure and numbering sequence is a pain I agree).
 
well here is MY recent 60d story. I just got it a couple of days ago and fell in love instantly with it. It feels perfect! The size and weight are wonderful. And the LCD is amazing! Best LCD ever! Sadly though everything changed when I dropped it into my timeline. The footage is very soft. At first I thought it was because I was shooting wide open at night. So I shot closed down the next day still very unhappy with the lack of detail. I was also surprised at how bad the noise was. I knew it would look softer and I was cool with that but I thought it would at least give me that "canon" look. Instead it just looks like up-rezzed SD footage like everyone else has been saying. It actually looked very similar to my hacked GF1 footage. After looking at only GH13 footage everyday for months, my eye has been trained to be extremely critical of image detail. I wish I could put the GH1's insides into the 60d. I almost want to keep the 60d just because its so lovely on the outside. Sadly though I will be returning this camera to Adoroma tomorrow and ordering the GH2. Also the 60d files ran very slow on my crappy PC in CS5 but my GH1 files play fine.
 
Yeah - if they came out with a GH2B with a 1,040,000 pixel EVF and 1,040,000 pixel flipout panel I would be willing to pay $1500 for it. Also if they added the ability to shoot 4K jpeg sequences with unlimited record time I'd pay another $300 on top of that ...
 
If you want to keep the file numbers consecutive on the GH1, don't erase the whole card, just delete the files in the 'stream' folder once you've transferred them. :)
 
Im ready to switch to the gh2 myself, just can't find one anywhere. Im really tired of the t2i overheating. The summer was rediculous, tried doing a shoot in fairly hot weather, it was shutting down every five minutes. bit embarassing I have to say. " excuse me, ahhh, my camera is overheating" huh???? never heard of that before. "Welcome to Canon Dslr's"
 
Ahhhhh....Matthew, do you have any idea how hard I've looked for a solution like that? Thankyou Thankyou Thankyou!!!!.

So I delete the MTS files on the computer, not on the camera, and then empty the trash to free the space up, right?


What do I do regarding renaming them now that I have 6 files called 00000 etc.??? I can't just re-name the file itself because of all of the corresponding files (of which there are quite a few), can I? Should I just rename all the related files the same thing? I could try it...
 
I edited native AVCHD in Premiere Pro CS5 and had NO problem without a CUDA enabled video card. Not sure why you call it rubbish. Worked great. (However, the file structure and numbering sequence is a pain I agree).

It is the file numbering mess that I'm talking about, but I have also heard of complaints (from professionals) about Premiere's handling of AVCHD files when doing a lot of cutting to make fast cut, complex edits. Admittedly I need a CUDA card to make it work as it should.

The file management is a crime though. Horrible! Lovely files, horribly managed.
 
6. I am shocked to report that I used the 14-140mm lens exclusively for 2 days solid. I have Zeiss manual primes that I've had from the Canon 5D days, and I love them. Not only that but historically I've always said that I hate autofocus and zoom lenses, being a purist manual focus primes man. But on this shoot, I started off with the 14-140 as I needed a wide, and I just loved it. I didn't need short depth of field as the background was blacked out, creating highly focussed subjects anyway. Great lens. It did go hunting now and then, but I my friend Adam on the 60D fared worse focussing manually. I shot at 140mm a lot too - really great lens.

I say it many times in various treads the 14-140 is a nice lens if have enough light with it, i already used in 2 TVSpots with nice results.
 
It is the file numbering mess that I'm talking about, but I have also heard of complaints (from professionals) about Premiere's handling of AVCHD files when doing a lot of cutting to make fast cut, complex edits. Admittedly I need a CUDA card to make it work as it should.

The file management is a crime though. Horrible! Lovely files, horribly managed.

Hmm.. Here's what I do in CS5 with the GH1/2. I number the cards in separate bins. I don't need each file to have a unique number. I manage them myself and it only takes seconds to do.
GH1/2\
Card_1\ files
Card_2\ files

and so on... Been editing AVCHD in CS5 since it came out. I edit events that last hours and have never had a management issue. As for performance, get a cuda card, or even a lower end hackable version (I recommend at least a GTX260 1GB) and the AVCHD files will edit like butta.
 
If you want to keep the file numbers consecutive on the GH1, don't erase the whole card, just delete the files in the 'stream' folder once you've transferred them. :)

I don't have a GH1 or GH2 but coming from dealing with P2 for a long time (and other file format based acquisition) this just seems like a recipe for unusable footage at some point. Use Metadata entry methods inside your NLE for designating the files separately from one another. Card and file structures are written by these cameras for a reason, and NLE's need these for a reason. Seems silly to risk for just consecutive file numbers.
 
From a Final Cut Pro perspective, if you place the private directory into another directory, like ; 'DVXPROJ - D1 - C1' (Day 1 Card 1) when you log and transfer, it will use that information in the names of the clips.

I always back up the whole card into a directory on 2 drives.
 
I don't have a GH1 or GH2 but coming from dealing with P2 for a long time (and other file format based acquisition) this just seems like a recipe for unusable footage at some point. Use Metadata entry methods inside your NLE for designating the files separately from one another. Card and file structures are written by these cameras for a reason, and NLE's need these for a reason. Seems silly to risk for just consecutive file numbers.

I don't think you get what he's saying. This method would keep the file structure intact, but deleting only the large video file after digesting it would mean that the numbering would continue from the last one, because the small metadata files would retain their numbering, and the camera builds numbering upon them, hence, complete file structure on all files with sequential numbering for a whole project. That's how I understood it, anyway.
 
Hmm.. Here's what I do in CS5 with the GH1/2. I number the cards in separate bins. I don't need each file to have a unique number. I manage them myself and it only takes seconds to do.
GH1/2\
Card_1\ files
Card_2\ files

and so on... Been editing AVCHD in CS5 since it came out. I edit events that last hours and have never had a management issue. As for performance, get a cuda card, or even a lower end hackable version (I recommend at least a GTX260 1GB) and the AVCHD files will edit like butta.

My fear about doing this is that situation where it asks me "where is file 00000?" and asks me to locate it...how do you manage that if you have 25 versions of 00000?

Admitedly this only happens if you start shifting folders around and upgrading drives etc., but in my experience, this inevitably happens and only unique file number structures can make this simple, .
 
Back
Top