For me, it's every time I travel with my laptop and then every time I return back to my desktop.Īre you using any workarounds or other solutions to achieve your goals in Capture One? that are not the same in my other licensed installation. If your feedback is more general, simply let us know how much your workflow is affected.Įvery time I switch systems and find settings changes, new recipes, new styles, etc. When was the last time you were affected by this lack of functionality, or specific tool? Some preferences may be system dependent and should perhaps not be synced. Note: A thoughtful implementation would examine every user preference separately in nfig to decide if it should or should not be synced. If the perpetual license client stops paying the add-on fee, then all clients would just continue to work fine without syncing. This could be offered to perpetual license users for a small annual add-on fee of like $25/yr (defensible and logical since there's a hosted component to it) and included in a subscription (would offer further incentive in favor of a subscription). If a need for data encryption beyond https transport is envisioned (I'm not sure there's anything that warrants encryption in these settings and it should only be accessible by the license holder anyway), the data could be encrypted with an encryption key derived from the license key. If a client is working offline, they will function just fine with the last set of settings that they have, but will queue up any changes to be sent the next time the client is online. When any licensed product modifies anyone of the synced settings, that delta can be pushed to the hosted repository (as a single setting change only, not sending everything to minimize the chance of concurrency issues). Though there are many ways this could be implemented, but for maximum user simplicity, this is envisioned using a hosted service by Capture One such that when a licensed product starts up, it queries the hosted service for any updates and downloads and applies any changes (since last sync) pushed to the preferences service from other clients using the same license. This can be a user preference whether you want settings synced or not (defaults to "on"). Note, all this stuff is saved in /users/username/AppData/Local/CaptureOne and /users/username/AppData/Local/Capture_One (on Windows), but you don't want to sync everything there because you should NOT sync some of the things that are there like /ImageCore, /MSALCachexxx, /Logs, /Batchxxx. Clearly you don't want a default workspace from iPad overwriting a default workspace from a 30" desktop, but if each client's workspace was saved separately as a separate name, there would be benefit to have them all available at any time, particularly if you use multiple systems of similar monitor size (such as multiple desktops, perhaps home and work) where you might like to maintain the same workspace in each. It is not clear if workspaces should be synced or not. import settings and saved import recipes.This would provide you these same items across all your licensed installations: This can be solved by implementing automatic synchronization of the user profile/settings for multiple computers (laptop, desktop, mobile) all on the same Capture One license. You set up a great rename strategy upon import in one and it's available on the others and so on. You create a new Export recipe in one and its not available the others. You add a custom keymap in one and it's not available in the others. The general problem is that you have multiple licensed copies of Capture One (laptop, desktop, mobile) and they all have their own customizations that are different and time consuming to try to keep the same. Think about what it is that you're trying to achieve, and the reason why you are trying to do it. Describe the problem or issue you are having in Capture One.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |