Skip to main content

⚠️ Please note that this topic or post has been archived. The information contained here may no longer be accurate or up-to-date. ⚠️

Can not import images to a session I am Begging for HELP!!! Answer FOUND! Kinda

Comments

24 comments

  • Corey Brown

    UPDATE!!!!!

    The Solution I have found is On the import drive / location. loses its place. even though all photo show in the importer and every thing looks find it has lost it's path. So I take and give it a different location then go back to the original Drive D in this case and whala it works. It has now not been able to import to my session three times and each time the above has worked to be able to use the importer. 

    1
  • Shuzo Yamanaka

    I've had a same issue. thank you for finding that workaround!!  

    1
  • Larry Godwin

    Same issue here and the workaround works as well.

    1
  • Zeemon Erhardt

    +1 here 16/01/2023 on windows

    Reselecting the folder fixed the issue for me even though everything EXCEPT the actual import worked as it should.

    Lame bug. Pls fix. 

    1
  • Ian Wilson
    Moderator
    Top Commenter

    I'm not sure that I fully understand what you are doing and what isn't happening. 

    But as you are working in a session, here is something you can do. Outside of Capture One, transfer the images you want from your memory card to the Capture folder of your session. Then open Capture One in that session, and you should see the images. No need to use the importer at all.

    (This works fine in a session, but not in a catalog. It is in fact the way that some users work anyway, instead of using the importer. Ideally, you want the importer to work for you, but until you manage to work out why that isn't happening, you can get round it in the way I have described.)

    Ian

     

    0
  • Corey Brown

    Thank you Ian. Yes this worked. As far as what is happening. in the importer I select images to import. when I hit import the importer disappears like normal however the import does not start in the session. Nothing happens. 

    0
  • Baz

    I'm having the same issue, the current version of C23 isn't letting me import straight from memory card in sessions. The issue isn't isolated to upgraded session (C22 session), creating a new session in C23 also didn't work.

    Faster culling and upgrades to the importer turned into impossible to cull :(

    0
  • Ian Wilson
    Moderator
    Top Commenter

    I wonder whether this is in any way a Windows-specific issue? It certainly seems to work OK for me on a Mac.

    Ian

    0
  • Louw van Staden

    Same issue here. Capture One 23, I found the import screen to be sluggish and lagging (Win 10). Clicking on the images to be imported, you have to wait about 30 seconds they are selected or un-selected.  

    Clicking import more often than not, the Untitled Album folder is created but no images are being imported. As a wedding shooter I have images from different cameras for 1 session, so do not want to dump all the images in one Capture folder. 

    Never had these issues until C23.  

    I have tried different card readers, with the same result.  

    Any advise will be welcomed. 

    Solution/Workaround
    In the import screen, select Import From, click on the down arrow and select Choose.
    Select your card reader, DCIM folder and then select the folder with the required images. Some folders might have images from different dates. Click on the Date Modified in the top row to arrange in date order. Highlight required images and click on Review for Import.   

    0
  • Mateusz Lenik

    Confirming the problem on 16.0.1. Unless I use the workaround, the import successfully completes with a "0 images imported" message.

    Thanks for finding that workaround, it was not obvious!

    0
  • BeO
    Top Commenter

    Yes Ian, I'm one of those guys, I copy the images into the Capture Folder or sub folder when working with sessions. No importer needed, nor wanted.

    Culling with C1 functions is faster than every importer I've ever seen (though not tested v23), e.g. when using the various Select Next and Next Set/Previous Set functionality, shift double click to zoom in etc.

    The importer has these presets which can be applied during import though.

    Similar with catalogs, copy to final destination and then synchronize folder without the importer can work around the importer, I also cull after the import.

    0
  • Streetlife Photographer

    I have this issue with the importer too. I have 1,000 images to process from the Edinburgh Hogmanay event. My first import worked as expected, thereafter the importer process never imported any images. I was tearing my hair out! We are doing time-critical work here. If we can't file in time, we don't get paid. CO engineers need to do more testing before releasing upgrades.

    0
  • gb

    Just ran into this problem myself.

    0
  • Streetlife Photographer

    Case raised: 171021. I'm providing logs . . .

    0
  • Carlos Fuentes

    I have that problem but nothing works, I think this must be caused by CO not having permissions to import the files from an external storage medium. If I copy the files to a folder on the disk of my pc the process works properly. It is not possible to import files from the card or my camera directly. It is a failure of the CO program.

    0
  • Ian Wilson
    Moderator
    Top Commenter

    If it's a matter of permissions, it should be possible to solve it. (I know how to do it on a Mac, but someone else would have to tell you for Windows.)

    Ian

    0
  • Carlos Fuentes

    Ok thanks, at the moment what I do is copy the folder generated with the photographs of my camera on my desktop using an adapter. (My pc does not have an sd memory reader) and there Capture One if it works without problem. Capture One cannot copy photos from any SD card connected to the usb port. It also doesn't recognize my connected camera, a Fujifilm Xt30. That's why I interpret Windows as not giving write permissions from other devices via COne. I'm not sure though. all this operation is somewhat cumbersome but I see that more users have this problem, I trust that the Capture team will fix the problem. ¿?

    0
  • David Hayden

    THANK YOU Same problem here.

     

    0
  • FirstName LastName

    I had the same issue just now. I sorted through hundreds of photos. Nothing happened when I selected import. Reselecting the sd card allows me to import but I lost all my selections so I had to redo an hour of work. Please fix. 

    0
  • FirstName LastName

    Just encounter the same problem, and the workaround doesn't work for me. Even if I copy the images files into capture one and edit them in the said folder, nothing comes out when exported. Very frustrating.

     

    0
  • Ian Wilson
    Moderator
    Top Commenter

    If your issue is that you can't export, then that may have a different cause from difficulty with importing. 

    What does your export recipe look like, in particular where does it specify that the output goes?

    Ian

    0
  • Matthew Bushey

    Hey there Ian - 

    Sorry to post to an old thread, but I'm also having the same issue as those above; and none of the workarounds mentioned are working for me.

    C1-23 has worked fine day-in/day-out for me since I purchased this version (at least a year ago?), until this week. As a commercial shooter, on average I've been importing or tethering images into C1-23 at least 5-8 times/month the whole time.

    Specs: using C1-23 v16.2.6.7 . . . . Mac OS Ventura 13.5.2, MacBook Pro M1 MAX

    Getting the same error code (513) when, after creating either a Catalog or Session, trying to import RAW files created by a Sony A7R3. All files get sorted into individual folders ("Looks"), stored on external SSD's for culling/editing; when projects are finished, moved to RAID for longterm storage. I only edit off of TB3/4 SSD's. Unfortunately I cannot just "dump" an entire shoot separately into a created Session (side-stepping import), as file renaming upon import is an important step for me with (typically) thousands of images that need to have proper naming and identifiers.

    No matter what I do in the Import screen, I can never get the importer to "process" any images into the Capture folder. I just get error codes in the Event's panel.

    Any thoughts or help appreciated. Thanks!

    0
  • Matthew Bushey

    Hey there SFA - 

    You, my friend, nailed it!

    Upon checking out what you mentioned above, I found that - for some reason - C1's default in the Import window had changed to a random output folder from a prior shoot's Session? I can't imagine why/how it would have changed to that, since I only "Import" directly to subfolders within the Capture folder.

    I went in and manually changed (just to make sure) that C1 was actually directing the new images into the actual Capture folder of the Session I'm working in, and Boom . . . . it worked!

    Thank you for your help! I've been chatting with a member of C1's Tech Support for more than a week now, and between the 2-3 day lag times awaiting responses from them, was only getting "run-around" solutions . . . update to this, try redownloading C1, etc blah blah

    You've helped me a great deal. Thank YOU!

    :-)

    0
  • Matthew Bushey

    SFA: I appreciate your ramble (ha!) and musings on the shortcomings of a Technical Support role, when the software being utilized has a lot of nuanced adaptability and customizability to the users preference.

    And for this and many similar reasons, I understand how Tech Dept's have resorted to - like you suggest with the IT Dept description - the Western Medicine analogue of the "Allopathic" form of diagnosis: start withthe most basic, and work your way deeper when necessary . . . but usually ONLY when necessary.

    Yeah, sometimes a good ol' reboot, delete/reinstall, etc does the trick . . . but it's issues like this one in the thread that can potentially have many viable answers or fixes, given the users unique settings and preferences. It is for that reason that I think your "flow chart" idea is even more tantilizing, in that it would give a Tech Support person the ability to scale issues not just to their lowest common denominator, but to cover some potential "oh duh, I totally missed that" simple stuff that gets swept under the proverbial rug of "the user has used the software for 2 years now, that "xyz" thing should be more than obvious" . . . . when sometimes its not.

    I'm sure you could also use AI to help develop that flow chart, given the amount of process data/steps/etc that exist throughout the web when browsing for the "How-To" side of C1. You'd likely have to limit much of the source material for the AI work to more recent C1 versions, as even though the DNA of C1 largely has been the same for quite some time, little nuances have fleshed out even the basics of C1 in the last few series updates.

    As for your AI test above for that "513" error code, I actually think the AI did a pretty bang-up job! It's well-explained, doesn't feel robotic, and I think the answer it gives is a great jumping off point for the average->advanced C1 user.  

    Keep up the good work and AI investigations, and again - I'm truly thankful for your help with my situation. :-)

    0

Please sign in to leave a comment.