Images stuck in Auto Import

Two images files  I was working on are stuck in Auto import into iphoto. They will not import into iphoto nor can I delete them. Everytime I try to use Adobe or iphoto it try's to import. Any help would be very welcome

To get rid of them you will need to find that auto import folder and delete them. If you search for the name in spotlight, then do Show All, when you click on a name you should see the file path to it at the bottom of the finder window, like this:
If you double click the name of the enclosing folder it will open and you can see the file to delete it. In my example if I want to get rid of roykitchen.jpg, double clicking the roykitchen folder name will show it to me.

Similar Messages

  • Custom Image Capture that Auto Imports the OS WIM and Creates a New Task Sequence

    We just finished a consulting project where our customer requested an easy solution to capture thick images.  After hearing their reasoning it made sense for their circumstances.  The people that
    will be managing the system will be non-technical and all they wanted was a very, very simple method of capturing and deploying images with no learning curve.   They wanted the ability to Deploy the images via PXE.  
    This quickly became both our easiest scope project but making MDT simple for non-technical users can be challenging.   The MDT capture and staging steps are pretty easy for tech savvy person but for non-technical people it presented a learning
    curve that the customer wanted simplified. They didn’t want to understand sysprep, capture, importing an OS and then creating a Task Sequence to reference that new image.        
    So we changed the scope of our project to automate MDT to perform additional steps following the capture that would:
    Automatically Import the Captured OS into the MDT Deployment Share
    Automatically Create a new Task Sequence that references the newly imported image
    Auto Name the Task Sequence with the Model Name, Date and Time of Capture
    The Final Solution:
    Customer will setup a Windows PC Thick Image (All software and drivers)
    The customer will Kick-off the Sysprep and Capture Task Sequence
    The customized Task Sequence will capture, import the new image, and create a new TS with the new image
    Customer can then PXE boot a new computer and Deploy the image or stage to media and deploy the image
    We were able to remove the import OS and create new task sequence steps and this simplified it for our customer considerably.  If anyone is interested in this functionality
    let me know and I can send you instructions.  We used Vbscript, Powershell and PSExec.exe from PowerShell.  It seems to being working pretty good so far
    MDT Task Sequence Duplicator https://panaconsulting.egnyte.com/h-s/20130614/61707be809944999 Application Bundle Duplicator https://panaconsulting.egnyte.com/h-s/20130614/405e7d64e5d54610

    We just finished a consulting project where our customer requested an easy solution to capture thick images.  After hearing their reasoning it made sense for their circumstances.  The people that
    will be managing the system will be non-technical and all they wanted was a very, very simple method of capturing and deploying images with no learning curve.   They wanted the ability to Deploy the images via PXE.  
    This quickly became both our easiest scope project but making MDT simple for non-technical users can be challenging.   The MDT capture and staging steps are pretty easy for tech savvy person but for non-technical people it presented a learning
    curve that the customer wanted simplified. They didn’t want to understand sysprep, capture, importing an OS and then creating a Task Sequence to reference that new image.        
    So we changed the scope of our project to automate MDT to perform additional steps following the capture that would:
    Automatically Import the Captured OS into the MDT Deployment Share
    Automatically Create a new Task Sequence that references the newly imported image
    Auto Name the Task Sequence with the Model Name, Date and Time of Capture
    The Final Solution:
    Customer will setup a Windows PC Thick Image (All software and drivers)
    The customer will Kick-off the Sysprep and Capture Task Sequence
    The customized Task Sequence will capture, import the new image, and create a new TS with the new image
    Customer can then PXE boot a new computer and Deploy the image or stage to media and deploy the image
    We were able to remove the import OS and create new task sequence steps and this simplified it for our customer considerably.  If anyone is interested in this functionality
    let me know and I can send you instructions.  We used Vbscript, Powershell and PSExec.exe from PowerShell.  It seems to being working pretty good so far
    MDT Task Sequence Duplicator https://panaconsulting.egnyte.com/h-s/20130614/61707be809944999 Application Bundle Duplicator https://panaconsulting.egnyte.com/h-s/20130614/405e7d64e5d54610
    I would love to get the instructions to this process, as I have a simular client.

  • Improve auto-import for tethered capture...

    Simply add an option to have new images automatically inherit the develop settings of the previous image (all settings including crop).
    Currently, when shooting tethered, I capture and adjust an image - but before I can go back to camera I need to create a new develop preset and point to it in auto-import settings (simply re-saviing the current preset doesn't work). However, this doesn't consistently hold the crop -- and so much commercial work is shot to a specific layout or proportion. Instead, I rely on the previous and/or sync function. Ideally, there would be a way to know that the new images would easily auto import with the same look as previous photos.
    Thanks,
    Andy

    This would be more readily solved by adding crop to develop presets, which is useful for other purposes also.

  • Lightroom 2.1 Auto Import problem

    Everything works fine with Auto Import except when an image arrives in LR so does the Import Dialog Window and I have to click it away with every shot. I am in the Library Loup View in the Fit mode. This happens weather the Import preferences has "Show import dialog when a memory card is detected" checked or not. I have checked with NAPP and they have no answer. I have Win XP 64bit.
    Thanks, Tom

    Hi Josh,
    I just had a friend help me out to solve my problem. I use Canon. Within the Canon software under preferences, there is a tab called Linked Software. In the drop down window I had choosen Lightroom. It turns out this should be None. With Lightroom choosen the Canon software is telling Lightroom to open and causes the Import dialog window to open.
    Hope this is your problem also.
    Tom

  • Auto Import - Is only ONE watch folder allowed across several catalogs?

    I am looking to confrim that Lightroom v4.4 only allows for one watch folder to be set up under File>Auto Import and therefore I cannot set up a differnet watch folder for each of my multiple catalogs.
    I represent several artists and need to manage their image database separately and thought I would be able to auto import from a folder they drop images to; But now I realize Lightroom may only allow one watch folder overall because when I open a catalog I notice the watch folder is set to what I selected when the previous catalog was being used.
    Is their a way to have each catalog watching a folder unique to it or is only one watch folder possible?
    Thanks in advance for the answer and any solutions.

    Yes - watched folder is handled as Lightroom preference, not catalog preference...
    For greater flexibility you'll need a plugin. Consider:
    * jf Folder Watch
    * rc Ottomanic Importer
    Rob

  • LR doesn't auto import Jpegs after editing in PS

    I have searched the internet and cannot find an answer for this.  When I am in LR and right click and choose to edit in photoshop, then retouch it and then save as a jpeg, LR does not automatically import the jpeg into the catalog.   So I synchronize the folder and it imports them in but then won't put by the original, even when I sort by name.  I want this to be automatic.  It was on my older version of LR but the new one I downloaded doesn't do it automatically and I can't figure out how to auto import the jpegs.
    I am not tech saavy so go easy on me.

    Ah, I think I have it figured out. My Canon software was also setup to push the image into LR as a registered application. With that disabled the auto import seems to be doing what I want. For anyone reading this later... Simply set the current image view to the preview size you want and all the imported images should open up at that preview size.

  • Include mask overlay with Auto Import preset.

    It would be nice to automatically show an overlay mask in the picture as you Auto Import it via the Watched folder.
    Most of the digital back software have this mask overlay posssibility.
    All it does is it obscures the area you don't want to see (a bit like the crop tool, with adjustable black opacities, but without actually cropping the image).
    The reasoning behind this is that you often need to take pictures with plenty of surrounding space in your layout, for instance, blank space to the right of left of the image for putting text, or to allow for multiple output formats, but at the time of viewing, you just want to concentrate on the masked area, free from distractions.
    Art directors are always asking for this: "What would it look like when it's cropped?" You can go to the crop tool and show them, but it would be better and quicker to have an auto import overlay mask which you can flick on and off.
    Edward

    Sounds like another use for TPI's. Transparent PNG Images (Id Plates) that only have limited use and one at a time, now. Currently only usable in Slideshow and Print.
    See TPI's at Downloads
    Lightroom Extra. We have been asking for expanded use of TPI's (which can be used for Framing and Watermarking) in Export and Web and now you have presented one more potential use bringing the need for there expanded capabilities even more to the fore.
    Don
    Don Ricklin, MacBook 1.83Ghz Duo 2 Core running 10.4.9 & Win XP, Pentax *ist D
    http://donricklin.blogspot.com/

  • Auto Importing in Aperture

    I would love to shoot tethered with my Nikon D3 and have images go directly into Aperture.  I realize Aperture has a tethering feature, but my clients have become spoiled by Live View and being able to see small changes on the screen before pressing the button.  So is there any way to shoot with Nikon Camera Control Pro and direct files to a folder where Aperture would automatically import them?  I just read instructions on setting it up for LightRoom w/ auto import, but I don't use Light Room ;-)

    Adding to Frank's spot-on instructions:  I settled on having a dedicated Finder folder on my system drive, and a dedicated Project in Aperture.  This should give you a base to vary to your needs.  The Finder folder is named "To Hot Upload to Aperture". It can be anywhere on your system.  The Project is "_Hot Uploads".  (The underscore forces it to the top of an alpha-sorted list.)  My Sony software retains the setting of which Finder folder to put the images in.  I set the Folder Action to delete the originals.
    I take a picture.  Camera sends image file to Sony software→Sony software puts file in "To Hot Upload to Aperture"→Folder Action forces Aperture to import file into Project "_Hot Uploads".  In use I put the Sony software on one monitor and Aperture on another, with "_Hot Uploads" selected.
    NB:  Because you are importing this way, no metadata presets are applied.
    When the session is over, I move all the Images into a newly created Project (I always put each Shoot in its own Project) and I run "Metadata→Batch Change" to apply my standard metadata preset (copyright and so forth).  That leave both "To Hot Upload to Aperture" and "_Hot Uploads" empty, and ready for the next session.
    Screenshot of Automator:
    Message was edited by: Kirby Krieger -- screenshot added.

  • LR4 still brings up import dialog when auto import is on

    Mac 10.7.   Shooting tethered with 5D Mk II and Canon EOS Utility.  Auto import is importing the images into my catalog, but for every shot, the import dialog box appears and I have to click "Cancel".  This dialog should not be appearing when auto import is on, correct?
    Thanks.

    1) Be a little more specific... with your questions... Describe what happens...
    2) Perhaps FCPx does not like the .thm (thumbnail files) in the folder...
    I

  • IPhoto had a auto import folder. does this exist in photos for mac?

    I used image capture to get the photos from my iPhone, so that iPhoto didn't open every time i plugged in. there was an auto import folder in iPhoto which i could dump my photos in, then when i did open iPhoto it would import everything in that folder. is there a folder that will import everything in that folder whenever Photos for Mac is opened?

    What does iPhoto do with photos as they are imported?
    What you tried was a very complicated and unsupported way to import from one iPhoto library to another.
    The safest way would have been either
    to use iPhoto Library Manager to export a new library from the old one
    or to export the original files using iPhoto and to import the exported files.
    But pasting the Masters folder into a temporary "Importing" folder put your photos at risk. The Importing folder is a temporary cache that will be emptied, when an Import has finished.
    It started to get very slow and sluggish, so I decided I would move the photos to a new library on the same drive.
    It would have probably sufficed to repair or to rebuild the library and safe all your edits and albums, instead of migrating the photos to a new library.
    Since you do not have a backup, and your Masters folder got erased, I recommend to stop using the drive with your library immediately and to try data recovery software, for example Disk Drill. It has a free trial mode.
    http://www.cleverfiles.com/mac-data-recovery.html

  • Lightroom auto import/tethered shooting strangeness

    Hello, I'm trying to work out a tethered shooting workflow for the 1Ds MKIII that can keep up with a fairly rapid lifestyle shooter. I'm on a Windows XP system, 1.86 GHz Intel Core 2 duo system with 3 GB of ram. I'm seeing this same behavior in LR 1.3 and LR 2.0 beta.
    I've followed the steps Martin Evening outlines on his blog (Canon EOS utility in conjunction with Lighroom auto import) here http://lightroom-news.com/2008/02/07/shooting-tethered-with-the-canon-eos-1ds-mkiii/ and everything is working _almost_ smoothly.
    When I fire off a single frame with the camera, it takes about 5 seconds for the Canon EOS utility to copy the file to the hard drive and for lightroom to see and move the file from the watched folder to the destination folder. This seems reasonable.
    However, when I start shooting at a normal pace (approximately 1 frame a second) it seems like Lightroom stops watching the watched folder until I stop shooting for an extended period of time.
    I would have thought Lightroom checked the folder at a standard interval, every 5 seconds or so. However, if I snap, say 40 frames at the rate of 1 a second, Lightroom doesn't realize there are new images in the watched folder until I stop shooting and let the camera's buffer empty out.
    Has anyone else seen this behavior? Does anyone know if there is a registry hack to force lightroom to check the watched folder more frequently? Even better would be a hook, like a command line switch, that tells LR to check the watched folder immediately. The EOS utility 'linked software' preference could be configured to call this hook, and would result in much snappier performance.
    Thanks for the help,
    Andris

    Hi Andris,
    It strikes me that you have hit the maximum buffer that the combination of the Windows OS, EOS Utility and Lightroom are capable of managing. As you will have read in the report, I was able to fine-tune the tethered import to a rate of 3 seconds per capture image. This was with an Intel iMac 2.8 GHz duo core running Windows XP with 4 GB RAM. So a little faster than your Windows machine, which would explain why my download tests were faster.
    Look at it this way. There is the usual buffer of up to 12 frames on the camera in raw mode, which when combined with the 2 seconds it takes to transfer say, 25MB data from the camera to the computer via USB 2. This means that you can shoot at a rate of 1 frame per second, but will soon hit the camera buffer first in around 20 seconds or so at that rate. it takes about a further 1 second for the files to auto import into Lightroom and as you point out, Lightroom appears to do this in bursts. How to speed that up, I don't know. What I do know is that any background activity will slow down the import. On a shoot this week I was busy building an export of high res JPEGs from the catalog as I was shooting more downloads and as one would expect, this did affect the performance.
    It would be nice if the tethered shooting could be made faster, but as far as I am aware, this combination is the fastest yet and certainly faster than downloading from a card. As for Capture One, I don't know yet if they have managed to get tethered shooting sorted out for the MkIII.
    Martin

  • Auto-import Presets

    I searched the forum(s) for this request but didn't find anything that seemed relevant, so here goes (and my apologies if this has been requested before or is already available through some option I missed): I use auto-import all the time -- it's a standard part of my workflow for new images from my cameras, whether tethered or not. To cope with the half dozen or so different scenarios and situations that are repeatedly part of those workflows, I'd like to be able to have a pull-down list of named auto-import presets under the auto-import preferences dialog. This would cover things like location the imported files are moved to, canned metadata to be applied, processing, etc. in named configurations.
    Not a huge deal, but it'd certainly make my life somewhat easier and less error-prone while out in the field....

    I second that. Plus an option just to watch a folder, instead of auto-copy only

  • Auto Import Settings needs same robust features as regular Import Photos feature...

    Hello,
         It is disappointing to not be able to select the feature to auto convert RAW images to DNG as well as copy/move files to subfolders (in my case date folders) using the Auto Import Settings feature in LR 3.3.  The main intent of my usage is not for tethered shooting as the feature may have originally been setup for, but moreover to import images from my Eye-Fi Pro SD card automatically to my LR catalog.  In fact, this limitation makes the auto import completely useless for me as I have to remove the SD card and mount it (or tether camera via USB) and import standardly.  Please make a stronge effort to unite the functionality of all import functions in LR and allow the customer to choose which settings work the best for their needs.
    Thanks,
    ~David

    The Eye-Fi Pro X2 (8GB) handles RAW imagery uploads, and does so in a pretty quick manner.  I have a Canon G9 that I use the Eye-Fi in and it's RAW images take about 4 seconds per 12.1 MP .CR2 image which isn't too slow for me really.  I am also right next to the access point so the wifi signal is stronger and transfers are therefore a bit faster.   I use this card also with ShutterSnitch (for iPad) and a 1DS Mark III for location shooting so the AD can monitor shots remotely on the iPad and not have to look over the shoulder at an LCD screen or through a loupe.  At any rate, I also have a few other gripes about what LR should be doing with imported images that it isn't currently that seem like big misses, but I will add these to another feature request.

  • Auto Import feature lacking convert to DNG and move to subfolders...

    Folks,
        As many of you may be aware, when setting up a folder for auto import, LR 3.3 does not give you the same options as you might see in the regular import functionality.  Namely, the ability to convert to RAW images to DNG on the import as well as move to subfolders is not available.  This is a real bugger for me as I have a nice new Eye-Fi Pro card that I have setup to dump all images from my camera to a "watched" folder which is then imported into LR automatically.  Unfortunately, auto import doesn't solve the issue for me, so I am back to doing the same old import routine I had done before which is tethering the camera back up via USB (or popping out the card and mounting it instead) and use the regular import feature.
        I realize a lot of the design impetus for auto import is around tethered usage, where a photographer may want to see the images as fast as possible, but why would Adobe cripple the auto import functionality deliberately.  Give the auto import the same functionality as the regular import and let the customers decide which works best for their setup.  Geez!!
    ~David

    I believe I watched a tutorial that indicated that Lightroom now downloads the raw files first and then does the conversion. This speeds up the download process and enables you to go back to my room to do other work more quickly. I cannot comment on the speed of the conversion because I don't convert to DNG. But my thoughts are that 700 raw files will take some time to convert.

  • Auto import missing full Import options

    Setup
    Nikon D2X with LR 1.3 Windows XP Pro sp2
    I am shooting NEF (Raw) with a D2X tethered to a laptop
    Nikon Capture Control drops new images in to a folder
    LR auto import is watching this folder and duly imports the pictures
    adding metadata as it does so.
    The options on the auto import are much more basic than the standard import features.
    I would like to import the NEFs to DNG and backup the NEFs.
    Are there plans to fix/improve this situation.
    Or am I missing something.
    (Apologies if this is a duplicate post I have spend quite some time searching and checking FAQs)
    /Graham

    I don't know if there's any impediment doing it this way shooting tetherered, but it seems a clunky workflow. Why convernt to DNG on import when you want the tethered operation to be as fast as it can be? Why backup images when you don't know what to keep?
    Best import RAW, then after at least one cut ediiting/culling, then convert and backup.

Maybe you are looking for