Auto stack based on image similarity

Can you implement this in Lightroom 3 please?  Copy the implementation in Elements 8.  Having similar looking images stacked together would be extremely useful.

The same thing has been reported for the T410. You can see how to fix it here:
http://forums.lenovo.com/t5/T400-T500-and-newer-T-series/T410-unstable-screen-brightness/m-p/212492#...
It appears to occur anytime you are on battery and the intel graphics power plan is set to anything other than 'maximum performance.' It's pretty subtle, but really annoying when it happens.

Similar Messages

  • Auto-stack bracketed raw images?

    When I execute the auto-stack panorama / HDR command on a directory filled with exposure bracket groups intended for HDR processing, Bridge issues a warning message "Image is missing preview data" apparently for each and every image it inspects.  If I click through however many warning messages come up, eventually, the command properly stacks the raw images.
    I actually tried the build and export cache feature, exporting  a cache directly to the directory of raw images I wanted to stack.  That did not help.  Still get the same warning message over and over again.
    Can anyone help me with this issue?

    I actually tried the build and export cache feature, exporting  a cache directly to the directory of raw images I wanted to stack.  That did not help.  Still get the same warning message over and over again.
    Never used this before (I always first sort and rate my files manually) but tried it on a folder and first time had two of those messages (but there where a few other files- already fused using Photomatix- and some layered etc etc. that might have caused that). Then I tried it with a bunch of HDR and Panorama  files (already saved as tiff for use in Photomatix BTW) that I placed in a new folder. Now the result was better but to be honest not completely flawless, it left out 1 file out of 4 stacks from total 22 files.
    Then tried again on the folder before and this time no error messages but also a pretty lousy result I'm afraid. Some clearly 1 stop difference series of 6 shots divided in 2 stacks so I stick with my manual method
    However it might be a cache related problem for you. If you have one folder for testing first try a purge cache for folder using the menu tool / cache / purge cache for folder and try again

  • Better auto-stacker: based on camera mode

    Now automatick stack creation uses only time difference between frames. But many cameras record mode (single frame/continuous shooting) into EXIF, and this information can be used to create stacks (something like option "Stack only continuous shooting frames" option).
    Other useful option could be to stack only bracketed sequences of images. Many cameras record bracketing information to EXIF too.

    Use dbms_advisor.implement_task
    Thanks

  • Improve Auto-Stack and Process Collections with user settings

    I have read through all of the Bridge request discussions, and encountered a few comments on the stacking process but nothing to explain my critique and feature request. My apologies for any redundancy.
    Bridge CS4 includes two features that would (virtually) streamline my entire photo-organization workflow. Brilliant! Except that they offer zero configuration and my default scenario is very different from Adobe's, so these two would-be-wonderful features are pretty much useless to me, and to anybody else who doesn't happen to shoot in the way the presets are configured.
    The first feature is to automatically group images into stacks, based on their similarity, exposure settings, and timestamps. Unfortunately Bridge considers no minimum or maximum amount of photos per stack, and has a fixed timestamp window of 18 seconds. I shoot everything in three-exposure bursts and sometimes multiple shots in less than 18 seconds, so being able to say "process collections in 3-item stacks only" would be absolutely perfect. For other people, being able to limit the timestamp range or other min/max exposure options would work great.
    The second feature, which could save me hours every week but is equally useless, is to automatically process collections in Photoshop. My biggest ire about this function is that it completely ignores stacks that I have manually created AND stacks that were previously created using the auto-stack feature. Every time this function is run, it re-runs the auto-stack process from scratch and then delivers the collections to Photoshop. Not only is this made useless by the previously mentioned inflexibility of the auto-stack process, but even if auto-stack worked perfectly, this would waste time by doing the entire thing again and denying the user the option to review the stacks before committing to the Photoshop processing. The process collections feature would also be much improved if the option were given to process ONLY panoramas or HDR photos, or auto-detect. I have never shot a panorama in my life and I'm sure plenty of people have never shot HDR, but Photoshop isn't capable of knowing our intentions and there's no reason why we shouldn't be able to instruct it.

    Agree. It is an interesting capability that falls short of being really useful. I feel like an ingrate to complain, but ...
    I'd also like to see the capability to specify something than "Auto" for the panorama option. My experience is that most of my panos work best with "Cylindrical + Geometric Correction".
    My experience is that once you get past 5+ images in a pano, it becomes very tedious ... and then 20+ images in rows is painful. Unlike a single image that you can quickly evaluate, with panos I find I need to make the pano to tell if it going to turn out.  I have been generating smaller 1800x1200 or 1200x1800 files to speed up the evaluation process, but it is still very manual and tedious.
    The Auto-Stack generates a AutoCollectionCache.xml, but I haven't found it workable to edit this. I'd like to be able to modify it to "force" my knowledge of what is in a group. It seems to check the time-stamp, and re-do the Auto-Stack, thus ignoring my changes. Sigh.

  • 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.

  • Auto-stack Panorama/HDR question

    When I try to use the auto-stack command in a folder open in bridge I get a warning box stating "Image is missing preview data" for every image in the folder. Is there a way to get around this, the folders I would like to use it on have between 400-1000 images. Thanks

    Lightroom already has an  export option in the Library or Develop module's Photo>Edit In menu. Check it out - it's called Merge to Panorama in Photoshop. All you need do is select the relevent images then choose this command, Ps launches and you do the rest from there. A similar command exist for HDR.
    Edit: added screenshot

  • CS4 Bridge Auto stack tool makes my computer Crash

    I'm using a modern computer running Windows XP, 3 GB of memory , a modern video card with 1 GB of memory and the latest drivers, Photoshop CS 4 (with the latest updates), and the bridge auto-stack panorama/HDR doesn't work. When I click on the tool I get an error message that says "images missing preview data (then the image name) within okay box. This repeats on and on, until a file is created named "auto collection cash.XML). It would appear that the process is complete however this is not the case as bridge locked up and I can't access the stack. Closing and reopening bridge allows me to delete the XML file. I can then unstacked the images. Incidentally, if I manually select the files, I can successfully use either the panorama, or HDR tool, so it would appear that it's not a problem with the files themselves. If I use the auto stack tool on JPEG files it works. If I use it on any folder with raw files (in this case canon CR2), the 'images missing preview data" dialog box opens up.
    Recently, I worked with several Adobe support technicians, who came to the conclusion that I had a problem with my Windows user file, and not with Photoshop and bridge. I accepted this principle and created a new user account in Windows, I used the Adobe downloadable uninstall program (to clean out Photoshop and any registry entries). I then reinstalled Photoshop and re-created my preferences etc. and found that the auto stack tool worked fine. It's been about two weeks, and as you may imagine there is an ongoing development and improving of the Windows user file. Yesterday I found the auto stack lockup problem has returned.
    Can anyone suggest why I'm having this problem? I'm aware that I can repeat the above, but I'm concerned that it will not solve the problem long term. This auto stack tool could be very helpful, but I'm not sure it's worth all the time and effort to fix it only short-term.
    Michael

    Hello:  I notice that no one has replied to your post. That is a shame.  I am having the exact same problem that you described and it is happening in two different macs running the latest version of Leopard, OS 10. 5.8. I believe the problem is with Adobe  and not your operating system, or any corrupted files in your user files.   Have you had any luck solving your problem?  If so, please share it with me, as I think our problems are related.  Thank you, GuruDog

  • Auto-stack by name

    One feature that I feel is currently missing from Lightroom is the ability to *automatically* stack multiple versions of the same images when they are(/were) made outside of Lightroom. Usually, these versions are related to each other by their name. It would be convenient if there were an auto-stack function that would use the file names to determine which files to stack.
    Such a function could split the file names into a base name and a suffix, and stack all images with the same base name. Preferably, there should be a couple of ways to determine the base name:
    1) Use a user-definable suffix delimiter (for example '-').
    2) Use a fixed base name length (n characters).
    3) Use a pattern (such as 'P##??-', where # is any digit and ? is any character)
    I think this simple function would greatly improve the ease of use of stacks, especially when using Lightroom alongside other applications.
    Simon

    Yes, that sounds like a good idea. This could be easily implemented by dragging the 'stack by time' slider all the way to the left. Currently, this simply splits all stacks, like the 'unstack' command.
    The only (minor) disadvantage of this method would be images that have no, or inconsistent, time information, such as composites or JPGs with stripped headers. Despite this, stacking by identical date/time would certainly be a good start.

  • Auto Stack Freezes Program

    I have a Dual 2.5Ghz G5 with 7GB ram and a Nvidia 6800 Ultra video card - well over the recommended specs in everyway. I am having issues with Autostack being slow (hours) and/or hanging the program. I have tried importing 6900 medium sized jpegs (shot with a Nikon D2h) from a folder containing a older projects I am doing, which seems like it should be with within the capablities of the program with the hardware I am using. I will then select auto stack, and can move the slider slightly to adjust the time interval before the program gives me the spinning beachball, which it will then spend hours trying to process or will then freeze the program indefinitely (I let it go for 11 hours once) at which time I have to force quit it.
    I then tried it with a ancient project with jpegs from a Nikon Coolpix 950 which produced a averagew file size of less than a 1 Mb. I Auto-stacked 650 photos but still had the beach ball and it took about 10 minutes to complete- much longer than I expected with such small files.
    I have not tried RAW files yet.
    I hope somene has a answer on how I can possibly alleviate the problem, the auto stack is one of my favorite features so far when I can get it to work.
    Even with this problem I can say this program is awesome. It's very power hungry, but truly unlike anything I have used and a excellent 1.0 effort.
    Dual 2.5ghz G5   Mac OS X (10.4.3)  

    Maybe this is why in the training DVD supplied with Aperture Apple recommends using the auto stack feature at the time of import from memory card or camera. There's a slider at the bottom of the import page which, if memory serves me correctly, does the auto stack command. This way you'll be stacking only say 100 raw images from a 1gb card and the numbers won't get too taxing.
    Still, this should be a fairly simple fix for Apple to sort out so here's hoping they get on the case sharpish! I think the auto stack HUD is loading each individual image instead of just working with the attached data.
    Power Mac G5 dual 2ghz Mac OS X (10.4.3) 2.5GB RAM, 9800 Pro graphics

  • PSE wish list - Auto stacking RAW + JPGs

    I'm using PSE V10 and have a 'wish list' item for suggested improvements to the program.
    A feature that would be extremely valuable to many users would be the ability to auto stack photos where there are the RAW + JPG images present in the Catalog. The JPG would end up on top of the stack.
    This can be done manually but is tedious when there are many photos to deal with. Failing an automatic feature a single action shortcut to access the 'Stack | Stack selected photos' command would be useful.
    a forum discussion on this topic is here: http://forums.adobe.com/message/4585792#4585792

    As reported above I THOUGHT I'd found a shortcut suitable for stacking a JPG over a RAW.
    However, the stack command in the main menu, which has the shortcut Ctrl+Alt+S will stack the RAW over the JPG whenever the RAW thumbnail is ahead of the JPG in the Catalog. I want the reverse to happen.
    I found I can get the JPG to stack over a RAW, if the RAW appears before the JPG, by selecting the RAW first then with the Ctrl button down select the JPG. Then using 'Stack | Stack selected photos' in the mouse right click menu. However, this fails when using Ctrl+Alt+S whenever the RAW is listed before the JPG. Am I missing something?

  • CS6 Bridge "Auto-Stack" question

    As a landscape photographer I shoot multiple exposures of the same image for use in HDR.  I recently used the Auto-Stack feature under Stacks in Bridge.  It did not work well, it grouped the images incorrectly.  Now I want to undo this and go back to the basic panel where all the images are shown in sequence.  How do I do this?  I have tried to purge this file, restarted Bridge but always shows it with stacks.  Any help is appreciated.  Thanks.

    Don't have Bridge active for the moment but in the same menu as you found autostacks there is an option to unstack all from groups. You probably have to select all files first. After unstack all you can use the sort filter date created to getbthem again in the right order.
    Regards
    Sent from my iPad

  • Importing from camera, auto-stack doesn't work

    Hi all,
    I've been using aperture for a while now. According to the manual Aperture should be able to do an auto-stack to the imported pictures and I can see the interval seconds slider on the import page. My camera is Canon 5d and I'm importing raw pictures.
    My problem is that if I touch the slider, it creates one huge stack of all the images on the camera memory card. So if it does an autostack, it treats all images as if they'd been shot at the exact same second. This is illustrated also if I tell aperture to sort the not yet imported pictures according to shooting time. They just appear in a random order after that.
    When the pictures have been imported, there is a correct shooting time/date in the EXIF information of the pictures. I'm not even sure if this is an aperture problem or a camera setting problem. When I look at the pictures on the camera screen, I can see the correct shooting time even in there.
    Any ideas?
    /hv

    Not sure if this would make a difference, but are you importing the photos directly from the camera or are you using a card reader with your memory card?

  • Auto-stack doesn't work

    I am new to Aperture and am exploring all of it's features. Unfortunately I cannot get auto-stack to work. I have a project with 900 pictures. When I slide the auto-stack slider to the right, I get a spinning ball. After a minute it looks like the images have been stacked. When I close the auto-stack HUD, all the stacking disappears again. Am I doing something wrong here? I do not think it has to to wit my MBP. It has to be fast enough.

    Not sure if this would make a difference, but are you importing the photos directly from the camera or are you using a card reader with your memory card?

  • 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)

  • Auto-stack hanging up machine?

    Hello,
    I'm trying to use the 'auto-stack' feature. Unfortunately, every time I try to use it, it seems to hang Aperture for a very long time. I'm wondering why this is, as I'm using a Quad G5 with a 7800GT graphics card & 4Gb ECC memory. (The project I'm trying to stack has only 1100 images.)

    I started over. I deleted all 20,000 photos, and began importing folders one at a time, working from 2005 backwards. This time, rather than having top level folders = projects and subfolder = albums, I made every subfolder its own project. This kept every project under a few hundred photos.
    Autostacking both in the import tool and after import remained lightning fast.
    Around mid 2002, I had a single folder with 600 images. I carelessly imported it, and ...
    Ooops!
    Autostacking anywhere including projects that had worked moments before now gives the spinning beachball. Projects with ~30 photos which I've been restacking every so often during this process to see what happens, suddenly take 120 seconds to restack.
    On startup, Aperture says 64 projects, 7,269 items not stored in vault. In the library, I find 5,796 images if I open all stacks, 2,246 if stacks are closed.
    Have I crossed a total image threshhold? Or was it having a single project with 679 images?
    I dunno, but it's not the Quad G5, since from the delete-all until this latest folder was imported, everything was screaming.
    G5 Quad   Mac OS X (10.4.3)   6.5 GB RAM / CD 30" / Aperture

Maybe you are looking for