-
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] #AUDIO as alternative to #MP3 to specify audio file #21
Comments
I would favor the support for #AUDIO (in addition to #MP3 for backwards compatibility). If USDX and others implement support, they could convert #MP3 to #AUDIO on save. The Syncer could convert it as well, but ideally usdb would support it as well so that it’s adoption spreads. (related: why not use #VOCALS and #INSTRUMENTAL instead of the longer #VOCALAUDIO and #INSTRUMENTALAUDIO?) |
#VOCALS makes no sense to me. It's just #AUDIO, #MUSIC, #AUDIOFILE. |
This discussion has its own issue: #20 Please use this issue here only for "#AUDIO as alternative to #MP3". |
Thanks for your discussion. So we have a consens here. ✅ I've put #AUDIO to the Overview Version spreadsheet mentioned in #31 . |
Lets write a conclusion as the completed message so it doesnt get lost in translation :) |
SUMMARY / FINAL RESULTS 🏁So here are the final results for this issue. We add this tag in version 1.1.0:
We deprecate this tag in version 1.1.0:
#MP3-Tag will be removed in version 2.0.0 (probably in 1-2 years). The description in the spec (website) is:
|
Suggestion
Historically, the
#MP3
header field is used to specify the audio file.However, mp3 files are not the only supported audio format.
Thus, one could argue that
#AUDIO
would be a better name for the field.But this could only be done as an alternative to
#MP3
to not break compatibility with the thousands of existing txt files.So there is no clear winner:
What do you think?
Use case
For newbies and tutorials, it might be more intuitive to use and show #AUDIO instead of #MP3.
But it is only a minor issue.
Extra info/examples/attachments
No response
The text was updated successfully, but these errors were encountered: