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

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

New empty catalog created on opening C1

コメント

10件のコメント

  • ReiniMUC
    AndyE wrote:
    Nearly each time when I open C1 20 I get an empty new 'Capture One Catalog' created in my pictures subdirectory if it is not already there and it opens.

    I really do not want a new empty catalog as I generally use another catalog named in the same subdirectory but also do use catalogs and sessions on other direct attached drives. Before in C1 12 I always got a dialog that allowed me to choose of my recently opened catalogs or sessions or to create a new one, in C1 20 this seldom happens. But almost every time this new and unwanted catalog is created and opened automatically. Does anyone know what is triggering this and how to suppress it forever?

    I know I could right click on C1 in the dock and start with the latest choice of catalogs or sessions but I mostly forget about that and click the C1 icon instead and bingo I have another unwanted catalog.


    I notice same problem opening C1 20.

    first time this happend I got afraid all my images got lost ...
    0
  • Permanently deleted user
    I agree, it is getting annoying closing this catalog every time I start CO. It would be great to have a preference to disable this and start with the open/create dialog instead.
    0
  • Ian Wilson
    Moderator
    Top Commenter
    Several people have commented on this new behaviour in Version 20. Whether it happens partly depends on your habits when you close Capture One. I generally only have one Session or Catalog open at a time, but when I close the app, I just quit without closing the session or catalog first. Most of the time, I will want to go back to the same one next time. Then it opens that one when I restart the app.

    Ian
    0
  • Permanently deleted user
    Ian3 wrote:
    Several people have commented on this new behaviour in Version 20. Whether it happens partly depends on your habits when you close Capture One. I generally only have one Session or Catalog open at a time, but when I close the app, I just quit without closing the session or catalog first. Most of the time, I will want to go back to the same one next time. Then it opens that one when I restart the app.
    Ian


    Exactly not what happens here. It doesn't start with the last open catalog or session it starts with an empty new catalog that I don't want at all and the selection dialog is not presented.
    0
  • Ian Wilson
    Moderator
    Top Commenter
    AndyE wrote:
    Ian3 wrote:
    Several people have commented on this new behaviour in Version 20. Whether it happens partly depends on your habits when you close Capture One. I generally only have one Session or Catalog open at a time, but when I close the app, I just quit without closing the session or catalog first. Most of the time, I will want to go back to the same one next time. Then it opens that one when I restart the app.
    Ian


    Exactly not what happens here. It doesn't start with the last open catalog or session it starts with an empty new catalog that I don't want at all and the selection dialog is not presented.

    Yes but did you close Capture One without closing the session first (what I recommend) or did you close Capture One after closing the session? If it's the latter, and it still doesn't work right, I'd suggest contacting Support, because it seems to work fine on that method for me and others. (And did you close the unwanted catalog?)

    (I suppose it's a nuisance rather than a fatal error, if you have to close an unwanted catalog and open the session or catalog you really want. But I agree that it is annoying.)

    Ian
    0
  • Permanently deleted user
    Ian3 wrote:

    Yes but did you close Capture One without closing the session first (what I recommend) or did you close Capture One after closing the session? If it's the latter, and it still doesn't work right, I'd suggest contacting Support, because it seems to work fine on that method for me and others. (And did you close the unwanted catalog?)

    (I suppose it's a nuisance rather than a fatal error, if you have to close an unwanted catalog and open the session or catalog you really want. But I agree that it is annoying.)
    Ian


    Thank you Ian for clarifying. It exactly works like you described.

    But I just find the C1 opening behaviour very unhandy and illogical. Especially if one works with multiple catalogs and different sessions altogether.
    It's like you work with a Word processor. You mostly don't want to open the last document again next time you start the program and you also do not want an empty document created on each open. And that's why you get the template chooser for that you can choose exactly what you want.

    Therefore if C1 would let me choose on startup what I want that would be nice or at least let me toggle it somewhere in preferences.

    Andy
    0
  • Permanently deleted user
    When I created an empty new 'Capture One Catalog' last week, my CO 20 was disabled and I had to re-install.
    0
  • Alan Disler
    I always close open sessions before quitting C1 and still get an empty catalog when reopening C1.
    0
  • Ian Wilson
    Moderator
    Top Commenter
    Focuspuller wrote:
    I always close open sessions before quitting C1 and still get an empty catalog when reopening C1.

    Yes that's the point. If you close them all, you do get the default Capture One catalog next time.

    But if you close Capture One without closing every session or catalog, it should re-open next time to the same one that was open before. I never close them all first. Almost always, I only work on one session or catalog at a time, but I close the app without first closing the current session or catalog, and it opens for me in the same one. On the rare occasions when that is not what I want, I can hold down Alt while the app opens to be given the choice of what I want to be opened.

    Ian
    0
  • Ian Wilson
    Moderator
    Top Commenter
    Also see the new bug-fix release 20.0.1 released today. The release notes say it addresses this issue.

    Ian
    0

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