EXIF time adjustment extension

Currently LR allows only for some kinds of time adjustments in selected sets of images, but in situations in which more than one person, or more than one camera are being used in the same event, the problem is often that the time recorded by the cameras might be off sync in relation to each other.
I would like to suggest an extension to deal with this type of situations. I would like to be able to say something to the effect: Image A1234.raw Camera A was shot after B3456.raw camera B. LR should than take the exif times from A1234 and B3456 and find out the time offset to be applied on A1234, or even on a selected set of images made with a camera A.
Currently I use Exiftool to do it manually, throw all images out from LR and reimport them after the EXIF adjustment, because "sync folder" does not reflect changes done to exif time by Exiftool..
Thomas

There are several known bugs relating to the way LR handles the time and date fields.

Similar Messages

  • Need to batch reset iPhoto pic time to EXIF time

    Hi gang,
    I have found a bunch of old pics in my iPhoto library that don't have the correct time assigned to them.  For example, a pic taken at 5 PM is listed in iPhoto as having been taken at 8PM.  If I "Reveal in Finder", then open the pic in Preview, the EXIF time is correct (5PM).
    Is there a way to have iPhoto reset pic times back to the original EXIF time?  I found some old scripts (Joe's iPhoto Applescripts), but they look quite out of date.  I would be anxious running them on my current library.
    I am using iPhoto 11 (v9.4.2).
    Cheers!

    I'm not sure how you have changed the date/time in iPhoto - but using smart albums you can identify photos form a specific camera - or many other attributes
    in Events view the default sore is by date/time so I would expect the problem photos to be grouped together  --  and in Photo view you can select several different sorts and by truning off show event titles you can view all of your photos as a single group
    I'm not clear on whart you found or what you are expecting but the way to modify the contents of the iPhoto database is to only use iPhoto to do it - never make any changes of any sort directly to the files in the database
    LN

  • Changing exif: time

    Hello to everybody,
    Being new in this forum, I would like to introduce myself as an photo-fan working regular with Aperture. That does not mean, I know that program in all details.
    So here is my first question: in mobile me, I published my fotos in a gallery. A friend uploaded his photos as well. Now I recognised, that fotos are not in correct order. Error was on my side, since my time settings in my 5D where 1 hour too early, e.g. 10.30 where it should have been 11.30.
    I filtered now all my 5D pictures - but how can I edit time settings now ?
    BR,
    Henri

    Found the solution!
    Very easy:
    Go in "Metadata"
    Select "Change Date and time"
    Adjust the time setting
    Very intelligent: if you choose e.g. 60 pics, Aperture applies a relative time change, e.g. 2h and 40m are added to all pictures. Mighty feature to get fotos from different users with different time settings in right order.
    Regards, Henri

  • EXIF time difference once images imported into Organizer in PSE8

    I have been frustrated for a very long time and did some reading on the web - The solution: Sorry it is a bug
    in PSE* and cannot be fixed!!!!!
    The problem: Once I have imported images into PSE8 Organizer the EXIF time is converted to exactly two hours earlier, i.e. to GMT whereas I am at GMT+2. Note that the time on my Canon 7D and my computer (on windows 7) are correct!!!!!! If I do not use organizer, I do not have the problem!
    From what I have read it is a bug in PSE and there is no permanent fix, but really.... How can Adobe not solve the problem?
    Will it help if I purchase another copy of PSE8, is there a PERMANENT fix available and if so, what?
    I am really frustrated, as I want to use the organizer, but cannit do it as the time is of great importance to me in my wildlife photography!!!!
    Anyone?
    Rudi

    Wonderful! This EXIF standard, 2.2, http://www.kodak.com/global/plugins/acrobat/en/service/digCam/exifStandard2.pdf explains to me that the original form of the material digitized could be a "slide", "paper", "map" and so forth; so it's a standard for many types of digital still "cameras", not just a standard for typical, portable consumer cameras. EXIF time recording is first described on page 55.
    Most of the time (or all of the time for me?), in Lightroom, the "date time original" and "Time Date digitized" has been the same and changing the original date will obviously (?) change the digitized date, too.
    Thanks!
    PS: re-reading my post, I don't want anyone to think I was really getting RAW data from my Sony. It's a great little pocket camera but it only produces JPG's.

  • Applying time adjustment twice.

    I guess the time adjustment works on what is showing, not on the original photo time. I used Batch Change twice on some photos because some of them weren't imported with the time adjustment, so I thought, what the heck I'm just telling it the camera time (always UTC) and the local time zone, so if I do it again it shouldn't matter (I'm assuming Aperture is looking at the original photo time capture). But Aperture does the shift twice. I see this as a bug, but maybe my thinking is wrong.
    This happens frequently for me because I use two camera's and also my girl friends pictures, and when I'm importing I sometimes forget to set the time adjustment.
    Update:
    I dug into the library and the original photo has not been change and "Date Time Original" and "Date Time Digitized" are still the correct UTC zone. (But we all knew that since Aperture never changes the original.) Why can't I use this as the basis for resetting the "Image Date"?
    Message was edited by: MtnBiker

    user12860499 wrote:
    Hi all,
    A developer came to me saying that he put a 11gr2 table into default compression mode which was already in default compresssion mode.After that 32GB of table got compressed to 26GB. How is this possible?Is it that it is double compressed?
    Right now I do not have access to that database nor do I know how to find what happed there. Only thing I can think of is that , the table was originally put in compression in 11gr1 and then again applied compression in 11gr2,so some algorithm enhancement might have done this.
    Any thoughs?
    with this I am also wondering what happens when enahancements are introduced in any feature I mean let say in case of compression if a algorithm enhanced will the enahancement be applied on the whole table or the data that will be inserted/updated post such upgrade?multiple compression option available in 11gR2 with different compression level.
    see complete detail
    http://docs.oracle.com/cd/E11882_01/server.112/e25494/tables002.htm#ADMIN11630
    and Compression can occur while data is being inserted, updated, or bulk loaded into a table.

  • NI 1772 camera exposure time adjustment resolution

    What is the exposure time adjustment resolution capability for the NI 1772 camera?  I'm getting only 10ms.  Can I get 5 or even 1ms resolution?

    Hi Rob,
    I am unclear what the problem you are seeing is. Vision Builder AI does not appear to impose any restrictions on the granularity of the exposure time. You can put any value with precision down to sub-microsecond levels (no need to go by units of 10 microseconds).
    As for the changes in intensity vs exposure time, keep in mind that image sensors and the hardware that reads them don't necessarilly behave linearly and so you may not see such a linear relationship in the data. While you said that you saw no change in intensity from 70us to 80us, were you looking at a single pixel or an average of the entire sensor? If you average it over the whole sensor I think you'll see the difference (although it might be small and less than a single count).
    Eric

  • What does "Exif Time Stamp Error" mean?

    Hi there,
    could anyone be so kind and explain to me the meaning / impact of the "Exif Time Stamp Error" that was introduced in the 1.4 update for lightroom?
    I imported about 200 pics yesterday and converted let them be converted to the DNG format automatically.
    Actually I did not see any errors or strange behaviours. Will this change when working with these pics? Do I have to take some kind of countermeasure?
    Kind regards,
    J. Toennissen
    MacBook, Mac OSX 10.4 (Tiger), Lightroom 1.4

    Dear Franz,
    thank you for your post but I already read through this text and after I did not get the point (maybe because of my by far not perfect English) I did search the forums. But I did not find any furher explanation.
    There I wrote this post.
    So, as a special rule, sometimes people do use the search and really need help. ;-)
    Jan

  • Exif Time

    I have just noticed that the exif time displayed in Lightroom is +1 hour compared to Exifer and CS3. Is anyone else seeing this?
    Ian

    There are several known bugs relating to the way LR handles the time and date fields.

  • Times ten extension

    After installing the times ten extension sql developer is totally trashed. NOTHING WORKS. ABSOLUTELY NOTHING WORKS. I downloaded SQL*Developer w/JRE and installed. Worked fine. Then I imported my old connections. Worked fine. Then I installed the extension. Nothing works. I keep getting stack traces. I am running Windows 2003 server.
    I just installed times ten from the CD I got at OpenWorld. (Which comes with the old version of SQLDeveloper that is incompatible with times ten).

    I reentered did my search and found the answer. You all need google or something to improve searches. It wastes my time and yours.
    Anyway, thanks. :-)

  • Printing problem linked to EXIF time data for JPEG images.

    For some years I have been using Photoshop Elements 8.0 with no problems of any kind. My computer runs on XP Professional with a system comfortably in excess of the minimum requirements to run Elements 8.0. I load my images into Elements from a card reader which is the same one since I got this version of Elements. I shoot mostly in JPEG with a Nikon D300. I print to one of 2 Epson printers, an SX100 and a PX700W. I don't use the wireless feature of the PX700W, connecting it via USB.
    About a year ago I suddenly began to experience printing problems. If I tried to print an image Elements crashed just at the point where printing would begin. By trial & error I discovered that if I adjusted the time in the EXIF data of the image in Elements, whether by advancing or retarding it by hours or days and then adjusted it back to the original time I had no problems printing that image thereafter.
    I also discoveredc that where I had shot in RAW I could print direct from the RAW image in Elements or from the JPEG I saved from an edited in RAW and had no problems.
    I saw the forum discussions about the issues about the date/time in EXIF having been changed following the import into Elements. For those images I still had on my memory cards I checked the EXIF data in Elements and compared it what was on the image on the card. They were the same. I also checked the time zone and time settings of the camera and they were correct.
    I backed up my catalog, re-formatted the computer to bring it back to its ex-factoy status, re-installed Elements and restored my catalog. I imported new images, tried to print them and the problem was still there.
    Before I might upgrade to Photoshop Elements 10 I'm hoping someone else may tell me they have had the same problem and, hopefully, be able to tell me how they fixed it. I know the workaround will bypass the problem but it really annoys me that it suddenly appeared and I seem to be stuck with it. I'm also concerned that, given I totally re-formatted my computer but the problem  is still with me, that the problem may be imbedded in my catalog and simply gets backed up to,\and restored from,  my backup.
    I'd be grateful for any ideas.

    Hi Miceal,
    Though I'm not sure, but see if Catalog repair and optimize helps resolve the issue.
    For doing this, click File >> Catalog and selec your catalog and then click "repair' button.
    Tick the checkbox for rebuilding indices in the repair workflow.
    Now perform the optimize operation on the catalog similarly.
    Let me know if that helps.
    Thanks
    andaleeb

  • Printing Problems with Elements 8.0 and EXIF time data

    I've been using Premiere Elements 8.0 in Windows XP Professional for a couple of years with no problems. I shoot mostly in JPEG. I've always imported my images using a card reader (the same one). About a year ago suddenly I ran into printing issues. When I imported my images and tried to print them Elements crashed just at the point where it should begin the actual printing.  By chance I discovered that if I adjusted the time EXIF on the images in Elements by either hours or days, back or forward and adjusted them back to the original time/date the problem disappeared. If I had shot in RAW and edited these images there were no problems with the resultant JPEG.
    I noted the discussions about Elements changing the time in the EXIF and checked for this but this hadn't happened. The EXIF in camera and in Elements were the same. I also checked this against the time settigs of the camera and they were the same. I shoot with a Nikon D300.
    I backed up my images and did a complete re-format of my computer so that it was back to its ex-factory settings, re-installed Elements, restored my catalog from the backup and the problem still arose. I'm reluctant to upgrade to Elements 10 until I (hopefully) I find out  if (a) anyone else has the same problem; and (b) if anyone who had it has fixed it.
    Any ideas would be very welcome.

    Miceal,
    I am confused. Do you mean Photoshop Elements? Premiere Elements does not have a Print function. On can Export/Share, but not Print. For Photoshop Elements, you will want the PSE Forum.
    Good luck,
    Hunt

  • EXIF date adjustment - how to adjust years?

    I was abroad some months ago, and made several hundreds of pictures. I also got pictures from my friend. It turns out his camera date was set (or perhaps wasn't set at all!) to 2030-10-12 01:30:00AM, while in reality it was 2006-09-09 10:30:00AM.
    My question is - how can I adjust year, month and date in EXIF headers? Because now I cannot auto rename files - I get wrong names based on EXIF info, I also cannot sort these files by date, because they are always at the end of the list, and do not merge with my images, as they should (based on real date/time).
    Is there anything I can do? Adjust Time Zone doesn't help here - that adjusts only few hours, but I need to change date in EXIF by several years...

    You could try "A Better Finder Attributes" - part of a great OS X utility:
    http://www.publicspace.net/ABetterFinderAttributes/index.html
    I believe you would have to do this BEFORE importing into Aperture, but its date options are quite nice.
    I use "A Better Finder Rename" to handle all my naming before importing, and I often have to tweek the date/time attributes as well. Funny how I always forget that when travelling!

  • ICM Server Time Adjustment

    Dear All,
    We have the Hosted IPCC 7.0 Setup, As we understand the time synchornized with the Domain Controller timing,
    When ever we would like to adjust the time 1 or 2 minutes difference we are getting the following error on the NAM router.
    Peripheral CVP_PG1_PIM5 (ID 5004) switched to half-hour 32 approximately 161 seconds before the central controller.
    Peripheral CVP_PG1_PIM2 (ID 5001) switched to half-hour 32 approximately 161 seconds before the central controller.
    We have understood that above mentioned peripheral (CVP Call Servers) timing got changed but none of the ICM machines timing affected.
    Due to this problem we are getting the above error. Any body experienced the same kind issue, Kindly share your experience / work around / best practise.
    Thanks in Advance.
    Manivannan

    If everything is set to sync their time to the domain, the best thing to do is to change the time on the DC, and let everything change on its own (which it seems you've done).
    The message you see is Informational, not necessarily an error.  It is just an indication that your ACD reporting may be slightly off vs. ICM reporting.
    As you see, the CVP boxes will change time 'immediately' when it gets a time change message from the domain.
    The ICM servers (rtrs, pgs, etc.) will not 'jump' their time ahead/back by the two minutes.  One of the functions of MDS on these servers is to manage ICM time.  ICM time will 'drift' faster or slower by 10% until MDS time matches the system (domain) time.  This is to prevent jumping backward/forward by such large increments.
    I.e. if you change your domain time by six minutes, it'll take an hour for ICM time to 'drift' and eventually match the domain time.
    IOW - the system is working as designed, and you really shouldn't do anything other than what you did.

  • EXIF time altered on conversion from PEF to DNG

    Converting Pentax PEF files from my *istDS to DNG using the Adobe DNG converter (4.1) results in the EXIF date/times all being shifted forward by six hours. I gather that the camera and the converter are miscommunicating regarding time zone. But the question is: short of running a batch operation to correct the times after the fact, what can be done about this to prevent this from happening in the future? I've also asked in the Pentax forums, in case someone there knows about any answers from the camera side of the equation.
    One workaround I've found is to generate XMP files for my images before running the converter. I have discovered that if the EXIF info is present in the XMP file - and ACDSee Pro 2 will do this for me by default as soon as I try to write copyright info or anything else to my PEF - then DNG will use that instead of the "real" EXIF info to populate the EXIF fields of the resulting DNG file. Actually, I'm kind of guessing it is still messing up the "real" EXIF version of the info in the DNG, but it is also reproducing the XMP version info, and ACDSee is using the latter, and that's probably good enough for now. Still, I'd prefer other alternatives.

    I still don't understand the issue *fully*. But examining my files with ExifTool, I see that the DNG converter is *not* in fact altering the EXIF info per se at all. What it is doing is adding an XMP block to the DNG file that contains a modified version of the DateTimeDigitized field. This modified version actually contains the time as shot, but it has the current time zone offset appended to it. That is, if the original EXIF dates read 09:00, and I am located in a time zone 6 hours behind GMT, the new DateTimeDigitized field created by the DNG Converter reads 09:00-06:00. Some applications will still display this as 9:00 AM, but others will display it as 3:00 PM - the GMT equivalent of 9:00 AM for folks in this time zone. In the case of the application I have been using (ACDSee Pro 2), if it sees time zone info on this field, it goes ahead and displays *all* times for the file in GMT, making it looks like the converter has modified more than it has.
    I don't know if the converter is wrong to append the current time zone offset, or if ACDSee (and, apparently, some other applications) are wrong to display the time in GMT. The folks are ACDSee are looking into whether and how they should change the behavior of their application. I would also suggest Adobe consider whether appending the time zone info from the computer on which the conversion is being run really makes sense (perhaps it could be made an optional behavior). But I am inclined to suspect the real problem is an overly-vague specification - there may be no definitively correct behavior here.
    So for me, this is enough understanding to feel like my workround is the way to go for me here. It actually suits my workflow better to generate XMP files before running the converter - it's the most convenient time for me to enter location information. Another workround would presumably be to run ExifTool to delete the XMP:DateTimeDigitized field immediately after running the converter.

  • Approval time for extension?

    A procedural rather than a technical question: Does anybody know how long it typically takes to hear back from Adobe after submitting a Dreamweaver extension to the Exchange?
    Thanks.

    I haven't submitted an extension for several years, but I seem to remember the approval process was lengthy. It took at least a couple of months to get an extension fully approved, although part of that time was taken up by needing to resubmit after I had made requested changes.

Maybe you are looking for

  • BPM sync to jdbc produces No receiver could be determined

    Hi, I am sending a sync select statement from BPM to JDBC adapter but I get the following error: No receiver could be determined. I checked in MONI and I can see the select statement, even the response but I get this error. I looked at the graphical

  • File opens in Reader, but prints with Acrobat

    Hi If I double click on a PDF file it opens in Reader. If I right click it and select 'print' it will attempt to print using Adobe Acrobat 5. I think Adobe Acrobat 5 is required for some old systems my company uses. How can I change default behaviour

  • Configuration files 2

    Im still a litlle confused. Let me explain We have an application which uses there types of configuration files: - default - dynamic - customer created What we know: Dynamic .cfg files are created by our application which can then be cached locally w

  • 6310i Locks up Exiting Text Editor

    I have 2 x 6310i both of which have shut down and will not restart. All I did was try and Exit Editor having successfully Forwarded an SMS. The phones turned themselves off and now when I go to turn them on they simply flash the screen a few times li

  • Confusing Packets Received vs. Packets Sent... Security breach?

    Hello, I want to know if the non-logical difference in bytes received and bytes sent is signaling a securty breach.  I controll my wireless connection very tightly; meaning, I only enable wireless when I am goint to use the internet wirlessly.  If I