From a1d4847d078f4f807f5697f299eea834797f4287 Mon Sep 17 00:00:00 2001 From: Chris Robinson Date: Mon, 9 Feb 2015 15:59:29 -0800 Subject: Use B-Format for HRTF's virtual output format This adds the ability to directly decode B-Format with HRTF, though only first- order (WXYZ) for now. Second- and third-order would be easilly doable, however we'd need to be able to up-mix first-order content (from the BFORMAT2D and BFORMAT3D buffer formats) since it would be inappropriate to decode lower-order content with a higher-order decoder. --- Alc/ALu.c | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) (limited to 'Alc/ALu.c') diff --git a/Alc/ALu.c b/Alc/ALu.c index 2e94ad63..33a9c410 100644 --- a/Alc/ALu.c +++ b/Alc/ALu.c @@ -98,10 +98,10 @@ extern inline void aluMatrixSet(aluMatrix *restrict matrix, ALfloat m00, ALfloat * output mixing format, and the DryBuffer is then converted and written to the * backend's audio buffer. * - * With HRTF, these fields correspond to a virtual format (typically 8-channel - * cube), and the actual output is stored in DryBuffer[NumChannels] for the - * left channel and DryBuffer[NumChannels+1] for the right. As a final output - * step, the virtual channels will have HRTF applied and written to the actual + * With HRTF, these fields correspond to a virtual format (typically B-Format), + * and the actual output is stored in DryBuffer[NumChannels] for the left + * channel and DryBuffer[NumChannels+1] for the right. As a final output step, + * the virtual channels will have HRTF applied and written to the actual * output. Things like effects and B-Format decoding will want to write to the * virtual channels so that they can be mixed with HRTF in full 3D. * -- cgit v1.2.3