Not a member of Pastebin yet?
Sign Up,
it unlocks many cool features!
- ---- Sound Profiles V1 Proposal (Draft 2) ----
- 1. Overview
- A Sound Profile is a self-contained JSON-based format describing how audio
- should behave under specific game contexts, without modifying scenes, scripts,
- or assets directly. The schema's main goal is to provide an abstraction layer
- for defining audio behavior separately from script behavior, while being
- accessible enough for non-technical team members to comfortably create and edit.
- These profiles can be layered and swapped based on any kind of game state or
- condition, all with minimal coordination necessary between the technical and
- non-technical team members, hereon referred to as "programmers" and "designers"
- respectively.
- 1.1 Pain Points Addressed / Why This System Exists
- Without Sound Profiles:
- * Audio behavior is scattered between scripts, scenes, or project settings,
- which makes modification more difficult and unpredictable
- * Changing settings relevant to one state often risks unintentionally
- affecting others.
- * Designers would need programmers to tweak even the simplest of audio logic
- or asset wiring, as trying new mixes, presets, etc. requires touching scene
- files or code directly.
- With Sound Profiles:
- * Audio behavior is centralized to one type of file (potentially two at most;
- see "2.1 Context Definitions"), while being external to any script or scene data.
- * Any designer or programmer can adjust audio behavior in isolation,
- making its definitions predictable and testable.
- * The extent to which coordination is necessary between designers and
- programmers is greatly reduced, and is mostly limited to agreeing on what
- context a given profile is relevant to, as well as its name.
- * Global accessibility mixes or effect chains become one-line swaps.
- * Context-based mixing becomes trivial: transitions, menus, cutscenes, etc.
- * Future dynamic systems (ducking, RTPCs, interpolation) get a stable backbone.
- In short, Sound Profiles create a layer of abstraction for audio, that the
- entire team can iterate on without risking scene or code integrity in any way.
- 2. Profile Contexts
- In order to separate audio pipeline behavior from anything implementation or
- design-specific, profiles are instead attached to Profile *Contexts*. These are
- named identifiers that can represent *any* game state, such as:
- * Scene transitions
- * Menu screens
- * Story mode vs. Match gameplay (!!! REPHRASE THIS)
- * Accessibility modes (e.g., "Soft Mix")
- * Any arbitrary state/tag/event the game defines later
- This abstraction allows the underlying profile format to remain stable,
- even if the game's notion of "state" evolves or expands.
- 2.1 Context Definitions
- Contexts may be defined in:
- * A separate JSON file that contains references to profile IDs (recommended)
- * A special "contexts" field inside the profile file.
- A context simply maps a name (e.g., "UI_MAINMENU", "GAMEPLAY_MATCH") to a
- profile (or profiles) that should be considered active while that context is
- live, subject to priority index rules (!!! CITE; ELABORATE).
- 2.2 Global Contexts
- Some profiles must always run before or after any other context, such as:
- * Accessibility mixes (e.g., Soft Mix vs. Normal Mix)
- * System-level music selection rules
- * Baseline gain adjustments
- These are expressed using special affixes:
- * "PRE_..." profiles are applied first, before any others.
- * "POST_..." profiles are applied last, after all others.
- Priority rules still apply inside each group (!!! CITE; ELABORATE).
- This lets the team swap global mixes dynamically (e.g., toggling Low-Intensity
- mode) without altering any other profile.
- ?. Footnotes / Implementation Notes
- (These will be assigned as actual footnotes in the final Google Doc!)
- * "RTPC" stands for "Real-Time Parameter Control"
- * Only one instance of each property type can exist per profile.
- An error is to be handled in the event of a malformed or duplicate property key.
- * The property key strings should be verbose enough to serve as the canonical
- specification name, with little to no elaboration.
- * Audio element categories and IDs are TBD; schema should/will accommodate both.
- * Linear <-> dB conversion rules must be documented.
- * Effect preset system is TBD and may be added as a 'V1.1' extension.
Advertisement
Add Comment
Please, Sign In to add comment