Latest WACUP public preview for x86 & x64 is build #24360 (April 20th 2026) (x86 & x64 changelogs)
Latest restricted WACUP beta release is build #24360 (April 20th 2026) (x86 & x64 changelogs)

Author Topic: My MP4/Video Issue  (Read 33655 times)

Nazgul

  • Newbie
  • *
  • Posts: 1
    • View Profile
Re: My MP4/Video Issue
« Reply #15 on: Yesterday at 03:06:19 PM »
I've been using the latest original Winamp build (5.9.1 from Dec 2022), but now that I am having more and more 4K video files in my library, it needs replacement, because there is a 50% change it will crash/freeze when playing back the 4K MP4 video file.

So, I tired the latest WACUP. The good news is - it doesn't crash/freeze when playing 4K videos. The bad news is, I am experiencing pixalation artefacts when playing back ANY video in the library, including the 1080p ones that the original Winamp plays back just fine.

This thread discusses adjusting some setting to mitigate playback issues, but I couldn't find any adjustable options for the in_mp4.dll under the "Input plugins" section. Is there some other place I can adust it?

dro

  • Admin / WACUP Developer
  • Administrator
  • Hero Member
  • *****
  • Posts: 5709
    • View Profile
    • WACUP (Winamp Community Update Project)
Re: My MP4/Video Issue
« Reply #16 on: Yesterday at 03:21:07 PM »
Without knowing what codecs are needing to be handled within these mp4 files, I'm going to assume it's h264 content & by default for that video codec via my in_mp4 plug-in it'll attempt to use the OSes mediafoundation api which should work unless it's not able to trigger the hardware handling which is more likely going to cause the rendering issues.

Alternatively it can be made to try to use the openh264 decoder by changing the setting on the Video prefs page which can work better for some or it can be worse (as is the case for me).

If that still doesn't help then you can try setting MP4 to be handled by wacup's DirectShow decoder plug-in (in_what) which if these files are all named .mp4 then you can just remove that from in_mp4's configuration list & that should then force them to go to the in_what plug-in without having to mess around with it's configuration since it's the default fallback plug-in for any local files not handled by the other input plug-ins. This does require there to be the appropriate DirectShow filters correctly setup to be used by it.