Where Does Denemo Store Templates and Prefs?
Where Denemo keeps templates, prefs and downloaded commands on Linux and Windows, and which folder is versioned.
Last updated
Denemo keeps user state in a versioned home folder with templates, prefs and downloaded commands inside. The folder name carries the app version, so upgrades create siblings rather than overwriting. A startup score and a new score template serve distinct roles at launch.
System wide commands ship in the shared tree apart from user data. That split means user backups stay small while studio installs need no per user seeding. Check the version token in the folder name before scripting restores. Keymaps and score directives travel with the versioned home, so copy it whole.
Where Denemo stores this, by platform
~/.denemo
Versioned home with templates, prefs and downloads inside. Folder name carries the app version. System commands ship separately in the shared tree.
%USERPROFILE%\.denemo
Versioned home with the prefs file carrying the LilyPond path entry. Templates and downloads mirror the Linux layout. Match versions before restoring.
Frequently asked questions
How do I set a default Denemo score template?
Create a templates folder under the Denemo home for your OS and save a score as default there. New scores opened with the shortcut read that template first. The startup score in the home folder serves a different first launch role.
How do I move Denemo settings to a new machine?
Copy the versioned home folder with its prefs file plus the templates and download children. System wide commands ship separately in the shared tree and need no backup. Match Denemo versions on both ends before restoring.
Notice an outdated path? Let us know.