Guest
home
beatmaps
rankings
community
store
help
forum
  1. Forums
  2. Beatmaps
  3. Mapping Discussion
  4. Ranking Criteria

[Audio] Specify that only Vorbis works for .ogg

posted
Total Posts
8
Okoayu
Nomination Assessment Team / Elite Nominator
4,956 posts
Joined May 2012
Topic Starter
Okoayu
Basically https://github.com/ppy/osu-wiki/pull/12187#issue-2541044644

I dont 100% like that wording but at the same time can't really say it's wrong or anything
**...use the `.mp3` or `.ogg` file format. `.ogg` files must be encoded in Vorbis**

But at the same time it's not wrong and until we rearrange the section that should do. Any objections?
lewski
1,324 posts
Joined September 2014
lewski
just tried to import an Opus OGG into stable and it was super broken, probably worth it to specify Vorbis since it only takes like 7 extra words and makes the codec restriction 100% clear

do must be encoded with Vorbis or must use Vorbis encoding feel any better than the PR's wording? also missing period at the end, touhou reference
RandomeLoL
Nomination Assessment Team
222 posts
Joined September 2015
RandomeLoL
Personally, I think the addition of this in the RC is indifferent. Whether something is game breaking or not seems to be outside the scope of the Ranking Criteria. What the game does or doesn't support shouldn't be all specified in here. There are a plenitude of audio and video formats that could theoretically fit in the allowed containers that the game doesn't support.

Would be redundant information at best - if something is game breaking, users should know of it at the time of submission, not when they're in the process of ranking their sets. Any beatmap can encounter these issues, whether they're going to be ranked or not.
McEndu
1,161 posts
Joined March 2019
McEndu

RandomeLoL wrote:

Would be redundant information at best - if something is game breaking, users should know of it at the time of submission, not when they're in the process of ranking their sets. Any beatmap can encounter these issues, whether they're going to be ranked or not.
I don't think BSS will ever care about audio formats, only the client which needs to play back audio will.

The term "file format" in the filename suffix sense is somehow ambiguous, as the suffix generally only implies the container format which can support many audio or video codecs. IMO it is better to specify the audio codec directly, with the expected filename extension in parentheses:

...be encoded in MP3 (.mp3) or Ogg Vorbis (.ogg).
clayton
1,917 posts
Joined November 2013
clayton
mcendu's suggestion seems good to me
Last edited by clayton , edited 1 time in total.
RandomeLoL
Nomination Assessment Team
222 posts
Joined September 2015
RandomeLoL
Think it's a good compromise. Though still believe this information (re; allowed encoders and other audio/video formatting shenanigans) should really get their own article and not be bound by the scope of the Ranking Criteria alone.
clayton
1,917 posts
Joined November 2013
clayton
there are other references to ".mp3" and ".ogg" that should get the same treatment in this PR I think. also ".wav" (-> "LPCM (.wav)" if talking about an encoding)

and maybe some links to wikipedia cuz wtf do any of these words mean if this is the first time you're seeing them
McEndu
1,161 posts
Joined March 2019
McEndu

clayton wrote:

there are other references to ".mp3" and ".ogg" that should get the same treatment in this PR I think. also ".wav" (-> "LPCM (.wav)" if talking about an encoding)

and maybe some links to wikipedia cuz wtf do any of these words mean if this is the first time you're seeing them
yea I am also thinking about Wikipedia links

.wav could be stated as "uncompressed audio (.wav)" or "raw audio (.wav)" though if buzzwords become a problem
Last edited by McEndu , edited 1 time in total.
Please sign in to reply.

New reply

0
1 / 8