-
Notifications
You must be signed in to change notification settings - Fork 78
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
Introduce #VOCALS #627
Comments
That's the most challenging change for the new song format, as it has impact on the game logic. I would split that into several parts, next to some preparations. Preparations:
Step 1: Playing multiple files in sync
Step 2: Add game logic for it
Step 3: UI enhancements
Complexity: L to XL. |
Love to see this feature 😊 I would suggest that Vocaluxe will have default filenames for #INSTRUMENTAL and #VOCALS, e.g. adding pre/postfix on the #MP3 filename. In case the two new tags aren't present Vocaluxe will try to fetch instrumental and vocals files based on the default name. The reason for that... when an user wants to split the vocal of an existing song he only needs to get the filenames right and no need to touch the existing TXT-file. |
@marwin89 are there some thought on a naming convention for these files in the spec? I like the idea of having them as this is a common thing for the most singing programs... |
@flokuep @bigboss97 , thanks for asking. yes we already defined a naming convention for these files in the spec in october 2023. I just forgot to mention it here. Here it is:
|
Thanks! I've added that to the issue description. |
Great! Please let me know when there's any test version ready, thanks. |
Suggestion:
#VOCALS: Artist - Title of the song [VOC].mp3
#INSTRUMENTAL: Artist - Title of the song [INSTR].mp3
(according to official common Song format Specification v1.1.0 - release on: 1th Dec 2023)
The text was updated successfully, but these errors were encountered: