pdsilen wrote:
I recently did a very big photo shoot. The customer required a wide angle lens, 16-50mm and RAW images. I was told that they would do the editing. So, I programmed my crop sensor camera to shoot in RAW format. When I returned home from the shoot I transferred my photos to MS Photos only to find that they all came out in JPG. And how can I prevent this from happening again? Your feedback would be very much appreciated.
Like others have said look at your cameras files with the Windows File Explorer. Set the View to show extensions.
Why aren't you using Photoshop, Lightroom, or some other professional grade image processor/editor? If you set your camera to Raw the files should be Raw on your PC unless you did something really strange to change them. I beleive only a Raw processor can change the camera output. Learn and live.
Gene51 wrote:
You don't program a camera to record raw. It is a simple setting off a menu or a dial. It is a simple matter to change the File Explorer Options to NOT hide extensions for known file types. Just pick a folder to display, then click on the View option in the top menu (View, Home, Share, View) and once that opens, you will see the checkbox for File Name Extensions. If it is not clicked, then click it so they will be visible. You can also arrive at the same place by typing in File Explorer Options in the search field at the bottom left corner of your screen (desktop).
Word of advice - never ever take on a job when you are uncertain about your skill level vis a vis the client's request. Nothing more embarrassing (or potentially exposing you to a lawsuit) than over promising and under delivering. If you are not 110% you can deliver what they need, then politely pass on it. Though, this is very basic stuff, and you really do need to get up to speed regardless of whether you are doing work for a client or for yourself.
You don't program a camera to record raw. It is a ... (
show quote)
For security, I always have file extensions visible in explorer. Then you can always see if it's an exe file that someone wants you to double click.
Another possibility:
I am sure, by now the OP has "learned his lesson" about undertaking jobs that he might be ill-prepared for, etc.
However! It also sounds like the client does not exactly know what they were specifying either. They asked for a "wide-angle lens" and RAW files. They might be parroting technobabble that they heard kinda thing.
If the exposures and white balance are correct on these Jpegs, and the files do not need an extensive recovery of detail, the Jpegs might suffice.
The assignment was all that "BIG" why did the client not hire an experienced professional? Sometimes you see a case of the blind leading the blind.
I've been in this business for a very long time and I can write a very funny book about things perfectly nice clients had asked for and my job began by deciphering their incorrect terminology.
This is just a wild guess based on kerfuffles and unmitigated mess-ups I have seen. Typically, I would get a panicked call from a "client" complaining that "we hired this terrible photograher who came up with lousy pictures and we need them yesterday, can you shoot it right away? Then, when they tell me their specifications and what THEY THINK needs to be done, I have to tell them that if they hired Hoodidi, he'd have a hard time filling that requirement and let alone at that budget"!
YES! I agree that folks shod not undertake jobs they are not qualified or prepared for. Professional photographers need to develop a slight case of paranoia and be in constant fear of MURPHY'S LAW! That means double-checking all settings that can cause an entire job to go south. Shooting RAW and Jpeg symotanously is a good practice, a bit of "chomping" before breaking down a set or leaving a location is not a bad idea! Checking flash synch, reviewing menu settings, and verification of all exposure and white balance settings should become reflexive and routine. It's when you put your guard down that things go wrong.
Even seasoned professionals can make mistakes. It's a good thing if you can learn from them and do better next time!
The files on the memory card may still be in RAW format. Perhaps MS Photos converted only the files on your computer to jpeg, not the original files stored on the card.
rmalarz wrote:
I don't believe MS Photos knows how to read RAW files and presents the embedded jpg file.
--Bob
It can if you have downloaded the RAW Codecs pkg from MS.
smussler
Loc: Land O Lakes, FL - Formerly Miller Place, NY
That codec is so Windows
explorer will display thumbnails for Raw Nikon .nef files, Windows
OS doesn't really care or need to recognize anything in data/image files. It's a binary data file - a bunch or zeros and ones. Applications need to be compatible with what ever binary file format that you're trying to use with it. Some people seem to think that just changing a files extension will then magically change it's format. Doesn't work that way. And raw files differ between Manufacturers and even between camera models with Nikon. So the appropriate codec needs to be installed for the particular Camera's files being viewed in explorer - if you want thumbails to appear, which is downloadable from Nikon's site and
probably most other Camera manufactures sites. Whether that codec is installed or not - Window OS itself doesn't care.
pdsilen wrote:
I recently did a very big photo shoot. The customer required a wide angle lens, 16-50mm and RAW images. I was told that they would do the editing. So, I programmed my crop sensor camera to shoot in RAW format. When I returned home from the shoot I transferred my photos to MS Photos only to find that they all came out in JPG. And how can I prevent this from happening again? Your feedback would be very much appreciated.
Put the card in a reader in your computer.
The raw will be there.
If indeed you shot in RAW, hopefully you did not format the SD card yet. Your RAW files will still be there. Let us know...
cjc2 wrote:
Where did you go wrong? By taking on a big photo shoot without knowledge of you camera and software. I could go on!
Ad hominem has no place on this forum, regardless of how you were raised.
11bravo wrote:
For security, I always have file extensions visible in explorer. Then you can always see if it's an exe file that someone wants you to double click.
Good point. I am cautious about downloaded EXE files too. Especially when I am expecting graphics or audio files.
E.L.. Shapiro wrote:
Another possibility:
I am sure, by now the OP has "learned his lesson" about undertaking jobs that he might be ill-prepared for, etc.
However! It also sounds like the client does not exactly know what they were specifying either. They asked for a "wide-angle lens" and RAW files. They might be parroting technobabble that they heard kinda thing.
If the exposures and white balance are correct on these Jpegs, and the files do not need an extensive recovery of detail, the Jpegs might suffice.
The assignment was all that "BIG" why did the client not hire an experienced professional? Sometimes you see a case of the blind leading the blind.
I've been in this business for a very long time and I can write a very funny book about things perfectly nice clients had asked for and my job began by deciphering their incorrect terminology.
This is just a wild guess based on kerfuffles and unmitigated mess-ups I have seen. Typically, I would get a panicked call from a "client" complaining that "we hired this terrible photograher who came up with lousy pictures and we need them yesterday, can you shoot it right away? Then, when they tell me their specifications and what THEY THINK needs to be done, I have to tell them that if they hired Hoodidi, he'd have a hard time filling that requirement and let alone at that budget"!
YES! I agree that folks shod not undertake jobs they are not qualified or prepared for. Professional photographers need to develop a slight case of paranoia and be in constant fear of MURPHY'S LAW! That means double-checking all settings that can cause an entire job to go south. Shooting RAW and Jpeg symotanously is a good practice, a bit of "chomping" before breaking down a set or leaving a location is not a bad idea! Checking flash synch, reviewing menu settings, and verification of all exposure and white balance settings should become reflexive and routine. It's when you put your guard down that things go wrong.
Even seasoned professionals can make mistakes. It's a good thing if you can learn from them and do better next time!
Another possibility: br br I am sure, by now the ... (
show quote)
Excellent points. Let us all hope that is the case.
CaltechNerd wrote:
And never take on a job that you are CERTAIN about without testing your plans first. I "knew" what I was doing. In other words, I had no idea that I didn't know what I was doing. I'd just gotten my first real DLSR. I shot some things that were gathered for an exhibit, never to be gathered together again. Tripod, long exposure, etc. for shooting art objects. I set ISO to 100 BUT, I left auto adjust ISO on because I didn't know it was there. The camera shot all the photos at high ISO and they came out grainy. I'll never be able to recapture those shots of a remarkable collection. Hurt my pride, but the foundation I was volunteering to will never get them back. I still feel guilty many years later.
And never take on a job that you are CERTAIN about... (
show quote)
First clue you didn’t really know what you were doing: “I'd just gotten my first real DLSR.”
These posts show an incredible amount of naivete.
--Bob
photoman022 wrote:
something about this post let off a bit of an odor... (
show quote)
If you want to reply, then
register here. Registration is free and your account is created instantly, so you can post right away.