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

Session becomes empty

Comments

5 comments

  • SFA
    No idea what is going on but I really don't think you are getting the full benefit of sessions from the process you have described.

    I would assume that Windows/C1 is trying to keep up with 'last used' and struggling.

    If you only ever use a single session you could put a shortcut link to the .col70 file on your desktop (.col50 for version 5 and 6) and simply start the whole C1 interaction from there.

    Would that work for you?

    Grant Perkins
    0
  • Raymond4
    I don't know, I will try this. The settings obviously get lost as my "developed images" should go to a folder I call "processed", but after getting things back new developed images finish up in C1's "output" folder. I have worked with this from v3.6 to v6 no problems - ever. So somehow v7 is losing information when closing.


    Ray
    0
  • Raymond4
    I stated C1 from the cosessiondb file - worked ok but now i cannot get C1 to remember my output location - defaults to "output" when reopening.

    I think a reinstall is called for - do I have to deactivate then reactivate on install, to do this?
    0
  • jonpaul
    Raymond4: RE your statement: "I use ...just one unamed "Untitled Session""

    This is a very bad practice. Go to the session folders with a file manager like Ultraexplorer, and you will see the amazing mess of files and the size of it!

    According to P1 support, each session has data accumulated on every change to ever image recorded and grows amazingly as you continue to use it. The very long and complex file structure thus created is bound to cause many problems.

    You should open an new session EVERY TIME you you start a project or shoot, or at least daily or weekly.

    I wonder if P1 experts can add to my comment?

    Kind Regards,


    Jon
    0
  • Raymond4
    Thanks. I do realise this but I use C1 purely as a raw converter and clear out the session when done, moving stuff to 'selects' and deleting the rejects. My problems have occurred with very little use of ver 7.0.2. I used ver 6 (and ver 7 trial, 7.01 no problems.
    I have deactivated and completely removed all trace of v7.0.2, then performed a fresh install to my 'D' drive. However C1 has created it's default session on my ssd where I don't really want it, so I will be creating a new session on my 'D' drive (if I can)

    The fresh install has repaired the issues I have been suffering. I will take on board yours and other advice re. new sessions for each job, but will wait to see if problems reoccur so that I can maybe identify any particular instance that might be causing them.

    Ray
    0

Post is closed for comments.