What problem do you see this solving?
Capture One starts by default with the most recent session opened - this might be problematic as it changes timestamps on its .cosessiondb file and would be an unnecessary use of resources, if not planning any work on it.
When was the last time you were affected by this lack of functionality, or specific tool?
Just now - I noticed that I don't have any dummy/test sessions available locally, only the big ones, which I don't want to open.
Are you using any workarounds or other solutions to achieve your goals in Capture One?
There is supposedly a key that switches Capture One into Most Recent mode while holding during startup, but I don't remember it, don't know how to recover that info, and it's not a safe approach anyway, as it is an override of an already ongoing process - and this override might fail, so a better option would be to start application with the explicit target "Create a new session".
Another option is an instant kill to trigger the "crash failsafe".
As a workaround could be considered a startup setting like in https://support.captureone.com/hc/en-us/community/posts/14710415218717-Capture-One-startup-behaviour-settings-option , but if I had opening most recent enabled, disabling it would be possible only through editing settings file manually, as I could not access GUI obviously. My request is to have a CLI parameter, shortcut or a "Task" (this is apparently how Windows Start Menu calls RMB menu extra options; they are most common on internet browsers) that says "Create a new session..."
Are you happy to be contacted further about this suggestion or request?
Please sign in to leave a comment.