Zum Hauptinhalt gehen

⚠️ 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

Kommentare

28 Kommentare

  • 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
  • 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
  • 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
  • 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
  • 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
  • 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
  • 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
  • SFA
    Top Commenter

    Have you checked whether the location of the CAPTURE folder is 

    a) Where you think it should be 

    and 

    b) Accessible

    Whilst C1 will create a session folder structure with a "physical" folder called "Capture" it also has a virtual folder "modifier" that may be pointing elsewhere. This might be especially the case where a studio shoot, working with "Looks", has an array of subfolder in the Capture folder (or indeed anywhere available to the system at the time of the shoot) and Capture has ben re-defined to point to a sub-folder.

     

    Similarly, the Import process will (usually) retain a "last used" "import to" folder - which could be the currently defined "Capture folder" proxy location.

    If that was on an external SSD that is not presently available you might expect to see a connection failure. 

    The addendum paragraph to the very first post in this thread describes something along those lines.

    If you have not done so already it would be worth checking exactly where that "Import to" location is pointing and perhaps resetting it, as described in that addendum, before trying again.

    If that does not produce a result or any further ideas, then it may require a deeper dive.

    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
  • SFA
    Top Commenter

    Hi Matthew,

    I'm glad that worked out for you.

    When I first started to use C1 I came to it from a quite similar application (no catalog at the time) and was using Sessions. I still do. 

    The session structure seemed to be a bit of an odd thing so I just carried on as before and things were OK but once in a while odd situations arose. 

    After a while I decided that understanding the intended benefits of sessions was important so I spent some time learning enough to make better use of what was on offer. It was during that exercise that I realised the power of the Capture folder concept but also the potential issues related to the "Capture" proxy name concept, especially when using multiple sessions with multiple "import to" folders, just as one might do in a studio shoot.

    The basis of the problem is that one gets into a simple habit that always works  - until it doesn't for some reason that one does not even recognise at the time. It might be something one did during an import activity and instantly forgot about, it might be a coincidence of something else not significant at the time or it could be some sort of system glitch. All of this can be confusing if you cannot immediately see something relatively obvious, like the full path to the currently set "import to" location, which would probably immediately indicate a wrong session or a wrong folder on the screen or in the "recent import locations" list. In your case it might be an SSD disk that is not connected or, perhaps, has a different drive letter now than what it was at the time the link was created. There are a number of technical possibilities for such a missing location error.

    The problem that the Tech Support people face, as I have personally experienced when in such a role many years ago and observed in many other examples subsequently working with customers operating technical support departments, is that people may be asked to support things with processes that are very "user-defined". A strong technical understanding of an application that is highly user "tuneable", like many parts of C1 for example, does not necessarily mean that their personal experiences with the functionality have ever touched on the operational nuances.

    The other challenge for Tech Experts, something that I have observed a number of times, is that "expertise" may sometimes lead to people skipping some of the base starting points and diving straight into the more interesting, to them, world of technical problems that they are most often presented with. That is, after all, what is expected of them most of the time and is why they are employed in the role.

    It's the sort of thing that a good, old-fashioned, process flow chart could help with if there was a way to create and maintain one based on tech support input and user feedback. Maybe AI, applied to the Topics in the Community pages combined with the FAQs, could derive some useful results.

    On the other hand, there is also the possibility that such an analysis would deliver as much misleading guidance as it would useful assistance.

    For some years I worked with a large client where the IT support group had a policy for desktop users (not so much the main UNIX-based system) that almost any problems were best resolved with a re-installation of the "standard" suite of business programs. Plus the data from the previous night's automated backup  - assuming it was good.

    Not really a great solution but is seen as cost-effective - at the IT support level - as corporate policy. It's no great surprise that most remote support operations for consumer software  - when they exist - use much the same strategy. Anything else is likely to be quite difficult to deliver and not very cost-effective even if offered as a chargeable service.

    That's where user communities can be helpful but may still be a bit hit-and-miss. Especially for in-depth technical issues where system configurations may be quite different, machine to machine, but not in ways that are obviously significant or even vaguely identified.

    Perhaps one or two of the C1 staffers could try running an AI app or two on the Community records using some of the more specifically described questions to see whether some good and helpful ideas could be extracted quickly, efficiently, and with accuracy in the suggestions that populate the results.

    It would likely be quite interesting either way.

    My apologies for the ramble. Your question, and others very similar to it, pop up quite often and my gut feeling is that the answers  - or at least some enlightening ideas that could lead the questioner to the answer they need, could be with the enquirer in seconds if a suitable discovery method was available.

    The simple community search may already provide such a response for a curated reply prepared to answer the exact question asked. But it's the slightly odd problem or something that might raise inconsistently phrased questions that would benefit from speedier and more pertinent discoveries through the search mechanism.

    I wonder if it could be useful?

    1
  • SFA
    Top Commenter

    OK, out of interest I decided to do a little investigation about my AI suggestion.

    Using MS Copilot in the Edge browser on a PC running Win 10 I entered a question and the first response was provided.

    Quite good but the question was not precise enough to properly cover the specific subject of this thread.

    So I tried a slightly modified question and got the second result below. It is closer to the answer needed but falls just short of hitting the specific target. Or at least I think it does - but what do others think?

     

    --------------------------------------------------------------------------------------------------------------------------

    Question asked in MS Copilot: capture one software import folder missing.

    Result:

    If you are using Capture One software to edit your photos, you may encounter a problem where the import folder is missing from the library. This means that you cannot access the images that you have imported into the software. This report will explain the possible causes and solutions for this issue.

     

    One possible cause is that the import folder has been moved, renamed, or deleted from its original location. This can happen if you use a file manager or another software to organize your photos. To fix this, you need to locate the import folder and reconnect it to Capture One. You can do this by right-clicking on the import folder icon in the library and choosing Locate. Then, browse to the folder where you have moved it and select it. Capture One will then update the library and show the images in the import folder.

     

    Another possible cause is that the import folder has been corrupted or damaged by a virus, malware, or disk error. This can prevent Capture One from reading the folder and displaying the images. To fix this, you need to scan your computer for any viruses or malware and remove them. You also need to check your disk for any errors and repair them. You can do this by using the tools provided by your operating system or a third-party software. After that, you need to rebuild the import folder by deleting it from Capture One and importing the images again.

     

    These are some of the common causes and solutions for the missing import folder issue in Capture One software. If none of these work, you may need to contact the support team of Capture One for further assistance.

    ==========================================================================

     

    Question asked: capture one software import folder not found error 513

    Result:

    This report describes the problem of importing folders in Capture One software and the possible causes and solutions for the error 513. Capture One is a photo editing and management software that allows users to import folders of images from various sources. However, some users may encounter the error 513 when trying to import folders, which means that the folder could not be found or accessed by the software. This error can be caused by several factors, such as:

     

    - The folder has been moved, renamed, deleted or corrupted after being selected for import.

    - The folder is located on a network drive, external drive or cloud storage that is not connected or available at the moment of import.

    - The folder has insufficient permissions or is protected by encryption or password.

    - The folder contains files that are not supported by Capture One or have invalid names or extensions.

     

    To resolve the error 513, users can try the following steps:

     

    - Verify that the folder still exists and has not been modified in any way since being selected for import. If the folder has been changed, users need to select it again for import or create a new folder with the same name and location.

    - Check that the folder is located on a local drive or a drive that is connected and accessible by the software. If the folder is on a network drive, external drive or cloud storage, users need to ensure that they have a stable and reliable connection to the drive and that the drive is mounted or synced properly.

    - Make sure that the folder has adequate permissions and is not encrypted or password-protected. Users may need to change the permissions of the folder or enter the encryption key or password before importing it.

    - Remove any files that are not supported by Capture One or have invalid names or extensions from the folder. Users can check the list of supported file formats and naming conventions on the Capture One website or user manual.

     

    If none of these steps work, users can contact the Capture One support team for further assistance.

     

    ===========================================================================

    1
  • 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
  • SFA
    Top Commenter

    Hi Matthew,

    Thanks for the kind words.

    I too was quite surprised at how close the AI result got to an almost spot-on identification of all the potential problem points related to the 513 code. Indeed that the 513 code was referenced at all and put in context.

    I'm wondering whether a slightly different choice of search words might hit the solution directly and consistently.

    However, it's the precision required for guessing the right words that then becomes part of the search and retrieve problem, especially in a global support context with multiple languages involved. 

    The thing is I'm only doing this as a passing interest and relating it to things I experimented with unofficially in a job role 3 decades ago, long before the world's computer systems had anything like the data processing capacity needed to create the concept of AI. 

    In fact, as I recall, the Internet was in its infancy and just beginning to appear in places other than the Military applications and Technical universities that spawned the concept. It was that long ago.

    If C1 could allocate some resource to spend a little of their working time for spotting common issues,  like the one in this thread, run the AI, find all the possible very similar solutions by using slightly different word choices and then use the AI output (perhaps slightly enhanced by editing for different contexts and word choices) as an official guidance document with flow chart if appropriate, it might be possible to greatly enhance the way the community can be used for self-support.

    If, for example, one could spend 15 minutes creating, refining and enhancing an AI-originated document that hits 80 to 90% of the necessary information as a first response that would be time well spent. To create a similar document from scratch, even if it is directly related to one's "expert knowledge", would likely take half a day by the time one had checked it for accuracy and completeness.

    The Community Search facility is quite good at finding references but not in a way that makes it attractive to use and concise in its output. That is where the AI part of the search starts to shine. An AI front end to the search facility, dedicated to the community FAQs and form contents, might be a great way forward if C1 are prepared to consider it.

    0

Bitte melden Sie sich an, um einen Kommentar zu hinterlassen.