Music Pipeline Configuration Hardening
This commit is contained in:
@@ -114,7 +114,7 @@ music:
|
||||
max_stem_length: 16
|
||||
naming_scheme: nwn_bmu
|
||||
output_extension: .bmu
|
||||
convert_extensions: [.mp3, .ogg]
|
||||
convert_extensions: [.flac, .m4a, .mp3, .ogg, .wav]
|
||||
datasets:
|
||||
westgate:
|
||||
source: envi/music/westgate
|
||||
@@ -259,7 +259,7 @@ music:
|
||||
max_stem_length: 16
|
||||
naming_scheme: nwn_bmu
|
||||
output_extension: .bmu
|
||||
convert_extensions: [.mp3, .ogg]
|
||||
convert_extensions: [.flac, .m4a, .mp3, .ogg, .wav]
|
||||
```
|
||||
|
||||
Music datasets define individual music collections with independent sources and
|
||||
@@ -269,6 +269,12 @@ naming prefixes. `source` is the authored input root under `paths.assets`;
|
||||
configured source extensions into generated HAK resources; `package_mode: none`
|
||||
scans and writes credits without adding generated HAK resources. The legacy
|
||||
`music.prefixes` shorthand is automatically normalized into datasets.
|
||||
`convert_extensions` is configuration-driven; the built-in default set is
|
||||
`.flac`, `.m4a`, `.mp3`, `.ogg`, and `.wav`.
|
||||
Those extensions are discovered from YAML within configured music dataset source
|
||||
roots, so setting them in `music.defaults.convert_extensions` or a dataset
|
||||
override is sufficient; you do not need a parallel
|
||||
`inventory.asset_extensions` override just to make music scanning see them.
|
||||
|
||||
Music can also be run directly:
|
||||
|
||||
|
||||
Reference in New Issue
Block a user