Minor fixes for interleaved .vag loop points

This commit is contained in:
spicyjpeg
2025-12-05 02:26:01 +01:00
parent ae864bf940
commit d1bc6e2f5f
2 changed files with 12 additions and 8 deletions

View File

@@ -80,17 +80,16 @@ Notes:
[.vag header](https://psx-spx.consoledev.net/cdromfileformats/#cdrom-file-audio-single-samples-vag-sony)
at the beginning of the file. The header is always 48 bytes long for `vag`
files, while in the case of `vagi` files it is padded to the size specified
using the `-a` option (2048 bytes by default).
- The `vagi` format extends the standard .vag header by changing the signature
to `VAGi` and adding the following fields:
using the `-a` option (2048 bytes by default). The `vagi` format extends the
standard .vag header by adding the following fields:
- the file's interleave size at offset `0x08-0x0B` (little endian);
- the loop start offset in bytes-per-channel, if any, at offset `0x14-0x17`
(little endian);
- the file's channel count at offset `0x1E`.
- The `spu`, `vag`, `spui` and `vagi` formats support setting a loop start
point. If the input file is either a .wav file with sampler metadata (`smpl`
- The `spu` and `vag` formats support encoding a loop point as part of the ADPCM
data, while `vagi` supports storing one in the header for use by the stream
driver. If the input file is either a .wav file with sampler metadata (`smpl`
chunk) or in a format FFmpeg supports parsing cue/chapter markers from, the
first marker will be used as the loop point by default. The `-l` and `-n`
options can be used to manually set a loop point or ignore the one present in