Import Stalling

I've just started using Lightroom (4 is my first version!) and so far I really like it.
I am seeing one significant problem in the beta version, though.  When I start an import it will often stall.  It works fine when I am importing D90 NEF files and many kinds of JPG files.
I have narrowed it down to two different files that are causing me problems.  TIFF and D90 movies.  I don't care much about the movies, but the TIFF files will be a problem with my scanning!
When I import one of these files, dynamiclinkmediaserver runs continuously (12.5% - a single virtual  core) and does not stop.  Even when I close Lightroom and quit the import, that process does not close until I kill it.  I have tried importing as a copy, an add, and a copy to DNG with the same results.  I have no processing options during import set.
I am running Win 7 64-bit with the 64-bit LR4 beta 1 on an I7-2600K.  I do have a small tif file that reproduces the problem.
Any thoughts/suggestions?

I guess others are not seeing this problem.  Due to other problems, I have since re-installed Win7 and the import problems have gone away.  I am not sure what was triggering the problem at this point, so I will close this one.

Similar Messages

  • Aperture Importer stalls during import - can I resume?

    I tried to import my photos from Aperture to Lightroom using Adobe’s tool with no success. Every time I try, the import stalls after about 25-27% complete. To make sure I don't end up with duplicates in my new Lightroom catalog I deleted all the images that were imported (both in the LR catalogs as well as at the physical location on my NAS where I had copied them to as part of the migration process).
    Is there a way to resume such a stalled import without producing duplicates in both LR and in the folder structure on my NAS or do I have to start all over from scratch (only to end up with another stall …)?

    I haven’t seen this problem with my own eyes, but it’s not surprising. After all, Adobe’s developers are having to figure out what’s going on inside Aperture libraries, and Apple aren’t helping them!
    My guess is that it’ll be something annoyingly simple – like odd text characters in metadata or an unusual file – which you may be able to fix in Aperture before doing the import again.
    To see where the problem happened, in your Documents folder should be a LibraryImporter.log file. Double-click this file and it should open in the Console application, and the most recent entries might reveal information about where the problem occurred.

  • Lightroom 1.1 Import Stall and Poor Performance: a solution?

    My lightroom is extremely slow (unusable) when trying to import approx. 1000 JPGs into a brand new, fresh catalog. I've got a Intel Mac 2.33Gz MBP w/2G RAM running 10.4.10 and lots of free disk space.
    A workaround?: As soon as I select "Quick Collection" during the import (since I currently have no images in "Quick Collection", no images are displayed during importing), the import process immediately started progressing at reasonable and acceptable speeds. So this import performance and stall seems to be related to lightroom trying to display photos or metadata info on image sets that are in the process of being imported.

    Jerry,
    What you suggest really is not an effective solution. Go to File>Catalog Settings>Metadata and uncheck 'Automatically write changes into XMP'. That should speed it up considerably. If you have already done that and are still having the problem, do a search for other solutions.

  • Import Stalls from CF Reader

    Does anybody know why Aperture stalls at the beginning of an import session of raw images from an 8-GB SanDisk card, using a SanDisk card reader (it has the same behavior from the camera)? Aperture shows the spinning progress indicator and "Scanning."
    Can I drag-and-drop the images from the CF card to a project?

    Jerry DaBell wrote:
    Does anybody know why Aperture stalls at the beginning of an import session of raw images from an 8-GB SanDisk card, using a SanDisk card reader (it has the same behavior from the camera)? Aperture shows the spinning progress indicator and "Scanning."
    Do not import directly from camera or card into Aperture or any other application. Instead Finder-Copy the images from the card to an appropriate original-images folder on the hard drive. After backup and ejection of the card import from the newly created original-images folder on the hard drive.
    Also, set Previews to be built manually when you are otherwise not working in Aperture. Automatic Preview-building can kill an Aperture workflow.
    Also Max the RAM and make sure that hard drives stay less than 70% full, and do not use (slow) USB for hard drives, except for backup. Ideally by a FW card reader for loading from CF and use fast CF cards.
    Can I drag-and-drop the images from the CF card to a project?
    No.
    HTH
    -Allen Wicks

  • Upgraded from Panther to Tiger. Mail import stalls.

    I just upgraded from 10.3.9 to 10.4.9 and in the process, Mail.app was updated (as expected). When I launch Mail.app, it starts importing my fifty-seven thousand old emails. It stops on message 3991 and never continues. I sits there forever, perpetually increasing the estimated time to completion. I haven't been able to check my mail since upgrading over the Memorial Day weekend.
    I'd like to follow Ernie Stamper's instructions at http://discussions.apple.com/message.jspa?messageID=2529207#2529207 but I do have several .imapmbox directories and the instructions for converting those were never posted.
    I have a tar archive of my old Mail directory and my old Preferences directory, so no data has been lost yet.
    I have several mail accounts, some of which no longer exist on any server, but I still have the messages stored locally. I have messages in all of my inboxes, but I do try to trim them down from time to time by moving them to dated "On My Mac" subfolders. I've got a lot of messages in my trash that can be lost if necessary. The same goes for my old Junk mail.
    I have never had any mail plugins installed, so the instructions in the kb article "Mac OS X 10.4: Mail unexpectedly quits, stops responding, or won't import previous mailboxes" were useless to me.
    I'm very comfortable at the command line, so if anyone has any suggestions that require some shell hackery, don't hesitate to post them.
    15" AlBook   Mac OS X (10.4.9)  

    The conversion from Mail 1.x to Mail 2.x is broken. Here’s an example of the most common variant of this problem and how to proceed in those cases:
    Just upgraded, Most of my old Inbox is gone!
    Your problem, however, is different in that you don’t even get an incomplete conversion. If Mail stalls during the conversion process, you may try to identify the mailboxes that Mail is choking on, quit Mail, move those mailboxes out of ~/Library/Mail/ (e.g. to the Destkop), and trash any Envelope Index-named files you may see in ~/Library/Mail/, so that Mail re-creates the index and tries to import the remaining mailboxes again, then manually import the problematic mailboxes as Other.
    Alternatively, you may want to set up Mail from scratch and manually import your mail back afterwards. This would allow you to use Mail normally while solving the problem of importing the old mail as you see fit:
    1. Quit Mail if it’s running.
    2. In the Finder, go to ~/Library/. Move (not copy) the entire Mail folder out of there, to the Desktop.
    3. In the Finder, go to ~/Library/Preferences/. Locate com.apple.mail.plist and move it to the Desktop.
    4. Open Mail and set it up again from scratch. If given the option to import existing mailboxes or something like that, don’t. Just enter the account information and check that everything works fine.
    5. You’ll have to re-configure all your settings in Mail > Preferences. For spam-related security reasons, the first thing you should do is go to Preferences > Viewing and disable Display remote images in HTML messages if it’s enabled.
    6. Do File > Import Mailboxes and follow the instructions to import your mail from the old Mail folder that’s now on the Desktop. Import the Mailboxes folder first, then each of the POP-username@mailserver account folders, if any.
    There are two ways to import Mail 1.x mailboxes into Mail 2.x. The obvious one is importing them as Mail for Mac OS X. But Mail 1.x stored mail in standard mbox format plus some additional support files, and this allows Mail 1.x mailboxes to also be imported as Other, i.e. as generic mailboxes in standard mbox format.
    Importing as Mail for Mac OS X produces the best results when it works, because it takes into consideration all the files in the mailboxes, not just the mbox files where the messages are stored, and hence, allows information such as status flags to be preserved. Importing as Other, on the other hand, may work in cases where importing as Mail for Mac OS X doesn’t, because it looks at the mbox files only, ignoring the support files which is what Mail 2.x usually chokes on, but precisely because of that, information such as status flags is lost and previously deleted messages may reappear.
    Hence, you may try importing as much as you can as Mail for Mac OS X, then import the problematic mailboxes as Other.
    Note that what Mail asks for when importing depends on the format chosen. Mail always asks for the folder that contains the “things” to be imported. If Mail for Mac OS X is chosen as the data format, the “things” to be imported are the *.mbox folders, so you must choose the folder that contains them, not the *.mbox folders themselves. On the other hand, if Other is chosen as the data format, the “things” to be imported are the mbox files, so you must choose the *.mbox folders that contain them in that case.
    Note also that some of the mailboxes now on the Desktop may have already been partially converted to the new *.emlx format during the previous (failed) attempt to convert them in place. If you tell Mail 2.x to import as Mail for Mac OS X a mailbox that already has a Messages folder, Mail will simply ignore the Mail 1.x files present there. If the mailbox was successfully converted to the new format, that’s fine, but if the conversion was incomplete, that’s not what you want.
    As a result of doing all the above, some messages may be duplicated. Andreas Amann’s Mail Scripts has a Remove Duplicates script that you may find useful.
    If all is well and you don’t miss anything, the files on the Desktop can be deleted, although you may want to keep them for a while, just in case.
    Note: For those not familiarized with the ~/ notation, it refers to the user’s home folder. You can easily locate any of the folders referred to in this post by copying the folder path here, doing Go > Go to Folder in the Finder, and pasting the folder path there.

  • Iphoto import stalled when mac ran out of power

    I was trying to import photos into iPhoto from a digital camera, when the Mac battery ran out of power. This seems to have caused the import to stall, and now I can't make it restart or even stop.
    Here are the system data:
    OS X Yosemite
    iPhoto library is running from an external hard drive
    Digital camera is Canon LG20

    Apple Menu -> Force Quit.
    There is a high likelihood that your library will be damaged. Do you have a back up?

  • Stalls on import - possible clue & solution

    Just in case anyone else is having this prob:
    I've had a persistent problem with LR - from the very start - on my laptop where part way through importing Canon raw files from a CF card the import will stall. I would have to relaunch the app and then retrying to import the images would result in several duplicate images (usually 5 or 6) from the point where the first import stalled being duplicated in the library - noted with a -2 at the end of the filename. A possible clue to the problem and a seemingly good solution is by not having the top tool bar showing - the one with the ID plate, modules and thumbnails alongside the progress bar then this seems to stop the freezes. I've done card after card like this and it seems to be working just fine. My guess is that it is the accessing of the thumbnail image for the progress bar which was causing the problem.
    I still get regular freezes when LR 1.2 is building the initial previews, sometimes it restarts by itself, other times I have to restart the app. This is a known problem.
    Steve

    My choice is to first copy all the files from the CF using a card reader to a folder on disc and then import them to Lightroom from the folder on disc.
    If you look at that process it is relatively slow. So what I would recommend is to copy all the files off CF card first. I also disable my Anti-Virus software when copying from CF card. (why have it intercept my files when I know that my Nikon/Canon/etc is virus-free).
    (If there is any problem, do a quick look through your copied files and compare them to the listing of the CF card. (Open two Windows, side-by-side, one with a listing of the CF card and the other with a listing of the folder on disc where you copied them. Difference will be easy enough to spot).
    Then import your files to Lighroom from your disc.
    That is how I do it and it always works.

  • Can't import with "Do not import duplicates"  checked

    When I import photos from my camera, I always use Do Not Import Duplicates/Apply to All. Lately, however, when I do this, the import stalls- the progress bar goes gray, and nothing happens. I have to Cancel, then start the import again, and import all duplicates. When I do this, the import works.
    What might be causing this? It's a pain to have to bring in these duplicates over and over.
    Thanks.
    BC

    It is a bug in the software, do a search of older posts. This happens to me when the memory card is quite full. There are several options.
    1) use the application image capture
    2) clear your memory card after you download (no duplicates)
    3) use Finder and open the memory card sort the list of photos by date and select and drag the desired photos to iPhoto
    Hope this helps

  • Iphone photos won't import

    this has been a problem with two differenent iphones i've owned - i have about 4,400 photos on my iphone, but only about 1,600 will import to my iMac through BOTH iphoto and image capture. all i want is every single photo on my iphone to be backed up as a usable .jpg in it's original file size on my iMac - why does this seem to be impossible for me? i've scoured forums for a similar problem, but have not found myself a fix. in iphoto - the import stalls out at around 2,800 count and just sits there - so alas i only get about 1/3 of my photos.
    in image capture, it goes through all the photos and imports "what it wants" i guess, skipping huge chunks of photos, about the same amount as iphoto. i'm beginning to think something is corrupted, or perhaps there is a specific photo or vid that is crashing both applications - if i only get a similar count of photos from two different imports. HELP!!!!

    Try transferring them wirelessly with an app like PhotoSync.  I haven't noticed any reduction in image size with photos taken on the 4S.

  • Problems importing email from Snow Leopard Mail into Lion Mail

    I've recently moved from a MacBook Pro 1,1 running Snow Leopard to a new MacBook Pro running Lion.  I had the folks at the Apple Store do the set up - they migrated everything from my old to my new.
    Everything is where it should be and most everything works, except Mail. 
    I have about 90 GB (yes, I know) of stuff in the Mail folder and every time I try to import the old emails into Lion Mail the process stalls out.  And when I try to restart I have twice as many emails and I lose 10+ GB of hard drive space. I've gone from having 110GB available to 50 GB in two days and I still don't have access to my old emails.
    I've deleted the envelope files, the smart mailbox files, deleted old attachment files and other cruft still floating around the Mail folder but my last attempt at importing stalled out and quit after getting halfway through.
    Any suggestions or ideas?  Help!

    Thanks.... I actually managed to find nearly 70 GB of attachements and trashed emails which apparently Apple Mail still keeps in the Mail folder.  I'm trimming now and I'll try another import this evening. In related news, my system is working much much faster now. 

  • "At Work" Indicator

    I've found that the most frequent case of LR crashing or freezing up is when, after importing, LR tries to do work in the background with no indication of being "busy" and I try to move on to do other things. I realize that I'm telling LR to create "Standard Previews" but I have no indication of LR's progress -- I have to open the Windows Task Manager and look at the Lightroom.exe Process until the CPU usage drops significantly below 50% before I try to do something else.
    Right now, as I type this, LR is hung up on an error message: "method not found: viewAttribute" while trying to view the latest folder I imported. This doesn't relate to the "Busy Signal" so much, though -- I waited until the task bar showed LR to be "not busy" -- it relates more to the fact that LR is still a "work in progress".
    Anyway, it does take a long timefor LR to get "Not Busy" in the Task Manager!
    So, there's no indicator that the system's too busy to handle another task, but when I do try another import, for example, LR freezes up.
    BTW, I'm not a complainer about new software -- I've done critical software development and testing. Right now I'd say LR is still a "work in progress": a lot of great features but some real hang-ups. I have thousands of images on an external (USB 2.0) hard drive and I have LR freeze up or take unacceptably long on just about every folder import attempt. I'd say that needs attention!
    In the meantime, a meaningful "Busy" icon would help!

    *UPDATE!!!*
    OK, here's the latest. After my last message, I attempted to Cancel the stalled Import, and nothing happened (which I find to happen whenever the import stalls) so I exited LR and restarted it. I reinstituted the Import and noticed that the first unimported image was a PSD file. This attempt worked, and LR correctly flagged the PSD file as Non-Compatible and didn't import it.
    Conjecture: LR may occasionally gag on non-compatible files!
    I then continued to successfully import several thousand files, but then it stalled again...on a folder of JPEGs...with *two AVI video files!
    Conjecture: LR may occasionally gag on non-compliant files!
    The next stall was just a few minutes ago. While an import operation was underway I used a Windows Explorer window to check the contents of the folder being imported -- no strange file types, all RAW, but while I was scrolling the folder (with no alterations going on) LR stalled!
    Conjecture: perhaps LR doesn't like anything messing around with it's Imports in anyway???
    Well, on with the show!
    Tony

  • Transport set : Migration in progress

    Dear all,
    I'm stuck with a transport set that is in status : "Migration In Progress"
    First the db import stalled (no conspicuous lock in the db). All db objects had actually been correctly imported. I had to interrupt the import script.
    I can't delete it wih the portal interface.
    Any idea ?
    Alain

    OK, I've just deleted the entry in WWUTL_EXPORT_IMPORT$ and dtarted again.

  • Mac photos App issues

    Is anyone else having import issues with Mac Photo app?? Import stalls at 12%

    Try posting here:
    iPhoto for Mac

  • ITunes media on Linux server via SMB - slow imports, changes and stalls

    I have an unRAID server (lime-technology.com) which is a Linux based server. I'm getting terrible performance with iTunes. The music playback is fine. But if I import a song file or change any metadata, it has problems. This isn't new, I've read many, many posts complaining about this and other problems concerning SMB shares and file systems. But I think I may be onto something and would like some advice.
    This is what I've found so far. Snow Leopard, OS 10.6.x, has a problem with SMB and/or any file system other than HFS+. HFS+ is the common files system for OS X.
    There are hundreds of posts on the web complaining about temporary freezes, slowdowns, sometimes crashes with SMB shares and other file systems. I have yet to see Apple acknowledge that there is a problem, but there are a few suggestions out there that seem to have helped people. I'll be trying out some of these this week and post the results here.
    From my own observations, specifically with iTunes, I've noticed some strange behavior. Here's my setup. I have an iMac running 10.6.4 (the latest update), the latest iTunes 10. The iTunes app is located on the local internal HD, I have my iTunes library files and all my media on disk 1 of my unRAID server. I'm hard wired to the server via a gigabit router. I have iTunes set to keep the media organized and copy the media files to the server.
    When importing a song file into iTunes, the file initially seems to copy at a good rate, the file appears in it's proper place and you can see the size increasing as it copies. Then it stalls for a while, then the name changes to a long hex number for a few seconds and then reverts back to its' normal state. The process can take 30-40 seconds, even with a small song file. I looked at the console and I got the following error message:
    Quote
    +11/8/10 12:24:28 AM /Applications/iTunes.app/Contents/MacOS/iTunes[2820] Possible unresolved transaction race -103/(Master Music Library/John Lennon/Rock 'N' Roll,(null))+
    The same thing happens when I make a change in the metadata. For example, I added onto the name of an album and for each song it changed I got:
    Quote
    +11/8/10 12:37:36 AM /Applications/iTunes.app/Contents/MacOS/iTunes[2820] Possible unresolved transaction race -103/(Master Music Library/John Lennon/Signature Box Set 5 - Walls And Bridges,(null))+
    This happens for each file imported or changed even within iTunes.
    I followed the first path in the error message: /Applications/iTunes.app/Contents/MacOS/iTunes[2820].
    In the /Applications/iTunes.app/Contents/MacOS/ folder I find the following files:
    iTunes
    libgnsdk_musicid.1.7.1.dylib
    libgnsdk_sdkmanager.1.7.1.dylib
    libgnsdk_submit.1.7.1.dylib
    where iTunes is a Unix Executable File.
    I did some more research and have found some posts about file systems other than HFS+ having trouble with app packages. I believe that all OS X apps are actually packages, like folders, but appearing as a single file. Other file systems don't seem to know what to do with these. There was some talk of "flattening" these app packages, but I haven't gone forward with that yet because I'm not sure I understand it enough yet.
    I've also noticed that in the getinfo box under sharing & permissions I usually get "You can read and write", but with apps I get "You have custom access". This was something i had noticed before and thought it was a problem on the server, but I didn't realize it until now, I'm getting the custom access on every app. So I think that's probably normal.
    I'm wondering if I'm having a permissions problem with the iTunes Unix Executable File. Right now the permissions are set as follows:
    system: Read & Write
    admin: Read & Write
    everyone: Read only
    Maybe it's trying to write to that file or another one and doesn't have the right permissions since the song file is now on the server and that's causing the stalls? I'm over my head here. Anyone have any ideas?

    I have the same problem with Excel files on an external drive. The drive is attached to my computer which is on a network and another user accesses the external drive. The problem of "custom access" began after our main server went down. I hope someone can come up with a solution so that I can set the permissions. For now the Excel files are all read only.
    Linda

  • LR 6 stalls on local folder import. Not all my pics get imported.

    LR 6 stalls on Import. I'm only importing from a local folder and it keeps stalling and not importing all my pics. Those pics were exported from Apple Photos to a local folder which I'm trying to
    to add to LR 6. Nothing is connected to my computer. I've tried many times over to remove the folder in LR and add it again but it behaves the same.
    Any pointers? Many thanks!

    Actually I have more info now. Poked around on LR as well. I DO see the pixel in LR. BUT, it's only for a split second...after in fully renders, it's gone.
    Maybe the preview of each pick has the pixel, but full res Master does not? Isn't there a difference b/w what "preview" you see in Aperture and LR?
    Regardless, it must be a hot-pixel in the camera. I have done more importing and it appears to be on a small set of pics from 2-3 years ago. Not on my most recent pics...yet.

Maybe you are looking for