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

"cannot process the current selection"

mattcohen
http://matthewcohen.org/lolwtf.png

everything is connected and i can't see any reason why this wouldn't process a jpg
0

Comments

18 comments

Date Votes
  • Ian Wilson
    Moderator
    Top Commenter
    I don't know the answer, but I do remember that other users have posted about this error message before, So it may be worth searching the forum to see what they came up with.

    Ian
    0
  • mattcohen
    thanks. they were having online/off-line issues in previous versions. mine appeared to be online, but C1 is treating them like they are offline. even after pointing C1 at the file, it still won't do anything with it.

    this version is so far from ready
    0
  • SFA
    mattcohen wrote:
    thanks. they were having online/off-line issues in previous versions. mine appeared to be online, but C1 is treating them like they are offline. even after pointing C1 at the file, it still won't do anything with it.

    this version is so far from ready


    Very large or very small files may be limited but that may not be either of those constraints by the looks of it.

    Are you using an Output Process recipe?

    If so what does the Process Summary tell you (if anything?)

    Log file may have some clues to consider too?

    You are sure the image is available to the C1 at the known catalogue link?

    Are all images giving the same result?
    0
  • mattcohen
    SFA wrote:
    Are you using an Output Process recipe?

    If so what does the Process Summary tell you (if anything?)

    Log file may have some clues to consider too?

    You are sure the image is available to the C1 at the known catalogue link?

    Are all images giving the same result?


    I had been using a recipe, like I usually do. Seeing your question I tried export > variant and that actually worked. Nothing changed in my setup, or my settings. Nothing in the log file. The image is available, double checked via finder, and "show in finder". All are giving the same result.
    0
  • SFA
    IS there a difference between the Export recipe and the Process recipe?

    Anything funny hanging around i the process queue or the History?

    It certainly sounds like an odd thing.

    Maybe the system throwing up the only message available to it but at a different point from where the problem is initiated?

    Is the file it's referring to actually the file you are trying to process - for example.


    Grant
    0
  • Abbott Schindler
    I've encountered this problem in C1 11 and 12, where the files are online (and C1 doesn't say they're offline), the preview seems to draw correctly, but C1 says that it can't process images. Invariably, waiting a couple of minutes solves the problem. I've never figured out what's going on but it seems to be a transient issue.

    Have you tried waiting a little while and seeing if you can process those files? Or quitting C1 and reopening it?
    0
  • mattcohen
    SFA wrote:
    IS there a difference between the Export recipe and the Process recipe?

    Anything funny hanging around i the process queue or the History?

    It certainly sounds like an odd thing.

    Maybe the system throwing up the only message available to it but at a different point from where the problem is initiated?

    Is the file it's referring to actually the file you are trying to process - for example.


    Grant


    it's all files, and i seriously didn't change anything at all.
    0
  • mattcohen
    Nature Isme wrote:
    I've encountered this problem in C1 11 and 12, where the files are online (and C1 doesn't say they're offline), the preview seems to draw correctly, but C1 says that it can't process images. Invariably, waiting a couple of minutes solves the problem. I've never figured out what's going on but it seems to be a transient issue.

    Have you tried waiting a little while and seeing if you can process those files? Or quitting C1 and reopening it?


    this sounds close to what i'm seeing. time doesn't seem to help.
    0
  • Abbott Schindler
    The amount of time is variable for me and I haven't figured out a pattern. Really irritating but invariably I'm able to edit the images after at most a few minutes. What's really weird is that the processors don't show measurable activity, which suggests that C1's "thinking" and not really processing.

    Maybe filing a Support Request with logs attached would help. I haven't done that because it happens so infrequently and is transient, which makes it hard to know if it's C1, mac OS, or something else. Support is probably the best option for you.
    0
  • mattcohen
    Nature Isme wrote:
    The amount of time is variable for me and I haven't figured out a pattern. Really irritating but invariably I'm able to edit the images after at most a few minutes. What's really weird is that the processors don't show measurable activity, which suggests that C1's "thinking" and not really processing.

    Maybe filing a Support Request with logs attached would help. I haven't done that because it happens so infrequently and is transient, which makes it hard to know if it's C1, mac OS, or something else. Support is probably the best option for you.


    there's literally nothing in the log
    0
  • Paul Steunebrink
    If processing via a process recipe does not work but export does, I suggest you create new process recipe and try that one.

    I would also do a verification of your catalog (File menu).
    0
  • Abbott Schindler
    Paul,

    In my case, I can neither Process nor change adjustments in images when the [transient] problem happens. Changing the process recipe doesn't matter. C1 acts as though the image is offline, but doesn't label it that way. Something else is going on, but in my case it happens so infrequently and goes away fairly quickly, so I haven't filed a Support Request. Hasn't happened yet in v20.
    0
  • Peter Schäfer
    I was testing how is with my system. I start the process and also got this message and now. The result is that I "killed" the V20. I cannot make any process and cannot edit any image any more. All is grayed out. I restart system, application all. This is with all my catalogs. I made a request to the support but what should I do now? Is there a possibility to reset parameters?
    0
  • Peter Schäfer
    I think this that this is a missleading message. Meanwhile I detect that I have a wrong licence key (Fuji instead Sony). I don't know why I was able to work with key before and when I begin to use the proces recipe the programm detect that this is not this type of image I'm using for this key. Then I also was not able to edit any image any more. Anyway, what I found out when I load a rawfile which is not valid for my licence and I wish to use a procece recipe I get exactly this error message. When I use "export", this is possible without error. The question is wether after activating the licence the programm calling home wether the licence is still valid (are you offline when happen this?) and do not get the information and block.
    0
  • Paul Steunebrink
    So a mismatch between a kind of raw file (Sony for example) and a license (Fuji for example) gives this error.

    How have you solved this? Did you trade-in your license key for the right one?
    0
  • mattcohen
    I'm still getting this more often than not. no pattern. and my license isn't limited by brand.
    0
  • Paul Steunebrink
    mattcohen wrote:
    I'm still getting this more often than not. no pattern. and my license isn't limited by brand.

    Thanks for letting us know.
    0
  • Peter Schäfer
    I'm in contact with the support that they send me the correct license key for Sony.
    First I was using a test key before I changed to the branded full version. Because I was able to work with my Sony images I did not look closer. After I got the problems I saw this and switched now back to the test key for Sony. With this at the moment is working without problems.
    0

Post is closed for comments.