UsEac3to v1.3.4: a different GUI for eac3to

[tormento]

Does it work with last eac3to?

I have tried to read a mkv video and the eac3to about appears, instead of the track list.

Yes, I have set the exe paths.

[tebasuna51]

No problem here:

eac3to v3.52
command line: "C:\Portable\eac3to\eac3to.exe" "D:\Temp\t\00_HD.mkv" -progressnumbers -log="C:\Portable\eac3to\UsEac3to\UsEac3To.log"
------------------------------------------------------------------------------
Running in fast mode
Removing dialnorm
MKV, 1 video track, 1 audio track, 0:00:21, 25p
1: h264/AVC, English, 720p25
2: DTS Hi-Res, 7.1 channels, 2814kbps, 48kHz, dialnorm: 0dB
(core: DTS-ES, 5.1 channels, 1509kbps, 48kHz, dialnorm: 0dB)

[tormento]

Originally Posted by tebasuna51

No problem here

I did a clean installation of last version and no way to make it work, both drag and dropping and opening. Tried to rename file to a single character but nothing helped.

It opens a cmd window telling "analyze" and then the useac3to shows eac3to help page.

Would you please post here your eac3to.ini file?

Is there any way to trace the commands sent to eac3to? The log doesn't contain them.

[tebasuna51]

UsEac3to not need any installation other than fill the Settings options (if can't obtain them automatically):
Path to eac3to
Path to MkvMerge
Path to TsMuxer
Encoders Folder
Output Folder

You don't need eac3to.ini at all because the -progressnumbers -log= is added by UsEac3to (or can be added manually), but I have:

-fast
-progressnumbers

And the command line is show in the log like you can see in my previous post.

[tormento]

Originally Posted by tebasuna51

You don't need eac3to.ini at all because the -progressnumbers -log= is added by UsEac3to (or can be added manually), but I have

Ok, found the problem, I had '-nolog' in eac3to.ini.

[Axeldook]

Hi All,
when trying to encode to true hd. i lose channels.
5.1 come out 5.0
7.1 come out 5.0

how do i fix this ?

Thank you

[tebasuna51]

Originally Posted by Axeldook

5.1 come out 5.0

Work fine here:

"C:\Portable\0\ffmpeg.exe" -i "C:\tmp\6p321.wav" -vn -strict -2 -acodec truehd "C:\tmp\6p321.wav_.thd"
ffmpeg version N-116720-g5c1c0325cd-20240817 Copyright (c) 2000-2024 the FFmpeg developers
Input #0, wav, from 'C:\tmp\6p321.wav':
Stream #0:0: Audio: pcm_s24le ([1][0][0][0] / 0x0001), 48000 Hz, 5.1(side), s32 (24 bit), 6912 kb/s
Output #0, truehd, to 'C:\tmp\6p321.wav_.thd':
Stream #0:0: Audio: truehd, 48000 Hz, 5.1(side), s32p (24 bit), 128 kb/s

7.1 come out 5.0

You are right here:

"C:\Portable\0\ffmpeg.exe" -i "C:\tmp\8w341.wav" -vn -strict -2 -acodec truehd "C:\tmp\8w341.wav_.thd"
Input #0, wav, from 'C:\tmp\8w341.wav':
Stream #0:0: Audio: pcm_s16le ([1][0][0][0] / 0x0001), 48000 Hz, 7.1, s16, 6144 kb/s
Output #0, truehd, to 'C:\tmp\8w341.wav_.thd':
Stream #0:0: Audio: truehd, 48000 Hz, 5.0(side), s16p, 128 kb/s

The ffmpeg thd encoder only can encode to 5.1, then need downmix previously 7.1 -> 5.1 and the last versions have a bug (already reported but ignored) when do so.

To recode to thd 7.1 you need any commercial encoder.

[Axeldook]

thank you !

[DanDare1983]

I've come across a DTS-HD MA 5.1 track which has a 1000ms DELAY. The Log is telling me that a remaining delay of -2ms could not be fixed. I understand that -2ms is nothing to worry about but could someone explain how eac3to has got the delay down to -2ms? I've also seen an ATMOS track with a delay of 3003ms too. Also if i was to just convert the track to ac3 would it sort the problem? I'll also add that the video is 2: h264/AVC, 1080i50 (16:9).

[tebasuna51]

To fix delay without recompress eac3to add silent frames (or remove frames).
Only multiples of 10.666 ms (512 samples in each frame at 48 KHz) can be fixed exactly.

[DanDare1983]

Originally Posted by tebasuna51

To fix delay without recompress eac3to add silent frames (or remove frames).
Only multiples of 10.666 ms (512 samples in each frame at 48 KHz) can be fixed exactly.

Thanks for the explanation. So there's nothing to worry about and eac3to is doing its job?

[tebasuna51]

You preserve the quality (without decode/recode) and the remaining delay is always less than 6 ms., far than the duration of a video frame.

[DanDare1983]

Originally Posted by tebasuna51

You preserve the quality (without decode/recode) and the remaining delay is always less than 6 ms., far than the duration of a video frame.

I'm currently trying to convert DTS-HD 7.1 to AC3 5.1 640kbps. Can I just choose the ac3 option or do I have to enter -down6 too?

[tebasuna51]

You can use the automatic ffmpeg downmix, the -down6 eac3to method or the recommended downmix 71-51o using F-FFMPEG functions

[SeeMoreDigital]

Originally Posted by DanDare1983

I'm currently trying to convert DTS-HD 7.1 to AC3 5.1 640kbps. Can I just choose the ac3 option or do I have to enter -down6 too?

Out of interest... Is there any reason why you don't want to use the 5.1 DTS 'core'?

[tebasuna51]

The core is a lossy encoded, for what use it if you have the losless source?

[SeeMoreDigital]

Originally Posted by tebasuna51

The core is a lossy encoded, for what use it if you have the losless source?

DanDare1983 is encoding from lossless 7.1 DTS-HD MA to lossy 5.1 Dolby Digital. So my question is, why not extract 'and play' the lossy 5.1 DTS stream instead of encoding and playing a lossy 5.1 Dolby Digital stream?

[tebasuna51]

Of course, but some players (like some TV's, for instance the mine) can't support even the lossy core DTS, without problem with AC3 (my TV can send by SPDIF the AC3, also EAC3 5.1.2 to my Denon 5.1.2)

There are also the size to store, the AC3 640 Kb/s have equivalent quality than DTS core 1510 Kb/s (size x 2.3)

[DanDare1983]

Hi just a quick question. I have a playlist where the DTS-HD MA track has a delay of -1001ms. eac3to gets it down to -2ms which i understand is perfectly fine. Can I ask if the DTS core also has the same delay? If so, does that also get fixed?

[tebasuna51]

In fact when eac3to do the delay correction only add silence frames at the begining (delay +) , and that silence frames are only core frames because don't need MA extensions to codify silence.
To delay - delete first full frames (core+MA extensions)
Then the core is fixed also.