Not halted just resting a little. Also, Rocky is hogging the PC for his CUDASynth stuff. We got the low-hanging fruit on eac3to and what's left to do is hard stuff. Be patient I'll get back to it. Are there some bugs that you particularly would want to see addressed? Hey Curly, no worries I underst...

I was wondering if eac3to development has halted, will there be any further bug fixing? I believe it was said at some point that @Sherman would take over development as @Curly was taking a break, is that correct?

Page 180 https://www.etsi.org/deliver/etsi_ts/102100_102199/102114/01.03.01_60/ts_102114v010301p.pdf Hey Curly, I'm not sure if this was previously posted but thought I'd mention it regarding MKVToolNix having a DialNorm removal issue with DTS-HD headers too, there is some discussion where DTS-HD M...

@Curly I believe @Thunderbolt is referring to the DTS-HD MA/HRA DialNorm that is not removed for these codec variants, not sure why he mentioned "still works" as according to my knowledge it has never worked in previous Madshi builds, I've verified that it still is the case with the latest 3.47 rele...

I believe @digimaster's E-AC3 7.1 decoding bug is already referenced in the "Features and Functionality" list by @Guest 3, " Still decodes all eac3to streams as 5.1 (the core AC3 or EAC3) ignoring the depending frames with the extra channels. Maybe fix with updated libav dll's (ffmpeg can't create 7...

@ DelBoy83 , I personally never remove dialnorm on TrueHD/Atmos tracks and just turn off any related Dolby processing in my Denon AVR settings instead . This keeps Atmos track unchanged, for preservation and perfect playback on all compatible devices, while you can always convert to any other (loss...

When the Free Guy french (or german) eac3: 4: EAC3, French, 7.1 channels, 48kHz, dialnorm: 0dB "DDP 7.1" is extracted and loaded in eac3to show correctly: E-AC3, 7.1 channels, 0:01:01, 896kbps, 48kHz, dialnorm: -27dB (core: AC3, 5.1 channels, 0:01:01, 512kbps, 48kHz, dialnorm: -27dB ) maybe is a pr...

@curly I have a small sample of the 2021 film "Free Guy" that has a couple of secondary EAC3 tracks with a DialNorm value of 0dB, oddly this file previously exhibited the "Bitstream parsing" warning messages on these EAC3 tracks but are no longer present, perhaps @nautilus7's issue is a different on...

Hi, thanks for taking over the development of eac3to. There is an issue with 7.1 eac3 tracks (I believe only those without a 5.1 core) not recognised when muxed inside an mkv container. See log: MKV, 1 video track, 6 audio tracks, 5 subtitle tracks, 1:57:50, 24p /1.001 1: h264/AVC, 1080p24 /1.001 (...

I too can confirm that the latest 3.43 build has fixed the issue with this particular file I was having issue with that had AVC/DTS-HD streams, as @skull had discovered HEVC/DTS-HD streams were unaffected, I failed to mention I had no issues with HEVC with the previous 3.43 test build, anyway thanks...

Thanks for that @curly can confirm 3.43 test now indeed works fine without the INI present, sorry to ask but I'm assuming the 3.42 build is still affected here https://www.rationalqm.us/eac3to/ Not sure why I'm getting a crash with UsEac3to 1.3.3 with the latest 3.43 test build but not with 3.41 or ...

Hmm, I couldn't find an option for that. I suppose it happens automatically when needed. One thing to note is that if the DTS frame has a CRC, then repair cannot be done. That is similar/related to the inability to remove dialnorm for DTS. Are you asking what are zero bytes and/or what is an outdat...

I was curious if anyone could explain how eac3to actually removes "DTS zero padding" & repairs "outdated DTS ES headers", it's a notable feature " can remove DTS zero padding and repair outdated DTS-ES headers " of this utility, I know it was the only solution in allowing my DTS-HD MA 6.1 audio trac...

Oh thanks so very much for tackling it so swiftly, you're the man Curly

I noticed the cosmetic bug "-0 dB should be given as 0 dB." will not in fact be fixed, perhaps it is rather trivial but thought it would be deemed as a rather easier enough fix like the DTS "core" cosmetic bug that was displayed as "4" but is now correctly "-4dB", is this definitely not something to...

Hi Curly, I had brought this DTS DialNorm value cosmetic bug discrepancy that you had fixed concerning the -logdts command where the "core" DialNorm value wasn't displayed accurately like the master track, it was merely "4" when it should be "-4dB", it displays as "4dB" currently as you can see in t...

it removed DN for the DTS core & returned a value of -0dB I don't know why it is -0db instead of -31dB as for (E)AC3. I'll have to look into that too. Making an entry in the bug list. Still completing the list so remain patient for a while longer. Yes I will not bother you about it further, I under...

Hi Curly, I'm a bit confused by -removeDialnorm's behaviour with my sample file that I attached in my first post of this thread, the DTS-HD MA 7.1 audio stream has a DialNorm value of -4dB & when using -removeDialnorm & -logdts it still has a -4dB value not -0dB or -31dB, is that the expected behav...

Here is a test version for the DN changes: * You now have -removeDialnorm instead of -keepDialnorm. You will keep dial norm automatically unless you give -removeDialnorm. * Performance has been substantially improved by removing unnecessary CRC checks. * In the streams listing the dialnorm values a...

Thanks for that, then why does demuxing the core with tsMuxer, well it's including the sub-extension which is the DTS ES 6.1 Matrix extension, it reports it as DTS ES Matrix "7 channels" Really I don't know. I never see a software decoder than obtain 7 channels from a DTS ES Matrix , only hardware ...

Talking about XLL (like Atmos) don't exist a fix configuration and maybe for that can show the message I believe you meant XLL X (DTS:X) as that is like Atmos with its object-based audio metadata, the "XLL" (Extension Lossless) is simply referring to the DTS-HD MA extension. Do you know what "Bitst...

I believe eac3to has an issue with DTS-HD MA 7.1 streams that have a DTS ES 6.1 Matrix extension "DTS ES XLL", it is incorrectly flagged as DTS ES "5.1" when it should be "6.1" I don't think so. Only must be flagged 6.1 when there are 6.1 discrete channels (DTS-ES, 6.1 channels), the DTS ES Matrix ...

I believe eac3to has an issue with DTS-HD MA 7.1 streams that have a DTS ES 6.1 Matrix extension "DTS ES XLL", it is incorrectly flagged as DTS ES "5.1" when it should be "6.1", eac3to mentions "strange setup" in the log analysis. 2: DTS Master Audio, English, 7.1 (strange setup) channels, 24 bits, ...

I didn't mention my driver as I'm ashamed to say it is still on its release driver 301.10, I don't have much faith in Nvidia's driver stability they are always rife with issues, so for me I just let it remain on 301.10 & have been fine, I understand it's most certainly ill-advised for gaming but fin...

I also tried DGDecNV build 246 with the same "The procedure entry point cuvidGetDecoderCaps could not be located in the dynamic link library nvcuvid.dll" error, my GPU is a woefully outdated & underpowered GTX 680, I'm still on Windows 7 Professional 64-bit, is Windows 7 still supported?