メインコンテンツへスキップ

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

QLICProcessor CRASH + C1PRO 6.2 that follows

コメント

8件のコメント

  • julien lanoo
    Ah and when i import the images by copy pasting them in the folder, it doens't crash...
    So it's only when i use the import Window in C1PRO 6.2
    0
  • julien lanoo
    Correction, it does it also when i copy files from CF to HD, via my Finder...
    0
  • Paul Steunebrink
    [quote="julien lanoo" wrote:
    Correction, it does it also when i copy files from CF to HD, via my Finder...

    Makes sense, that is that the QLICprocessor is the Quick Look processor that allows Finder to render the raw contents of the image. CO 6.2 installs a different QLICproc. But that does not provide a solution. This is quite specific. Best to contact support, I think. You could report back if you like to make more information available here.

    Good luck.
    0
  • julien lanoo
    I'll do so but how can i send this to phase one?..
    0
  • Paul Steunebrink
    [quote="julien lanoo" wrote:
    I'll do so but how can i send this to phase one?..

    Go to:
    http://www.phaseone.com/supportmain.aspx
    and login and click Contact Technical Support. Copy/paste the text from you post into the case description or refer to the post with a link.
    0
  • julien lanoo
    Ok, so,
    i had a responce, we're still looking for the correct soluiton..
    But apparently what i understood is that the best thing is to update to Mac os X 10.6...

    cause now the support is advising me to turn back to 6.1.1, but that's no solution I want to use the 6.2..

    So i've aske them if it would be better to update to 10.6... still w8ing for awnser,
    But as they are great at the support, that will come soon..


    greets
    ju
    0
  • julien lanoo
    Hi Ju,

    As far as we know, the QLIC crash only effects 10.5.8. So yes, 10.6 is another workaround (probably a the best one.)

    Br
    Support
    0
  • Ulf Liljegren
    FYI, issue should be resolved with 6.2.1
    0

投稿コメントは受け付けていません。