Reply to thread

Message: [QUOTE="Bombastus, post: 92261, member: 2178"] Difro 1.2.0 now puts key and scale information into filenames for MIDI clips dragged out of the app or saved as bookmarks. Exported MIDI also gets more readable filenames, which matters once generated ideas start piling up outside Difro. A useful clip is much easier to recognize when its name carries musical context instead of looking like another anonymous export. The wording of the update deserves a careful read. Initial Audio says key and scale are saved in the filename, not that Difro writes or updates the Standard MIDI File key-signature event inside every exported clip. MIDI can carry a key-signature meta event, but the new feature should be treated as visible file naming unless Initial Audio documents something more. [HEADING=2]Readable filenames matter once MIDI leaves Difro[/HEADING] Difro already lets you bookmark generations, assign categories, and open the bookmark folder on your hard drive. Version 1.2.0 makes that folder more useful because a filename can now tell you something musical before you reopen the app. The same advantage follows a clip when you drag it into a DAW, copy it into a project folder, or keep it with a personal MIDI collection. This is the practical value of [B][URL='https://goldmidi.com/community/threads/initial-audio-has-refreshed-difro-1-2-0-with-midi-tools.77644/']Difro’s clearer MIDI file naming[/URL][/B]. A producer comparing several saved ideas no longer has to rely entirely on memory, waveform-free file browsers, or repeated imports just to remember which clip belongs to which tonal setting. The gain is small per file and much larger once you have dozens of variations from several sessions. Good filenames also survive software boundaries better than app-specific organization. A bookmark category helps while you are working inside Difro, while the filename remains visible after the file has been copied elsewhere. A [B][URL='https://doi.org/10.3233/SW-210446']MIDI metadata retrieval model[/URL][/B] was developed around the broader problem of weak metadata in large symbolic-music collections, where missing descriptive information makes retrieval harder. [HEADING=2]Key and scale labels are context, not permanent truth[/HEADING] A filename is only correct for the state it describes. Transpose the exported notes in your DAW, reharmonize the phrase, or merge it with another clip, and the original key or scale text does not update itself. Keeping the old name after a major edit can turn useful metadata into a quiet source of confusion. Standard MIDI files can contain a key-signature meta event, but even embedded metadata should not be confused with the note data itself. A key label does not force notes into a scale, and changing descriptive information does not automatically rewrite the performance. Difro’s new filename behavior is therefore best understood as identification rather than musical enforcement. This distinction becomes important when you reuse clips months later. Seeing Am or another tonal label in a filename can narrow the search quickly, but you still need to audition the phrase against the current harmony and inspect the notes if the arrangement has changed. File naming helps you find the candidate; your ears and the piano roll still decide whether it fits. [HEADING=2]A useful filename should survive outside one project[/HEADING] Difro’s automatic naming gives you a stronger starting point, but it does not need to carry every detail of your production. Key and scale are useful search cues, while your own additions can identify musical role, project, or revision when those details matter. Names such as Hook_Am_v03.mid or VersePluck_Cmin_v02.mid stay readable without becoming miniature session logs. Avoid replacing meaningful automatic information with names such as good.mid, new2.mid, or finalfinal.mid. Those labels work for a few minutes because the project is fresh in your head, then decay quickly when files move into a larger collection. Keeping tonal information alongside a short role and version marker makes later sorting less dependent on memory. Bookmarks deserve the same discipline. Difro’s categories can separate keepers while you generate, but the hard-drive folder becomes the long-term handoff point once the files leave the immediate session. Retaining readable filenames means the organization still makes sense in Finder, File Explorer, a DAW browser, or a backup folder without requiring Difro to reconstruct the context. The new naming behavior is most useful when you resist treating it as decoration. Preserve the key and scale label when it still describes the clip, rename it after substantial harmonic edits, and add only the identifiers you will genuinely search for later. Clean filenames will not improve the melody itself, but they can stop a good one from disappearing into a folder full of nearly identical exports. [/QUOTE]

Name