Auto-stack by capture time not correct

Hi,
I have 28 photographs taken sequentialy but not at same intervals; they are part of a collection. I proceed to select all of them and choose "Stacking-Auto stack by capture time..." from the context menu and choose time between stacks as 0:01:00 (one minute)
However I find the capture time of photos in any one stack exceed 1 minute!!  For instance, these are the capture times of photos in a single stack:
     8:19:12PM, 8:19:25PM, 8:19:43PM, 8:20:24PM, 8:21:19PM, 8:21:45PM
We can clearly see that the capture times between members of this stack are not within 1 minute. What can is happening?
Thanks,
Juan Dent

However I find the capture time of photos in any one stack exceed 1 minute!!  For instance, these are the capture times of photos in a single stack:
     8:19:12PM, 8:19:25PM, 8:19:43PM, 8:20:24PM, 8:21:19PM, 8:21:45PM
This is a maximum interval setting.  It has nothing to do with the total timespan of the whole sequence. Just, how closely-spaced the individual shots  were. These were less than half a minute apart.
IOW: how long can pass between one shot and the following one, before that is no longer considered to be part of the same continuing sequence.
RP

Similar Messages

  • Auto-stack by capture time messed up my stacks

    After manually creating many dozens, perhaps a hundred stacks, I tried the Auto-stack by Capture Time feature.  Now my stacks are totally messed up; I either have way too many or none.  Is there any way to get back to where I was except by reverting to an earlier saved version of the catalog?

    However I find the capture time of photos in any one stack exceed 1 minute!!  For instance, these are the capture times of photos in a single stack:
         8:19:12PM, 8:19:25PM, 8:19:43PM, 8:20:24PM, 8:21:19PM, 8:21:45PM
    This is a maximum interval setting.  It has nothing to do with the total timespan of the whole sequence. Just, how closely-spaced the individual shots  were. These were less than half a minute apart.
    IOW: how long can pass between one shot and the following one, before that is no longer considered to be part of the same continuing sequence.
    RP

  • Auto-Stack by Capture Time: results don't match selected interval

    I selected a collection of 2075 images in Grid mode, and invoked Auto-Stack by Capture Time, with "Time Between Stacks" set to 0:10:00. This resulted in all images being grouped into 7 stacks -- but the difference in capture time between one stack and the next stack was only a couple of seconds.
    I then changed the interval to 0:20:00, and repeated the Auto-Stack command. This resulted in all images being grouped into 4 stacks -- and again, the difference in capture time between one stack and the next stack was only a couple of seconds.

    Thanks Bob for that very fast reply!
    But neither "Modifying hal configuration" nor "Using the Desktop Environment settings" (xfce) worked. So I tried the "I don't want this crap, how do I turn it off?" solution and well it works
    Maybe I turn it back on in a month or so.. but for now i'm fine with no hot plugging but a working keyboard...
    Thanks and Bye!
    smax
    Last edited by smaxer (2008-12-09 17:42:43)

  • Intelligent Auto-Stack by burst Time?

    Hi,
    I'm just back from a dawn shoot by the sea where I was using auto-bracketing. Have hundreds of shots as each moment gives different reflections, blurry movements of boats, and people (late partygoers, early fishermen ;-) etc, I had lots of ND etc in use to get really silky water ... the result?
    Lots of small groups of shots (3 at a time) that are spread over a lot of time, and the existing auto-stack is reasonably useless. But, they were taken with high-speed drive on, and so I know there is only fractions of a second BETWEEN the shots - please can you give us an option to auto-stack by the time *between* the shots? You have the start time of a shot, and the length of a shot (shutter speed), so you  could compute the gap between them just as easily as just looking at the start time.
    This would allow me to stack by (say) 1/4 second which would catch all of my groups of shots perfectly, even though some shots in a group are 15s long
    And, at a sporting event, I could auto-stack my shots by each burst of the shutter, no longer how long, and still get seperate stacks for bursts taken even half a second apart!
    Ppppppplllllleeeeeaaaaassssseeeeeee ................

    However I find the capture time of photos in any one stack exceed 1 minute!!  For instance, these are the capture times of photos in a single stack:
         8:19:12PM, 8:19:25PM, 8:19:43PM, 8:20:24PM, 8:21:19PM, 8:21:45PM
    This is a maximum interval setting.  It has nothing to do with the total timespan of the whole sequence. Just, how closely-spaced the individual shots  were. These were less than half a minute apart.
    IOW: how long can pass between one shot and the following one, before that is no longer considered to be part of the same continuing sequence.
    RP

  • Edit Capture Time - not working?

    I recently updated my Lightroom to LR 5.3, and since then, I haven't been able to edit the Capture Time on my images. I select METADATA --> Edit Capture Time. This used to bring up another dialog box - now it does nothing. I'm in Library, Grid view. Any suggestions? Is this a problem with this version?
    (side note: when I went to Help, About Adobe Lightroom - to get my current software version, it randomly said "applying preset" to all my images and never brought up a dialog box with the version number. When I did it again, same thing. ??)

    Dorin: I know that the Capture Time/Date in the files themselves are not changing because I check the metadata by looking at the files in Finder, and in Photoshop (View > File Browser and File > File Info).
    No, the file modification date does not change when I do Edit Capture Time, but it
    b does
    change when I do Save to Metadata (but only in the NEF, not in the JPG).
    In LR's Library Module > Metadata palette > EXIF section, all 3 of those date/time fields
    b do
    change per my Edit Capture Time (
    b not
    just the 1st and 3rd fields that you mentioned), all the while no changes on the files themselves (as I've described).
    Supposedly, if "Write date or time changes into proprietary raw files" is selected in Catalog Settings > Metadata > EXIF, then running Metadata > Edit Capture Time
    b should
    change the files to show the corrected Date/Time in the file itself (and thus show up as corrected no matter what app you're viewing it from). This is supposed to be the case, whether the file is a proprietary raw file, jpg, or otherwise. But it ain't happening!

  • Video capture time not present

    In LR 4 beta, I can't find the capture time of videos that I have taken. The time doesn't appear in grid view, when I hover over the image, or in the EXIF data. The videos all show, in grid view, a capture time of 12/31/1979 11:00:00 PM. Am I doing something wrong to hide this information? I know it's there someplace because when I export videos and use YYYYMMDD in the file naming template, the correct date (and time with the time templates included) is written in the file name. Thanks.
               Dilip

    I think there are two long-standing issues causing your symptoms:
    - LR doesn't read video metadata, including capture time.
    - LR behaves quite inconsistently with images and videos for which it doesn't have an explicit capture time, sometimes using the file's date-created and sometimes using date-modified:
    http://feedback.photoshop.com/photoshop_family/topics/inconsistent_dates_for_files_missing _date_time_metadata
    I suggest adding your comments and vote to that thread in the feedback forum (the feedback forum is where Adobe wants product feedback and bugs reported).

  • "Sort: Capture Time" not working in LR 5.2

    I just imported a bunch of photos & videos from my cell phone into LR 5.2.  I noticed that all the .JPGs are at the top of the grid view while all the .MP4s are at the bottom.  They should be interspersed in the grid view because that is the order that I took the photos & videos  AND I have "Sort: Capture Time" selected.  This looks like a bug to me unless someone can tell me what I am doing wrong.

    See my response in the feedback forum:
    http://feedback.photoshop.com/photoshop_family/topics/lr_5_2_sort_capture_time_not_working

  • Outlook 2007 syncing issues. Time not correct.

    I setup a reoccuring appointment on my iPhone for every saturday 8:00PM to 9:00PM through August. When I synced through iTunes, the appointment appeared in Outlook through August, but set to 4:00pm to 5:00pm. Four hours off. I added another test event in Outlook from 8:00pm to 9:00pm and then synced back to the iphone, it showed up as 12:00am to 1:00am.
    Both are set to EST (the iPhone set to Boston, USA)...
    Any ideas?

    I had a similar experience when I saw several older meetings that were previously setup in Outlook 2007, that had originated from an Exchange server.
    These meetings did not appear correctly on my Palm Treo 680, which is what I have upgraded from (to iPhone). These Exchange-originated meetings never synced properly to my Treo 680 - always came over many hours off of the correct meeting time, though on the correct day.
    When I first synced Outlook '07 to my new iPhone the meeting on the iPhone was wrong as well. However, I then modified the meeting on the iPhone and re-synced and (unlike the Treo 680) the meeting is now correct in both places.
    So, I am happy with iPhone.
    I am holding my breath however for my next business trip to another time zone. For some reason Palm could not get this to work correctly on the Treo.
    iPhone    

  • Oracle Queries - Time not correct

    When we execute an Oracle query from MII all fields with an Oracle datatype of DATE are not displaying correctly.  The date (MM/DD/YYYY) is fine, but the time portion is displaying as all 0's (00:00:00).  Does anyone have any ideas of how to correct this?  I have verified the data in the source Oracle database and the data does include times.  Thanks.

    SELECT SYSDATE FROM DUAL gives me 2011-01-17T00:00:00
    Then,
    select * from 
    (SELECT * FROM EVENT_LOG ORDER BY  EVENTTIMESTAMP DESC)
    where ROWNUM <= 1
    returns
    EVENTID EVENTTIMESTAMP EVENTDESCRIPTION EVENTSEVERITY
    881458.00 01/17/2011 16:04:45 PMU OK ROUTINE
    The ojdbc14.jar driver works ok with oracle timestamp fields. Usually I convert all dates to timestamp (as below) and the jdbc driver and/or oracle client on the MII box adapts even to different timezones (i.e. it knows that the client is -3h if the database in EST timezone and the MII box/client is in PST timezone).
    The following deletes everything from the logs older than 3 months (as related to the date.time.milis when I run it).
    DELETE FROM  EVENT_LOG WHERE EVENT_LOG.EVENTTIMESTAMP <= to_timestamp(ADD_MONTHS(SYSDATE,-3))
    short answer .. try to_timestamp() applied on your date fields on the Oracle side, why is this considered drastic?

  • 6500S SMS RECIEVING TIME NOT CORRECT

    Hey, I've prob with my recieving time. when I got a message from my country(macedonia) it shows me that I recieve it 1 h earlier, but when I recieve it message from another country(usa) it shows the correct time. I tryed to set the gmt and daylight saving but I can't set correct (if I set it correct for macedonia it's wrong for usa and backwards). My phone is now gmt: 00, and daylight saving:00. I read here that many people have this prob and tell me if you solved it.
    Very annoying.
    please help

    Hi deko_mac
    You might like to look at this post by adamf; although this applicable to British Summer Time(BST) which is one hour ahead of Greenwich Mean Time(GMT):
    /discussions/board/message?board.id=connectivity&m​essage.id=18595#M18595
    Message Edited by scoobyman on 23-Sep-2008 05:30 PM
    Happy to have helped forum in a small way with a Support Ratio = 37.0

  • Ical time not correct when viewing published version

    I have struggled with this problem for a while now. When I view my published calandar, it is out by +8 hours. 9AM appointments show as 5PM appointment on the same day.
    I have done the following:
    1. Made sure I am GMT on my system preferences
    2. Checked that time zone support is swithced on in iCal
    3. Made sure Dot Mac has me registered as GMT
    On the web version of my calander is actually says the time zone is Europe/London, which is the correct one for me. I'm really at a loss.
    Can someone/anyone help with this?

    I'm having exactly the same problem.
    iCal & my Blackberry are OK, but when I publish it goes wrong - even though I have the timezones set for London. I've tried unpublishing and repuplishing, but to no avail.
    This is a major problem for me - any ideas on whot to do?

  • Lr no longer sorting images by capture time

    Good afternoon,
    I've been using Adobe Lightroom 2 with Photoshop CS4 without any problems.
    However, recently I've been having problems with the order in which LR is storing my images.
    I work in Raw and always start from LR. From there I open my image in Photoshop before making any adjustments and then saving as a 16bit PSd or Tiff.
    On the first save the psd/tiff file is stored as normal in LR - i.e next to the original raw and virtual copy. But now, when I return to make any alterations in Photoshop the re-saved psd file is moved to the very beginning of the Lightroom library. The box around the image is blacked out and against it it has a message '2 of 0' and the phrase 'photo is part of a stack'.
    I don't understand why it's doing this and I don't use stacks purposely. I just want my images all on display, next to each other for ease of use.
    All my photos are sorted by capture time and even though the files in question are of the correct time it still doesn't stop Lightroom from placing it at the top, well away from where it ought to be.
    It's not a massive issue but it is quite annoying when you have thousands of images in your catalogue, and it's never done it before. I've restored LR to the default settings but it hasn't made any difference.
    Please can anyone help.

    Thank you very much.
    I tried as suggested
    > Stacking> Auto Stack By Capture Time
    and that moved the psd file back into line.
    I've tried opening up a few of the psd files into Photoshop and re-saving and so far so good! They're still alongside the original raw files.
    The strange thing is that the sort order is/was set to capture date so I don't know why it moved it in the first place.
    Thank you again. Much appreciated.

  • Aperture not reading EXIF Image Capture time properly

    Hi
    I have recently imported a folder of Raw/JPEG files into Aperture as a new project.  They previously had been managed in Media Pro.  When I sorted the images by date, I found that some (but not all) Raw files didn't have the image capture time recognised.  I.e. the image date time was shown as 'Date X time 00:00:00'.  These are Olympus ORF files (from the E-M5 and XZ-1.  The JPEG files are properly date-stamped.
    I have tried to alter the image date/time as per the Metadata menu command.  However, although looks like it is doing the job, when next I open the library there is no change to the information and the image is still sorted in the wrong place if I sort by image date.
    The wierd thing is that the capture time is correctly shown in the image EXIF (I can see it in EXIF Editor, Olympus Viewer and in Media Pro), but that it isn't being seen by Aperture or OS X properly.  Something somewhere has obviously got muddled.  Any ideas on how this can be sorted out?  It has been driving me mad trying to sort this out!
    Andrew

    Here is another example of this effect, but with a different type of subject matter: a ball. The original is a raw file from a Canon 350D/Digital Rebel.
    In Aperture's Zoom mode there is a pattern on the ball that looks like Maze Craze:
    The pattern is maintained to a lesser degree as the image is sized down:
    Exported as Original Size png:
    Exported as Half Size png:
    Now, as pointed out in the earlier post, the real problem is that other apps do not have this problem. The following is from ACR:
    Aside from the pattern, Aperture does look better, but the pattern is nasty and almost makes the image unusable.
    Will
    Dual Core 2.3GHz PowerMac G5, 2GB RAM, GeForce 6600   Mac OS X (10.4.6)   Canon Digital Rebel XT, Edirol UA-5
    Dual Core 2.3GHz PowerMac G5, 2GB RAM, GeForce 6600   Mac OS X (10.4.6)   Canon Digital Rebel XT, Edirol UA-5
    Dual Core 2.3GHz PowerMac G5, 2GB RAM, GeForce 6600   Mac OS X (10.4.6)   Canon Digital Rebel XT, Edirol UA-5

  • Edit Capture Time XMP vs. EXIF

    Scope:
    - LR 1.4.1 and 2 Beta
    - Any file that is edited using Metadata:Edit Capture Time
    (Note: detail info below may be helpful to those seeking to understand date/time problems/issues with LR and other tools)
    Background:
    LR allows editing/offsetting of image capture time via the Metadata:Edit Capture Time menu option.
    Changing the time in LR alters the following EXIF date/time metadata fields as displayed in LR:
    - Date Time Original
    - Date Time Digitized
    - Date Time
    Writing the LR metadata to the image file via the Metadata:Save Metadata to File command writes the values into the images relevant EXIF and XMP date/time metadata fields.
    Challenge:
    LR writes the correctly edited times into the XMP date/time metadata fields but writes incorrect times into the EXIF date/time metadata fields.
    LR uses XMP date/time metadata fields for its displayed time data, not EXIF date/time metadata fields. As a consequence, the user does not know the EXIF time fields have been incorrectly changed unless they check them in a tool that displays or uses the EXIF date/time metadata fields.
    Solution:
    Use a batch file based on exiftools to copy the LR edited XMP date/times into the EXIF date/time metadata fields.
    Resources:
    - Batch file LR XMP/EXIF date/time bug fixer here - LR-xmpdatetime2exif.bat: http://www.hackneys.com/photos/lr/LR-datetimexmp2exif.bat
    - Batch file arguments file (required) here LR-xmpdatetime2exif.args: http://www.hackneys.com/photos/lr/LR-datetimexmp2exif.args
    A few useful tools to better understand this challenge:
    - Batch file to display relevant date/time metadata fields here - list-exif-tags-sample-datetime.bat: http://www.hackneys.com/photos/lr/list-exif-tags-sample-datetime.bat
    - Batch file to display set of EXIF metadata here - list-exif-tags-sample.bat: http://www.hackneys.com/photos/lr/list-exif-tags-sample.bat
    - Batch file to display set of XMP metadata here - list-xmp-tags-sample.bat: http://www.hackneys.com/photos/lr/list-xmp-tags-sample.bat
    - Batch file to display complete set of metadata here- list-metadata-tags-sample.bat: http://www.hackneys.com/photos/lr/list-metadata-tags-sample.bat
    - Sample photo file here sample.jpg: http://www.hackneys.com/photos/lr/sample.jpg
    Preparation:
    All batch files require an installed copy of exiftools by Phil Harvey (free) available here: http://www.sno.phy.queensu.ca/~phil/exiftool/
    1. Download exiftools windows command line version and rename the file exiftools.exe.
    2. Place the exiftools.exe file in your windows directory or on your system path.
    Utilization
    1. In Lightroom, select the folder containing the photos you need to fix.
    2. In Lightroom, select all the photos you need to fix.
    3. In Lightroom, select Metadata:Save Metadata to File (this step ensures you dont lose any Lightroom specific metadata that has not been embedded in the file).
    4. Using Windows Explorer or another utility, backup your jpg files
    5. Using Windows Explorer copy the LR-xmpdatetime2exif.bat and LR-xmpdatetime2exif.args files to the folder with the jpg files you need to fix.
    6. Using Windows Explorer double click on LR-xmpdatetime2exif.bat
    7. Wait for the batch file to process.
    8. In Lightroom, ensure the photos you just fixed are still selected, if not, re-select them.
    9. In Lightroom, select Metadata:Read Metadata from File (this step ensures that Lightroom has all the revised EXIF date/time metadata loaded).
    Detail:
    This challenge is a subset and another manifestation that LR 1.4 uses the XMP date/time metadata fields, not the EXIF date/time metadata fields that other programs use and rely on. There have been numerous posts regarding other manifestations of this problem.
    Most of the confusion relates to several primary factors:
    1. Cameras embed EXIF metadata into photo files. Adobe products, and some others, support XMP metadata, which is not part of the EXIF standard. If a tool was developed p

    Detail:
    This challenge is a subset and another manifestation that LR 1.4 uses the XMP time data fields, not the EXIF fields that other programs use and rely on. There have been numerous posts regarding other manifestations of this problem.
    Most of the confusion relates to several primary factors:
    1. Cameras embed EXIF metadata into photo files. Adobe products, and some others, support XMP metadata, which is not part of the EXIF standard. If a tool was developed prior to XMP, such as Exifer or PSP 9, then that tool has no way to view or edit XMP metadata. If a tool only displays, edits and maintains XMP, such as LR, then the two data sets can become de-coupled for common data points, such as date/time. If a tool relies on the EXIF version of a common data point, such as RoboGEO, but the date/time was edited by a tool that only maintains XMP data, such as LR, then the EXIF dependent tool will be working with out of synch data.
    2. LR, PSE, Bridge, etc. use, either exclusively or primarily, XMP metadata, even though they may label/display it as EXIF. LR, for instance, only displays the XMP date/time values, even though they are labeled EXIF.
    3. The EXIF specification assigns time field names different than those commonly used in various tools when labeling/displaying EXIF time data fields. You will find the very same EXIF date/time field labeled a wide variety of ways in even a handful of tools.
    4. The XMP specification has a namespace area labeled EXIF. Adding to the confusion even more, the XMP-EXIF namespace has date/time field names that duplicate those of EXIF date/time fields.
    As you can see, if you add these four factors together, it is no surprise there is widespread confusion related to photo file date/time in general and LRs handling of it in particular.

  • Auto-stack on import in Aperture 3?

    My recollection of the Aperture 2 trial was that I could choose to auto-stack, based on times, while importing images. I can't seem to find the option to do that in Aperture 3. Once the images have been imported into a project, I can then have them auto-stacked, but they don't seem to come in that way.
    Am I missing something obvious in Aperture 3? Did I hallucinate this feature in Aperture 2?

    I've found a way to do it, but it's not as intuitive as it was in Ap2.
    The box that shows which images will be imported now as a little check-box by it, and they all start ticked, by default. You have buttons, up top, to check all, or uncheck all. And the button down in the lower right is now labelled "Import Checked," when I think on used to have the option to "Import All" or "Import Selected" (after you'd done normal style multiple selection on the files).
    There's an auto-stack dialogue, that you can access at any time from the stacks menu, but you can't actually move the slider unless images are selected. So, on import, do a command-A to select all (as opposed to the check all that's done by default), and then open the auto-stack dialogue and set your time, and you can see how things will stack. Then, press "Import Checked" (assuming they're all still checked), and the images will come in, and already be stacked as they were at the source. So, it's available, but nowhere near as friendly to use as it was.

Maybe you are looking for

  • Can't swipe between months with gestures in iCal since I updated to Maverick.

    I used to be able to use two fingers in ical to move forward to the next month. Or vice versa swipe back to get to the previous month. Since I updated this gesture will not work. What am I missing? Thank you for any support. Not a huge deal just anno

  • Bought a Skype phone but it doesn't work. How do I...

    I bought a Skype telephone through internet from the 'Skype shop'. I tried to install it but it doesn't work. Someone else tried to install it too - someone used to those things - but it does not work. I need to send it back to Skype but how do I go

  • Any similar transaction in PM/CS like CO1P in PP

    Hi, This is just for clarification. We have CO1P transaction(Predefined Confirmation processes) in PP and as like that do we have any similar transaction in service/maintenance order confirmation. As I know we have only IW46,COGI and COFC for post pr

  • FM for checking Available Capacity of Work Center

    Dear All, I have trying to find a Function Module to get the latest available date of the Work Center (The Period where no Production Orders has been dispatched to it).  It is only when the Work Center is available then we can dispatch the Production

  • Not enough disk space for asset ecoding

    Hi all, I have a dvdsp project with: a feature: 3.3 gb dvd extra: 289 menu assets: 65mb and shows that it is 3.8 mb all together, but when i try to build/format it stops the build at the menu and gives the error message: Not enough disk space for ass