Problem with certain .wav files

Hi all,

I've noticed that in the most recent versions of MPC-HC 64-bit (I'm currently using the version included with K-Lite Mega 13.0.0; I apologize but I am unsure with which version this problem originated), there's a bit of a problem when playing 22050 Hz .wav files that are recognized by MPC as 0 seconds or 1 second in length--namely, the file will "play" as complete silence for the same length of time, and then play properly, as it should (I hope my wording makes sense). The time indicator will be at the end while the sound plays correctly.

Note: I have tested .ogg and .mp3 files as well, and they do not have this problem. I have also tested 11025 Hz and 44100 Hz .wav files, as well as 22050 Hz .wav files that are recognized by MPC as longer than 1 second, and they do not have the problem either. (EDIT: I have one file of a very uncommon sample rate--15616 Hz--which is recognized as 2 seconds long and does the same thing. Also, for 44100 Hz .wav files, it does seem to happen when the file is recognized as less than 1 second.)

It's weird that it only happens with these specific kinds of files. Other media players (such as VLC and--bleh--Windows Media Player) play the sounds the way they should be played.

This isn't a major issue, but is there some way to fix this? It annoys me when this happens, for some reason.

Could you upload one (or more) of those files for me? Then I can check what is wrong.

http://www.sendspace.com

https://www.sendspace.com/file/1th669

1 second sine at 22050 Hz.

This should fix it:
LAV Splitter settings > Input formats > wav should be unchecked
MPC-HC options > Internal Filters > DTS/DTS-HD source filter should be unchecked

Now you should see "Wave Parser" in Menu>Play>Filters during playback.

I will investigate why it fails with LAV Splitter.

In next version of the pack, it will also work properly with LAV Splitter. The problem has been fixed.

Admin wrote:This should fix it:
[...]
MPC-HC options > Internal Filters > DTS/DTS-HD source filter should be unchecked
[...]

Just doing that seems to have fixed it for me. Thanks!