Kitomas

SP V1 D2 I1

Dec 11th, 2025
96
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 4.35 KB | None | 0 0
  1. ---- Sound Profiles V1 Proposal (Draft 2) ----
  2.  
  3.  
  4.  
  5. 1. Overview
  6.  
  7. A Sound Profile is a self-contained JSON-based format describing how audio
  8. should behave under specific game contexts, without modifying scenes, scripts,
  9. or assets directly. The schema's main goal is to provide an abstraction layer
  10. for defining audio behavior separately from script behavior, while being
  11. accessible enough for non-technical team members to comfortably create and edit.
  12. These profiles can be layered and swapped based on any kind of game state or
  13. condition, all with minimal coordination necessary between the technical and
  14. non-technical team members, hereon referred to as "programmers" and "designers"
  15. respectively.
  16.  
  17.  
  18.  
  19. 1.1 Pain Points Addressed / Why This System Exists
  20.  
  21. Without Sound Profiles:
  22. * Audio behavior is scattered between scripts, scenes, or project settings,
  23. which makes modification more difficult and unpredictable
  24. * Changing settings relevant to one state often risks unintentionally
  25. affecting others.
  26. * Designers would need programmers to tweak even the simplest of audio logic
  27. or asset wiring, as trying new mixes, presets, etc. requires touching scene
  28. files or code directly.
  29.  
  30. With Sound Profiles:
  31. * Audio behavior is centralized to one type of file (potentially two at most;
  32. see "2.1 Context Definitions"), while being external to any script or scene data.
  33. * Any designer or programmer can adjust audio behavior in isolation,
  34. making its definitions predictable and testable.
  35. * The extent to which coordination is necessary between designers and
  36. programmers is greatly reduced, and is mostly limited to agreeing on what
  37. context a given profile is relevant to, as well as its name.
  38. * Global accessibility mixes or effect chains become one-line swaps.
  39. * Context-based mixing becomes trivial: transitions, menus, cutscenes, etc.
  40. * Future dynamic systems (ducking, RTPCs, interpolation) get a stable backbone.
  41.  
  42. In short, Sound Profiles create a layer of abstraction for audio, that the
  43. entire team can iterate on without risking scene or code integrity in any way.
  44.  
  45.  
  46.  
  47.  
  48.  
  49.  
  50.  
  51. 2. Profile Contexts
  52.  
  53. In order to separate audio pipeline behavior from anything implementation or
  54. design-specific, profiles are instead attached to Profile *Contexts*. These are
  55. named identifiers that can represent *any* game state, such as:
  56. * Scene transitions
  57. * Menu screens
  58. * Story mode vs. Match gameplay (!!! REPHRASE THIS)
  59. * Accessibility modes (e.g., "Soft Mix")
  60. * Any arbitrary state/tag/event the game defines later
  61.  
  62. This abstraction allows the underlying profile format to remain stable,
  63. even if the game's notion of "state" evolves or expands.
  64.  
  65.  
  66.  
  67. 2.1 Context Definitions
  68.  
  69. Contexts may be defined in:
  70. * A separate JSON file that contains references to profile IDs (recommended)
  71. * A special "contexts" field inside the profile file.
  72.  
  73. A context simply maps a name (e.g., "UI_MAINMENU", "GAMEPLAY_MATCH") to a
  74. profile (or profiles) that should be considered active while that context is
  75. live, subject to priority index rules (!!! CITE; ELABORATE).
  76.  
  77.  
  78.  
  79. 2.2 Global Contexts
  80.  
  81. Some profiles must always run before or after any other context, such as:
  82. * Accessibility mixes (e.g., Soft Mix vs. Normal Mix)
  83. * System-level music selection rules
  84. * Baseline gain adjustments
  85.  
  86. These are expressed using special affixes:
  87. * "PRE_..." profiles are applied first, before any others.
  88. * "POST_..." profiles are applied last, after all others.
  89.  
  90. Priority rules still apply inside each group (!!! CITE; ELABORATE).
  91.  
  92. This lets the team swap global mixes dynamically (e.g., toggling Low-Intensity
  93. mode) without altering any other profile.
  94.  
  95.  
  96.  
  97.  
  98.  
  99.  
  100.  
  101. ?. Footnotes / Implementation Notes
  102. (These will be assigned as actual footnotes in the final Google Doc!)
  103. * "RTPC" stands for "Real-Time Parameter Control"
  104. * Only one instance of each property type can exist per profile.
  105. An error is to be handled in the event of a malformed or duplicate property key.
  106. * The property key strings should be verbose enough to serve as the canonical
  107. specification name, with little to no elaboration.
  108. * Audio element categories and IDs are TBD; schema should/will accommodate both.
  109. * Linear <-> dB conversion rules must be documented.
  110. * Effect preset system is TBD and may be added as a 'V1.1' extension.
Advertisement
Add Comment
Please, Sign In to add comment