Canon EXIF Data

When I try and export images taken with a EOS 1DS MKII or a EOS 20D, iPhoto conveniently leaves out the 'Owner Name' and 'Serial' fields. Is there any way to add this data in JPG export. All data is present in the initial RAW files but is not passed in the conversion/export process. It is highly important that this data remains with the JPG's for organisation purposes and I dont want to have to launch EOS Viewer just to acomplish this simple task.

Yes, by default, JPG images from the camera have that EXIF data in them, but I shoot in RAW for obvious reasons (which also contains the exact same data). I dont use iPhoto for image managment, but sometimes use it for quick preview jobs, but on conversion, it strips the key EXIF data that I need it to keep. The only way for me to add this back is in the form of IPTC captions which is both time consuming and annoying. EOS viewer is the only utility that I use for exports now as a result of this. Any ways around it?

Similar Messages

Importing Canon EXIF data into Lightroom

Hi,
sorry if this is a stupid question...
I noticed that when using Canon Image Browser software, that the amount of image information is much more extensive than what I can see in both LR and in Bridge. As an example: In Canon Image Browser I get data for flash exposure compensation, in Bridge and LR I do not have detailed flash information.
Any suggestions?
Also, does anybody know if it is planned to add the feature where you can see the AF point(s) (again, I see it in Image Browser, but not in Bridge or LR)
Thanks,
VR

Most Canon's MakerNotes tags are "public secret", which means: there's no official documentation, but everybody knows them :-)
As FEC info resides in the same (MakerNotes) section as some other info (which is recognised by LR), it shouldn't be difficult for LR to show FEC value too. I believe there could be other problem...
LR should deliver same infos for all camera brands and maybe FEC value of some other brand isn't so easy to "decode". So, it wouldn't be "fair" if LR would show particular values only for some brand. There's no other reason I can think of.
In regard of focus points.. I don't miss that info at all -and even Canon's DPP doesn't show them up.
Bogdan

Exif data in RAW Canon image : timing question

In Photoshop CS 6 ex ( creative cloud ), when I open a Canon T3i DSLR RAW image it does not give the time the picture was taken to the second, only to the minute. In my old Photoshop CS 3, Canon raw images are identified to the second.
For my work I need to know the time when the image was shot to the second.
Am I missing a setting or something?
Thanks in advance for any help on this matter.
Thomas

I was able to solve this problem.
I am using Macs running Mac OS; snow leopard and mountain lion.
Soultion:
In Mac OS : Click on date and time in the top menu bar. Then go to "Open Language and Text...." in the box. Then go to "Region" or "Formats" depending on your operating system. Click on "Times" and customize the settings as to your own needs.
This then enables up to millisecond time for the Canon RAW exif data.
Thomas

Photoshop not seeing lens model in exif data from A3 export

Hi, I am trying to use the lens correction features in CS5 but the lens type can't be read in the exif data of an image I've exported from A3. It sees the focal length and body type. The lens type is listed in the Metadata Inspector in A3. I took the image into iPhoto and checked "extended photo info" and the lens type isn't there either. This happens with at least 2 lenses. One prime and one zoom. Any ideas?

Hi again
Having played with metadata a bit more, it is possible to include EXIF data for the lens size etc.. eg...EF300mm f2.8L IS USM But it doesn't append the manufacturer's name, eg I use Canon, yet 'Canon' is not appended to the Lens data like it is to the camera name..
In the library Inspector click > Metadata > where it says 'General' click the down arrow, then click > Edit > from the window that appears click > EXIF > from the drop down list click > Lens (scroll down a bit)
The lens you used will now be appended to your data.
I have not tried exporting this to Photoshop so maybe you could post back if its possible to export this data to PS or not.
Maybe someone has information on this and can chip in here with advice....
Hope this is helpful....... Gerry....
PS to all reading this, I also noticed while playing around with this ( I have not delved into metadata too much since Ap2) that all my personal details like mobile number, address, email etc are all appended by default, I imagine my address book info has been used here.
A useful feature indeed while selling photo's, or if you intend it to be there..... but not so good if you are not aware it's there in the first place.....!
Just a shared thought to whom it may concern....... Gerry.
Message was edited by: windhoveruk

From Bridge To PS To Export - EXIF Data Lost

Hi all,
I'm wondering what happens to my EXIF data when I import a Canon RAW file via ACR from Bridge to PS. When I export the file as a JPG and then right-click the jpg properties, none of the camera data is recorded. Perhaps there is a tick-box I've just not ticked?
Also, if I add keywords in Bridge, should they carry through the export process? I'm interested to know if it's possible to auto complete the keyword field in flickr when uploading an image.
CS5 with W7 and Canon 5Dii RAW.
Thanks in advance.

Can you be a little more explicit about the exact steps you're taking?
I just opened an image from Bridge into Photoshop by right-clicking a CR2 file, choosing Open In Camera Raw, then hitting the [Open] button in the Camera Raw dialog. Then I did File - Save As - JPEG, and all the camera metadata was retained (per Explorer's Properties, Details tab).
When you say "export", exactly how are you saving the file? With File - Save For Web & Devices, there's a Metadata field that allows you to specify how little or how much to keep.
-Noel

Wrong EXIF data for JPEGs in Bridge and PS

Hello,
My Nikon D300 files are not being properly read by Bridge and Photoshop. RAW files are fine. When I get file info for JPEGs, though, much of the EXIF data is corrupted. For instance, ISO Speed is shown as "51200" instead of 500, and Focal Length is shown as "2.0 mm" instead of 140mm, etc. This incorrect data shows up in Bridge (in the metadata panel and file info) as well as the file info dialog box in Photoshop.
When I get the EXIF info in Preview.app, all the info is correct.
Anyone know what might be going on?

Update - this problem is not limited to my D300 files. I just realized that the JPGs from my Canon SD800IS point & shoot are also not being "seen" properly by the Adobe apps. The ISO value doesn't even show up in CS3 apps, but I can see that data in Preview.app.

Lightroom strips very valuable EXIF data - details

Hey everyone - I've just been playing around with some EXIF stuff, and I noticed something very concerning.
I do a lot of macro photography, specifically with Canon's MP-E 65mm 1x-5x Macro. This lens records its macro magnification factor in the EXIF data, and does so far more accurately and conveniently than I can.
I know that Lightroom and Photoshop strip out A LOT of obscure EXIF data when processed, but this magnification data is extremely valuable when reviewing my photos at a later date.
I can provide sample files if needed, and here is my observations so far:
- data stays intact when converting from .CR2 to .DNG
- data is stripped when converting to JPG, TIFF, and other formats
- data is stripped by both Lightroom and Photoshop
Here is the EXIF data (from exiftool) right from the Canon CR2 or DNG file (both are identical):
http://don.komarechka.com/exif/exif-original.txt
Here is the EXIF data (from exiftool) from a jpg that has gone through Lightroom:
http://don.komarechka.com/exif/exif-lightroom.txt
You'll notice a HUGE amount of extra data in the original raw file. It is certainly worth noting that the EXIF data in a JPG, unaltered from the camera, contains all of the same data as the RAW file.
So, is this something that has been overlooked, is there any way to change this behaviour? Even though Lightroom might not be able to decode this data, I don't see a reason why it cannot be left intact.
Thank you.
- Don Komarechka
http://don.komarechka.com

donkom wrote:
clvrmnky, thanks for your response.
Here's an example for you, the one I've been giving:
I shoot with a special macro lensm the Canon MP-E 65mm f/2.8 1-5x Macro. This lens does not zoom, but the magnification can change from 1x to 5x.This lens communicates its magnification to one decimal point accuracy to the camera, which adds it to the maker notes.
This is important in reviewing images for a number of reasons, including calculating the effective aperture and depth fo field. This is a valuable piece of information that is stored within the makernotes that is removed from the image when sending it through LR, Photoshop, or ACR.
That isn't the only valuable information, however.
The makernotes will tell me if the image was captured using LiveView, if Mirror Lockup was used, if the shot is part of a bracketed set, what the internal camera temperature was, etc. etc.
I'm not sure you've justified your reasoning behind why this block of data shouldn't be blindly copied. If it is removed simply because it is not understood, I would like the option to understand this data on my own, using third-party tools, after the image has left LR.
I understand that this can be proprietary, but likely far less so than the RAW file formats that LR and ACR already understand. It would be trivial to understand where this block of data begins and ends and to leave it in the file on export.
I think this would allow for more in-depth searching based on metadata, for whoever wants to take up that torch. For example, what if I want to see all macro photos I took at a 4x magnification or higher. What if I want to see all photo I took using LiveView. Even if LR doesn't want to do this, stripping the data out prevents anyone else from doing it in the future.
Well, there is an SDK for metadata that has been around for awhile, which allows for custom metadata definitions. But, according to the SDK:
"Values stored in custom metadata fields are stored only in Lightroom's database. In the current release, a plug-in cannot link custom metadata fields to XMP values or save them with the image file."
So, this is more for searching and interfacing with tagset plugins.
Even so, using the SDK to get at maker notes is a losing proposition.
Note that some metadata is proprietary and will not be read into the database. This is to be expected. Lr is not an arbitrary metadata reading app, and there is no guarantee that any app could read all metadata. For example, Lr tries its best to get the serial number info, but this is because there is a lot of value in that for other Lr operations. So the contortions necessary to reliably get that is worth it. Another example is lens info (which is a twisty maze of passages; no app is ever guaranteed to actually retrieve lens info reliably in all cases) where there is a lot of value trying to extract the information that makers often store in very interesting ways. In some of those cases I think Lr will look in the maker notes, but only after exhausting other avenues, and with the caveat that it may never be able to get some information. The app does its best to get at the most valuable info it can get that fits with the standardized metadata models in place.
However, the key here is that maker note data is not in exported files that Lr makes, because it is not normalized data that belongs to the vendor. (This obviates the recommendation of using Metadata Wrangler, which can filter out only that metdata that exists in Lr; I had vaguely remembered a setting that referred to this section but was wrong.)
The field and data formats are not standardized, so you are asking Lr to understand most or all data from all or most lenses and bodies (all of it in varying degrees of similarity and difference) not just data from this lens and this body.
This is also not a trivial matter of "copying" the maker notes over, because copying implies parsing and duplicating what is essentially unknown formatted data containing proprietary data, possibly by custom serialization routines. Remember that maker notes were never intended to be editable, and could be composed of any number of data formats. Some cameras make maker notes that are megabytes of nulls and nothing else!
I think you are out of luck for this specific case. Perhaps with EXIF 3 we will have a more standardized interface cameras and software can more easily interoperate on shared data. Makers need to stop using the maker notes! It was always an egregious hack.
One workaround I can think of is to have a post-export action that uses EXIFTool to update exported images. For those cases where it matters, you could create your own "sidecar" file that has only the maker notes, and then shove those into the JPEG after they are created, or just read it from the on-disk copy and then put it in the new file (possibly in the same directory and added back into the catalogue for convenience.)

Lightroom strips out certain EXIF data (maker notes)

Hi there!
Simple issue: Lightroom and Camera Raw strip certain EXIF data that is extremely useful to macro photographers.
Use case: Canon macro photographer using the MP-E 65mm lens. The lens communicates its Macro Magnification value and this is passed to the camera which stores it in the maker notes. This data is extremely valuable to determine scale and measurements of photographed subjects.
This data is removed when the image is processed through any Adobe product.
Here's some supporting documents:
- RAW file from Canon 5D mark II: http://donkom.ca/lr4-makernotes/_MG_1848.CR2
- EXIF data (extracted via exiftool), please note the inclusion of "Macro Magnification" and the value "4.8x": http://donkom.ca/lr4-makernotes/_MG_1848.txt
- Processed JPG file from Canon 5D mark II through Lightroom 4 (all exif data selected to be included): http://donkom.ca/lr4-makernotes/_MG_1848-processed.jpg
- EXIF data (extracted via exiftool), please note the absense of "Macro Magnification": http://donkom.ca/lr4-makernotes/_MG_1848-processed.txt
Thanks very much,
- Don Komarechka
www.donkom.ca

Just checked this in the final release of LR4 and this issue has not been addressed. I'm hoping that someone has noticed this and can give it some attention!

IPhoto '08 loses exif data when exporting RAW to JPG

I'm using a Canon 40D shooting only RAW. I just recently noticed that when I export to JPG, iPhoto loses quite a bit of important EXIF data, including, aperture info.
Is this a known issue, or is it something unique to my system?

I guess I misworded it. I understand that the info doesn't go away or come back. Either there's a problem in both Finder and flickr (I've uploaded the file to flickr.com) where neither finds the info in the jpeg or there's a problem in the way iPhoto writes the EXIF data to the file.
Today, I downloaded EXIFViewer for an alternate look at the EXIF fields and the aperture data is there according to EXIFViewer. So, now I think the bug may be with flickr. Can't really call it a bug in Finder, since the expected functionality for finder is not to get "aperture info", but "More info."
In any case, these are the fields in the More Info:
|RAW:Name_|_RAW:Value_|_JPEG:Name_|_JPEG:Value|
|Dimensions|2586x3892|Dimensions|2586x3892|
|Device make|Canon|Device make|Canon|
|Color space|RGB|Color space|RGB|
|Profile name|Adobe RGB (1998)|Profile name|Generic RGB Profile|
|Focal Length|44|Focal Length|44|
|Alpha channel|0|Alpha channel|0|
|Red eye|0|Red eye|0|
|FNumber|4|
|Exposure|1/60|Exposure|1/60|
|Last opened|Monday, May 19, 2008 6:31 PM|Last opened|Today, 9:31am|
And the meta info on flickr is here:
http://www.flickr.com/photos/carloscervantes/2536040124/meta/
Again, no aperture data in either flickr or Finder.

IPhoto '08 corrupts EXIF data on export

Hello All,
In using iPhoto '08 (including the latest update to 7.1) I am noticing the when I export files the EXIF data is getting corrupted.
My original files are fine--all EXIF data shows up properly, and galleries which I post to that are capable of displaying EXIF data display it just fine. However, when I export a file from iPhoto to JPG format, the galleries are unable to display the EXIF data. Using the Firefox extension, 'EXIF Viwer' ( https://addons.mozilla.org/en-US/firefox/addon/3905 ), I see there are errors in the data (screenshot here: http://jaaulde.com/exif_viewer.png )
Thanks for any help you can provide.
Jim

Jim:
It may be the server side software that's causing the problems. Another thread went thru something like this extensively and we found that files from some cameras, Canons for one, are not read properly by the software. We've downloaded the files and read the EXIF data and it was all there. I have a gallery of files from various cameras as an example: http://gallery.mac.com/toad.hall/100196. Click on the "i" button in the slideshow and you'll see those that get the EXIF data correct, primarily the shutter speed, and those that do not. I don't remember the thread but you can search this forum for "EXIF web gallery" or similar.
Do you Twango?
TIP: For insurance against the iPhoto database corruption that many users have experienced I recommend making a backup copy of the Library6.iPhoto database file and keep it current. If problems crop up where iPhoto suddenly can't see any photos or thinks there are no photos in the library, replacing the working Library6.iPhoto file with the backup will often get the library back. By keeping it current I mean backup after each import and/or any serious editing or work on books, slideshows, calendars, cards, etc. That insures that if a problem pops up and you do need to replace the database file, you'll retain all those efforts. It doesn't take long to make the backup and it's good insurance. iPhoto doesn't not have to be closed to run it, just idle.
I've written an Automator workflow application (requires Tiger), iPhoto dB File Backup, that will copy the selected Library6.iPhoto file from your iPhoto Library folder to the Pictures folder, replacing any previous version of it. It's compatible with iPhoto 08 libraries. You can download it at Toad's Cellar. Be sure to read the Read Me pdf file.

EXIF data - Why is so much is missing in LRx but in RAW / DNG / CR2 images

I've seen the limitations in the EXIF data as shown in LR. I've seen the comments that it would be SO useful to sort / filter by all the EXIF data available in LR.
However LR shows a small proportion of the information that is available in the Meta data but there is missing EXIF data, that is of use to users, not every day, but it is there and with the aforementioned improvement of searching / sorting / grouping / stacking, I'd like this data to be accessible.
I was looking to find all the correctly exposed images in sets of 3 auto bracketted images -2, 0, +2 from todays shoot but this info is not listed in LR
So I looked in PhotoGrok, and it told me that the image I was looking at was AEBBracketValue -2, ie 2 stops under exposed in a set of auto bracket.
It also told me my camera was 37º when I was shooting in Cape Town this morning. It most certainly was not that warm outside.
My reason for finding the correctly exposed images in the sets was to see if they had sufficient exposure data to be used as one image rather than combining the 3 bracketted images using fusion / enBlend software to rescue the shadow detail and highlight detail in my shoot.
If you do play with PhotoGrok, you see more info than may be / is / could possibly be useful. But it does list a great deal.
I do get the basics
exposure
aperture
focal length
35mm equivalent
focal distance
hyperfocal distance
colour balance
AEBBracketValue
and the list goes on.
More importantly, this data has been extracted by LR from Canon 5DII CR2 files to DNG, so LR can see all this info.
Anyway, that is my request.
There is limited EXIF data displayed in LR, there are requests for sorting / searching / listing / stacking by more of the meta data that LR accesses.
I would like to see much more of this data available to be sorted / searched / stacked, so I can find amongst all the EXIF data, the AEBBracketValue = 0, ie correctly exposed images.
Rob Cole - Does your anyfilter access more of this info?
Hillrdg- you asked me to give my motivations for making suggestions, so I''ve taken your advise on board and to substantiate my argument.
yes, there is a workaround - It is to sort all the photos by capture time or file number and arrange them into 3 images in a grid view and just select the correct column, but this is slow. More importantly, this request is about vastly improving access to EXIF data and for other uses of the vast amount of EXIF data available in images.
hamish NIVEN Photography

EricInsalaco wrote:
Now I was under the impression Preview/Versions only take up a miniscule space on the HD since they don't FULLY copy the master file, they more create a bridge between the two that amounts to a few MB. Is it possible that it's taking up a much larger amount than intended here (a la the same basic mail attachment problem, but with Preview)? If so, what directory would that be located in?
Apple's documentation on Versions and what is kept in the Versions database is misleading, in my experience, though others will argue to the contrary.
In any case, all the Versions files and the database that keeps track of them are in an invisible folder in the root directory called
.DocumentRevisions-V100
The easiset way to check its size is to show invisible files by pasting the following command in Terminal:
defaults write com.apple.finder AppleShowAllFiles TRUE; killall Finder
press 'return' on the keyboard.
Now navigate to the hard disk in Finder and you should see DocumentRevisions and its size.
To turn off invisible files, use the same command as above but replace TRUE with FALSE.
Message was edited by: softwater

Lens-to-subject distance in EXIF data

I'm looking for lens-to-subject distance in my EXIF data (Canon 7D Mk II). Is it captured?And if so, how do I view it?

Hi wildimagesfla!
Thanks for posting.
The distance between the lens and the subject being focused on is not something that is captured and recorded in the EXIF information.
Did this answer your question? Please click the Accept as Solution button so that others may find the answer as well.

Cs6 focus distance in exif data.

cs6 doesn't save the focus distance in the exif data (Canon 7D) like cs5, is there a fix for this?

I opened your images in CS6 and CS5 this is what I see in file info:
CS5Cs6
Windows Explorer does not show Distance and Chrome does not show it either
Propoerties does in the cs5 not CS6

IPhoto exif data

Does iphoto strip some of the exif data from photos? I'm currently using iPhoto as my photo management tool and I also use photoshop elements to do some editing. When I view the photo info in iPhoto, it seems like the data is pretty skimpy.
Specifically, I'm looking for white balance data (right now). I'm taking a photography course and was testing different white balance settings... and those settings aren't showing up in my photo info. I REALLY don't want to have to buy another program like Aperture, especially considering I already have photoshop. If iPhoto has this info somewhere, can you help me find it?!?!
Please help!! Thanks!
Erin

Erin:
iPhoto doesn't strip the data it just doesn't read all of it. You can get all of the data read by using a 3rd party application likeEXIF Viewer. Just put the app in the Dock and drag a photo from iPhoto onto it. It will open and give you the following information:
File name: 2008-06-12-Mateo graduates KB-137.JPG
File size: 3060921 bytes (2816x2112, 4.1bpp, 6x)
EXIF Summary: 1/60s f/2.8 5.8mm
Camera-Specific Properties:
Equipment Make: Canon
Camera Model: Canon PowerShot SD700 IS
Maximum Lens Aperture: f/2.8
Sensing Method: One-Chip Color Area
Lens Size: 5.80 - 23.20 mm
Firmware Version: Firmware Version 1.01
Owner Name: W. FRITTS
Image-Specific Properties:
Image Orientation: Top, Left-Hand
Horizontal Resolution: 180 dpi
Vertical Resolution: 180 dpi
Image Created: 2008:06:12 13:07:51
Exposure Time: 1/60 sec
F-Number: f/2.8
Lens Aperture: f/2.8
Exposure Bias: 0 EV
Flash: No Flash, Compulsory
Focal Length: 5.80 mm
Color Space Information: sRGB
Image Width: 2816
Image Height: 2112
Rendering: Normal
Exposure Mode: Auto
Scene Capture Type: Standard
Focus Type: Auto
Metering Mode: Center-Weighted
Sharpness: Normal
Saturation: Unknown
Contrast: Unknown
Shooting Mode: Manual
Image Size: Large
Focus Mode: Single
Drive Mode: Single
Flash Mode: Off
Compression Setting: Superfine
Macro Mode: Normal
Subject Distance: 0.540 m
White Balance: Auto
Exposure Compensation: 3
Sensor ISO Speed: 224
Image Number: 100-4933
Other Properties:
Resolution Unit: i
Chrominance Comp Positioning: Centered
Exif IFD Pointer: 196
Compression Scheme: JPEG Compression (Thumbnail)
Horizontal Resolution: 180 dpi
Vertical Resolution: 180 dpi
Resolution Unit: i
Offset to JPEG SOI: 5108
Bytes of JPEG Data: 6214
Exif Version: 2.20
Image Generated: 2008:06:12 13:07:51
Image Digitized: 2008:06:12 13:07:51
Meaning of Each Comp: Unknown
Image Compression Mode: 5
Shutter Speed: 1/60 sec
Metering Mode: Center Weighted Average
Focal Plane Horiz Resolution: 12515 dpi
Focal Plane Vert Resolution: 12497 dpi
Focal Plane Res Unit: i
File Source: Digital Still Camera
White Balance: Auto
Digital Zoom Ratio: 1
Base Zoom Resolution: 2816
Zoomed Resolution: 2816
Exposure Mode: Easy Shooting
ISO Speed Rating: Unknown
Digital Zoom: None
Self-Timer Length: 0 sec
Canon Tag1 Length: 92
Flash Bias: 0.00 EV
Sequence Number: 0
Canon Tag4 Length: 68
Image Type: IMG:PowerShot SD700 IS JPEG
TIP: For insurance against the iPhoto database corruption that many users have experienced I recommend making a backup copy of the Library6.iPhoto (iPhoto.Library for iPhoto 5 and earlier) database file and keep it current. If problems crop up where iPhoto suddenly can't see any photos or thinks there are no photos in the library, replacing the working Library6.iPhoto file with the backup will often get the library back. By keeping it current I mean backup after each import and/or any serious editing or work on books, slideshows, calendars, cards, etc. That insures that if a problem pops up and you do need to replace the database file, you'll retain all those efforts. It doesn't take long to make the backup and it's good insurance.
I've created an Automator workflow application (requires Tiger or later), iPhoto dB File Backup, that will copy the selected Library6.iPhoto file from your iPhoto Library folder to the Pictures folder, replacing any previous version of it. It's compatible with iPhoto 6 and 7 libraries and Tiger and Leopard. iPhoto does not have to be closed to run the application, just idle. You can download it at Toad's Cellar. Be sure to read the Read Me pdf file.≤br>
Note: There now an Automator backup application for iPhoto 5 that will work with Tiger or Leopard.

Custom white balance and EXIF data

Using 3.1.1 for two weeks or so, all is good for now but I have a question. After shooting the same subject with different white balance (still learning digital photography) with my D7000, a few with auto WB, a few with the camera's incandescent settings and a few with customized K degrees, 4,500K, 5,000K and 6,200K to analyze the differences, on the exif data, Aperture only shows AWB and the "incandescent" setting on the camera whenever used, but it doesn't show me when I set the degrees by numbers on the camera, it shows as "auto white balance", is this part of the white balance glitch? Although I can see the difference between those custom K degrees on preview, how do I find out in Aperture the exact K used on those custom WB other than looking back on the camera?

Thanks for replying.
No, not in Auto mode. I was in Aperature mode.
I have used custom white balance many times before.
I tried the battery removal etc. No luck there.
Removed and reinserted card. No help.
I finally got out of this hangup.
I downloaded all images to PC using the Canon EOS software.
Then I deleted all images from card in camera.
Then when I set up custom white balance again, it worked just as expected.
There was a very brief flash of the "Busy..." message and then into the next step to set .
Have no clue as why this suddenly started.
Maybe struck by stray gamma ray burst
Canon 3Ti, EF 50mm f/1.4 USM, EF-S 18-55mm f/3.5-5.6 IS II, EF-S 55-250mm f/4-5.6 IS II, 320EX Speedlite

Canon EXIF Data

Similar Messages

Maybe you are looking for