Skip to main content
Participating Frequently
December 5, 2023
Open for Voting

Advanced time-based automatic saving with version management

  • December 5, 2023
  • 14 replies
  • 1682 views
  1. Automatic Save Interval Setting: Users can set the application to automatically save their work at regular intervals, such as every 5 minutes.

  2. Version Management:

    • Short-Term Versions: The application will keep the most recent 10 versions saved at the short-term interval (e.g., every 5 minutes).
    • Long-Term Versions: In addition to short-term versions, the application will also save at a longer interval, such as every hour. From these hourly saves, the application will maintain a separate set of up to 10 versions. This ensures that users have access to not just the most recent changes, but also to versions from earlier in their workflow.
  3. Save Location Selection: Users should be able to choose where these versions are saved, such as on a local folder, network drive, or cloud storage.

  4. User Customization: Users should have the flexibility to adjust the number of versions saved both in the short-term and long-term intervals, depending on their specific needs and storage capacity.

This feature is designed to provide comprehensive version control, allowing users to revert to earlier stages of their work easily while also protecting against data loss due to unforeseen issues or errors in recent edits.

14 replies

Participating Frequently
December 6, 2023

"Cloud storage already has versioning."
We know. It seems you haven't read the post thoroughly. I think the least you could do is read it before responding or commenting. I specifically mentioned this, knowing that it would be the starting point for many, which obviously isn't the solution but rather an alternative that only works for a few. But I'll write it again, what I've already mentioned once:

Additional Consideration: Limitations of Creative Cloud for AutoSave Feature

While Creative Cloud offers numerous benefits, there are scenarios where it may not be the ideal solution for the AutoSave feature. These scenarios include:

  1. Offline Work: Users working without an active internet connection would be unable to utilize cloud-based auto-saving, making a local save option essential.

  2. Slow or Limited Internet: In areas with slow or limited internet connectivity, uploading multiple versions to the cloud could be impractical and time-consuming.

  3. Traveling Users: For users who frequently travel, reliable internet access might not always be available, necessitating the need for robust offline saving capabilities.

  4. Large File Handling: Working with large files, such as high-resolution images or complex graphics, may require faster storage solutions like PCIe SSDs for efficient saving and versioning. Uploading these large files frequently to the cloud could be inefficient and resource-intensive.

  5. Storage Concerns: Users might be cautious about uploading numerous versions to the cloud due to storage limits or data privacy concerns. Local saving options provide an alternative for managing large numbers of file versions.

In light of these considerations, it's crucial for the AutoSave feature to offer flexible saving options, accommodating both local and cloud storage, and allowing users to customize their saving preferences based on their specific needs and circumstances.

D Fosse
Community Expert
Community Expert
December 6, 2023

Cloud storage already has versioning.

 

What bothers me about any automatic saving is this simple question: save where? This is a recipe for an unholy mess. I certainly don't want anything automatically saved back to the same location - that's most likely not where I intend it to be. Maybe a separate folder on your desktop, where you can see it. Temp directory wouldn't work here - it would fill up people's drives faster than you can say "scratch disk error".

 

An alternative would be to not initiate until you had already saved it once - but then you're already going with incremental saving and all you need is ctrl+S.

Participant
December 6, 2023

+1

Participating Frequently
December 5, 2023

Additional Consideration: Limitations of Creative Cloud for AutoSave Feature

While Creative Cloud offers numerous benefits, there are scenarios where it may not be the ideal solution for the AutoSave feature. These scenarios include:

  1. Offline Work: Users working without an active internet connection would be unable to utilize cloud-based auto-saving, making a local save option essential.

  2. Slow or Limited Internet: In areas with slow or limited internet connectivity, uploading multiple versions to the cloud could be impractical and time-consuming.

  3. Traveling Users: For users who frequently travel, reliable internet access might not always be available, necessitating the need for robust offline saving capabilities.

  4. Large File Handling: Working with large files, such as high-resolution images or complex graphics, may require faster storage solutions like PCIe SSDs for efficient saving and versioning. Uploading these large files frequently to the cloud could be inefficient and resource-intensive.

  5. Storage Concerns: Users might be cautious about uploading numerous versions to the cloud due to storage limits or data privacy concerns. Local saving options provide an alternative for managing large numbers of file versions.

In light of these considerations, it's crucial for the AutoSave feature to offer flexible saving options, accommodating both local and cloud storage, and allowing users to customize their saving preferences based on their specific needs and circumstances.