Skip to content

Conversation

@maiko3tattun
Copy link
Contributor

@maiko3tattun maiko3tattun commented Apr 29, 2025

Development Background:

  • In Windows, placing data in the Documents folder causes various troubles.
  • There is a demand to specify the location of folders with large data size such as Singers, Cache, and Resampler.
  • Confusion arises during user support because the data path changes depending on whether the installer was used or not.

Improvements:

  • Data path can now be changed/checked in preferences.
  • Check if the custom data path can be written to at startup and when the path is changed. If not authorized, fall back to the original data path.
  • The location of prefs.json has not been changed.
  • For now, it will not automatically move data when a path is changed.

@maiko3tattun
Copy link
Contributor Author

I understand that there are multiple opinions regarding the data path. Please consider this one of the suggested solutions.

@oxygen-dioxide
Copy link
Collaborator

I think we can follow what zotero does.
After changing data path, zotero won't autometically move the folder. It will show a dialog to tell user about this and exit.
image
image
image

OpenUtau should exit after changing data path, and use the new data path after the user launches OpenUtau the next time. because if data path is changed but the software is still running, voicebanks and resamplers may not work correctly.

@oxygen-dioxide
Copy link
Collaborator

Also users can use the changeable data path to separate their singers into multiple workspaces, because the more singer user installed, the slower OpenUtau launches.

@maiko3tattun
Copy link
Contributor Author

  • A message is displayed when the custom data path is changed.
  • Logs, Note Presets, and Backups are not moved to the custom data path.
image

@maiko3tattun
Copy link
Contributor Author

  • After selecting a custom data path, the dialog will no longer appear if the path remains unchanged
  • Fixed a bug where errors during preference loading were not logged

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants