Kitomas

SP V1 D2 I2

Dec 12th, 2025
128
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 5.53 KB | None | 0 0
  1. ---- Sound Profiles V1 Proposal (Draft 2) ----
  2.  
  3.  
  4.  
  5. 0. Introduction
  6.  
  7. Right now, our audio behavior is spread across scripts, scenes, and project
  8. settings. That makes it harder to change, easier to break unintentionally, and
  9. difficult to predict how one tweak will affect other gameplay states. It also
  10. forces designers to rely on programmers for even small adjustments, like trying
  11. a new mix, swapping a preset, or rewiring an audio asset, because those changes
  12. often require touching scene files or code.
  13.  
  14. Sound Profiles solve this by introducing a clear, centralized layer of
  15. abstraction for audio. Instead of editing scenes or code, the team can iterate
  16. on audio behavior safely in one place, reducing risk to scene integrity and
  17. keeping changes consistent, controlled, and easy to maintain.
  18.  
  19.  
  20.  
  21.  
  22.  
  23.  
  24.  
  25. 1. Overview
  26.  
  27. A Sound Profile is a self-contained JSON-based format describing how audio
  28. should behave within specific game contexts, without modifying scenes, scripts,
  29. or assets directly. The schema's main goal is to provide an abstraction layer
  30. for defining audio behavior separately from script behavior, while being
  31. accessible enough for non-technical team members to comfortably create and edit.
  32.  
  33. These profiles can be layered and swapped based on any kind of game state or
  34. condition, all with minimal coordination necessary between the technical and
  35. non-technical team members, hereon referred to as "programmers" and "designers"
  36. respectively.
  37.  
  38.  
  39.  
  40. 1.1 Pain Points Addressed / Why This System Exists
  41.  
  42. Without Sound Profiles:
  43. * Audio behavior is scattered between scripts, scenes, or project settings,
  44. which makes modification more difficult and unpredictable.
  45. * Changing settings relevant to one state often risks unintentionally
  46. affecting others.
  47. * Designers would need programmers to tweak even the simplest of audio logic
  48. or asset wiring, as trying new mixes, presets, etc. requires touching scene
  49. files or code directly.
  50.  
  51. With Sound Profiles:
  52. * Audio behavior is centralized to two file types (excluding whatever form
  53. sound categories and IDs take) that are external to any script or scene data.
  54. * Any designer or programmer can adjust audio behavior in isolation, making
  55. its definitions predictable and testable.
  56. * The extent to which coordination is necessary between designers and
  57. programmers is greatly reduced, and is mostly limited to agreeing on what
  58. profiles(s) a given context(s) is relevant to and vice versa, as well as
  59. their name and use case.
  60. * Global accessibility mixes or effect chains become simple, if not one-line swaps.
  61. * Context-based mixing becomes trivial: transitions, menus, cutscenes, etc.
  62. * Future dynamic systems (ducking, RTPCs, property interpolation),
  63. get a stable backbone.
  64. * Schema allows for future, interactive authoring tools to be integrated.
  65.  
  66.  
  67.  
  68.  
  69.  
  70.  
  71.  
  72. 2. Sound Profiles
  73.  
  74. A single Sound Profile can do any number of things. However, limiting each one
  75. individually to serve 1-3 purposes is ideal in order to maximize modularity and
  76. reusability. For example, within a single profile, you could define an audio
  77. effect chain that can be used in multiple *Profile Contexts* (see next section),
  78. where any change to that profile's settings would apply to any associated
  79. contexts, like a macro of sorts.
  80.  
  81.  
  82.  
  83. 2.1 Profile Contexts
  84.  
  85. In order to separate audio pipeline behavior from anything implementation or
  86. game design-specific, profiles are instead attached to Profile *Contexts*.
  87. These are named identifiers that can represent *any* game state, such as:
  88. * Scene transitions
  89. * Menu screens
  90. * Map mode vs. NPC mode
  91. * Accessibility modes (e.g., "Soft Mix")
  92. * Any arbitrary state/tag/event the game defines later
  93.  
  94. This abstraction allows the underlying profile format to remain stable, even
  95. if the game's notion of "state" evolves or expands.
  96.  
  97. One Profile Context can theoretically contain multiple profiles to be applied
  98. all at once, and each profile can theoretically be attached to multiple contexts.
  99.  
  100. In future versions, it should be possible to bind certain parameters within
  101. a context to more specific states, like attenuating the game's volume globally
  102. whenever the game window goes out of focus, for example.
  103.  
  104.  
  105.  
  106. 2.2 Context Definitions
  107.  
  108. Profile Contexts are defined in a separate JSON file that contains a context
  109. ID, followed by an (optional) "priority" index (see next section), followed by
  110. references to profile IDs in an array. Each profile's load order is determined
  111. by their placement in that array.
  112.  
  113. A context ID simply maps a name (e.g., "UI_MAINMENU", "CTX_CUTSCENE") to a
  114. profile (or profiles) that will be considered active while that context is live.
  115.  
  116.  
  117.  
  118. 2.2 Global Contexts
  119.  
  120. Some profiles must always be applied before or after any other context or only
  121. a select number of contexts, such as:
  122. * Accessibility mixes (e.g., Soft Mix vs. Normal Mix)
  123. * System-level music selection rules
  124. * Baseline gain adjustments
  125.  
  126. These profiles' load order is determined by the previously mentioned "priority"
  127. index, which is 0 by default. Values lower than a given priority will result in
  128. that context being applied *before* the other, whereas values higher than a given
  129. priority will result in it being applied *after* the other. For example,
  130. a priority of -1 will be applied before a priority of 0, which will too go before
  131. a priority of 1, and so on.
  132.  
  133. This lets the team swap global mixes dynamically (e.g., toggling Low-Intensity
  134. mode) without altering any other Profile Context.
Advertisement
Add Comment
Please, Sign In to add comment