Skip to main content ↑ ↓

Notice

Please note that most of the software linked on this forum is likely to be safe to use. If you are unsure, feel free to ask in the relevant topics, or send a private message to an administrator or moderator. To help curb the problems of false positives, or in the event that you do find actual malware, you can contribute through the article linked here.
Topic: foo_input_dts "Malformed audio chunk" (Read 1606 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

foo_input_dts "Malformed audio chunk"

When I scan ANY .dts file (tried with multiple sources, whether standard, 96/24, etc.) with ReplayGain, even though they all play fine with no audible glitches, ReplayGain throws up an error under the "Status" column, "Malformed audio chunk", and refuses to give results in any of the other columns. Said malformed chunk, I'm guessing, is "read" at the end of the file rather than the beginning, because the progress bar does take its time to complete.

This did not always happen (I have some old .dts files that I DID successfully ReplayGain at one time) but has been happening for at least several months; I'm using the current version of Foobar as I write this (1.6.11). Sadly I didn't think to document which version it started with. I have tried this on both Windows 7 and Windows 10 on fresh installations of both Windows itself and Foobar, with no other 3rd-party components besides foo_input_dts installed.

Does anyone else have this issue? Thanks.

Re: foo_input_dts "Malformed audio chunk"

Reply #1 –
Quote from: neotwinkie on
Sadly I didn't think to document which version it started with.
There are old fb2k versions at https://www.foobar2000.org/old . Portable "install" and try?

(I don't use .dts so I hardly have anything else to contribute.)
 

Re: foo_input_dts "Malformed audio chunk"

Reply #2 –
Excellent idea, thanks so much!

I worked my way through the old versions using the current foo_input_dts, and it seems to break when foobar2000 goes from v1.4.8 to 1.5. I really hope this helps get the issue fixed, but at least now I have a way to scan and tag my current .dts files.  :D