Safari doesn't index metadat in raw or dng files? What the heck?

I've been busily adding keywords to my photo files, most of which are dng's from Canon cr2 raw files, but also a lot of jpegs. Today I wanted to find all the photos of a particular type, but all I got were the jpegs. It appears then that Safari is ignoring the keywords in the dng and cr2 files. How can this be? More importantly, how can one do keyword searches on these files?

I think you meant "spotlight" and not "safari", but I've seen this same issue too, and I think its a feature/flaw of the way Mac OS X does keywords on RAW files.
When you assign keywords in iPhoto to raw files, those keywords get associated with the jpeg copy that iPhoto makes, not the original RAW file.
To me, that seems to make Spotlight searching of photos by keyword pretty much useless. I still use keywords, though, so I can make smart albums within iPhoto.
I hope that Apple will change this behavior or at least give the user an option in a future version.

Similar Messages

Where do you put the upgraded raw or dng file in the latest Lightoom 5????

How do you upgraded your raw or dng in lightroom 5, Where does it go.?

Not sure exactly what you mean? Are you inquiring about what happens when you upgrade from an earlier version of LR to version 5?
Maybe the link below can provide some answers.
How To Upgrade To Adobe Photoshop Lightroom 5

"Edit In" Photoshop CC not working for RAW or DNG files after applying LR 5.3 and Camera Raw 8.3

I just applied the Lightroom 5.3 and Camera Raw 8.3 updates and now am no longer able to open RAW or DNG files into Photoshop CC. When I select a file and choose "Edit In" Photoshop, photoshop will launch, then nothing will happen. After 2 to 5 minutes, an error will popup in Lightroom saying "The file could not be edited because Adobe Photoshop CC could not be launched." An error I've never seen before. When I click "Ok", Lightroom will show that it's "preparing a file for editing" in the upper left, it will create and save a psd to disk and in the catalog (another new behavior), then it will open in photoshop. All other file types (jpgs, tiff, psd) seem to work/open fine between applications. No difference if I open photoshop prior to selecting "Edit In". Selecting "Edit In" other applications, like Viveza, work fine.
I tried first deleting preference files in both applications. No luck. Ditto for plugins. Notta. Eventually I completely uninstalled and fresh installed Photoshop, Lightroom, and Bridge from the cloud. Same deal...can't open raw/dng files into Photoshop.
I'm at a complete loss, dead in the water, with a mountain of editing work piling on top of me. Kicking myself for applying the upgrades, which I had been delaying for some time to avoid just such a cluster%#$. Ugh.
I'm on a PC running Windows 7 64bit.
Any suggestions would be greatly appreciated.

In the normal situation, LR needs to see a PS installed for it to detect the Edit In PS option is possible, so if you uninstall both, then install PS, first, then LR. Of course with this release there may be some hiccup that requires installing either one or the other, again, but if you've uninstalled both and are reinstalling both, then install PS, first.

None of any of the pictures on Facebook can be opened and seen on the website, I have absolutely no problem on Safari, but I would much rather use Firefox..What the heck is going on????

About a week ago, I had no problem clicking on pictures to open them to bigger size.....As of about 4 days ago - If I try to open a picture on Facebook, it shows the comments but no picture..I don't know what is going on!!! It works fine on Safari, but I would much rather use Mozilla for my own selfish reasons, WHAT THE HECK IS GOING ON????? ( I'VE TRIED EVERYTHING!!!!!)
== This happened ==
Every time Firefox opened
== About a week ago.....

I agree the phones are supposed to come with the battery and battery door missing that is policy of every wireless company. The problem is that the rep that you spoke with wasn't being as thorough as they could have been to ensure that you got complete equipment, is was a processing error from the first representative. Most of the information for exchanging a phone is auto completed by the computers as well so when the rep processes the exchange they don't have any say so as to what is actually in the shipping box so being that you didn't activate the droid 3 on your account when you called in about the missing battery and complained the computer only recognized the droid x because that probably what you had activated on your account, so that's why the second replacement was droid x equipment and not droid 3

How can one convert a PSD file into a RAW or DNG file?

Lightroom does not assemble panoramas. One must use an external editor,eg, Photoshop Elements, to construct a panorama. Lightroom prepares the selected images by converting them to PSD files before sending them to the Elements Editor. When the panorama is achieved, it cannot be saved as a RAW nor DNG file even if either of those formats were the original data format type in Lightroom. Thus when the panorama is imported back into Lightroom it is brought back as the PSD or something of your choosing; but you cannot choose a RAW nor DNG format. The result is a folder in Lightroom with a hodge-podge of formats.
Question: How can the PSD file panorama be converted into a RAW or DNG file in this transfer from an outside editor to Lightroom?

That simply cannot be done. The conversion has to take place in order for Photoshop to create the panorama. Photoshop, by itself, without Camera Raw, cannot edit raw image data. By the time an image is opened in Photoshop is no longer raw image data. Photoshop is not capable of saving raw image data. The best thing to do is perform is much of the work as possible using using Lightroom. When I do a panorama image, I highlight all of the images and use the menu option to match total exposures. Then I do as much as possible on those images in Lightroom. Once the images leave Lightroom the raw editing is finished. Anything from that point onward that is done in Photoshop must be saved to a different file format.

Camera Raw reduces DNG file size

I have raw file(CR2) size at 13.6 mb straight out of my Canon 7D. When I convert them in Adobe dng converter 5.7 I get 21.7 mb. When opening in Photoshop CS3 with Camera Raw 4.4.1 I get image size as W:3888 pixels by H:2592 pixels. I dont understand at which point the file size reduction takes place, as its supposed to be larger than that providing it was 13.6mb original file size. ( There is no compression option in camera raw or dng converter).

There is a hyperlink at the bottom of the Camera Raw interface that allows you to change some of the settings. One of the changes is to make the image smaller, the image that is sent to Photoshop. Is it possible that you have a setting chosen that reduces the size? Additionally, DNG files are usually a little smaller. Are you embedding the raw file in your DNG file? The DNG converter does not change the size of the image. It simply takes the raw image data and puts it in a new container DNG file.

Camera raw and DNG files appear as generic icons

Camera raw and DNG files appear as generic icons instead of image previews (Bridge CS5)
What can I do ?

Hi Yammer.
First thanks a lot for taking your time to help me. I am really happy about it!
I will try to answer:
1)
I meant by having the Camera Raw.8bi placed in BOTH "C:\Programmer\Adobe\Adobe Bridge CS5\Plug-Ins" and in C:\Programmer\Fælles filer\Adobe Plug-Ins\CS5\File Formats" the ACR will be found in two versions - or rather in two places (I know the former shouldn't be, but it solved my preview problem).
2)
YES - I do have tried twice starting the Adobe Bridge holding down the Ctrl-key and ticking the two (the third was greyed out but ticked anyway) and with no help.
3)
I have tried to do the *.8bi search you suggested, and this gives me the following dump - absolutely with a few more entries than yours. Some are like doubled.
Do you think I can just delete these?
Kind regards, Jan

D750 Nikon are the camera raw or DNG file ready to work in the Raw format in Lightroom?

D750 Nikon are the camera raw or DNG file ready to work in the Raw format in Lightroom?

Crazy idea - do a site search for "D750"...

Why is Lightroom5 copying both RAW and Jpeg files into the destination folder ?

Hi all Lightroom experts,
I want to copy the RAW files from my SD csrd to my Drobo harddisk. And everytime I did that, Lightroom copied BOTH the raw & jpeg files
How do I instruct Lightroom to copy only the RAW files ?
Just to disgress a bit, in fact the same problem happens in Adobe Bridge despite me selecting only the RAW files to be copied but it always copied both !!
Any tips ?
Thanks

dj_paige wrote:
You can tell Lightroom to treat JPGs next to RAW as separate photos, or treat the JPG as a sidecar file using the instructions here:
Lightroom Help | Set import preferences
If the JPG is a sidecar file, the JPG is still imported but doesn't show in your Library module.
If you really don't want to import the JPGs, you'd have to select the RAWs but not the JPGs in the Import dialog box; or import them all and then delete the JPGs from Lightroom and your hard disk (easier, but takes a little longer); or don't shoot RAW+JPG
Thanks dj_paige and F.MacLion for the solution.
Can I check, if i tick the the check-box and ask LR5 to treat the jpeg as a separate file, FR5 won't import the jpeg files (which is what I wanted) but will LR5 still generate a sidecar file for each of my RAW files ? (I hope it does)
Thanks

What the heck is going on with Safari 7.0?

Ever since I upgraded to Mavericks, Safari is just sucking out my RAM and slowing my machine.
I use FreeMemory Pro to keep an eye on RAM usage. iMac 2.8 i5, 16GB RAM.
Until I upgraded to Mavericks, my system would almost always have about 8 to 10GB unused RAM. I usually have these apps open: Safari, Mail, iTunes and sometimes iPhoto. (Previously iPhoto was a RAM hog but that doesn't seem to be a major issue now.)
After the upgrade I noticed the system slowing down and the available RAM dropping dramatically.
A little while ago my available RAM dropped to 256MB!!! This is shocking ...
As soon as I quit Safari, available RAM climbs up to 8 to 10GB available.
The culprit clearly is Safari.
Anyone else have the same experience? Any way to fix this? I'm using Chrome now to post this.

Thank you Carolyn. Turning off plug-ins did fix the problem.
Not the ideal solution as I do like to use some of those plug-ins. I did try to isolate them to figure out which one was causing the problem ... but in the end I couldn't identify any one plug-in.
I've moved away from Safari now ... because I do like the four plug-ins that I use, to improve browsing.
Pity that Safari won't work well with them ... I do prefer Safari to Chrome, but had to move.
Appreciate your directing me to the cause of the problem.
Thank you, again.

Converting RAW to DNG! What are the advantages / disadvantages?

I have Canon cameras and shoot RAW, but the question itself is surely also valid for Nikon, Sony or other brand-shooters.
When importing my pictures to Lightroom, I could convert them to DNG but didn't do this up to now, because I do not know what I loose. I suppose that I loose the ability to process my files with DPP, but I will not do that anyhow. I can appreciate the advantage of having the file in an open documented format, where even I could easily write a reader for it. So the answer should not be what I can easily find in the Adobe introduction into DNG. I have also the DNG specification in front of me, and I can read it, because I once wrote a program to read TIFF files. I understand that I could add the original RAW image stream, but I do not want using up the space wasted for this. I know, that all development parameters used for the specific RAW image can be written with the image file instead of having those stored in a database or a side-car-file.
But what I did not find until now a technical explanation about what happens during the convert. Who can enlighten me? Where do I find the missing technical explanations?
Thanks in advance!
Lucien.

Feierwoon wrote:
That wasn't the question... .
Based on the title of the thread and your initial post, it seems like your question had a lot of
"What are the advantages / disadvantages?"
in it, and only a little
"What happens at a technical level when converting"
But if you want more detailed info about conversion, and you have the aptitude to understand, I recommend doing what Lr5user-pt recommended:
Download the DNG SDK and dig in - all your questions will be answered (and if not, you can also ask DNG-specific technical questions in the DNG forum).
As far as my "sources" regarding the technical summary I presented, they are many and varied, none of which are the DNG SDK. In other words, my knowledge is based more on experience over the years - I don't know all the details under the hood..
Some experiments to consider doing:
* exiftool (-X) a proprietary raw file, then convert to DNG and repeat.
* open a proprietary raw in a DNG-supporting software of your choice and inspect metadata, then open the converted DNG in the same software and re-evaluate. Compare to proprietary raw opened in manufacturer's software, and what you see via exiftool.
Tom Hogarty (Lightroom project manager) and others who know have said: "DNG converter discards no metadata", and I believe them, but haven't verified for myself. Yet once proprietary metadata is in the DNG, most (all?) software will no longer decode it. A prime example is focus points - presumably they're there, but once converted, focus point feature is no longer supported. The amount of work required to support converted focus point data is unknown (to me), but as far as I know, no software has ventured to do it. If you want focus points, don't convert.
If you want the truth, I think for most people it's "not wise" to convert to DNG. Why? because unless you already know why you are converting (and need to convert to satisfy your goals), or you already know why you must NOT convert (e.g. so you can open the files in mfr.software, and see focus points..) the pros and cons are likely to be a wash, and now you have twice the number of raw files, unless you discard your originals, which would be REALLY "not wise", in my opinion. If you find the notion of "openly documented format" sufficiently compelling, then, ya know, more power to ya (I don't judge..), but there is no guarantee that DNG will outlast NEF (or..), and if it does, there will be ample opportunity to convert before you're left in the cold, unless you're stuck in a cave for a few decades, or are kryogenically frozen.. True, if all companies die, you may be able to write your own DNG converter (/reader), given the DNG documentation, but FWIW, NEF is also thoroughly documented (document is in freely downloadable SDK), and reverse engineerable (that's what Adobe and Phil Harvey does), so you could also write your own NEF converter, so not really a very compelling argument, not this year anyway - ask me again in a few decades..
If filesize is a main draw, then be sure NOT to save the hi-rez previews in your DNGs, otherwise you've just lost most or all of the filesize advantage. Also, you can strip previews from some proprietary raws (e.g. NEFs), to reduce filesize.
Personally, if DNG supported sidecars, I would be more likely to convert, because file-management/backup is only an issue if you "forget" about xmp sidecars (and I do not forget), and I'd rather have my xmp in separate ready-to-read xml text files, rather than embedded in binary files, but hey, that's me..
PS - I always use/encourage-others-to-use DNG when distributing raws to others for use in Adobe software, so xmp is not separate and can not get lost.
PPS - proprietary raws and dngs are both just glorified tiff files - raw data, previews, and metadata..
Don't get me wrong: I am NOT anti-DNG, and in fact - just the opposite: I am PRO dng, it's just that I wouldn't (don't) convert my own raws to DNG at this point. If you find the reasons to convert now are sufficiently compelling, you have my complete support and cooperation, fwiw..
Cheers,
Rob

Does Final Cut Pro X support RAW Cinema DNG files?

I'm looking at a pro/broadcast project that I'll be shooting in RAW Cinema DNG. Does Final Cut Pro X support this format? I can shoot in ProRes, but I don't want to for this particular project.

http://help.apple.com/finalcutpro/cameras/en/index.html

When will Camera Raw support .arw files for the new Sony RX-100?

I have Photoshop Elements 9 and just purchased the RX-100. Currently the .arw raw files the camera produces are not supported in Camera Raw. When will Adobe be supporting this format?

No one can tell you when, but the new RX100 has support in the beta of Camera Raw 7.2 RC for Photoshop CS6 so I would guess that PSE11 will either ship with or could soon after be updated to ACR 7.2 with RX100 support.
PSE10 is the current version, but in the past, a new version of Elements has come out about this time of year so sometime in the next couple months.
What you can do right now is download the beta of the DNG Converter 7.2 RC from Adobe Labs which will convert a folder of ARW files to DNG files which can then be processed with older versions of Camera Raw including what comes with PSE10 or PSE9.
You could also download and use the beta for Lightroom 4.2 RC from on Adobe Labs to work with your files natively until the beta expires by the end of October, but before then you’d probably have a new version of Elements that would work. If you go the LR 4.2 RC route, you’d want to save your changes to XMP sidecars in LR so you could read them using ACR in Elements, later.
Betas/RCs are available at: http://labs.adobe.com/

Why no 'Edit Original' with raw or dng files?

Is there a reason Lightroom does not allow the ability to use an external editor on the original raw/dng file? Why force people to use the Capture NX raw converter if they would like to use their camera specific converter instead?

This is a great point. There are many instances where I need to use a camera manufacturer's conversion software because I am unable to get similar results in Lightroom (Still a problem in LR3 - many posts about this in these forums).
I was going to write about a tip for a workaround, but instead I actually uncovered a very unfortunate behavior in LR3.
Previously, in LR2.x, you could drag any thumbnail from the Grid view onto the app of your choice in the dock. It would immediately open the original file (including RAW images) in that editor, and you could then save a Tiff to be re-imported into LR, or whatever you wanted to do. It was great flexibility, and got around having the formal ability to assign an external editor for RAW files (which by the way I agree, is necessary functionality, and should be included).
NOW, in LR3, this behavior has been shut down. You can no longer drag thumbnails from the grid view onto an external editor.
Adobe Lightroom team - this is a huge mistake. Please restore the old functionality. You should know - trying as hard as you do, your RAW rendering is still not the only game in town. I own your product, along with five other RAW editing applications. Sometimes I need to try each one to see how a particular image works out. I still prefer to use Lightroom as my cataloging software. This will change if you start to close things down to force users to stay in your ecosystem.
Apple Aperture takes a similar approach - when you drag an image onto an application, you only open a jpeg preview of that image, not the original RAW file. This is one of the reasons I ditched Aperture and moved to Lightroom. I liked the flexibility. Now that this has been taken away, it gives me another reason to consider passing on this upgrade. Please give this some thought. You do not have all the answers for RAW rendering, and realistically, unless camera manufacturers standardize, you probably never will. Give us back our flexibility, or better yet, build it in formally as the original poster suggested.

How to index text in TIFF and DWG files - and the attributes of the files

Hi all
Scenario
Portal installation with a TREX on the side (NW7.0).
No enterprise search involved.
Questions
1) Is it possible for the TREX to extract text from .DWG and .TIFF files in any standard way?
2) Is it possible to index custom properties that are maintained on a DWG-file and a TIFF-file? Or is it only the name and description fields that will be indexed?
3) If it is not possible for the TREX to extract text from DWG-files and TIFF-files, do you know of a third-party filter for TREX like dwgifilter for Microsoft software? http://www.dwgifilter.com/default.aspx
4) Would it be possible to code and implement your own python extension in order for OCR to work with the TREX? If yes, would this be a complicated or fairly easy task? Where would you start... ?
Thanks!
Best regards,
Martin

Hi,
my answers:
1) Is it possible for the TREX to extract text from .DWG and .TIFF files in any standard way?
for TIFF Not in the standard delivery. You have to develop this features.
for DWG? perhaps AutoCAD Interchange and Native Drawing Formats (DXF and DWG)
V. 2.5 - 2.6, 9.0 - 14.0, 2000i - 2002
see help.sap.com
2) Is it possible to index custom properties that are maintained on a DWG-file and a TIFF-file? Or is it only the name and description fields that will be indexed?
Within KM you can define some Meta-Properties. During upload of your documents you can maintain the values for this proerties for every file. It is possible to search for the content of the properties as well.
3) If it is not possible for the TREX to extract text from DWG-files and TIFF-files, do you know of a third-party filter for TREX like dwgifilter for Microsoft software? http://www.dwgifilter.com/default.aspx
I am not quite sure but I think there doesn't exist a third party solution for this.
4) Would it be possible to code and implement your own python extension in order for OCR to work with the TREX? If yes, would this be a complicated or fairly easy task? Where would you start... ?
You can implement your own python extention.
Add your coding for python extention in the default python extention code.
Best regards
Frank

Safari doesn't index metadat in raw or dng files? What the heck?

Similar Messages

Maybe you are looking for