INTERACT FORUM

Please login or register.

Login with username, password and session length
Advanced search  
Pages: [1]   Go Down

Author Topic: Weird Audio Path Information  (Read 988 times)

The Big Labinski

  • Regular Member
  • Galactic Citizen
  • ****
  • Posts: 442
  • Wake up and slow down
Weird Audio Path Information
« on: September 09, 2018, 01:27:56 pm »

Dear all, the info's from the audio path informationīs are a bit confusing for me.
They show as output 48 kHz 2 channels, but in the DSP Studio the audio is set to 5.1 channels.
The audio input from my Denon receiver shows then input signal "Dolby Digital" and as format 3/2/.1

Are somebody able to explain what happen here? Or do I some mistake regarding the sound setup in JR and/or Windows.
Any help is appreciate.

I added the pics for better understandings


Stefan
Logged
Wake up and slow down 😴

Hendrik

  • Administrator
  • Citizen of the Universe
  • *****
  • Posts: 10935
Re: Weird Audio Path Information
« Reply #1 on: September 09, 2018, 02:28:12 pm »

When Bitstreaming a compressed format like Dolby Digital, the output information is not meaningful, because thats the physical transport - ie. 5.1 is being compressed into Dolby Digital, so it fits into 2 channel after, so you can output it over SPDIF, which is limited to 2 channel afterall.
Logged
~ nevcairiel
~ Author of LAV Filters

blgentry

  • Regular Member
  • Citizen of the Universe
  • *****
  • Posts: 8014
Re: Weird Audio Path Information
« Reply #2 on: September 09, 2018, 03:14:18 pm »

Do you actually want to do this?  Convert from 2 channel to 5.1 using a lossy CODEC?  You are necessarily losing information doing this, not to mention converting 2 channel stereo to a synthetic (made up out of thin air) fake surround signal.  If the end result makes you happy, then I have nothing more to say.  Just making sure you intended to do this.

Brian.
Logged

The Big Labinski

  • Regular Member
  • Galactic Citizen
  • ****
  • Posts: 442
  • Wake up and slow down
Re: Weird Audio Path Information
« Reply #3 on: September 13, 2018, 10:48:56 am »

Dear Hendrik and blgentry; many thanks for your ideas and help.
I got it now by using the HDMI output instead of the tosLink.
The HDMI problem was always that the video must send it as well otherwise no sound is carried out.

Is there a wiki how the best connection are made between a computer and a high end AV-receiver?
Take care
Stefan
Logged
Wake up and slow down 😴

tij

  • MC Beta Team
  • Citizen of the Universe
  • *****
  • Posts: 1563
Re: Weird Audio Path Information
« Reply #4 on: September 13, 2018, 11:01:15 am »

probably hdmi ... then can bitstream lossless audio to your receiver to decode
Logged
HTPC: Win11 Pro, MC: latest 31(64b), NV Driver: v425.31, CPU: i9-12900K, 32GB RAM, GeForce: 2080ti
Screen: LG 2016 E6
NAS: FreeNAS 11.1, SuperMicro SSG-5048R-E1CR36L, E5-1620v4, 64GB ECC RAM, 18xUltrastar He12-SAS3 drives, 2x240GB SSD (OS)

The Big Labinski

  • Regular Member
  • Galactic Citizen
  • ****
  • Posts: 442
  • Wake up and slow down
Re: Weird Audio Path Information
« Reply #5 on: September 14, 2018, 12:21:35 pm »

Thanks to all. I have now a much better quality with the HDMI output.
What are you thinking about "Dolby Atmos"?
Logged
Wake up and slow down 😴

The Big Labinski

  • Regular Member
  • Galactic Citizen
  • ****
  • Posts: 442
  • Wake up and slow down
Re: Weird Audio Path Information
« Reply #6 on: September 27, 2018, 02:48:34 pm »

Have a question regarding the output stream which one is shown in the Output Tool - pic enclosed.
What does it mean "(not using enough bits to output the input directly)"?
The connection is with HDMI from my Geforce GT 1030 directly to my AV-Receiver. It happens just with 6 channels AC3 files. DSP Studio is not used. Using 6 channel FLAC files is working without this message.

Thanks for your kind informationīs
Stefan
Logged
Wake up and slow down 😴

Hendrik

  • Administrator
  • Citizen of the Universe
  • *****
  • Posts: 10935
Re: Weird Audio Path Information
« Reply #7 on: September 27, 2018, 04:38:49 pm »

The decoder outputs 32-bit floating point, your output is 24-bit integer. Hence the output bitdepth is smaller then the input, and that messages shows up. But its really not something to be concerned about with lossy audio codecs like AC3, because the large majority of audio devices won't accept floating point anyway, and because its a "lossy" codec, there really is no information lost when you don't.
Logged
~ nevcairiel
~ Author of LAV Filters

The Big Labinski

  • Regular Member
  • Galactic Citizen
  • ****
  • Posts: 442
  • Wake up and slow down
Re: Weird Audio Path Information
« Reply #8 on: September 28, 2018, 03:05:22 am »

Many thanks Hendrik, now everything is clear for me.
Very good support here.
tc
Stefan
Logged
Wake up and slow down 😴
Pages: [1]   Go Up