View Full Version : ArcSoft DTS decoder versions
Anakunda
16th December 2014, 10:28
HI
It was said that ArcSoft version 1.0 is the best for DTS decoding. Is this still valid or do already latest TMT versions perform better? Thanks for recommending best decoder up to day.
Sparktank
16th December 2014, 14:37
Well no one has provided a version of 1.1.0.9 to tenesbaus or madshi for reference.
So far, everyone with a solid opinion has used v1.1.0.0 without problems.
If you really want an opinion, make some sample rips of version 1.1.0.0 and 1.1.0.8 and 1.1.0.9 for posterity.
So far, v1.1.0.0 is valid for every format, while eac3to has been updated to handle current isssues with different versions of Arcsoft.
And, considering that Arcsoft is no longer in business for video/audio decoding (no longer maintaining TMT udpates), there isn't much to look forward to than personal opinions regarding different versions of Arcsoft, especially when you search and find that tenebaus and others have used only v.1.1.0.0 without problems that other versions have exhibited.
Midzuki
16th December 2014, 15:43
FWIW:
I tested 5 different versions of dtsdecoderdll.dll along with LAV Audio, here are results.
Versions tested: 1.1.0.0, .1, .5, .7, .8.
Samples tested:
1) Lossy DTS 2.0, 2.1, 5.1, 6.0, 6.1 configs, 16/48, 24/48 and 24/96 bitdepth/sample rate;
2) DTS-MA 1.0, 2.0, 2.1, 5.1, 6.1, 7.1 configs including 7.1 "strange setup" config (eac3to term), 16/48, 24/48, 24/96 variants.
My results differ from results that some people posted in eac3to thread, I guess there may be some eac3to specific problems.
lossy DTS
1) 1.1.0.0 and 1.1.0.1 always decode lossy DTS as 24 bit, and their decoding results differ from each other.
2) 1.1.0.5 and up decode in proper bitdepth.
3) Versions 1.1.0.5 and up decode lossy DTS identically.
4) 1.1.0.1 and 1.1.0.5 decode 24 bit lossy DTS identically.
5) Decoding of 16 bit lossy DTS was changed from 1.1.0.0 to 1.1.0.1 and from 1.1.0.1 to 1.1.0.5.
6) 1.1.0.7 and 1.1.0.8 decode 6.0 without back center channel.
The conclusion for lossy: I assume the best version for lossy DTS is 1.1.0.5. It decodes all configurations I've tested, in proper bitdepth, and decoding algorithm didn't change since this version (except 6.0 bug in .7 and .8).
DTS-MA
All versions output identical streams except mono case. Mono decoding was broken in 1.1.0.5 and partially fixed in 1.1.0.8 (outputs as stereo). Note that MA 7.1 16/48 "strange setup" is decoded as 24/48 by all versions.
The conclusion for lossless: the best versions are 1.1.0.0 and 1.1.0.1.
Of course, to be sure that decoding is done properly some "reference proper" decoder is needed. I don't have it.
EDIT: Forgot to mention about 2.1 bug. None of the versions can decode LFE channel in 2.1 files.
and
Yes, we need switch in this situation.
In case of non-standart scheme decoder 1.1.0.0 give garbage in some channels. So, i tried other two versions and they are decoded properly. If you have DTS-HD M.A.S. you can try yourself. If not, try decode test sample (http://www.mediafire.com/?kagbxe5zg7tdzg0) of DTS-HD 7.1 (scheme 2) and compare results.
AFAIK, there are only two differences between 1.1.0.0 and 1.1.0.8:
- 1.1.0.0 can decode DTS(-HD) 6.1/6.0 but can't decode non-standart 7.1
- 1.1.0.8 can't decode DTS(-HD) 6.1/6.0 but can decode non-standart 7.1
Both decode DTS(-HD) 1.0 correctly, unlike 1.1.0.7.
Sparktank
16th December 2014, 16:06
since eac3to has been updated since 2011, are those still valid?
"scheme 2" is very unkown to me.
"non-standard" is known, which I assume what "scheme 2" refers to.
ea3to has been updated, to the extent of old posts, I'm not entirely sure.
But I think a revisit would be worth it, especially since we have v1.1.0.9 now. (the latest version before Arcsoft dropped TMT entirely).
Anakunda
16th December 2014, 16:30
thanks for exhaustive info. Because 6.0 or 6.1 is very rare and 7.1 strange is more likely I guess updating to 1.1.0.8 will be good idea.
I wonder if decoder 1.1.0.9 fixes the 6.0/1 bug, but anyway it's not so important.
Sparktank
16th December 2014, 16:55
There's also the option of using MakeMKV which uses Arcsoft decoder on a different level than eac3to.
It particularly handles "strange setup" differently than eac3to.
There's several posts about in the eac3to thread.
Why not upload a few samples to test against v.1.1.0.9?
6.0/6.1/7.1(strange-setup)
nevcairiel
16th December 2014, 19:05
6.1 works fine on 1.1.0.8/9 in general, the problem is isolated to eac3to. Using the ArcSoft DTS decoder in LAV for example plays 6.1 just fine, only 6.0 is having issues (and thats super rare).
tebasuna51
16th December 2014, 23:01
FWIW:
Originally Posted by Gleb Egorych
lossy DTS
1) 1.1.0.0 and 1.1.0.1 always decode lossy DTS as 24 bit, and their decoding results differ from each other.
2) 1.1.0.5 and up decode in proper bitdepth.
3) Versions 1.1.0.5 and up decode lossy DTS identically.
4) 1.1.0.1 and 1.1.0.5 decode 24 bit lossy DTS identically.
5) Decoding of 16 bit lossy DTS was changed from 1.1.0.0 to 1.1.0.1 and from 1.1.0.1 to 1.1.0.5.
6) 1.1.0.7 and 1.1.0.8 decode 6.0 without back center channel.
The conclusion for lossy: I assume the best version for lossy DTS is 1.1.0.5. It decodes all configurations I've tested, in proper bitdepth, and decoding algorithm didn't change since this version (except 6.0 bug in .7 and .8).
Don't exist a proper bitdepth for lossy DTS, lossy DTS don't have bitdepth. Then is always better decode any lossy DTS to 24 bits instead 16 bits.
and
Originally Posted by TDiTP
- 1.1.0.0 can decode DTS(-HD) 6.1/6.0 but can't decode non-standart 7.1
That is not true for me. Only make a remix with Surround and Back channels to output wav channels Side and Back.
If you want assign the Surround channel (110-120º) to Side channels (90-100º) directly, without remix, you can use MakeMKV (with the same dtsdecoderdll 1.1.0.0)
nevcairiel
29th November 2017, 10:22
This thread is from 2014, in 2017 we actually have an alternative DTS decoder which supports all formats and all channel configurations without any issues. Its supported in both eac3to and LAV.
Anakunda
29th November 2017, 10:26
If I have ArcSoft decoders installed, which one is used by eac3to? Am I suggested to remove ArcSoft or do they yet have some use?
tebasuna51
29th November 2017, 11:31
If I have ArcSoft decoders installed, which one is used by eac3to?
By default libdcadec.dll.
But you can force ArcSoft with the parameter -arcsoft, default only for DTS-Express not supported by libdcadec.dll
New libdcadec versions supporting DTS-Express are in ffmpeg and LAV filters.
Am I suggested to remove ArcSoft or do they yet have some use?
Like DirectShow decoders can be replaced by LAV filters.
Only to decode DTS-Express with eac3to in CLI mode, but can be replaced by ffmpeg.
Anakunda
3rd December 2017, 09:22
Thanks!
vBulletin® v3.8.11, Copyright ©2000-2026, vBulletin Solutions Inc.