r/composer • u/Opus-Pocus • 12h ago
Discussion Composers: how do you organize your music, project files, and different versions of your compositions?
Hi everyone!
I'm a composer, primarily writing piano music, and I'm currently developing an application designed to help composers organize and keep track of their musical works.
Before going further with development, I'd like to understand how other composers actually organize their work.
One thing I've noticed is that every composer seems to have their own workflow.
Some use notation software such as MuseScore, Dorico, or Sibelius. Others primarily work in DAWs such as Cubase, Logic Pro, Reaper, or Ableton Live. Some combine several applications, while others still compose mainly on paper.
I imagine these differences have a significant impact on how we store our compositions, project files, exports, and previous versions.
I'd love to hear about your workflow, particularly regarding the following questions:
1. What software or tools do you use to compose?
Do you primarily use notation software, a DAW, handwritten scores, or a combination of different tools?
2. How do you organize your compositions on your computer?
Do you maintain a main composition library? Create one folder per piece? Organize your work by genre, year, album, opus number, or something else entirely?
3. How do you manage different versions of the same composition?
When you revise a piece, do you create a new project file every time? How do you know which version is the most recent or which one you should continue working on?
4. How do you manage the different files associated with a composition?
For example, project files, scores, audio exports, MIDI files, recordings, videos, reference material, and other related documents.
5. How do you find an older composition when you want to work on it again?
Do you usually remember where everything is stored, or do you sometimes find yourself searching through multiple folders to locate the right file?
6. What are the biggest problems with your current system?
This could include organization, backups, inconsistent file naming, multiple revisions, returning to unfinished projects, or anything else.
7. If you could improve just one thing about your current workflow, what would it be?
Just to clarify, I'm not here to promote or sell my application. I'm still trying to understand how composers work and what problems they actually encounter.
My goal is to avoid building a tool that forces everyone into a predefined organization system.
I'd rather understand existing workflows first and eventually design something flexible enough to accommodate different approaches to composition.
I'm interested in hearing from everyone, whether you're a professional composer, hobbyist, student, or someone just starting to write music.
You don't have to answer every question. Even a short explanation of your workflow, or an anonymized example of your folder structure, would be extremely helpful.
Thanks in advance for sharing your experiences!
2
u/David_Maybar_703 12h ago
That's a lot of questions. LoL I start my composing in a variety of ways. If I use my iPad, I use Symphony Pro to record the parts and import them into Finale. If I sketch out a score free hand I use Smart Score and import the result into Finale. If I hum out a phrase, I use Celemony Melodyne to ... you got it, import into Finale. I come up with a working title based on the mood of the piece then add other data. For example, Autumn_Bb-maj_95bpm_piano_concerto as a title tells me what I need to know. I have a folder called WIP for things that I'm actively working on. When the composition gets to the point that I am thinking about producing it as finished peace, I create a folder with the name of the composition. Then, within the folder, I have subfolders for things like score, music XML files, renders, Etc.
2
u/Opus-Pocus 12h ago
Haha, yes, sorry for all the questions!
Thank you for taking the time to explain how you work. :) It's really interesting, especially the way you use different programs before bringing everything into Finale. i also find your WIP folder system interesting. Keeping everything in one place while you're working on it, then creating a proper folder once the composition is more advanced, makes a lot of sense. i'm currently working on a composition manager, and I'm trying to understand how other composers organize their work. I have just one more question, if you don't mind! :D How do you manage different versions of the same composition? Do you keep them all in the same folder, or do you have another way of organizing them?
Thanks again for your help!
2
u/StudyStrict2385 12h ago
i use musescore studio.
i organize my compositions based on categories (nature, animals, playtime, etc.)
i make a new project file and delete the older one, so that i can keep on coming up with new ideas to improve it. or i can keep the older file and re-use the ideas from that file.
i only use the management method for stems.
i just look at the score.
i have the composition audio in separate folders (organized by version) and the sheet music (organized by type). if i were to make one folder per composition, it would turn into a mess.
it's how i organize my music. (because it now seems to be a mess, especially with my arrangements.)
1
u/Opus-Pocus 12h ago
Thanks for your reply!
It's really interesting to see how differently composers organize their work. I'm starting to notice that it varies a lot from one person to another, and probably depending on the style of music they compose too. :) For example, in my case, I mainly compose classical music, and I organize my compositions first by musical genre, then by opus number. That's actually why I'm asking these questions. I'm working on a composition manager, and I'd like it to adapt to the way each composer works, rather than forcing everyone to use the same system.
Thanks again for taking the time to explain how you organize your compositions! :)
1
2
u/goesonelouder 10h ago
Use what works best for you
Folder with Project name -> Folder ‘In Progress’, Folder ‘Completed’ ->
In Progress -> Folder ‘Piece 01’ containing project files saved as v1.1, v1.2 (saved after some progress is made), v1.3 etc. if it’s a complete redo in the same vein then v2.1, v2.2, or scrap it and begin another.
Keep all files for the same project in the same project folder, if there’s files for different DAWs then each DAW has its own folder within the ‘main’ project folder. Makes organisation simple as well as backing up.
1
u/Specific_Hat3341 9h ago
I primarily use Dorico. I've also used Cubase sometimes. I don't handwrite scores; I only handwrite for sketches or working some things out.
I don't. Dorico does. Every project automatically gets a project folder and the files go in there. Backups are created automatically too.
If I want to keep an earlier version, or if I'm still processing things and want to try out different ideas, I'll just duplicate the flow, or create a new flow, and then toggle flows on and off while I compare them. I absolutely wouldn't create another whole project file. Once I've finally made a decision, I don't normally keep earlier versions of anything, so usually I clean things up by deleting the rejected flows.
The Dorico files all get stored automatically. Audio exports or PDFs sometimes get stored on my desktop while I'm still using them, and then stashed away into a compositions folder later. Sometimes I might even just delete them.
I just search in the Dorico hub.
I don't really see any problems with my workflow. Maybe it could get a little unwieldy if I liked to keep a lot of earlier versions of things, but I don't.
Again, I can't think of anything.
1
u/ClarSco 5h ago
Don't do much composing, but do quite a bit of arranging/orchestration and editing/engraving work:
- Dorico as my primary driver, Sibelius/Musescore if needed for collaboration purposes. DAWs are not an important part of my workflow.
- "Live" project files in a monolithic folder, that follow the following naming convention:
<ARRANGER_LAST_NAME> - <Project Title>.ext. Will prefix with ensemble's initials and the librarian's assigned catalogue number, if applicable. I also prefix my own works with a single underscore so that they're kept separate from my clients' files. - I frequently duplicate the project file, and export a musicXML file and PDFs of the scores and parts (and sometimes an audio mockup) from that duplicate. Append the export date in /r/ISO8601 format to all files then compress them into a
.ziparchive file. I periodically review these and delete versions that are of no use. - All exports match the base filename of the project file, with additional info (eg. part index+part name) tacked on the end in a consistent manner where necessary. Exports intended for delivery will be renamed if the Initial Project Title and Work Title have diverged, or the client wishes me to follow their preferred naming conventions.
- Monolithic folder as mentioned in #2, but with an "archive" subdirectory (not compressed) holding any files not worked on in over a year to cut down on clutter (I used to further divide the archive by year, but found all that did was make it harder to find what I was looking for if I've forgotten the project title).
- Most notation software does a poor job of handling file metadata, particularly on PDF and audio exports. As a result, it often gets clobbered by email programs or cloud services such that instead of the true creation/export date, you get the date it was last sent or downloaded.
- I'm pretty happy with my current workflow. Most of the heavy lifting (batch renaming files, backups) is handled by existing free (and ideally open source) software. The only thing that would make it easier is if I had git-like version control at my disposal, but the applications/project files are the blocker on that due to them being binary blob-based rather than text-based (MusicXML is text based, but not a reliable enough source to be using for version control purposes, again due to the applications themselves).
2
0
u/WalkingEars 10h ago
Did AI write this?
Assuming it’s a human post and not a marketing research or content farming thing, much of the time I just name pieces after the day I started writing them, and every 6-8 months I go back through recent compositions and assess them, picking out the good ones to release. I recently made a Google Drive to backup all audio files and musescore files by year. I think it all works pretty well for me. Naming pieces after dates makes it sometimes hard to remember which is which but I don’t like coming up with titles and am a hobbyist so who cares if the names are boring lol.
5
u/tronobro 11h ago
I'll answer a couple of your questions.