Custom xmp in Lightroom?
I have written a few custom xmp panels that work beautifully in PS, IL, IND, Acrobat, Portfolio etc.. Alas I can't seem to access this info in LR.
Am i missing some crucial step?
I have the txt file in the adobe custom xmp panels folder but it is nowhere to be found in Lightroom's workspace.
Thanks.
a
I have also experimented with customized XMP data with Bridge and found it quite powerful and useful. You do need to work with a bit of Javascript to do this, but this is not too difficult to learn.
For example, you can create your own namespace (e.g. "http://ns.mynamespace.com/customdata/1.0/"). and then a series of custom fields (e.g. CustomSetting, CustomName, CustomGroup etc.).
You can then add this namespace and custom fields to any image (except RAW) without affecting any of the existing metadata or the image itself. Once you have this extra metatdata imbedded in images you can use it in a number of other metadata-aware programs for advanced searching or sorting purposes.
Creating a custom metadata field is better than using an existing metadata field (e.g. IPTC fields) for your own purposes. In this way you are free to define the purpose of these fields without worrying that other programs will mess-up this metadata or choke on your image.
Regards, Nigel
Similar Messages
-
Will Lightroom 4 support custom XMP?
XMP stands for eXtensible Metdadata Platform. Supposedly it is a standard developed by Adobe that permits image metadata not just be locked into one rather limited core set of fields like IPTC, but the design of custom metadata panels that in theory permits the addition of all kind of metadata fields.
Now, that sounds great - in theory...
Here is the catch: If you are not an advanced programmer, there is no way you will ever understand Adobes XMP Toolkit. For us normal earthlings it is essentialy impossible to make use of the X in eXpansible, we won't never be able to get a grips of programming custom metadata schemas ;-(
Worse: to date only Photoshop and Bridge even support custom metadata panels. Lightroom does not (please notice: I am NOT talking about the option to customize existing panels, I am talking about creating entirely new, customized panels!).
Currently there is unfortunately only one single software product on the market that fully supports XMP: IDimager. While IDimager is a great image database program it falls short in comparison to Lightrooms Image Editing/Adjustment/Developing capabilities. Thus it would be great, if Lightroom supported at least importing custom metadata panels created in other applications such as IDimager.
(specifically this one: http://wiki.idimager.com/index.php?title=DarwinCoreXMP#.27.27.27Darwin_Core_XMP.27.27.27)...Hi Cornelia,
unfortunately ALL these plugins have one severe limitation: They are not XMP custom metadata, they are not saved as XMP metadata to the image files themselves!
In fact this ability in lightroom to "create" your own custom panels is quite deceiving and not at all serving the purpose xmp was originally intended for.
The plugin by Rob Cole for example (the one you are referring to) permits you to create your own "custom metadata" in Lightroom, yet those metadata are NOT saved as XMP. Instead you have to manually backup the data, a rather cumbersome procedure, prone to data loss.
What is great about XMP is the ability to write metadata diretly into an image file. This way they always stay within the image metadata itself and are never lost. You open that file in another program or exchange it with someone else and there is the metadata - residing inside the file itself.
Now, why do I find custom metadata useful? Are there not enough xmp fields already?
I have been using an xmp implementation of the DarwinCore to manage metadata about photos of Natural History Collections, names of species for example, the genus, family, order, collection data where a specimen was collected, etc...
Although a standard for this kind of metadata already exists (i.e., the DarwinCore) this standard is unfortunately not generally available as XMP for image management. Thus, I made up a DarwinCore implementation of XMP in IDimager (http://wiki.idimager.com/index.php?title=DarwinCoreXMP#.27.27.27Darwin_Core_XMP.27.27.27) and it would be great to be able to use it also in Lightroom (at least be able to read it, better yet also write to those fields). In Photoshop and Bridge I can at least see that information, sadly though Lightroom does not even support reading custom XMP...
Frank -
Saving metadata from Lightroom erases custom XMP data in DNG...
Hello,
There seems to be an issue with the way Lightroom applies changes in from the LR catalog to the assets metadata. The setup is LR 2.5 and there is an orginal set of images that have custom XMP data applied to them via Bridge. There is one LR catalog that points to these images and the LR catalog ratings and labels match those that are in these images. A second LR catalog copy (not export) was made where additional changes were made only to ratings and labels. This catalog also points to the original assets. When using the Save Metadata to files function in LR for this catalog (and selecting ALL files), LR erases all the original custom XMP data contained in the DNG images and writes only the ratings and label information.
It doesn't seem that LR should be overwriting the entire XMP packet when only ratings and labels have changed and are saved back to the assets. Is that the way this is designed or is this a malfunction?
Thanks for any help on this!
DavidI may have answered my own question as we have run into this issue before. Lightroom is really not designed for any type of simultaneous workflow on the same files. Most content management applications utilize the check-in/check-out mechanism to avoid having to perform any type of merging or implement a logical business rule to determine which content updates "win" It is no different with Bridge and LR. You work in one application at a time doing specific things to the same files and then read from each other when those actions are complete. Working in this manner you never run into the merge issue or lose data from either side.
Our simple answer to this question is adjust our workflow timing for things to accommodate this behavior. The one thing that I will say is that LR does really need to provide some type of catalog history functionality that can be queried. I believe that LR does interact with the catalog database in this manner when you use the Save functionality from the context menu and have not imagery selected. It scans the database looking for any changes and then only updates those files it finds changes for. If we could only see this type of functionality added in a way that would show us history for changes to the catalog at large and not have to dig into individual assets to look for these changes that would be great.
We are going to look at a way to query the LR database itself to see if there isn't some time stamp information and file ID/filename data that can't be accessed as it would be invaluable to be able to look across large catalogs (well over 1000 images) and find the files that had been most recently updated (in updated I mean only simple updates to rating and label) and then separate these out to work with in their own group (collection).
I could also look at this as yet another opportunity to refine a workflow that doesn't create changes to identical data each time changes are incurred. I will look at that option much more closely as it is really the only thing we can easily control.
Cheers!
~David -
Add support for custom xmp panels
Please add support for custom xmp panels.
ThanksI would strongly support that too!!!
Here is why: We have been working at an XMP implementation of the Darwin Core to support standardized metadata on biodiversity information. Have a look here. I would love to have an Panel in Lightroom to support the metadata that I am embedding with IDImager:
http://wiki.idimager.com/index.php?title=DarwinCoreXMP#.27.27.27Darwin_Core_XMP.27.27.27
Cheers,
Frank -
Add support for custom file info panels just like PS does now with custom
xmp panels.[email protected] wrote:
> Add support for custom file info panels just like PS does now with custom
> xmp panels.
Are you talking about customizing the Metadata panel on the right hand
side of the library. If so, Lightroom already supports custom
panels...it just doesn't have the interface for facilitating the
customization. There is a nice website that lets you build a custom
metadata panel. Then you just download the resulting file and place it
where it tells you to on your hard drive.
http://regex.info/blog/2007-02-20/386 -
I want to crop my images to 840 px by 473 px but when I enter those numbers for a custom crop in Lightroom it defaults to 16x9. How can I change this?
I've tried ratios close to 840x473 and multiples of that combination but nothing allows me to get that exact ratio. I need this ratio for formatting on my website. Any help would be appreciated.In Lightroom, you don't crop to pixel dimensions, you crop to aspect ratio and then EXPORT to pixel dimensions as near as possible at that aspect. If you want to crop to pixel dimensions you will have to use another program, do a lot of draging the crop corners around, or use Rob Cole's XMP CROP plugin.
840X473 is less than one pixel width of aspect ratio off from 16X9 so I can't see why it would cause a problem. Lightroom tries to HELP by rounding the aspect to one in its list and this is really only a display bug/glitch. It actually rounds when the numbers are even further off than this. I agree that if you input 840X473 that Lightroom should just leave the aspect alone. This behavior causes problems/bugs to show up in other places with the crop tool. See posts #30 and above in this link.
http://forums.adobe.com/message/6218903#6218903 -
Bugs: open new doc, custom XMP panel crash
When opening a new document after starting Photoshop, it appears with half a checkboard pattern:
Drawing on it looks like below:
I also had an issue where I closed the doc (without saving) after drawing, then opened a new doc. The previous drawing then appeared partially twice (large, and a small version in top left corner) in the new doc, this only happened once though.
I added a custom XMP panel that works fine with CS5 to $user-dir\AppData\Roaming\Adobe\XMP\Custom File Info Panels\4.0\panels
On selecting the custom panel, in the File Info window, the panel window / CS6 crashes. (The grey window in the sshot below is an imprint of the irfanview settings I used to take these screenshots, this imprinting behaviour (not sure if it has a proper name) is reasonably common with crashed programs).
I am using the 64 bit version on Windows 7 business 64. 8GB RAM, Sys info from PS CS6 below:
Adobe Photoshop Version: 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00) x64
Operating System: Windows 7 64-bit
Version: 6.1 Service Pack 1
System architecture: Intel CPU Family:6, Model:15, Stepping:6 with MMX, SSE Integer, SSE FP, SSE2, SSE3
Physical processor count: 2
Processor speed: 2666 MHz
Built-in memory: 8191 MB
Free memory: 4745 MB
Memory available to Photoshop: 7256 MB
Memory used by Photoshop: 60 %
Image tile size: 128K
Image cache levels: 4
OpenGL Drawing: Enabled.
OpenGL Drawing Mode: Advanced
OpenGL Allow Normal Mode: True.
OpenGL Allow Advanced Mode: True.
OpenGL Allow Old GPUs: Not Detected.
Video Card Vendor: NVIDIA Corporation
Video Card Renderer: GeForce GT 240/PCIe/SSE2
Display: 1
Display Bounds:= top: 0, left: 0, bottom: 960, right: 1280
Video Card Number: 1
Video Card: NVIDIA GeForce GT 240
OpenCL Unavailable
Driver Version: 8.17.12.9610
Driver Date: 20120229000000.000000-000
Video Card Driver: nvd3dumx.dll,nvwgf2umx.dll,nvwgf2umx.dll,nvd3dum,nvwgf2um,nvwgf2um
Video Mode: 1280 x 960 x 4294967296 colors
Video Card Caption: NVIDIA GeForce GT 240
Video Card Memory: 512 MB
Video Rect Texture Size: 8192
Serial number: Tryout Version
Application folder: C:\Program Files\Adobe\Adobe Photoshop CS6 (64 Bit)\
Temporary file path: C:\Users\Rusty\AppData\Local\Temp\
Photoshop scratch has async I/O enabled
Scratch volume(s):
Startup, 136.7G, 48.9G free
Required Plug-ins folder: C:\Program Files\Adobe\Adobe Photoshop CS6 (64 Bit)\Required\
Primary Plug-ins folder: C:\Program Files\Adobe\Adobe Photoshop CS6 (64 Bit)\Plug-ins\
Additional Plug-ins folder: not set
Installed components:
A3DLIBS.dll A3DLIB Dynamic Link Library 9.2.0.112
ACE.dll ACE 2012/01/18-15:07:40 66.492997 66.492997
adbeape.dll Adobe APE 2012/01/25-10:04:55 66.1025012 66.1025012
AdobeLinguistic.dll Adobe Linguisitc Library 6.0.0
AdobeOwl.dll Adobe Owl 2012/02/09-16:00:02 4.0.93 66.496052
AdobePDFL.dll PDFL 2011/12/12-16:12:37 66.419471 66.419471
AdobePIP.dll Adobe Product Improvement Program 6.0.0.1642
AdobeXMP.dll Adobe XMP Core 2012/02/06-14:56:27 66.145661 66.145661
AdobeXMPFiles.dll Adobe XMP Files 2012/02/06-14:56:27 66.145661 66.145661
AdobeXMPScript.dll Adobe XMP Script 2012/02/06-14:56:27 66.145661 66.145661
adobe_caps.dll Adobe CAPS 5,0,10,0
AGM.dll AGM 2012/01/18-15:07:40 66.492997 66.492997
ahclient.dll AdobeHelp Dynamic Link Library 1,7,0,56
aif_core.dll AIF 3.0 62.490293
aif_ocl.dll AIF 3.0 62.490293
aif_ogl.dll AIF 3.0 62.490293
amtlib.dll AMTLib (64 Bit) 6.0.0.75 (BuildVersion: 6.0; BuildDate: Mon Jan 16 2012 18:00:00) 1.000000
ARE.dll ARE 2012/01/18-15:07:40 66.492997 66.492997
AXE8SharedExpat.dll AXE8SharedExpat 2011/12/16-15:10:49 66.26830 66.26830
AXEDOMCore.dll AXEDOMCore 2011/12/16-15:10:49 66.26830 66.26830
Bib.dll BIB 2012/01/18-15:07:40 66.492997 66.492997
BIBUtils.dll BIBUtils 2012/01/18-15:07:40 66.492997 66.492997
boost_date_time.dll DVA Product 6.0.0
boost_signals.dll DVA Product 6.0.0
boost_system.dll DVA Product 6.0.0
boost_threads.dll DVA Product 6.0.0
cg.dll NVIDIA Cg Runtime 3.0.00007
cgGL.dll NVIDIA Cg Runtime 3.0.00007
CIT.dll Adobe CIT 2.0.5.19287 2.0.5.19287
CoolType.dll CoolType 2012/01/18-15:07:40 66.492997 66.492997
data_flow.dll AIF 3.0 62.490293
dvaaudiodevice.dll DVA Product 6.0.0
dvacore.dll DVA Product 6.0.0
dvamarshal.dll DVA Product 6.0.0
dvamediatypes.dll DVA Product 6.0.0
dvaplayer.dll DVA Product 6.0.0
dvatransport.dll DVA Product 6.0.0
dvaunittesting.dll DVA Product 6.0.0
dynamiclink.dll DVA Product 6.0.0
ExtendScript.dll ExtendScript 2011/12/14-15:08:46 66.490082 66.490082
FileInfo.dll Adobe XMP FileInfo 2012/01/17-15:11:19 66.145433 66.145433
filter_graph.dll AIF 3.0 62.490293
hydra_filters.dll AIF 3.0 62.490293
icucnv40.dll International Components for Unicode 2011/11/15-16:30:22 Build gtlib_3.0.16615
icudt40.dll International Components for Unicode 2011/11/15-16:30:22 Build gtlib_3.0.16615
image_compiler.dll AIF 3.0 62.490293
image_flow.dll AIF 3.0 62.490293
image_runtime.dll AIF 3.0 62.490293
JP2KLib.dll JP2KLib 2011/12/12-16:12:37 66.236923 66.236923
libifcoremd.dll Intel(r) Visual Fortran Compiler 10.0 (Update A)
libmmd.dll Intel(r) C Compiler, Intel(r) C++ Compiler, Intel(r) Fortran Compiler 10.0
LogSession.dll LogSession 2.1.2.1640
mediacoreif.dll DVA Product 6.0.0
MPS.dll MPS 2012/02/03-10:33:13 66.495174 66.495174
msvcm80.dll Microsoft® Visual Studio® 2005 8.00.50727.6195
msvcm90.dll Microsoft® Visual Studio® 2008 9.00.30729.1
msvcp100.dll Microsoft® Visual Studio® 2010 10.00.40219.1
msvcp80.dll Microsoft® Visual Studio® 2005 8.00.50727.6195
msvcp90.dll Microsoft® Visual Studio® 2008 9.00.30729.1
msvcr100.dll Microsoft® Visual Studio® 2010 10.00.40219.1
msvcr80.dll Microsoft® Visual Studio® 2005 8.00.50727.6195
msvcr90.dll Microsoft® Visual Studio® 2008 9.00.30729.1
pdfsettings.dll Adobe PDFSettings 1.04
Photoshop.dll Adobe Photoshop CS6 CS6
Plugin.dll Adobe Photoshop CS6 CS6
PlugPlug.dll Adobe(R) CSXS PlugPlug Standard Dll (64 bit) 3.0.0.383
PSArt.dll Adobe Photoshop CS6 CS6
PSViews.dll Adobe Photoshop CS6 CS6
SCCore.dll ScCore 2011/12/14-15:08:46 66.490082 66.490082
ScriptUIFlex.dll ScriptUIFlex 2011/12/14-15:08:46 66.490082 66.490082
tbb.dll Intel(R) Threading Building Blocks for Windows 3, 0, 2010, 0406
tbbmalloc.dll Intel(R) Threading Building Blocks for Windows 3, 0, 2010, 0406
TfFontMgr.dll FontMgr 9.3.0.113
TfKernel.dll Kernel 9.3.0.113
TFKGEOM.dll Kernel Geom 9.3.0.113
TFUGEOM.dll Adobe, UGeom© 9.3.0.113
updaternotifications.dll Adobe Updater Notifications Library 6.0.0.24 (BuildVersion: 1.0; BuildDate: BUILDDATETIME) 6.0.0.24
WRServices.dll WRServices Friday January 27 2012 13:22:12 Build 0.17112 0.17112
wu3d.dll U3D Writer 9.3.0.113
Required plug-ins:
3D Studio 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
Accented Edges 13.0
Adaptive Wide Angle 13.0
ADM 3.11x01
Angled Strokes 13.0
Average 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
Bas Relief 13.0
BMP 13.0
Camera Raw 7.0
Chalk & Charcoal 13.0
Charcoal 13.0
Chrome 13.0
Cineon 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
Clouds 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
Collada 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
Color Halftone 13.0
Colored Pencil 13.0
CompuServe GIF 13.0
Conté Crayon 13.0
Craquelure 13.0
Crop and Straighten Photos 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
Crop and Straighten Photos Filter 13.0
Crosshatch 13.0
Crystallize 13.0
Cutout 13.0
Dark Strokes 13.0
De-Interlace 13.0
Dicom 13.0
Difference Clouds 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
Diffuse Glow 13.0
Displace 13.0
Dry Brush 13.0
Eazel Acquire 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
Embed Watermark 4.0
Entropy 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
Extrude 13.0
FastCore Routines 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
Fibers 13.0
Film Grain 13.0
Filter Gallery 13.0
Flash 3D 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
Fresco 13.0
Glass 13.0
Glowing Edges 13.0
Google Earth 4 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
Grain 13.0
Graphic Pen 13.0
Halftone Pattern 13.0
HDRMergeUI 13.0
IFF Format 13.0
Ink Outlines 13.0
JPEG 2000 13.0
Kurtosis 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
Lens Blur 13.0
Lens Correction 13.0
Lens Flare 13.0
Liquify 13.0
Matlab Operation 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
Maximum 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
Mean 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
Measurement Core 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
Median 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
Mezzotint 13.0
Minimum 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
MMXCore Routines 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
Mosaic Tiles 13.0
Multiprocessor Support 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
Neon Glow 13.0
Note Paper 13.0
NTSC Colors 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
Ocean Ripple 13.0
Oil Paint 13.0
OpenEXR 13.0
Paint Daubs 13.0
Palette Knife 13.0
Patchwork 13.0
Paths to Illustrator 13.0
PCX 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
Photocopy 13.0
Photoshop 3D Engine 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
Picture Package Filter 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
Pinch 13.0
Pixar 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
Plaster 13.0
Plastic Wrap 13.0
PNG 13.0
Pointillize 13.0
Polar Coordinates 13.0
Portable Bit Map 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
Poster Edges 13.0
Radial Blur 13.0
Radiance 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
Range 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
Read Watermark 4.0
Reticulation 13.0
Ripple 13.0
Rough Pastels 13.0
Save for Web 13.0
ScriptingSupport 13.0
Shear 13.0
Skewness 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
Smart Blur 13.0
Smudge Stick 13.0
Solarize 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
Spatter 13.0
Spherize 13.0
Sponge 13.0
Sprayed Strokes 13.0
Stained Glass 13.0
Stamp 13.0
Standard Deviation 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
Sumi-e 13.0
Summation 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
Targa 13.0
Texturizer 13.0
Tiles 13.0
Torn Edges 13.0
Twirl 13.0
U3D 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
Underpainting 13.0
Vanishing Point 13.0
Variance 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
Variations 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
Water Paper 13.0
Watercolor 13.0
Wave 13.0
Wavefront|OBJ 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
WIA Support 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
Wind 13.0
Wireless Bitmap 13.0 (13.0 20120305.m.415 2012/03/05:21:00:00)
ZigZag 13.0
Optional and third party plug-ins: NONE
Plug-ins that failed to load: NONE
Flash:
Mini Bridge
Kuler
Installed TWAIN devices: NONEAccording to Nvidia's website, I already have the latest drivers installed (I updated them just a few days ago). I turned off hardware acceleration as you suggested, and that fixed the problem.
You can download the XMP panel that causes the crash from: http://www.iliveinabin.com/image-xmpPanel%20v2.zip That contains the source for the panel and also the compiled panel I'm using, which is in the target folder. -
Using SDK to create custom XMP panel in Bridge CS4
Using the SDK materials how exactly does one go about creating their own custom XMP panel for Bridge CS4?
I feel like I'm getting close- I was able to copy the BasicControlSamplePanel folder from SDK to my local C drive @
C:\Documents and Settings\tony\Application Data\Adobe\XMP\Custom File Info Panels\2.0\panels
I figure once that file is in the right place I can simply modify it to get custom fields
Now when I did this I noticed in Bridge when rightclicked on an image and clicked file info- the BasicControlSamplePanel tab was visible but upon clicking on BasicControlSamplePanel tab there was nothing in this dialogue box. Tried restarting computer- and still nothing- seems like it is the correct folder what do I need to do to get the properties to show up
Help please
Thanks
TonyHi Tony,
please refer to the section "Creating custom XMP properties using XML" in the XMP FILEINFO SDK PROGRAMMER’S GUIDE for information how to create custom panels for the metadata panels in applications like Bridge or Premiere.
Regards
Jörg
Adobe XMP -
How to install custom XMP Get Info Panels in Adobe Bridge CC
Adobe changed their way they store the custom XMP Get Info Panels in Adobe Bridge CC. Check out this blog to see how you can install the XMP Get Info Panels that you used in Adobe Bridge CS6 in Adobe Bridge CC:
http://www.databasepublish.com/blog/installing-custom-metadata-panels-and-get-info-panels- adobe-bridge-ccCheck your Bridge preferences. It seems that you have the "Don't process images larger than…" option set to a lower amount than some of your files.
So, don't blame it on Bridge, but on the user who neglects that setting. -
Custom XMP palette in PSD...is it even possible?
Hi all,
I currently use DAM software that writes custom XMP info which I can see in the File Info dialog in PSD. I would like to see this info (read only) while I am working in PhotoShop. This custom XMP has instructions on what to do to the PSD file. In my perfect world it would be a floating palette in PSD that would show the XMP.
Stuck and would appreciate any expertise you might pass my way.
Thanks,
Lee>The ability to create a LabVIEW program from a script or
>from another LabVIEW program does not exist in version 7.
>The technology does exist and is being used but only by
>some NI programs (i.e. Vision Build and State Machine
>Toolkit).
Not any more.
I just create a VI, "Drop VI.vi", which let LabVIEW programmers creating VIs programmatically.
This VI drop a VI on the specified diagram progarmmatically at cursor position; drop a control/indicator on the specified front panel; or drop an image on the front panel/diagram. This VI can also be used to drop a file on Windows Explorer.
Demo can be downloaded from my web site.
George Zou
http://gtoolbox.yeah.net
George Zou
http://webspace.webring.com/people/og/gtoolbox -
[CS3 JS] Possible to Inspect Custom XMP Metadata With JavaScript?
I am using custom XMP metadata in InCopy and InDesign docs in CS3 to hold custom metadata that can vary wildly. I know the full set of possible items but not what values will be in a particular document.
Short of writing the XMP to a file and then processing that from my script, is there a way to inspect the custom properties from JavaScript. I didn't see a way to do it from the data model.
Thanks,
EliotHere is another script to catch MetaData, some more than the basic:
// metaDataOfLinks.jsx
//DESCRIPTION: Catches MetaData of linked images and creates a report at the DeskTop.
// Martin Fischer 10/2008
var myLinkXmpArray = ["author", "copyrightInfoURL", "copyrightNotice", "copyrightStatus ", "creationDate", "creator", "description", "documentTitle", "format", "jobName", "keywords", "modificationDate", "serverURL"];
var myIPTCArray = ["CiAdrCity", "CiAdrCtry", "CiAdrExtadr", "CiAdrPcode", "CiAdrRegion", "CiEmailWork", "CiTelWork", "City", "CiUrlWork", "CopyrightNotice", "Country", "CountryCode", "Creator", "CreatorContactInfo", "CreatorJobtitle", "DateCreated", "Description", "DescriptionWriter", "Headline", "Instructions", "IntellectualGenre", "JobID", "Keywords", "Location", "Provider", "Province-State", "RightsUsageTerms", "Scene", "Source", "SubjectCode", "Title"];
var myPSArray = ["photoshop:AuthorsPosition", "photoshop:CaptionWriter", "photoshop:Category", "photoshop:City", "photoshop:Country", "photoshop:Credit", "photoshop:DateCreated", "photoshop:Headline", "photoshop:Instructions", "photoshop:Source", "photoshop:State", "photoshop:SupplementalCategories", "photoshop:TransmissionReference", "photoshop:Urgency"];//var myPSArray = ["photoshop:AuthorsPosition", "CaptionWriter", "Category", "City", "Country", "Credit", "DateCreated", "Headline", "Instructions", "Source", "State", "SupplementalCategories", "TransmissionReference", "Urgency"];
var myTiffArray = ["tiff:ImageWidth", "tiff:ImageLength", "tiff:BitsPerSample", "tiff:Compression", "tiff:PhotometricInterpretation", "tiff:Orientation", "tiff:SamplesPerPixel", "tiff:PlanarConfiguration", "tiff:YCbCrSubSampling", "tiff:YCbCrPositioning", "tiff:XResolution", "tiff:YResolution", "tiff:ResolutionUnit", "tiff:TransferFunction", "tiff:WhitePoint", "tiff:PrimaryChromaticities", "tiff:YCbCrCoefficients", "tiff:ReferenceBlackWhite", "tiff:DateTime", "tiff:ImageDescription", "tiff:MakeProperName", "tiff:Model", "tiff:Software", "tiff:Artist", "tiff:Copyright"];
var myExifArray = ["exif:ExifVersion", "exif:FlashpixVersion", "exif:ColorSpace", "exif:ComponentsConfiguration", "exif:CompressedBitsPerPixel", "exif:PixelXDimension", "exif:PixelYDimension", "exif:UserComment", "exif:RelatedSoundFile", "exif:DateTimeOriginal", "exif:DateTimeDigitized", "exif:ExposureTime", "exif:FNumber", "exif:ExposureProgram", "exif:SpectralSensitivity", "exif:ISOSpeedRatings", "exif:OECF", "exif:ShutterSpeedValue", "exif:ApertureValue", "exif:BrightnessValue", "exif:ExposureBiasValue", "exif:MaxApertureValue", "exif:SubjectDistance", "exif:MeteringMode", "exif:LightSource", "exif:Flash", "exif:FocalLength", "exif:SubjectArea", "exif:FlashEnergy", "exif:SpatialFrequencyResponse", "exif:FocalPlaneXResolution", "exif:FocalPlaneYResolution", "exif:FocalPlaneResolutionUnit", "exif:SubjectLocation", "exif:ExposureIndex", "exif:SensingMethod", "exif:FileSource", "exif:SceneType", "exif:CFAPattern", "exif:CustomRendered", "exif:ExposureMode", "exif:WhiteBalance", "exif:DigitalZoomRatio", "exif:FocalLengthIn35mmFilm", "exif:SceneCaptureType", "exif:GainControl", "exif:Contrast", "exif:Saturation", "exif:Sharpness", "exif:DeviceSettingDescription", "exif:SubjectDistanceRange", "exif:ImageUniqueID", "exif:GPSVersionID", "exif:GPSLatitude", "exif:GPSLongitude", "exif:GPSAltitudeRef", "exif:GPSAltitude", "exif:GPSTimeStamp", "exif:DateTimeOriginal,", "exif:DateTimeDigitized.", "exif:GPSTimeStamp", "exif:GPSSatellites", "exif:GPSStatus", "exif:GPSMeasureMode", "exif:GPSDOP", "exif:GPSSpeedRef", "exif:GPSSpeed", "exif:GPSTrackRef", "exif:GPSTrack", "exif:GPSImgDirectionRef", "exif:GPSImgDirection", "exif:GPSMapDatum", "exif:GPSDestLatitude", "exif:GPSDestLongitude", "exif:GPSDestBearingRef", "exif:GPSDestBearing", "exif:GPSDestDistanceRef", "exif:GPSDestDistance", "exif:GPSProcessingMethod", "exif:GPSAreaInformation"];
var myCameraRawArray = ["crs:AutoBrightness", "crs:AutoContrast", "crs:AutoExposure", "crs:AutoShadows", "crs:BlueHue", "crs:BlueSaturation", "crs:Brightness", "crs:CameraProfile", "crs:ChromaticAberrationB", "crs:ChromaticAberrationR", "crs:ColorNoiseReduction", "crs:Contrast", "crs:CropTop", "crs:CropLeft", "crs:CropBottom", "crs:CropRight", "crs:CropAngle", "crs:CropWidth", "crs:CropHeight", "crs:CropUnits", "crs:Exposure", "crs:GreenHue", "crs:GreenSaturation", "crs:HasCrop", "crs:HasSettings", "crs:LuminanceSmoothing", "crs:RawFileName", "crs:RedHue", "crs:RedSaturation", "crs:Saturation", "crs:Shadows", "crs:ShadowTint", "crs:Sharpness", "crs:Temperature", "crs:Tint", "crs:ToneCurve", "crs:ToneCurveName", "crs:Version", "crs:VignetteAmount", "crs:VignetteMidpoint", "crs:WhiteBalance"];
var myInfo = new Array;
var myDoc = app.activeDocument;
var myLinks = app.documents[0].links;
for ( i = 0; i < myLinks.length; i++)
getMetaData ( myLinks[i] );
writeData ( 'Metadaten zu ' + myDoc.name + '\r-----------\r\r' + myInfo.join ( '\r\r'), File ('~/Desktop/Metadaten_' + myDoc.name.replace(/.indd$/, '') + '.txt'));
// ===============================================================
// Funktionen
// ===============================================================
function getMetaData ( aLink )
var myLinkXmp = aLink.linkXmp.properties.toSource().replace( /^\(\{/,'' ).replace (/\)\}$/,'').replace( /parent.+$/,'').replace(/:/g, ':\t').split( ', ');
var myString = aLink.name;
myString += loopLinkXmp ( aLink, myLinkXmpArray );
myString += loopArray ( aLink, "http://iptc.org/std/Iptc4xmpCore/1.0/xmlns/", "Iptc4xmpCore:CreatorContactInfo/Iptc4xmpCore:", myIPTCArray);
myString += loopArray ( aLink, "http://ns.adobe.com/photoshop/1.0/", "", myPSArray );
myString += loopArray ( aLink, "http://ns.adobe.com/tiff/1.0/", "", myTiffArray );
myString += loopArray ( aLink, "http://ns.adobe.com/exif/1.0/", "", myExifArray );
myString += loopArray ( aLink, "http://ns.adobe.com/camera-raw-settings/1.0/", "", myCameraRawArray );
myInfo.push( myString.replace( /, $/,'') );
function loopArray( aLink, s1, s2, anArray )
var temp = '\r\t--- ' + s1 + ' ---\r\t';
for ( var a = 0; a < anArray.length; a++)
try {
var theEvalString = 'aLink.linkXmp.getProperty(\"' + s1 + '\", \"' + s2 + anArray[a] + '\")';
var myCode = eval( theEvalString );
if ( myCode != '' )
temp += '[' + anArray[a] + ']\t' + myCode + '\r\t';
} catch (e){ //temp +=e + '\r'
return temp;
function loopLinkXmp( aLink, anArray )
var temp = '\r\t--- LinkMetadata ---\r\t';
for ( var a = 0; a < anArray.length; a++)
try {
var theEvalString = 'aLink.linkXmp.' + anArray[a] ;
var myCode = eval( theEvalString );
if ( myCode != '' )
temp += '[' + anArray[a] + ']\t' + myCode + '\r\t';
} catch (e){ //temp +=e + '\r'
return temp;
function writeData ( aData, theFile )
theFile.open ( 'w', 'Text', 'R*ch' );
theFile.encoding = 'UTF-8';
theFile.write ( aData );
theFile.close ();
Ressources:
Adobe XMP Developer Center: http://www.adobe.com/devnet/xmp/
XMP Specification: http://www.adobe.com/devnet/xmp/pdfs/xmp_specification.pdf
Martin Fischer -
Incrementally appending custom XMP metadata into PDF files
I have a problem writing custom XMP metadata into a PDF document (I'm using the XMP Toolkit SDK).
The problem is that I don't know whether is possible to expand the XMP packet in order to append metadata incrementally into the document, and, if it is possible, I don't know how to do it. The program I wrote succesfully appends an item to an array four times, but it fails when trying to append the fifth one. The reason obviously is that the packet gets full and there is not room for more metadata. The error message, if I force the PutXMP call, is:
ERROR: Can't fit into specified packet size
So, what can I do? How to enlarge the packet or make it expandable? Or, otherwise, have I to inject a new XMP packet with the up-to-date information in it? How?
And a last question: Have I to scan for packets when dealing with PDF files? No smart handlers are available for this kind of files?
Thanks in advance.
Xabier Artola.
Univ. of the Basque Country.Were you able to find a solution to this problem? I am having the same issue.
Jason -
Custom XMP panels don't show in Bridge CS4's Metadata palette
I've got a CS4 custom XMP panel working (using the "Generic" panel in the SDK) but I can't get it to display in the metadata palette of Bridge CS4 (the thing normally bottom right in the default Bridge "essentials" view).
In the old CS3 format, you could do this by adding an "fbname" attribute to fields of the custom panel. How do we now do this in the new SDK?
The Bridge metadata palette is mentioned on page 25 of the SDK programmer's guide, but the example given is merely of Dublin Core keywords (i.e. dc:subject) so shows in the Bridge metadata palette by default already.Following on from this question, is it possible to build up a Metadata panel group of fields drawn from different namespaces? (by group I mean something like the IPTC Core label and arrow which expands into the IPTC fields).
One would have a heading such as "My data", which when expanded shows x fields from one namespace #1 and y fields from namespace #2. I've tried to do this by leaving the namespace blank and hardcoding it and the prefix into the properties' name argument - eg http://ns.adobe.com/photoshop/1.0/photoshop:Urgency
Hope this isn't a hijack!
John -
Issues with Custom Package in Lightroom 3...please help
I am having issues with the custom package in lightroom 3. I am selecting diferent cell sizes (with different aspect ratios) and placing multiple images in these cells.
On screen everything looks good, but when it actually prints some of these cells are coming out stretched!! For example, the 6x4 cell comes out fine (same aspect ratio as the original capture), but i have 2 x 1.5 inch cell whose image comes out stretched??
The first thing I thought of was the "zoom to fit" option, but this is not present in picture package.
Then I thought it perhaps it was something to do with the my print settins, but cannot find anything there.I am having the same issue. I used a Matt Kloskowski print grid and when I printed it, or printed to file, some of the images in the 15 that were created in the template were distorted. Some the faces became wider and some narrower. Not just zoomed to fit. On screen it all looks correct. Many others on the forum where the template was posted don't seem to have this issue. I created a template myself just in case that was it but I got the same problem as walenahs. I tried to figure out what he had done but I didn't get it.
I have attached the two images. You can see the distortion in the second image on the top row (too narrow), and on the second row, the second in and second down, black and white (too wide).
Thanks -
Central (web based?) location for custom XMP panels
We maintain 3 custom XMP panels for a global network of photographers & DAM's. We'd like to be able to update our custom XMP panels (say add new drop down choices,) and have those immediately reflected globally. If Bridge checked a central resource (say a website) for what should be the most up to date version of an XMP panel, we would have an easier time managing the process.
Yes, the ability to subscribe to centrally-published custom XMP file info panels from CS apps would be extremely helpful, and since the CS4 panels are just XML files, a simple mechanism such as a subscription to an RSS feed would probably do the trick.
Maybe you are looking for
-
Hi I am trying to change the margins and layout of an existing in design document, help!
Hi I am trying to change the margins and layout of an existing in design document, help!
-
How to "smooth in" a gaussian blur fx?
Hi there I would like to know how can I "smooth in" a gaussian blur fx. I recorded a video and needed to add a tittle to the video and when I add the fx it doesn't fade in smoothly it's like ON and then OFF. Is there a way to make it like fade in
-
I create files using PS. Sometimes, these files will fail to open in PS at a later date. The error msg is that the file is corrupted. I can open them in Illustrator to view them. But they are lost to opening in PS. Why? And what can I do to corr
-
PDF line weight - please help!
Hi, When I save from InDesign as a PDF any line drawn with the pen tool/circle tool etc stay the same line weight no matter how much I'm zoomed in on the document. For example, I could zoom right out to 25% and the line thickness will still look at t
-
Cannot connect Ubuntu to AirPort Express WAP
Hello, I just installed Linux for the first time. I'm running Ubuntu 8.10 Intrepid Ibex. I have not been able to connect to our wireless network, which uses an Apple AirPort Express as its WAP. I have looked through the forums here, and done some sea