Menu

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Messages - tickerguy

#1
Remove the CF card and battery.

Re-insert the battery and close the card door (NO card in the camera)

Does it boot?

If so, the card is corrupt but the bootflag is set.  That is, the files that have to be on the card aren't but the camera is being told to look for the card files.

Either (1) reformat the card (in which case it will boot without loading ML) or (2) fix the card so it has the correct files on it.
#2
Tragic Lantern / Re: 7D Raw Thread
August 20, 2013, 05:36:28 AM
Quote from: Walter Schulz on August 17, 2013, 09:07:57 PM
AFAIK you can't set the camera's bootflag using a card with 64 GByte capacity.
I had the same benchmark problem with the non-bootable alpha 2 version.

My advice: Buy a cheap slower card (up to 32 GByte) and use this one for initialization and first tests.

Ciao
Walter

Yes you can.  It works on my 64GB card.
#3
There's a problem here in that it APPEARS that Canon is reading every third line (or thereabouts) from the sensor.  This is why you're getting the moire patterns and it's also why it appears that horizontal and vertical resolution in video lines are not equal.

That may not be fixable; to get the full quality the sensor can resolve you have to be able to read the entire sensor at the frame rate (e.g. 30 fps) and interpolate in the firmware.  It does not appear that any of these cameras can actually do that physically -- nor do they have to in order to shoot stills.

If you can't clock the data out of the sensor fast enough then the rest doesn't matter as you don't have the raw sensor data to interpolate; you cheated when you read the sensor, which limits your ultimate resolution.

From what I can determine this is what they're doing and it makes sense; even the 7D, which can shoot 8fps stills, only need to be able to read the sensor in 1/10th of a second or so at full frame rate.  There's quite a difference between that and reading it at 30fps or more.
#4
Well, I have a 128GB new one here..... let's hope it doesn't start doing creepy things -- I just got it.

My 32GB cards, of which I have many, have been flawless.
#5
Yeah, just tried that, it worked.  Something in the Canon firmware doesn't like setting the flag on these cards, but once it's set it works.
#6
I can't get it to come up with an XC card either; it will neither see it nor will it allow me to perform a firmware update from an XC card.