Log in

View Full Version : 48000hz / 24bit wasapi??


DigitalLF
2nd May 2014, 19:08
Hello!

i'm fairly use to the programs but im not very good with understanding lots of the settings so if im thinking wrong or doing something i don't need to please tell me!



I'm going nuts here... Is it me or is it not possible to output 48000hz 24bit (the dark knight rises) using LAV Audio Decoder with dtsdecoderdll.dll 1.1.0.1 and latest ReClock with WASAPI settings?

It just says "the audio format is not supported by hardware / software" but it works when i select DirectSound instead of WASAPI

Mangix
2nd May 2014, 19:15
AFAIK, 24-bit WASAPI doesn't work right. Select 32-bit instead. There's no quality loss as the extra bits are just padded 0s.

nevcairiel
2nd May 2014, 19:26
ReClock has a 24-bit in 32-bit mode which is designed specifically for this.

DigitalLF
2nd May 2014, 19:28
wierd... i set reclock to 24 padded 32 and it worked.. thank you Mangix. :)

DarkSpace
2nd May 2014, 19:30
Keep in mind that WASAPI talks directly to the audio driver while DirectSound talks to Windows.

That means that with DirectSound, you give the 48 kHz / 24 bit audio data to Windows, Windows then checks what format you told it to use when sending data to the audio driver, and then converts the input data to that format, applies Volume changes if requested (in effect, if you don't have the Windows Volume set to maximum), and gives the result to the driver. What's important to know here is that when you tell Windows what format to use when sending data to the audio driver, Windows checks with the audio driver and only lets you select formats that the driver says it supports.
Often, the driver will support a large variety of formats, but the device it is connected to (e.g. a TV's speakers) will only support a few formats. In that case, the driver will only "support" the formats that the TV's speakers also support.

WASAPI, however, circumvents those checks and just sends data to the driver as-is (ReClock also does some Volume change based on the Windows Volume, but I think it's noted somewhere that this volume change is low quality) without first checking if the driver supports that format. As a result, if either your drivers or your speakers don't like the format, there will be an error about that.
Keep in mind that ReClock expects you to know what output formats your drivers and speakers support, instead of limiting your choice based on what the driver says it supports. For example, my TV's speakers only support 44.1 kHz and 48 kHz, but even so, I can select 192 kHz output in ReClock (it will give me an error, of course).
Also keep in mind that "support" for audio formats includes the number of channels. For example, you may be able to send 48 kHz / 24 bit of 2.0 or 5.1 data, while 5.0 may make problems.

As such, I'm guessing that your speakers don't like 24 bit audio. Or maybe they don't like your mixing settings?

EDIT: Mangix is right, I forgot that sometimes, 24 bit audio is only accepted when padded to 32 bit. It's weird that I'd forget this, though, because I have to use it myself... :o

DigitalLF
2nd May 2014, 19:38
well i don't do a downmix or something like that and both my speakers and processor do like 24bit ;)

DarkSpace
2nd May 2014, 21:44
Sure... and Mangix was right anyway, I simply forgot that sometimes, you just need to use padded 24 bit. I just wanted to mention it in case it becomes useful, and when I wrote my response, there weren't any answers yet (only goes to show how long it takes me to write something that I perceive as more or less comprehensible).
It's good that it was solved, in any case!