-
Notifications
You must be signed in to change notification settings - Fork 2
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
[Spec] Add #VOCALS and #INSTRUMENTAL #20
Comments
from @bohning
Good question. So yeah, #VOCALS and #INSTRUMENTAL would make sense I only wanted to keep a reference to the #AUDIO field (although it is called #MP3). But now that I think about it, the AUDIO prefix is probably redundant. |
I guess you mean suffix, not prefix, but yes, for me vocals and instrumental imply audio. |
Hmmm what are we going to do with all the instrumental songs out there? (there's quite a lot on ultrastar-es) I'm all for including them both as it'd make for a way better integration than center muting the vocalized song... (current behavior in performous, its not bad, but far from great either...) As for popularity, most people would want to sing with vocals so they can match their singing to the original songtrack. Far less people are confident enough to do the instrumental versions as what i have experienced in the last decade |
#VOCALS makes no sense to me. It not says that it should contain the background sound. We should anyway mark Karaoke as Karaoke. So, then it should be ok to also split the files/folders. |
Now you got me confused. I would say that the full song is AUDIO, consisting of VOCALS (the singers voice(s)) and INSTRUMENTAL(S). So AUDIO would have the mixed signal of VOCALS and INSTRUMENTALS. In an ideal situation, the karaoke software could handle the mixture of the two on the fly (one player wants to sing real karaoke -> VOCALS: 0%, INSTRUMETAL: 100%, another player wants to sing pure sing-along -> VOCALS: 100%, INSTRUMENTAL: 100% and a third one wants is in between -> VOCALS: 50%, INSTRUMENTAL: 100%). Then the AUDIO would not be needed anymore, but 1. since this is not yet available in software and 2. the (automated) separation of the mixed signal is or may not be perfect, I think all three should be provided - the mixed AUDIO (or #MP3) as has always been the case, the VOCALS and the INSTRUMENTAL track. Or did I understand something wrong? |
If we can support all 3, then it should be good. |
Yes, this is exactly what I have in mind.
I agree. |
Cool we have a consens here too. 🎉 ✅ I've put #VOCALS and #INSTRUMENTAL to the Overview Version spreadsheet mentioned in #31 . |
Lets already come up with the description of the specified tags so this doesnt get lost within the issues. Aka i miss the conclusion in a single post :) |
SUMMARY / FINAL RESULTS 🏁So here are the final results for this issue. We add these tags to version 1.1.0:
The description in the spec (website) is:
|
Have |
Good point. I guess the most consistent would be #VOCALS (for non-duets), and #VOCALSP1/#VOCALSP2 for duets (extensible to any number of singers #VOCALSPx). |
@bohning yes that would be good. |
Let's discuss this in another issue. This could be something for v1.x.0 later. |
I doubt that this is a valid use case.
|
Suggestion
Melody Mania uses two new fields
to specify separate audio files for vocals and instrumental.
These files are created from audio separation AI model, e.g., Spleeter
I think it makes sense to add these fields to the format.
Note that I suggest to use AUDIO instead of MP3 in the tag name.
This emphasizes that also other audio formats (e.g. ogg) are possible.
Use case
It is used in Melody Mania to change vocals volume when singing a song.
This way players can decide how much of the original vocals they want to hear.
Further, the vocals audio is used in the Melody Mania song editor to
Extra info/examples/attachments
No response
The text was updated successfully, but these errors were encountered: