AVS Forum banner
1 - 7 of 7 Posts

· Banned
Joined
·
74 Posts
Discussion Starter · #1 ·

I have an X-Fi Titanium sound card with Dolby Digital Live, but I turn Dolby Digital Live off so that I can use SPDIF and enable Dolby Digital 5.1 bitstreaming. I use JRiver and LAV Audio Decoder. JRiver has settings for Dolby Digital encoding in its DSP Audio Format options, which I enabled. LAV also has AC-3 Dolby Digital bitstreaming options, which I also enabled. I set JRiver to use LAV Audio as the primary audio decoder. I also enabled bitstreaming over SPDIF in JRiver. Is that a proper configuration? I understand that LAV Audio is a decoder while JRiver DSP is an encoder, but should I keep Dolby Digital bitstreaming enabled in both of them? I am a bit confused because JRiver Dolby Digital AC-3 is for ENcoding, while LAV Audio is for DEcoding.

 

I guess it should be enabled in both of them ONLY if the signal is NOT Dolby Digital 5.1, but DTS, for example. LAV would decode that DTS signal into 6ch PCM audio, which would then be re-encoded into AC-3 by JRiver, correct? That, however, would NOT be bitstreaming...

 

What about pure Dolby Digital 5.1 signal? LAV Audio would NOT decode Dolby Digital 5.1 signal into PCM and would bitstream the untouched Dolby Digital 5.1 signal directly to JRiver if I enable AC-3 Dolby Digital bitstreaming in LAV Audio, right?  Then, would I have to turn OFF Dolby Digital 5.1 ENcoding in JRiver? If I don't, then JRiver would re-encode bitsreamed Dolby Digital 5.1 signal for no reason, breaking the bitstreaming, right???

 

JRiver also has Tempo & Pitch 64bit processing - would that break/interrupt bitstreaming? 

 

Last question - its really not possible to get a perfect audio and video sync using technologies like ReClock and VideoClorck (JRiver) with bitstreaming enabled, right?
 

· Registered
Joined
·
1,058 Posts
You can safely enable both Bitstreaming and AC-3 encoding. It'll bitstream existing AC-3 streams, and encode anything which was not AC-3. Any processing in JRiver is automatically disabled if a Bitstream comes from the decoder, and it won't break it.


Regarding the Audio Path, it shows a technical detail of the AC-3 output there, as AC-3 output over SPDIF uses an encoding that looks like 16-bit 2 channels, but its actually a AC-3 bitstream output. It gets a bit confusing, but its nothing to worry about.
 

· Banned
Joined
·
74 Posts
Discussion Starter · #4 ·

Quote:
Originally Posted by Nevcairiel  /t/1517201/where-should-i-enable-do...-in-jriver-or-lav-audio-decoder#post_24341553


You can safely enable both Bitstreaming and AC-3 encoding. It'll bitstream existing AC-3 streams, and encode anything which was not AC-3. Any processing in JRiver is automatically disabled if a Bitstream comes from the decoder, and it won't break it.


Regarding the Audio Path, it shows a technical detail of the AC-3 output there, as AC-3 output over SPDIF uses an encoding that looks like 16-bit 2 channels, but its actually a AC-3 bitstream output. It gets a bit confusing, but its nothing to worry about.
 

Well, I tried the other route - I enabled Dolby Digital Live, selected X-Fi Titanium Speakers (WASAPI) instead of SPDIF (X-Fi "Speakers" selection actually sends a 5.1 Dolby Digital Live signal over SPDIF), disabled bitstreaming for SPDIF in LAV Audio and JRiver because enabling bitstreaming for SPDIF with Dolby Digital Live enabled causes severe hissing. The Audio Path Output changed from 16bit 2 channels to 32bit 6 channels! I think it happens because X-Fi SPDIF in Windows settings can only be set to 2 channels, while X-Fi Speakers can be set to 5.1 channels. Dolby Digital Live descriptions says that it bitstreams... but I am not sure... 

 

So, I guess there is really no way to use X-Fi SPDIF and enable bitstreaming in LAV and JRiver and get more than 2 channel audio.... even if I use Creative X-Fi Control Panel and select 5.1 because it applies only to "Speakers", not SPDIF...

 

Creative also has ASIO driver, but it also forces me to use 2 channels... 
 

· Banned
Joined
·
74 Posts
Discussion Starter · #6 ·

Great! Thank you!

 

Would you know by chance, if JRiver plans on using HTML5 for its Netflix plugin? I have Windows 8.1 Pro that allows me to use HTML5 in IE11 or the Netflix app to receive SuperHD quality on Netflix. JRiver is using Silverlight plugin, even though it seems to be using IE also. Silverlight does not allow SuperHD... I also tried using Chromium, but that also used Silverlight. Maybe if I uninstall Silverlight it will switch to HTML5, but regular IE11 browsing uses HTML5 automatically/by default, so I am not sure what the problem is.
 
1 - 7 of 7 Posts
This is an older thread, you may not receive a response, and could be reviving an old thread. Please consider creating a new thread.
Top