madshi bug tracker - eac3to
View Issue Details
0000522eac3tobugpublic2017-11-06 14:182018-04-10 09:12
kron 
 
normalminorhave not tried
newopen 
32
0000522: Warning message
Hi, first of all, congratulations for such excellent program.

Well, respectfully, does this Warning message ("XLL output not lossless") means any problem?
When I use eac3to 31 it doesn't happen, so I ask you if there is a possibilty to make it disapears in version 32?

Thank you for the attention.
When converting audio DTSHD MA to flac using eac3to 32
eac3to v3.32
command line: "C:\Program Files\eac3to\eac3to.exe" "C:\Users\James\Desktop\Audio HD\Overdrive.2017.BluRay.1080p.DTS-HD.MA.5.1.AVC.REMUX-FraMeSToR_track2_eng.dts" "C:\Users\James\Desktop\Audio HD\Overdrive.2017.BluRay.1080p.DTS-HD.MA.5.1.AVC.REMUX-FraMeSToR_track2_eng.dts_.flac" -progressnumbers -log="C:\Program Files\eac3to\UsEac3To.log"
------------------------------------------------------------------------------
DTS Master Audio, 5.1 channels, 24 bits, 48kHz
(core: DTS, 5.1 channels, 1509kbps, 48kHz)
Decoding with libDcaDec DTS Decoder...
libDcaDec reported the warning "XLL output not lossless". <WARNING>
Encoding FLAC with libFlac...
Creating file "C:\Users\James\Desktop\Audio HD\Overdrive.2017.BluRay.1080p.DTS-HD.MA.5.1.AVC.REMUX-FraMeSToR_track2_eng.dts_.flac"...
The original audio track has a constant bit depth of 24 bits.
eac3to processing took 10 minutes, 51 seconds.
Done.
No tags attached.
Issue History
2017-11-06 14:18kronNew Issue
2017-11-08 10:52madshiNote Added: 0001902
2017-11-08 13:28kronNote Added: 0001903
2017-11-08 15:44madshiNote Added: 0001904
2017-11-09 17:04kronNote Added: 0001911
2017-11-09 18:07madshiNote Added: 0001913
2017-11-11 20:58kronNote Added: 0001918
2018-04-10 09:11GL1zdANote Added: 0002273

Notes
(0001902)
madshi   
2017-11-08 10:52   
eac3to just passes the message on to you, which the decoder reports to eac3to. There's nothing I can do about it. Of course I could silently surpress the warning. Or maybe updating to a newer decoder build would remove the warning. But this is not really a bug in eac3to.
(0001903)
kron   
2017-11-08 13:28   
Thank you for answering, madshi.

Well, I was worried because it didn't happen in eac3to 31. It's good to know there's nothing wrong at all.

BTW would it be easy to update the decoder, I mean could it be done just replacing it (the new version) into the eac3to's folder?

I hope you can forgive me for so many questions...

Thanks again, my friend.

P.S.: I don't know why my post is repeated, how can I delete the others?
(0001904)
madshi   
2017-11-08 15:44   
If the decoder interface stayed the same you could just drop in a new version of the dll.
(0001911)
kron   
2017-11-09 17:04   
Hi, madshi,

I've just done it, and the message's now gone.

Thanks for your attention, my friend.
(0001913)
madshi   
2017-11-09 18:07   
Great, where did you get the new version from?
(0001918)
kron   
2017-11-11 20:58   
I'm not sure, madshi... I just had this file here and decided to try with eac3to, fortunately it did work. I think I got it from eMule.
(0002273)
GL1zdA   
2018-04-10 09:11   
Version 0.2.0 can be found in releases here:
https://github.com/foo86/dcadec [^]
But the auhtor also recommends using ffmpeg now since it's integrated there.