Nikon D80 JPGs and PS3 Bridge metadata editing

PS3 Bridge will show thumbnails of Nikon D80 JPGs, but will not allow editing or additions to Metadata to be saved in Bridge. PhotoShop CS3 will allow adding, editing and saving metadata in the File Info section, but I can't edit it with Bridge.
Yeah, I need to upgrade to CS4, but can't get the bean counters to sign off on it!

Workaround. I created a metadata template in PS3 and Saved it. Then created an action that applied the template to the image in PS3 and saved the action. Then I went to Bridge and selected all the files and ran a batch on all of them that ran the action and saved the file. Now each file has the metadata common to them all in the metadata when looking at them in Bridge AND they can all have unique metadate ID added and saved in Bridge.

Similar Messages

Nikon d80 raw and elements 6

Hi all
When looking through the specs for the RAW 4-4-1 update, it lists the Nikon D60 as supported but no mention of the D80.
My main goal at the moment is to edit RAW (NEF) pictures and I want to find out what I need for that.
There are various questions spread over the forums from people who can not get elements 6 to work with RAW images.
Bottom line: does elements 6 fully support Nikon D80 image editing or not?
Thanks for your help.
Ben

All ACR releases contain support for ALL cameras supported in ALL previous versions.
YES, the D80 is supported.

Bridge Metadata Editing

I am having trouble getting Bridge to save changes made to metadata files. Using the same form I have no trouble with PS. I use, or used to anyway, bridge to batch fill metadata for entire folders of events ect prior to actual post in PS, where I can then fine tune metadata at a 1 photo level, having all the common data already filled.
I can fill the form or template in bridge, but it will not save it to the exp file.
What am I missing??

Workaround. I created a metadata template in PS3 and Saved it. Then created an action that applied the template to the image in PS3 and saved the action. Then I went to Bridge and selected all the files and ran a batch on all of them that ran the action and saved the file. Now each file has the metadata common to them all in the metadata when looking at them in Bridge AND they can all have unique metadate ID added and saved in Bridge.

Metadata edited in Bridge is not reflected in the Info Dialogue Box, but shows up in Photoshop.

Metadata edited in Bridge is not reflected in the Info Dialogue Box, but shows up in Photoshop.

Dear Ramón,
You are right that not all metadata is shown in the Finder info but in my case the once added in IPTC core do show as expected for most file types (but not CR2 raw). As you now I convert my CR2 to DNG for a long time now I had to look up the original Raw file and create the data for description, location, keywords again. The data you can add and alter yourself in the IPTC Core field. I added a series of screenshots showing different info and to my surprise (another reason to keep to DNG…) the Raw file had very less info and the xmp shows it all in a rather long and obscure way. Yet PSD, DNG and File info in PS show the same.
Could not recreate the Bridge metadata workspace from the OP because mine (Bridge CC) does not have the description field as an option anymore for some obscure reason. Also checked this in my CS6 version with same result, making the metadata workspace unusable but that was it already for a long time.
Still leaves us with the problem the OP showed, having all info in most files, as in Finder info, but not in Bridge. So could the OP respond to the purge cache for selection option in post 4?
Here are (a bit to many, sorry) my screenshots showing different file info (in Dutch but you will manage with that) and metadata in Bridge:
Finder info for PSD and DNG:
Finder info for CR2 and XMP:
File info Bridge / PSD:
And a Bridge Metadata view:

Lightroom 1.2 and PS3 color differences.

I am using LR 1.2 and PS3 for external editing. Once the file is opened in PS the color is different from LR. After the editing and saving the file in PS, edited file, again, look different in LR. In fact, if I open file in PS and close it without any editing, the copy created in LR look different already.
I do regular calibration of my monitor (DiamondPro 2070) with EyeOne and use sRGB color space.
How to get identical colors in both applications?

I spent some time trying different combinations with PS, LR and Preview.
It looks like color variations have a lot to do with my editing using Topaz PS plug-in. I do heavy editing with Psycadelic preset (http://levakhsanov.net/p193873551), then increase image size in PS, save in LR, tweak some more colors in LR and Export to the disk (Preview). As a result size of the file became 57MB (from original 4MB). Thanks to you, colors in PS and LR look consistent enough even with Topaz editing (as long as I do not do one more round with edited file, LR>PS>LR), but Preview colors are much more saturated. And really wierd thing is that some pictures look different in Library and Development modes in LR! With light editing without Topaz colors are the same in all 3 softwares.
I am not concerned that much with colors in Preview, but I am just woundering what colors I will see on a hard copy. Easiest way is to order small print and see, but MPIX have 25% limited time sale on big prints and there is no time for turnaround. I guess I need to make some sucrifices
Thank you very much for your help.

Editing and sharing custom metadata/keywords through Adobe Drive in Adobe Bridge

I am part of a four-person video production unit operating within a local governmental entity. We are currently using four licenses of Adobe Master Collection CS5, and are about to get access to dedicated SAN storage.
We would like each user to have the ability to assign specific keywords to any given video clip (or remove keywords from clips) within Adobe Bridge, and have the three other users see the same results. I've noticed that Bridge alone will allow for keywords to be added or removed, but this list is specific to each user. Importing one list into other users' profiles is a start, but would no longer work, once keywords are added or taken away.
The overview page for Adobe Drive 3 says that it, "allows users to edit and view custom metadata/properties through Adobe Drive in Adobe Bridge," but I haven't found any explanation in either the website, forums, or user's guides that delves any farther into this area. If we incorporate Adobe Drive/Bridge into our workflow, will we be able to share/sync keywords between users? Is there some other (affordable) solution that would let us do this?
Thanks for any insight you might be able to offer.
Chuck

Hi,
Thanks for sharing your case.
The keywords you mentioned is XMP metadata, if all your digital assets are managed by ADEP CQ DAM service, you can use AD3 with built-in ADEP connector to communicate with the DAM server, then, I think it can meet your requirement, it means, the keywords can be set by one user through metadata panel in Bridge, and can be viewed by other users.
for custom properites, it's different from XMP metadata, it refers to the properties of one asset which is managed by a Content Management service. users have to use another UI to edit/view them in Br after AD3 is installed.
here are some requirements to use it.
1) CMIS 1.0 compiliant server should be used to manage all your digital assets
2) use the built-in CMIS with AD3 to connect to the server.
if other kind of servers are used, you should develope a custom connector through AD SDK to enable custom properties feature as well as some other handler required by AD SDK
thanks

Poor quality RAW file when captured on Nikon D80 and imported

Anyone,
I shoot a Nikon D80 and when I import the RAW files, mostly when shot in RAW+JPG(fine, normal, basic) format, the RAW file turns out in very poor quality, usually alot of Noise in pic. It never use to do that before, is it just because it is coupled with +JPG files? Help would be greatly appreciated.
Cheers

I am also using a D80, and just recently switched from jpeg fine to RAW thinking it would give me some more flexibility in the post processing ... but I too have found that the images are very grainy...I'm a novice at some of the cutting edge digital editing technology... hence the use of Iphoto... but I'm disappointed that it seems my image quality has suffered.
any thoughts?

Adobe camera raw and the nikon D80 in photoshop CS version 8

How can I open RAW files from my nikon D80 in photoshop CS version 8 ? At the moment I have to open and edit my RAW files through Nikon View NX and then convert the files to Jpeg, dump them in a folder and then re-open them as Jpegs in photoshop, it's a very frustrating process so I'd really appreciate it if anyone can tell me how I can open them straight into photoshop, I really can't take this cross platform editing !!!! Thanks

This particular forum (sharing and storage) was created to help those transitioning from Photoshop.com to Adobe Revel. I am moving your post to the correct forum so that it can get proper attention. I understand that it is difficult to determine which forum to post in since there are so many.
I'll put I this posting in the photoshop community so the experts there can help you.
We also have many other forums relating to other Adobe products
http://forums.adobe.com/community/
http://forums.adobe.com
Out of curiosity, can you tell me how you found our forum page?

Aperture Metadata and Bridge Metadata

I am a photographer and my workflow is to import all my images into Aperture library and add metadata.
When exporting an image is it possible to integrate Apertures metadata with Bridge metadata? This is important feature as most people do not import images with Aperture. The issue is that many of the field names are different or non existent between the two programs. For example Location field in Bridge is Sub location in Aperture.
Can you add fields such contact info such as URL, email that are included within Bridge ITPC Metadata?
Is there a way to customize the metadata fields to work with CS3?

Unfortunatelly, not really.
I am currently using Nikon Transfer (latest version) to download the pictures from the camera. This software allows me to enter quite a number of IPTC data (including contact information, url, mail, phone, etc.), but maybe not all which are available in CS3.
Then I do import the pictures from the folder into Aperture where I only add contact information in the respective IPTC field. From the tests, I did I do know, that with this step I am using the "old IPTC standard" with Aperture and the new IPTC standard with Nikon Transfer. Clearly the newer is better and meets the needs you described.
In Aperture, I do only see the IPTC data fields, which are common between the two standards (copyright, keywords and description).
When I go to CS3 Bridge, I can see the IPTC data from both, but only of you turn on the "IPTC old" in the Photoshop Bridge settings.
This is how far I have come. I have tested the export with the original and the aperture work copy. As a test reader/viewer of the pics I used Photoshop Elements 5.0 ... but except the copyright information, key words and description, I could not find "my" IPTC data. So there was no contact info. This may be a problem of the old version, so I also checked on a windows PC the file properties (picture viewer), which has more or less the same information.
So the only work around maybe to add contact information into the copyright field - which is not ideal.
Regards
Diethard

I re-downloaded my Photoshop recently and Adobe Bridge no longer displays my Nikon NEF files and Camera Raw will not open them.

I re-downloaded my Photoshop recently and Adobe Bridge no longer displays my Nikon NEF files and Camera Raw will not open them. I get a message saying that Camera Raw does not support my camera type but it always has in the past. The bridge no longer shows the picture view of my NEF files. These are Nikon NEF files from the Nikon 5100 DSLR camera. How do I fix this?

I re-downloaded my Photoshop recently and Adobe Bridge no longer displays my Nikon NEF files and Camera Raw will not open them. I get a message saying that Camera Raw does not support my camera type but it always has in the past.
When you re-installed Photoshop, you also re-installed the version of Camera Raw which shipped with Photoshop - in other words you reverted to an older version of Camera Raw which does not support the D5100.
Camera Raw plug-in | Supported cameras
The D5100 was first supported in Camera Raw version 6.4.
In Photoshop, click Help > Updates to update Camera Raw.

HPX-370 P2 Metadata Support and Adobe Bridge

I'm having some trouble getting Adobe Bridge to write metadata to files generated with a Panasonic HPX-370 P2 camera.
The company I work for recently requested that I come up with a digital asset management plan for new video. Let me preface this by saying, I'm a shooter/editor, not a data manager. Since we were already buying the HPX370, all my research pointed to Adobe Bridge being a perfect solution for adding metadata in the form of keywords to our videos to make our video database searchable.
Now that the camera is in-hand, I have been unable to alter the metadata through Adobe Bridge. Here is my issue. Every time I go to add a keyword or change the metadata on one of the mxf video files within bridge, the stock response is: The file "filename" cannot store XMP metadata. No changes will occur.
I thought this would be fairly easy to find a fix to, but not a ton out on the net about this specific problem. What am I doing wrong here?
If this can't be fixed easily on my end, could it be an added feature? How do you request a feature addition?

A view problems here, first of all not many regulars (me amongst them) are very familiar with movie files.
Bridge does not seem to support MFX files in the Bridge preferences File type associations.
And in general, not all file types are able to write XMP data (keywords, IPTC etc) to, some just don't accept it.
Another possibility seems that you don't have read and write permissions to the files, folders or disk the files are on. The files also might been locked (but then they should show a small lock icon above the thumb.
Also try this page:
http://help.adobe.com/en_US/premierepro/cs/using/WSE2397406-3FEB-43df-868D-68EB20BBC021.ht ml#WSCEE5677A-075C-40bb-99D9-D8EE08FC68B4
and maybe even better, drop this question in the dedicated Premiere Pro forum:
http://forums.adobe.com/community/premiere
And while Bridge is a perfect application for the workflow needed for pre process and process it really is not all that good in dedicated DAM functions, maybe you also try to look at third party applications that can handle movie files better then Bridge can.

NEF files from Nikon d800 not visible in bridge and photoshop cs6- using mac ver.10.8.5. downloaded plugin from site 8.3 but issue unresolved

NEF files from Nikon d800 not visible in bridge and photoshop cs6- using mac ver.10.8.5. downloaded plugin from site 8.3 but issue unresolved

You can install and use Camera Raw 8.8 with OSX 10.8 Go to Help > Updates in Photoshop CS6

Lightroom Metadata editing and workflow is tedious nightmare!

I'm new to Lightroom in just the past month, but have used it enough to see that a serious interface problem makes Lightroom version 1x virtually unusable in a deadline-oriented publishing workflow. Lightroom's Metadata editing and workflow is just a terrible nightmare, and far too tedious and slow. It appears to be an afterthought implemented by good-hearted souls who've never had to edit this sort of information under serious deadline pressures. I know Lightroom is marketed as an image database and not a file browser, but we're all looking to simplify our workflow here and with just a few subtle enhancements, Lightroom could be an excellent file browser and file import manager too.
As it is now, the Lightroom v1x handling of File Naming and Renaming, Metadata Editing and Keyword Editing is poorly implemented and in need of an immediate overhaul to help professional photographers expedite this crucial and time-consuming first step in the archiving workflow. While Lightroom is very good at many other tasks, I give it a big fat "F" of a failing grade for these tasks.
First, the Lightroom Library Module needs an even more simple, linear interface that steps users through a precise procedures (and helps them remember them). Arguably, to accomplish this, the Import function may need to become a separate Module that can be selected and used separately before entering the Library. As File Naming and Renaming, Metadata Editing and Keyword Editing currently are implemented, I, for one, am always forgetting to fill out one of these critical sections and can't even seem to remember that some may need to be done before importing while others appear to be conceived to be done after importing. My point is, all these related steps really need to be done together, but the Interface spreads out the functions too much, and it is nearly impossible to build a logical and linear Import workflow, especially when you are first learning Lightroom.
I'd like to see a workflow that walks me through applying and editing (in order), File Naming, Basic and IPTC Metadata, Captioning and Keywords, so that I don't always forget some obscure step in the process (which I keep doing). Here are some specific suggestions, some of which may prove to be valid, some of which may be problems due to my lack of experience with thye software.
1. As currently implemented, Metadata editing requires too much thought, and does not have enough intelligent automation. Eliminate as much typing as possible (See Photo Mechanic!)
2. Lightroom needs better Metadata Presets. A "Quick Edit" view to simplify interface for editing minimal metadata info (File Name, Basic Info, Keywords, Headline, Limited Copyright Info).
3. Separating Keyword Tags, Metadata Browser, Keywording Presets and Metadata Presets confuses the workflow. They should all appear together under one selectable module that organizes a suggested, linear workflowfor these tasks, but allows it to be customized. This is the sort of tasks that need to be learned by rote memory, and having all these panes floating around on both sides of the photo make it impossible to quickly step through these tasks.
- Name (or Rename) files, Edit/Apply Basic and IPTC Metadata, Edit/Apply Keywords, Import or...
- Import, Name (or Rename) files, Edit/Apply Basic and IPTC Metadata, Edit/Apply Keywords, Import
4. Rename should offer the option of renaming the master file names on the disk, not just file names in the database (which I think is what Lightroom does, but again, this is very confusing for new users)! So, it is my belief that this feature needs a checkbox option to rename one, the other or both. But you need to be able to quickly find this dialog box every time you do an import, and it should not be hidden away out of view under the Library menu. Ideally and logically (for workflow), File Renaming should be handled when starting the Import into Lightroom.
This is critically important because many user

Lightroom metadata editing Part 2 (see Part 1 at top of thread)...
...This is critically important because many users just do not want to trust their images solely to any database and we want the ability to go look for master files with identical names should something go wrong with the software or we decide to edit the file in Photoshop outside of Lightroom or even switch to another library software program.
My own habit is to rename every file with the date followed by a unique, three-digit file number, as in 20070717_001, 20070717_002...up to 999 etc. (I have never shot more than 999 files in a single day, but this could be a four-digit number). To file these on disk, a folder with a similar naming scheme is created for each day's shoot, although a keyword slug is added to the end instead of file numbers.
5. Metadata Presets (Basic Info, IPTC metadata, EXIF metadata), Keywords need to be able to toggled on or off (promote/demote-expand/contract). Turning Off/On one section at a time via the Metadata Presets popup menu is too tedious...and you can't display IPTC and Large Caption together or leave Large Caption turned on. It also is difficult to remember where the Large Caption default (Preferences) setting is...
6. Please get the EXIF data out of the way entirely when editing captions and visa-versa...And the EXIF data should not separate Basic Info and IPTC Info fields. Please relocate the EXIF to the bottom of the Metadata pane...
7. IPTC Content, IPTC Copyright, IPTC Creator, IPTC Image expand/collapse sections need more automation:
- The Presets fields need Preset lists of entry choices for cities, states, countries, etc.!
- ISO Country Code automatically should be filled in when a country is entered.
- Date created automatically should be filled in from camera EXIF data
- Metadata Presets "Save As" should fill in old name, and allow you to rename it; (When it appears, the new name field should not be empty. This would aid in consistent, alphabetical naming
- Metadata Presets naming should support job names, with actual Presets saved under each job name...
8. IPTC Status EXIF, Contact, etc.
- Caption field MUST display more than one line...(6-8 lines)!
- Caption field MUST support Shift/Return!
- Headline (IPTC Content) should be displayed with (and above) caption. Please present information logically!
- Yellow popups should describe what each field name is for...some are real brain teasers...

JPG and TIFF colors in Bridge CS5 way off, but fine in Photoshop

Just started happening, but not sure if it was after updating to Bridge 4.0.3 or Camera RAW 6.2. The colors for RAW and PSD files are fine in Bridge, but all JPGs and TIFFs colors are blown out and way off. Opening the JPG or TIFF in Photoshop looks fine though. Anyone else having this issue, or know how to fix it?
Update: If I set the "Develop Settings" in Bridge CS5 to "Camera Raw Defaults" for the JPGs/TIFFs that are displaying improperly, the colors and tones go back to normal, but if I "Clear Settings" everything turns to crap again.

PLEASE help save my sanity and my reputation! --I have spent the last five days exhausting every possible solution to this debilitating issue. I have spent countless hours perusing the web for a solution, spent 4 hours yesterday with Adobe customer support and yet, there is no solution to be found. My issue is that the color (in every file format NEF, JPEG, PSD) completely changes color and desaturates in every one of the adobe products: Photoshop CS5, Camera RAW 6.2, Lightroom 3.2. -
Everything was working fine, and then out of no where my productivity has come to a crashing halt. This is the steps I have taken to this point:
-Uninstalling/re-installing all of the software
-Purging anything that can be purged.
-Changing color profiles
-Resetting defaults
-Resetting preferences
-Installing updated drivers for monitor, video cards
-rollling back drivers for monitor, video cards
-monitor recalibration
**and finally, today...I set the monitor up on another computer, OS windows xp, and to my complete surprise, the issue persists even on another pc with completely different hardware.
-I am at my wits end with this. I have clients ringing my phone off the hook. This is crazy!
-I have sent out for another monitor as a last ditch effort to see if something is wrong with the monitor.
PLEASE, if anyone has a solution please let me know. Apparently, the folks at Adobe are just as perplexed by these issues as we are, as I have found numerous posts on forums throughout the Internet with this same issue---and yet none of the post every found a solution.
Primary System
Windows7 64-bit
Nvidia fx 580 video card
Dell U2410 Ultra Sharp Monitor
Abobe CS5 Photoshop -64-bit
Lightroom 3.2
Camera Raw 6.2
Secondary
Windows XP
Nvidia GeForce 8400gs
Same software, just in a 32-bit

Can I merge a JPG and RAW folder in a catalog and keep the edits?

I usually shoot RAW plus JPG and always used to copy all of them into the same folder. That worked fine, but was a little pointless as the JPG was only used as a temporary preview before the RAW was loaded in behind it. For speed of editing at events, I started to split the files in to two separate folders and import both, but tag and do basic edits, crops etc on the JPGs so for 'news' website use, then work on any higher quality client requirements from the RAW. It would be nice if I could later merge the two together so that those basic edits - and ratings etc - were then applied to the RAW files. They have the same names - bar the extensions, of course - having be renamed by LR on import. I tried it on a test shoot, but it just seems to add separate JPG and RAW images to the catalog. Is there a way to have it associate the unedited RAW with the edited JPG?
Guy

Cornelia-I wrote:
Hello Guy gswarbrick,
I am not sure I understand where your current workflow with the JPGs saves you time:
Do you load them into your LR catalog, and do you do the ratings and crops there?
Then for selling on the web you export the JPGs thusly edited from LR?
Do you use a laptop on site/in the field for this?
I am just wondering, where you would actually loose time if your workflow would be the following:
General preparation of your LR set-up:
Define a default develop setting for RAWs that matches your camera's JPG-conversion pretty fine, so that the result would be almost identical without any explicit develop edit.
Define a default export setting for your JPGs to be sold on the web on the day: choose the quality, the size (resizing rules) fit for web, colour space most probably sRGB, ... (no adding to the catalog)
Workflow during the shooting day:
Only import RAWs, no JPGs at all. [Do you fear this takes longer than imprting the JPGs?]
Do the quick stuff during the day like you do today on the JPGs, just on the RAWs. Should also be rating/labeling and cropping, nothing more thanks to your prepared default develop settings.
...Compared to any option with ExifTool or the like for the final RAW-work (4.) you would definitely save the time there.
So the question is: would you really loose time during the critical phase on shooting day?
I guess not, provided your default develop settings achieve pretty much your camera's jpg-conversion. You may need to experiment a little there, make these defaults specific to ISO ranges and camera serial number if you shoot with several cameras, but once this prep is done there should be no more substantial delay.
Unless you post the images directly from camera to the web without passing through LR catalog. Or your field laptop would be of very low spec.
Where to start? Let's start with my laptop; it's about the highest spec available, coupled with Sandisk Extreme Pro cards and a high speed card reader. What about my fear that importing the RAWs would take longer than the JPGs? Well, a small, basic JPG is about 500k, the equivalent uncompressed RAW file is 12Mb, so I reckon about 24x as long to import - give or take. Plus the time to render the RAW file, which isn't required for the JPG. And that's assuming I'm not adding default develop settings, which have a small but not insignificant overhead. For that reason, the RAW imports are usually done after the events or during (rare) breaks.
I've arrived at this workflow through 5 years of experimentation. RAW-only simply does not work for these sorts of events. Most of my 'competitors' shoot JPG-only, for that very reason, but I don't want to lose the RAW option for the print work.

Nikon D80 JPGs and PS3 Bridge metadata editing

Similar Messages

Maybe you are looking for