Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Formatting of Song Name in Track Name #5

Open
SJ02 opened this issue Oct 14, 2024 · 2 comments
Open

Formatting of Song Name in Track Name #5

SJ02 opened this issue Oct 14, 2024 · 2 comments

Comments

@SJ02
Copy link

SJ02 commented Oct 14, 2024

Robust results seen here for your resolution of Issue #4. I was able to drag the entire set of over 1400 .mid files directly into Ableton Live and they landed there successfully! Thanks kindly for this, and it's great that your pipeline accommodates such efforts.

Snag_26749a

As the pic above shows, the files show up with clip names like so:

"Chord track for "+ACTUAL_SONG_NAME+".musicxml"

I'd like to advocate for making that simply ACTUAL_SONG_NAME , no more, no less.

ACTUAL_SONG_NAME is the information needed, and the rest is irrelevant and actually undesirable because a) it takes up real-estate, and b) if the user wants to edit it out then there is a huge manual job involved in trying to do that.

For those reasons, I think merely ACTUAL_SONG_NAME would be the best choice of output (and resulting clip names) here.

Alternatively (and a 2nd choice IMO), this would be possible:

ACTUAL_SONG_NAME+".chords" or very similar.

Moving ".chords" to the trailing position does allow the column width in Live to be narrowed down so that ".chords" is not visible and taking working space away from the rest of the Live UI. Still though, I see no real advantage in carrying the extra text in clip names. The fact that a column of clips contains the chords is sufficiently and succinctly expressed by the user applying a single column title such as: "Song Chords" or "XML Import Chords", or whatever is desired.

Thanks for considering this request.

@SJ02
Copy link
Author

SJ02 commented Oct 14, 2024

I'll add that the text "Chord track" is in-itself problematic because in DAWs (e.g. Cubase, Studio One) the 'Chord Track' is a very specific thing - it's own animal for sure. One doesn't want a track of imported note data to carry the same designation as the one-and-only actual 'Chord Track'.

@infojunkie
Copy link
Owner

Thanks for your feedback. As it's impossible to come up with a name that would satisfy every conceivable usage, I will keep the current name unchanged. I will revisit this request in the future for a way to customize the MIDI output more broadly.

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

No branches or pull requests

2 participants