A warning about the hack

Perhaps there is some misunderstanding of the b,c ratings,
Maybe the "b" setting should be renamed "safe"
and "c" should renamed "experimental" that would save some headache
 
At the moment I am using these settings. Thanks to Ipowell for this excellent AVCHD flavour.


40Mbps AVCHD High Reliability Patch

In short, this patch combines the average bitrate of the C settings with the reliability of the B settings.

40Mbps AVCHD High Reliability Patch:

Patches for End Users
. Wrapper
.. Native 24p/25p: unchecked
. AVCHD Compression
.. Video Bitrate FHD/SH: 41000000
.. Video Bitrate H: 24000000
.. Video Bitrate L: 16000000
.. Overall Bitrate: 43000000
. AVCHD GOP Length: unchanged

Patches for Testers
. AVCHD Compression
.. Preset bitrate: 180
.. Preset bitrate 2: 180


I haven't had an issue and the picture is gorgeous. In fact I don't think I've had an issue with AVCHD apart from the 24/25p check which definitely causes errors. I would only use my camera as a b camera and I would always carry a spare 132.bin firmware with me that I could apply to the camera should the worse happen. It takes less than 5 mins to de hack the camera back to virgin settings using a laptop and card reader.

As great as the picture is though I'd still be wary about using it on big paid gigs. I see it as an extension to a shoot and also as a superb timelapser.
 
Never have had another crash after I started using lpowell's settings with 24p unchecked.

Had constant crashes all the time with the C and B settings with 24p checked using a Class 10 card.
Installed the new settings and haven't had a one yet.
 
Ya, it seems like the 24p checked was the problem all along. Now with a free way to remove pulldown to a codec of your choice, it is not so bad...
 
At the moment I am using these settings. Thanks to Ipowell for this excellent AVCHD flavour.


40Mbps AVCHD High Reliability Patch

In short, this patch combines the average bitrate of the C settings with the reliability of the B settings.

40Mbps AVCHD High Reliability Patch:

Patches for End Users
. Wrapper
.. Native 24p/25p: unchecked
. AVCHD Compression
.. Video Bitrate FHD/SH: 41000000
.. Video Bitrate H: 24000000
.. Video Bitrate L: 16000000
.. Overall Bitrate: 43000000
. AVCHD GOP Length: unchanged

Patches for Testers
. AVCHD Compression
.. Preset bitrate: 180
.. Preset bitrate 2: 180


I haven't had an issue and the picture is gorgeous. In fact I don't think I've had an issue with AVCHD apart from the 24/25p check which definitely causes errors. I would only use my camera as a b camera and I would always carry a spare 132.bin firmware with me that I could apply to the camera should the worse happen. It takes less than 5 mins to de hack the camera back to virgin settings using a laptop and card reader.

As great as the picture is though I'd still be wary about using it on big paid gigs. I see it as an extension to a shoot and also as a superb timelapser.


hi, i use same patch. i haven' t any problem less that sometime, at indoor shooting, when i go from highlights to dark spots, the image become.. how can i describe.. very poor ..noisy like i use an phone camera.. but this happened just twice. an restart resolved the issue. im not sure if is some correlation here with that happened with first footage after i've switched from mjpeg to avchd lite. and i have pulsating light on motion jpeg ( indoor) but i heard that's quite normal.. and more obvious using patched firmware version then original 1.2 version. i use sandisk class 10 on gf1
 
Last edited:
Re: Popping in your faster class 10 card to avoid the problem, I think that is your problem not the hack. IF you're getting paid to shoot a gig and want to use the hack I can't understand why you'd be shooting on class 6 cards to save a few bucks. I'm on 32gig Dana Elect cards and they work great at high bit rates with the hack. Cost -- $99 for 32 gigs. Wouldn't dream of shooting on a class 6 with the hack if someone was paying me as a professional. FWIW: I shoot, immediately archive to a blu-ray disc at night, then reformat all cards for the next day. One lock up and missed shot probably costs you 10 times more than the diff between a class 6 and class 10 in lost income from the client.
 
I'm amazed that you do a paid-shoot without even bringing a backup recording device with you. Sorry, but that's just stupid. And I think it's really weird that you seem to blame the 'hack' for the faults. Hacking of the firmware is nothing more than changing some parameters the firmware and hardware already were capable of doing. It's not entering viruses or adding bonus crash-sensitivity areas in your camera that were not already in there.
Of course, if you stretch your hardware to the limit you'll always be at higher risk of equipment failures.

*All* digital cameras freeze from time to time, depending on electrical load entering the device, or using faulty or damaged storage media. I've had brand new SanDisk Extreme SDHC cards give up on me, I've had fairly new batteries fail on me. You name it, it happens. Especially in the digital world you should take this into account.

My guess is your problems had nothing to do with the camera, or the firmware patches, but everything to do with bad or damaged SDHC. If a digicam can't properly write or read from its storage medium, it will freeze on you. I've seen that happen even before using any firmware patches.
 
Back
Top