I hadn’t gotten far enough to create a second _display file but you make a great point about C1 being unable to overwrite files on export. I think the _display functionality is sort of a bandaid at this moment in time and while not ideal, it helps.
I think what would be best is if Mylio tried to look for the .cop file in the /Captureone/Cache/Proxies folder and leverage it as the preview rather creating it’s own preview from the raw. If you use Sessions, each time you “open with” a raw image in Mylio (selecting C1 as editor), the C1 Session looks at the directory for the file in question and automatically generates previews for every image in its folder (C1 creates that /CaptureOne/ folder and its children if they don’t exist). Thus, the C1 aware previews are already there for the taking , so-to-speak.
As far as I can tell, (and I could be wrong, wouldn’t be the first time ) Mylio would have to do two things to make C1 work a ton better with Mylio:
- Sync the /CaptureOne folder contents and C1 side car files (.cop, .comask etc). This would allow a user to move from one computer to another and continue editing in C1.
- Look for the .cop file (preview file) and if found, use it for the Mylio thumbnail/preview generation instead of the raw.
I think that’s it. That would eliminate the need for _display.jpg proxies.
Yes, like you said, I’d also add better support for variants. DXO has those too, DXO calls them “virtual copies”.