I’m a new Mylio user, really new, but a 25 year IT veteran, semi-pro photographer and long time CaptureOne Pro aficionado. I’m experimenting right now with some workflow options using Mylio as the tail end to my existing CaptureOne Pro workflow. My goal is to get a Mylio library going which is sort of a ‘best of the best’ from my piles of images in CaptureOne.
Right now it looks like this:
I often capture images using a CaptureOne Pro “session” (C1 supports both Sessions and Catalogs. A Session is meant to be used for a project or assignment, tethered or not tethered. I use Sessions for tethered headshot sessions, a vacation week, a family shoot, a sports event etc.). They are handy because all the edits and raws are kept within a single folder structure, making it easy to copy and move.
I can’t see making Mylio my raw processor for a number of reasons. Mainly I’ve grown to love the power of C1’s tethering ability and it’s extensive sets of editing tools (layers with masks, color management controls, curve tool with luminosity option, etc, etc). I do use Affinity Photo for certain edits outside of C1. I also have DXO Photolab which is also very powerful. I often take advantage of “bulk edits” where I can take, say, a white balance on one photo and paste it across multiple others rapidly so I’m not inclined to start in Mylio and go to an external editor one at a time.
I want to leverage Mylio as my “extended Portfolio” or my “catalog of keepers” . The goal is to render high quality jpgs to a new folder structure monitored by Mylio. Then have that catalog available on a few devices at all times.
Typically I will shoot a C1 Session (say a headshot session with 100 images). I will then whittle it down to 4 or 5 keepers that I send to a client. My keepers will have three stars and above.
Then I will run an output batch process to send ONLY the keepers (3 stars or more) to a folder structure monitored by Mylio. Mylio will get a JPG from C1 with all edits at a reduced size but big enough for viewing on most monitors.
C1’s output module is highly programmable, (they are called “process recipes”) and my plan is that the filename of the jpg landing in the Mylio folders will include where the processed image came from (camera filename, the C1 Session name and folder). This way, if I’m ever in Mylio and need to go back to the RAWs (perhaps to print, or maybe to reprocess), I know exactly where it resides. In that scenario, I would re-edit the RAW in C1, and re-export it to Mylio folders with a few clicks using a “process recipe”.
I understand I am not taking advantage of Mylio’s raw processor and ability to invoke external editors. But I feel this let’s me take advantage of my existing image editing tool (with the best tethering out there) while providing an “on every device” gallery or portfolio of my images. (For example, I shoot some sporting events sometimes where I may shoot 2,000 images in 3 hours and cut it down to a dozen “winners” that I’d send to Mylio).
So far I like how it’s starting to look (but all this is subject to change). I will probably use Mylio editing to some extent, mostly for my iPhone shots and other personal jpgs I send to the Mylio folders.
It’s not perfect but I’m able to go into C1 and filter to see all the images I sent to the Mylio folders based on some keyboarding I do.