LR reading accents in metadata

I'm adding metadata to my photos on a Mac using the command-line tool "EXIFtool" (www.sno.phy.queensu.ca/~phil/exiftool/).
This works wonderfully, including the addition of words with accents and carets. I can type them into my terminal window without any trouble, and read them back fine.
However, when I try to read that information in Lightroom, it doesn't read the characters correctly. "é" becomes "É", and "É" becomes "í"! In addition, ê comes out as a question mark!
Does anyone know how I can add this information and have it successfully display in LR? I want to embed the data in the RAW file, rather than have it as an XMP sidecar, and so data entry in LR is not an option.
Many thanks,
Haydn

Similar Messages

I would like to use slideshow in lightroom to export my video as a full screen 1920x1080 video with text overlays. I am using text overlay in lightroom as it reads from the metadata that is easy for me to input in the library screen. When i export from

I would like to use slideshow in lightroom to export my video as a full screen 1920x1080 video with text overlays. I am using text overlay in lightroom as it reads from the metadata that is easy for me to input in the library screen. When i export from lightroom slideshow and choose the 1920x1080 resolution the end product is a very small video in the middle of a black background. i have double checked and do not have any borders turned on. Another option would be to export from the library but lr mogrify does not seem to put text overlays on video either. Any input would be welcome.

I dont understand anything you said in your post.
Do you have a specific question about video production?
The forums are for individual technical or creative issues that users have with video production. I am sur someone will be able to help you, but and to get a response it is best to ask a specific question.
Is this about a technical problem you have or something about setting up a web site? If its the latter this is the wrong forum.

Problem with Bridge CS4 reading/editing XMP metadata added in Bridge CS6

Please excuse me if this is a dumb/obvious question. I did try searching the forums for similar problems and didn't find anything that seemed to speak to my issue.
I'm having a problem where Bridge CS4 won't read/edit xmp metadata (specifically, keywords and descriptions in the IPTC panel) that I have entered using CS6. it will read some files, not others. The files are all .mp4s. Of these files, I can read/edit IPTC panel metadata for some of them in Bridge CS4; I can add metadata for all of them in CS6. I see no particular pattern in these files to explain what is and isn't read/editable in CS4.
My question is whether this is a compatibility issue between different versions of CS (in this instance, CS4 and CS6). i know it's a tired refrain to blame software when it could easily be user error, in which case I'd be frankly delighted to know what i'm doing wrong. Please bear with me as I give a few more details.
I'm using macs. I've tried this on multiple systems - for instance, on a mac pro 3 which for some reason has both CS4 and CS6 installed, i can add and edit keywords using CS6, but not when using CS4. Again, in CS4, some .mp4 files read/edit, others do not.
Bridge CS4 blames the files and tells me that the selected file cannot store xmp metadata, and that the properties cannot be modified. To be specific, in the metadata panel it says "this property cannot be modified"; in the keyword panel, it says, "This file (zzz.mp4) cannot store xmp metadata. No changes will occur." This seems odd, because I'm able to add xmp metadata for the same files in CS6 on the same computer, and other computers. I know this problem would disappear if all our computers were using CS6 (or CC), but unfortunately that's not a possibility at the moment. Some of them only have CS4.
Computer details (not an exhaustive list, but two instances): mac pro 3.1 running snow leopard, 16GB memory; macbook pro 4.1 running snow leopard, 4GB memory; adobe bridge cs6 (5.0.0.399) and cs4 (3.0.0.464).
Things I have tried:
Permissions - the files are set to read/write for everyone. Given that I can add/edit metadata in CS6, it doesn't seem to be a permission issue.
Purging the cache - other users seem to have had problems adding metadata in Bridge CS4 where purging the cache for affected files solved the problem. Didn't work in this instance.
Upgrading all affected computers to CS6/CC is beyond my control. I need to figure out why CS4 won't let me read/add/edit xmp metadata, if only for the sake of understanding the broader implications for interoperability.
Any helpful suggestions would be much appreciated.
Thanks,
Kevin

adobe bridge cs6 (5.0.0.399) and cs4 (3.0.0.464).
Without having experience with mp4 files and metadata my observation is that you certainly have not updated Bridge CS6 ( should be 5.0.2.4) and I believe also not the latest version of CS4, can't imaging this also stayed at .0.0 so first try to update both.
And if CS4 can read the data of some files it should be capable of reading them all. Be sure to have the files completely cached first, can take a while.
Other things to try in CS4 is refresh preferences (hold down option key while restarting Bridge and choose reset prefs).
And also check for hidden cache files using menu view/show hidden files. Sometimes those cache files can be troublesome between versions.
If purge cache did not work and reset prefs also failed consider to also delete Bridge plist file and Bridge cache file manual (from user library)

Content Library Explorer error -error occurred while trying to read the package metadata (can't find package in console)

I have SCCM 2012 SP1 recently upgraded to R2. I'm currently setting this up to migrate my production 2007 site. However, I'm trying to use Content Library Explorer on my DP's. I have 3 dps. DP2 connects fine but when i try and connect to DP1 +3 i get
the following error: An error occurred while trying to read the package metadata. The package
PackageID is invalid and must be redistributed from the Configuration Manger console.
Now i can't find any trace of this at all in the console. In the SMSPackagesHist table i can see the package ID and the deleted time was 29-07-2013. This most likely was me trying to create software updates back last year when i initially setup the site.
The package is not listed as content on any of the 3 DPs and i can't find any trace of it at all in the console.
I'm not very familiar with 2012, so not sure what I've done.
Any help or advice appreciated.
Thanks
Jane

Hi Torsten,
thanks for this. I did a search of the WMI key and found this document: http://blogs.technet.com/b/configmgrteam/archive/2012/05/07/troubleshooting-content-mismatch-warnings-on-a-distribution-point-in-system-center-2012-configuration-manager.aspx (does
this mean it is supported?)
however, on those 2 DP's in that class, the suspect package ID is not listed!???
Any more ideas?
Many thanks
Jane

Tomcat unable to read accented characters from MySQL

Folks,
Can anyone help with me this problem?
It seems that my version of Tomcat is unable to read accented characters from my MySQL Database.
I've checked in the Database and the characters are all correctly represented there. But when, in my servlet code, I do:
String author = results.getString("author_surname");If the String contains any accented character then the character shows as a '?'. (Even before it gets to the JSP - I'm writing the results straight to catalina.out).
Looking around these forums I found that some people suggested adding
?useUnicode=TRUE&characterEncoding=UTF-8;to the end of my jdbc url. As in:
<ResourceParams name="jdbc/connection">
//a whole load of other params
<parameter>
<name>url</name>
<value>jdbc:mysql://localhost:3306/bookshop?useUnicode=TRUE&characterEncoding=UTF-8</value>
</parameter>
</ResourceParams>inside my server.xml
But it doesn't seem to make any difference. In addition, I doubt I even need to use Unicode as the accents I need are only: �� etc.
(Incidentally, writing that line into my server.xml, tomcat complains that it should finish with a semi-colon. Is that correct? Even if I put in the semi-colon, it still complains!!)
Any suggestions on this would be much appreciated. Thank you.

user13109986 wrote:
HI,
From http://download.oracle.com/docs/cd/B10501_01/server.920/a96529/ch9.htm
My understanding is the JDBC Api converts the string from the database to UTF-16.. If so is there any way to disable the UTF-16 encoding at JDBC API?That's exactly what it's supposed to do. There isn't even any concept of what it would mean to disable that: Java characters are UTF-16 representations of Unicode code-points, so there isn't anything else it could do.
I still suspect the JDBC part is working correctly and your writing-to-file isn't. I found this quote in the Wikipedia article on Windows-1256:
Windows-1256 is a code page used to write Arabic (and possibly some other languages that use Arabic script, like Persian) under Microsoft Windows. This code page is not compatible with ISO 8859-6 and MacArabic encodings.So was there a particular reason you chose Cp1256 and not ISO-8859-6 as the charset to write to the file with?

How I read the encoded metadata with OSMF as with the as3 onMetaData?

Hi All:
I have a Video Element, loading a clip. In As3 i can use the onMetadata() function to read the embedded metadata properties. I tried
videoElement.client.addHandler(NetStreamCodes.ON_META_DATA, onMetaData);
and I'm using the sprint 7. But it throws me an error:
at org.osmf.video::VideoElement/get client()[C:\Dev\osmf\public\trunk\framework\MediaFramework\org\osmf\video\VideoElement.as:164]
So I guess my code is older than sprint 7.
Any idea someone?
Thanks,
Chaim

Hi Chaim,
You didn't give us all of the error message there. The netStream.client gets set by the framework after the netConnection has succeeded, which translated into OSMF speak means the media is "loaded". Here is a sample code snippet that works with the current sprint (8).
         (videoElement.getTrait(MediaTraitType.LOAD) as LoadTrait).addEventListener(LoadEvent.LOAD_STATE_CHANGE, onLoaded);
        private function onLoaded(event:LoadEvent):void
            if (event.loadState == LoadState.READY)
                videoElement.client.addHandler(NetStreamCodes.ON_META_DATA, onMetadata);
        private function onMetadata(info:Object):void
Hope that helps,
- charles

Bridge script could not read PSD file metadata reliably

I'm trying to read metadata (specifically, xmp.CreateDate and tiff.DateTime) of a bunch of PSD files using a loop. Bridge script seems able to read most of them but always fails to read some (returns empty strings), though not necessarily any particular ones. That is, if I run multiple times, it fails on different files. Basically, it's just not reliable. Is there a solution for this? Please help. Thanks.

Hi skc_chat,
According to the error message, you may do not have the permission to view the metadata. Please follow the steps below to grant the permissions to the current login on the SQL Server Management Studio:
Right click on the server name and select properties.
Click on the Permissions tab.
Select the login name.
On the Explicit tap, Grant "View Any Definition" to this login.
To grant this permission by T-SQL:
GRANT VIEW ANY DEFINITION TO <loginname>
Go
For more information:
Cannot Create Script
Also have a look at this article with the same error:
http://blog.davidsilvasmith.com/2011/08/i-was-on-sql-server-2008-r2-database-i.html
Best Regards,
Stephanie Lv
Please remember to mark the replies as answers if they help and unmark them if they provide no help.

API for reading/updating Lightroom metadata

I've tried looking for documentation, and I can't find it, so...
Is there an officially sanctioned mechanism for third party applications to read and edit Lightroom metadata? In particular, the keywords that have been assigned?
My use case is as follows. I pull photos in to Lightroom, edit, adjust, add metadata, and so on. Then, for some of them, I export them to Flickr, using the Flickr Uploadr tool.
Sometimes, based on comments on the photos, I may want to edit the metadata. I can do this, but I need to edit it in both places, Lightroom and Flickr.
Flickr publishes an API for rummaging through photos, extracting metadata, and so on. So what I'd like to do is develop a tool that periodically looks at my photos on Flickr, compares the keywords it finds there with the keywords in Lightroom, and synchronises them. The Flickr side of that is fairly easy, but the Lightroom side doesn't appear to be documented.

Hi Birla,
try this:
IResource res = ResourceFactory.getInstance().getResource(path,context);
IPropertyName propName = new PropertyName("http://ars.com/xmlns/cm","Region");
java.util.List values = new List();
values.add("Asia");
values.add("America");
values.add("Muenster, Germany");
IProperty property = new Property(propName, PropertyType.STRING, values);
res.setProperty(property);
Best regards,
Michael

Zfs list on solaris express 11 always reads from disk (metadata not cached)

Hello All,
I am migrating from OpenSolaris 2009.11 to SolarisExpress 11.
I noticed that "zfs list" takes longer than usual, and is not instant. I then discovered via a combination of arcstat.pl and iostat -xnc 2 that every time a list command is issued, there are disk reads. This leads me to believe that some metadata is not getting cached.
This is not the case in OpenSolaris where repeated "zfs list" do not cause disk reads.
Has anyone observed this, and do you know of any solution?
This is on an IDLE sustem with 48 GB of RAM - with plenty of free memory.

Hi Steve,
Great info again. I am still new to dtrace, particularly navigating probes and etc. I've seen that navigation tree before.
I would like to start by answering your questions:
Q) Have you implemented any ARC tuning to limit the ARC?
-> No out of the box config
Q) Are you running short on memory? (the memstat above should tell you)
-> Definetelly not. I have 48 GB ram, ARC grows to about 38 GB and then stops growing. I can reproduce problem at boot at will with only 8GB used. Nothing is getting aged out of the ARC at that time. Only those metadata reads never get stored.
Q) Are any of your fileystems over 70% full?
-> No. I am curious, what changes when this happens? Particularly in regards to ARC - perhaps another discussion, I don't want to distract this subject.
Q) Have you altered what data is/is not cached? ($ zfs get primarycache)
-> No - everything should be cached. I also have recently added l2cache (80GB). The metadata is not cached there neither.
I am not yet familiar with dtrace processing capabilities, thus I had to parse output via perl. Notice how each execution has the exact same number of misses. This is due to the fact that these particular datablocks (metadata blocks) are not cached in the arc at all:
:~/dtrace# perl -MData::Dumper -e 'while (<>) {if (/.+(:arc-hit|:arc-miss).*/) { $h{$1}+=1}} print Dumper \%h' ^C
:~/dtrace# ./zfs_list.d -c 'zfs list' |perl -MData::Dumper -e 'while (<>) {if (/.+(:arc-hit|:arc-miss).*/) { $h{$1}+=1}} print Dumper \%h'
dtrace: script './zfs_list.d' matched 4828 probes
dtrace: pid 11021 has exited
$VAR1 = {
          ':arc-hit' => 2,
          ':arc-miss' => 192
:~/dtrace# ./zfs_list.d -c 'zfs list' |perl -MData::Dumper -e 'while (<>) {if (/.+(:arc-hit|:arc-miss).*/) { $h{$1}+=1}} print Dumper \%h'
dtrace: script './zfs_list.d' matched 4828 probes
dtrace: pid 11026 has exited
$VAR1 = {
          ':arc-hit' => 1,
          ':arc-miss' => 192
:~/dtrace# ./zfs_list.d -c 'zfs list' |perl -MData::Dumper -e 'while (<>) {if (/.+(:arc-hit|:arc-miss).*/) { $h{$1}+=1}} print Dumper \%h'
dtrace: script './zfs_list.d' matched 4828 probes
dtrace: pid 11031 has exited
$VAR1 = {
          ':arc-hit' => 12,
          ':arc-miss' => 192
:~/dtrace# ./zfs_list.d -c 'zfs list' |perl -MData::Dumper -e 'while (<>) {if (/.+(:arc-hit|:arc-miss).*/) { $h{$1}+=1}} print Dumper \%h'
dtrace: script './zfs_list.d' matched 4828 probes
dtrace: pid 11036 has exited
$VAR1 = {
          ':arc-hit' => 4,
          ':arc-miss' => 192
:~/dtrace# ./zfs_list.d -c 'zfs list' |perl -MData::Dumper -e 'while (<>) {if (/.+(:arc-hit|:arc-miss).*/) { $h{$1}+=1}} print Dumper \%h'
dtrace: script './zfs_list.d' matched 4828 probes
dtrace: pid 11041 has exited
$VAR1 = {
          ':arc-hit' => 27,
          ':arc-miss' => 192
:~/dtrace# I presume next steps would be to perform stack analysis on which blocks are been not cached. I don't know how to do this ... I am guessing this is a mid-function probe? "| arc_read_nolock:arc-miss" I don't know how to access it's parameters.
FYI, here's an example of a cache miss in my zfs list:
0 -> arc_read
0    -> arc_read_nolock
0      -> spa_guid
0      <- spa_guid
0      -> buf_hash_find
0        -> buf_hash
0        <- buf_hash
0      <- buf_hash_find
0      -> add_reference
0      <- add_reference
0      -> buf_cons
0        -> arc_space_consume
0        <- arc_space_consume
0      <- buf_cons
0      -> arc_get_data_buf
0        -> arc_adapt
0          -> arc_reclaim_needed
0          <- arc_reclaim_needed
0        <- arc_adapt
0        -> arc_evict_needed
0          -> arc_reclaim_needed
0          <- arc_reclaim_needed
0        <- arc_evict_needed
0        -> zio_buf_alloc
0        <- zio_buf_alloc
0        -> arc_space_consume
0        <- arc_space_consume
0      <- arc_get_data_buf
0      -> arc_access
0       | arc_access:new_state-mfu
0        -> arc_change_state
0        <- arc_change_state
0      <- arc_access
0     | arc_read_nolock:arc-miss
0     | arc_read_nolock:l2arc-miss
0      -> zio_read
0        -> zio_create
0          -> zio_add_child
0          <- zio_add_child
0        <- zio_create
0      <- zio_read
0      -> zio_nowait
0        -> zio_unique_parent
0          -> zio_walk_parents
0          <- zio_walk_parents
0          -> zio_walk_parents
0          <- zio_walk_parents
0        <- zio_unique_parent
0        -> zio_execute
0          -> zio_read_bp_init
0            -> zio_buf_alloc
0            <- zio_buf_alloc
0            -> zio_push_transform
0            <- zio_push_transform
0          <- zio_read_bp_init
0          -> zio_ready
0            -> zio_wait_for_children
0            <- zio_wait_for_children
0            -> zio_wait_for_children
0            <- zio_wait_for_children
0            -> zio_walk_parents
0            <- zio_walk_parents
0            -> zio_walk_parents
0            <- zio_walk_parents
0            -> zio_notify_parent
0            <- zio_notify_parent
0          <- zio_ready
0          -> zio_taskq_member
0          <- zio_taskq_member
0          -> zio_vdev_io_start
0            -> spa_config_enter
0            <- spa_config_enter
0            -> vdev_mirror_io_start
0              -> vdev_mirror_map_alloc
0                -> spa_get_random
0                <- spa_get_random
0                -> vdev_lookup_top
0                <- vdev_lookup_top
0              <- vdev_mirror_map_alloc
0              -> vdev_mirror_child_select
0                -> vdev_readable
0                  -> vdev_is_dead
0                  <- vdev_is_dead
0                <- vdev_readable
0                -> vdev_dtl_contains
0                <- vdev_dtl_contains
0              <- vdev_mirror_child_select
0              -> zio_vdev_child_io
0                -> zio_create
0                  -> zio_add_child
0                  <- zio_add_child
0                <- zio_create
0              <- zio_vdev_child_io
0              -> zio_nowait
0                -> zio_execute
0                  -> zio_vdev_io_start
0                    -> spa_syncing_txg
0                    <- spa_syncing_txg
0                    -> zio_buf_alloc
0                    <- zio_buf_alloc
0                    -> zio_push_transform
0                    <- zio_push_transform
0                    -> vdev_mirror_io_start
0                      -> vdev_mirror_map_alloc
0                      <- vdev_mirror_map_alloc
0                      -> vdev_mirror_child_select
0                        -> vdev_readable
0                          -> vdev_is_dead
0                          <- vdev_is_dead
0                        <- vdev_readable
0                        -> vdev_dtl_contains
0                        <- vdev_dtl_contains
0                      <- vdev_mirror_child_select
0                      -> zio_vdev_child_io
0                        -> zio_create
0                          -> zio_add_child
0                          <- zio_add_child
0                        <- zio_create
0                      <- zio_vdev_child_io
0                      -> zio_nowait
0                        -> zio_execute
0                          -> zio_vdev_io_start
0                            -> vdev_cache_read
0                              -> vdev_cache_allocate
0                              <- vdev_cache_allocate
0                            <- vdev_cache_read
0                            -> vdev_queue_io
0                              -> vdev_queue_io_add
0                              <- vdev_queue_io_add
0                              -> vdev_queue_io_to_issue
0                                -> vdev_queue_io_remove
0                                <- vdev_queue_io_remove
0                              <- vdev_queue_io_to_issue
0                            <- vdev_queue_io
0                            -> vdev_accessible
0                              -> vdev_is_dead
0                              <- vdev_is_dead
0                            <- vdev_accessible
0                            -> vdev_disk_io_start
0                            <- vdev_disk_io_start
0                          <- zio_vdev_io_start
0                        <- zio_execute
0                      <- zio_nowait
0                    <- vdev_mirror_io_start
0                  <- zio_vdev_io_start
0                  -> zio_vdev_io_done
0                    -> zio_wait_for_children
0                    <- zio_wait_for_children
0                  <- zio_vdev_io_done
0                <- zio_execute
0              <- zio_nowait
0            <- vdev_mirror_io_start
0          <- zio_vdev_io_start
0          -> zio_vdev_io_done
0            -> zio_wait_for_children
0            <- zio_wait_for_children
0          <- zio_vdev_io_done
0        <- zio_execute
0      <- zio_nowait
0    <- arc_read_nolock
0 <- arc_read                              I've compared the output of a single-non cached metadata read, to a single read from filesystem by running dd and read from a file that is not in the cache. The only difference in the stack is that the non-cached reads are missing:
0                                -> vdev_queue_offset_compare
0                                <- vdev_queue_offset_compare This is called in "-> vdev_queue_io_to_issue ". But I don't think this is relevant, perhaps related to metadata vs file data read.
What do you think should be next?

Read Image XMP Metadata

Hi All,
Hope I'm not spamming this thread to your mailbox as I felt this question asked in unrelated forum.
Question: Can we read image meta data from Flex ?
I tried it with xmp core library and passed a jpeg file to xmpMeta object :
private function getImageMetadata(jpeg:File):void
                              var meta:XMPMeta = new XMPMeta(jpeg);
                              var packet:XML = meta.serializeToXML();
                              var photoshop:Namespace = XMPConst.photoshop;
                              var value:String = meta.photoshop::AuthorsPosition;
                                trace(value); // returns null, not sure why
Can any one help me to get the image metadata.
Thanks in advance
Mac

I've got some content related to my issue from net but still it won't solve my problem
private function init():void {
                                        var ldr:Loader = new Loader();
                                        ldr.contentLoaderInfo.addEventListener(Event.COMPLETE, imgLoaded);
var s:String = "my/jpgPath/myjpgName.jpg";
                                        ldr.load(new URLRequest(s));
                              private function imgLoaded(e:Event):void{
                                        var info:LoaderInfo = e.target as LoaderInfo;
                                        var xmpXML:XML = getXMP(info.bytes);
//trace(xmpXML);
                                        var meta:XMPMeta = new XMPMeta(xmpXML);
//var packet:XML = meta.serializeToXML();
                                        var photoshop:Namespace = XMPConst.photoshop
                                        trace(meta.photoshop::AuthorsPosition);
                              private function trim(s:String):String{
return s.replace( /^([\s|\t|\n]+)?(.*)([\s|\t|\n]+)?$/gm, "$2" );
                              private function getXMP(ba:ByteArray):XML{
                                        var LP:ByteArray = new ByteArray();
                                        var PACKET:ByteArray = new ByteArray();
                                        var l:int;
                                        ba.readBytes(LP, 2, 2);
                                        http://www.adobe.com/devnet/xmp.html
                                        read part 3: Storage in Files.
                                        that will explain the -2 -29 and other things you see here.
                                        l = LP.readInt() - 2 -29;
                                        ba.readBytes(PACKET, 33, l);
                                        var p:String = trim(encode(PACKET) as String);
var i:int = p.search('<x:xmpmeta xmlns:x="adobe:ns:meta/"');
/* Delete all in front of the XMP XML */
                                        p = p.substr(i);
                                        For some reason this left some rubbish in front, so I'll hardcode it out for now
                                        TODO clean up
                                        var ar:Array = p.split('<');
                                        var s:String = "";
                                        var q:int;
                                        var j:int = ar.length;
                                        for(q=1;q<j;q++){
                                                  s += '<'+ar[q];
                                        i = s.search('</x:xmpmeta>');
                                        i += ('</x:xmpmeta>').length;
                                        s = s.slice(0,i);
/* Delete all behind the XMP XML */
                                        return XML(s);
                              private static function encode(ba:ByteArray):String {
var origPos:uint = ba.position;
var result:Array = new Array();
   for (ba.position = 0; ba.position < ba.length - 1; )
   result.push(ba.readShort());
if (ba.position != ba.length)
   result.push(ba.readByte() << 8);
ba.position = origPos;
                                                  return String.fromCharCode.apply(null, result);
It seems there is a bug in XMPMeta class where it always throws an exception "The XMPMeta object cannot have qualifiers", Even created with default (no param).
Does anyone have any clue on this? please help
Thanks
Mac

Using BI SDK to read Bex report Metadata

Hi,
I want to read the Bex Reports Metadata. Does BI SDK contains such routines?
I am anxious to know how BI SDK can be helpful in this requirement, please suggest any other alternatives that may help.
Thanks,
Neeraj Patwal

Try using the following
Suppose <b>TESTVAR</b> is having the value <b>A</b>
If TESTVAR is single value
var_name_1=TESTVAR
VAR_VALUE_EXT_1 = A
if TESTVAR is range
var_name_1=TESTVAR
VAR_VALUE_LOW_EXT_1 = A
VAR_VALUE_HIGH_EXT_1 = A

How to read the EXIF metadata from a .jpg file

hi,every one
Photos which are captured by a digital camera, have some parameters, such as the exposure time,ISO speed rating,camera model,focal length etc.
How to read this parameters???

Is it listed in the IIOMetadata?
import java.awt.*;
import java.io.*;
import java.net.*;
import java.util.*;
import javax.imageio.*;
import javax.imageio.metadata.*;
import org.w3c.dom.*;
public class IIOMetaDataExample {
    public static void main(String[] args) throws IOException {
        URL url = new URL("http://today.java.net/jag/bio/JagHeadshot-small.jpg");
        Iterator readers = ImageIO.getImageReadersBySuffix("jpeg");
        ImageReader reader = (ImageReader) readers.next();
        reader.setInput(ImageIO.createImageInputStream(url.openStream()));
        IIOMetadata metadata = reader.getImageMetadata(0);
        displayMetadata(metadata);
    public static void displayMetadata(IIOMetadata metadata) {
        String[] names = metadata.getMetadataFormatNames();
        for(int i=0; i<names.length; ++i) {
            System.out.println();
            System.out.println("METADATA FOR FORMAT: " + names);
displayTree(metadata.getAsTree(names[i]), 0);
public static void displayTree(Node node, int indent) {
indent(indent);
String name = node.getNodeName();
System.out.print("<" + name);
if (node.hasAttributes()) {
NamedNodeMap attrs = node.getAttributes();
for(int i=0, ub=attrs.getLength(); i<ub; ++i) {
Node attr = attrs.item(i);
System.out.print(" " + attr.getNodeName() + "=" + attr.getNodeValue());
if (node.hasChildNodes()) {
System.out.println(">");
NodeList children = node.getChildNodes();
for(int i=0,ub=children.getLength(); i<ub; ++i)
displayTree(children.item(i), indent+4);
indent(indent);
System.out.println("</" + name +">");
} else
System.out.println("/>");
static void indent(int indent) {
for(int i=0; i<indent; ++i)
System.out.print(' ');

Aperture unable to read/reveal Hipstamatic metadata

In the APP "Hipstamatic" you can click a button and the pic would turn over and reveal the type of film, lens and flash used... amongst other information. After importing these pics into Aperture 3.4.3 I am unable to detect or find any of this information (i.e. Salvador 84 + DreamCanvas + DreamPop) anywhere.
I've found other post suggesting to use a 3rd party software (i.e. Lyn = $20.00) might be the best solve but I would rather stay within Aperture and have less programs running.
Hoping there is a simple solve that I've overlooked.
Thanks a bunch...!

This thread (towards the bottom) has an okay fix....
https://discussions.apple.com/message/22642467?ac_cid=tw123456#22642467

How can I read out metadata for captions from a Canon photo

I have to tried to find an answer via Adobe and Google. Still not able to figure out on how to read out XMP metadata for captions out of my photos. Checking the XMP data in InDesign shows info on Camera Make, Exposure etc. But if I use metadata fields from "Caption Setup" like "Camera" the caption shows <No data from link>. Fields where the XMP field name matches (e.g. "Lens") are ok. I need following fields for the caption: Camera Make, Exposure (aperture and speed) and ISO.

Lets keep it simple then.
If I take my utf file generated and open and view it in notepad I can see the accented characters. But if I open it in Wordpad , the accented characetrs are corrupted.
If I then save the file specifiying type Ascii, then the characters are written out correctly.
What I want to do is to be able to write out the file in ascii format without having to open it in utf-mode and then having to save it in ascii.
Ie I want the file to be opened in ascii format
All the characters to be written in Ascii format
But the source is still a unicode database.
I have gone through using convert and characters get lost. In fact, at this stage, I'm not sure its possible to do What I need to do.
Remember I am using an 8 bit character set which is why I have values above 127.
So basically if you take the word 'Annulé'
if I view it in wordpad it displays as
AnnulÃ©
But if I view it in notepad it displays as
'Annulé' which is because notepad detects that the file has a utf-8 character in it.
When I save it as type ascii I can then open it correctly in wordpad.
So I basically want to open this file in Wordpad and have it display Annulé rather than the garbled characters,
without having to go through the process of opening and saving the file as type ansi.

How to re-read metadata from file in Photoshop Elements 11 Organizer?

I am currently testing Lightroom 4 and Photoshop Elements 11 as a replacement for my old softwarestack due to a new DSLR.
In Lightroom I can read and write metadata directly from/to file. In Photoshop Elements Organizer I have found an option to write tags to files, but none to re-read the metadata after the files has been imported to the catalog.
I would like to use Lightroom as primary organizer for import/tagging/basic corrections. But Lightroom does not have some nifty things like face/person recognition and SmartTags, so I need the Photoshop Elements Organizer to do that. The target workflow would be:
DSLR -> Import to -> Lightroom -> tagging -> basic corrections -> write tags to file in Lightroom -> import to PSE organizer -> person recognition -> smart tags -> image edits -> write tags to files in PSE organizer ==> tags can now be re-read in Lightroom, so I get the PSE organizer changes to Lightroom.
And that is the problem: If changes were made after this workflow in Lightroom, PSE Organizer does not know that until I can re-read the metadata from the files. If I press "write tags to file" in PSE organizer all newer Lightroom tags will be overwritten with the old tags from PSE organizer.
Does anyone knows a solution for this problem? Or should I file a feature request for both programs?

You can now do a lot more in the metadata panel in PSE 11. If you select a thumbnail in Organizer and click the three small dots it will bring up a dialog for the metadata fields. To add information to many photos all at once, select all the thumbnails, click the information tab and then click the button marked Add IPTC information. You can then choose to append new information to all of the selected items or to overwrite.
See image below

LR reading accents in metadata

Similar Messages

Maybe you are looking for