Repository navigation
.LRC File Name Convention #314
mandrews79
started this conversation in
Ideas
Replies: 2 comments 3 replies
3 replies
|
Thank you. I’ll give that a shot tomorrow.
On Sunday, August 16, 2026, 3:03 PM, jayfunc ***@***.***> wrote:
{Artist} - {Album} - {TrackNo} - {Title}
Try this pattern.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS and Android. Download it today!
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment


Uh oh!
There was an error while loading. Please reload this page.
The .LRC file name convention of "Artist - Name.lrc" does not work in all instances. For example, if an album has a song name listed twice, while rare, this means that you can't have separate .lrc files for each one. Also if a user stores all of their songs for an artist in a single folder with no subfolders for albums, if there are duplicate songs names due to LIVE versions of the the songs, then this naming convention also will not work. My naming convention is "Artist - Album - Track # - Name". If this could be user configurable, that would be great! Right now, I use LRCGet to automate finding and downloading the files to my folders, but LRCGet unfortunately uses the same naming convention as my music files and thus I then have to mass rename thousands of files each time I want to check to see if LRCGet finds new synced files. Not a huge deal, but would be nice to self define this.
All reactions