[CLOSED] Problems with not split TrueHD and FFMpeg

Support forum for DGDecNV
Post Reply
DAE avatar
Guest 2
Posts: 903
Joined: Mon Sep 20, 2010 2:18 pm

[CLOSED] Problems with not split TrueHD and FFMpeg

Post by Guest 2 »

I have bought the Zodiac (director's cut) BD.

I am going thru an issue with not split THD conversion thru FFMpeg to AC3, that the pure THD doesn't present.

My usual FFMpeg command line is:

ffmpeg.exe -i [eng].thd -acodec ac3 -ab 640k -af dynaudnorm=f=2000:g=23:m=15 [eng].ac3

If I convert pure THD (the one that generates AC3 file too), everything is ok, otherwise the original THD throws me a bunch of errors, when processing with FFMpeg.

What do you need to debug this? The original THD or the whole BD? :mrgreen:
User avatar
Rocky
Posts: 3557
Joined: Fri Sep 06, 2019 12:57 pm

Re: Problems with not split TrueHD and FFMpeg

Post by Rocky »

What are the errors? The last time I checked, my output was bit identical to eac3to's output (with keeping dialnorm). Does it happen with eac3to? If it is an issue with ffmpeg, I'm not going to debug that.
DAE avatar
Guest 2
Posts: 903
Joined: Mon Sep 20, 2010 2:18 pm

Re: Problems with not split TrueHD and FFMpeg

Post by Guest 2 »

THD+AC3 from DGIndexNV/DGDemux is not identical to eac3to one even if they have the same size.

They both produce the same parity error, so you can close this thread. If I will find any THD+AC3 that works with eac3to and not with DGIndexNV, I will report you.

Code: Select all

Stream mapping:
  Stream #0:0 -> #0:0 (truehd (native) -> ac3 (native))
Press [q] to stop, [?] for help
Output #0, ac3, to '1_3_audio.ac3':
  Metadata:
    encoder         : Lavf58.43.100
    Stream #0:0: Audio: ac3, 48000 Hz, 5.1(side), fltp (24 bit), 640 kb/s
    Metadata:
      encoder         : Lavc58.84.100 ac3
[NULL @ 0000028a942554c0] mlpparse: Parity check failed.
    Last message repeated 4 times
[truehd @ 0000028a942543c0] Invalid nonrestart_substr.
Error while decoding stream #0:0: Invalid data found when processing input
[truehd @ 0000028a942543c0] Invalid nonrestart_substr.
Error while decoding stream #0:0: Invalid data found when processing input
[NULL @ 0000028a942554c0] mlpparse: Parity check failed.
    Last message repeated 3 times
[truehd @ 0000028a942543c0] Invalid nonrestart_substr.
Error while decoding stream #0:0: Invalid data found when processing input
[NULL @ 0000028a942554c0] mlpparse: Parity check failed.
    Last message repeated 12 times
[truehd @ 0000028a942543c0] Lossless check failed - expected a8, calculated 5f.
[NULL @ 0000028a942554c0] mlpparse: Parity check failed.
[truehd @ 0000028a942543c0] Lossless check failed - expected 2d, calculated 53.
[NULL @ 0000028a942554c0] mlpparse: Parity check failed.
[truehd @ 0000028a942543c0] Lossless check failed - expected 47, calculated 6c.
[NULL @ 0000028a942554c0] mlpparse: Parity check failed.
[truehd @ 0000028a942543c0] Lossless check failed - expected be, calculated 47.
[NULL @ 0000028a942554c0] mlpparse: Parity check failed.
[truehd @ 0000028a942543c0] Lossless check failed - expected 4b, calculated 92.
[NULL @ 0000028a942554c0] mlpparse: Parity check failed.
[truehd @ 0000028a942543c0] Lossless check failed - expected 4a, calculated 51.
[truehd @ 0000028a942543c0] Invalid nonrestart_substr.
Error while decoding stream #0:0: Invalid data found when processing input
[NULL @ 0000028a942554c0] mlpparse: Parity check failed.
[truehd @ 0000028a942543c0] Lossless check failed - expected b6, calculated 82.
[NULL @ 0000028a942554c0] mlpparse: Parity check failed.
[truehd @ 0000028a942543c0] Lossless check failed - expected df, calculated c1.
[NULL @ 0000028a942554c0] mlpparse: Parity check failed.
[truehd @ 0000028a942543c0] Lossless check failed - expected 8e, calculated c4.
[truehd @ 0000028a942543c0] Invalid nonrestart_substr.
Error while decoding stream #0:0: Invalid data found when processing input
[NULL @ 0000028a942554c0] mlpparse: Parity check failed.
Etc.
User avatar
Rocky
Posts: 3557
Joined: Fri Sep 06, 2019 12:57 pm

Re: Problems with not split TrueHD and FFMpeg

Post by Rocky »

Probably ffmpeg is confused by the AC3.

The output will be different from eac3to unless you give --keepDialnorm.
DAE avatar
Guest 2
Posts: 903
Joined: Mon Sep 20, 2010 2:18 pm

Re: Problems with not split TrueHD and FFMpeg

Post by Guest 2 »

Rocky wrote:
Sat May 16, 2020 4:43 pm
The output will be different from eac3to unless you give --keepDialnorm.
True, just tried that.

You can close the thread as resolved (not DG* fault).
Post Reply