INTERACT FORUM

More => Old Versions => JRiver Media Center 18 for Windows => Topic started by: digi340 on May 31, 2013, 12:53:12 am

Title: Again "not using enough bits to output the input directly"
Post by: digi340 on May 31, 2013, 12:53:12 am

I have problems after the update to version 18.0.191

Wasapi settings:

Device: Soundmax
Disable event Style - unchecked

Bitdepth: automatic

1. from internet radio (radio extra MP3 STREAM 320 KBS)

-  output: 44.1khz 24bit 2ch using WASAPI direct conection

Audio Path

input: 44.1khz 2ch from source format MP3

output: 44.1khz 24bit 2ch using WASAPI direct connection

From DTS CD or native DTS file or AC3 file

input: 48khz 32 bit 6ch from source format DTS
output: 48khz 24bit 6ch using WASAPI  (not using enough bits to output the input directly)

In previous version DTS CD or native DTS or AC3 file file was bitperfect and not show strange message "not using enough bits to output the input directly" but when I listen MP3 or AAC stream  show "not using enough bits to output the input directly".
 

 
 
 

Title: Re: Again "not using enough bits to output the input directly"
Post by: InflatableMouse on May 31, 2013, 01:42:29 am

And what is the problem exactly?

Title: Re: Again "not using enough bits to output the input directly"
Post by: digi340 on May 31, 2013, 05:08:36 am

Quote from: InflatableMouse on May 31, 2013, 01:42:29 am

And what is the problem exactly?

In previous version listen DTS CD, DTS native file and AC3 file  in Wassapi Event style,  hardware direct connection, and AAC stream and MP3 stream not  in hardware direct connection  "not using enough bits to output the input directly' .
In latest version  listen DTS CD, DTS native file and AC3 file  in Wassapi Event style  not hardware direct connection "not using enough bits to output the input directly' , and  AAC stream and MP3 stream  hardware direct connection  .

Title: Re: Again "not using enough bits to output the input directly"
Post by: InflatableMouse on May 31, 2013, 05:49:52 am

I understand something changed, but I don't understand how that is a problem.

Is something not working properly?

Title: Re: Again "not using enough bits to output the input directly"
Post by: Matt on May 31, 2013, 08:49:55 am

The only change is the messaging.

Lossy formats like DTS and AC3 don't have a real bitdepth:
http://wiki.jriver.com/index.php/Audio_Bitdepth#Bitdepth_of_Lossy_Formats

So sometimes they get decoded at 32 or 64 bit, simply because using more precision allows them to be as good as possible.

But if we don't mark the format as "lossy", Audio Path displays that your 24-bit DAC can't fully represent the 32 or 64 bit lossy signal.

We'll look at marking DTS and AC3 as lossy to avoid this slightly confusing display issue.