WACUP
General => General Discussion => Topic started by: SuperVGBoy on December 04, 2024, 12:50:07 AM
-
A problem I have been encountering with playing music with WACUP is the start of some songs are completely cut off. This commonly happens with songs that have a bit of a lead-in before the rest of the song plays.
I assume it has to do with the volume of the lead-in, but I don't know how to disable/mitigate the cutoff.
Version I'm using: 1.99.22.20202
-
Do you remember what file type(s) those affected files might be?
-
They're .MP3 files
-
Hi SuperVGBoy,
Happy Holidays!
I have 6,693 mp3s in my collection. They vary in length from 1:14 to 20:06 minutes (with various amounts of silence or low volume when they start) and all are decoded correctly by the old input plug-in (in_mp3.dll v4.103). If your problem mp3s are encoded properly, maybe it's the output plug-in you're using that is causing your issue.
The out_notsodirect.dll output plug-in (v1.7.8.) has an option to remove silence at the start and/or end of tracks. It requires selecting the proper dB level and several seconds of buffer space. It doesn't work very well for me, so I just accept the few seconds of silence some of my songs start and/or end with. These few seconds of silence do not cut off any part of the actual songs.
The app "mp3 DirectCut" lets you delete (cut out) silence at the start and/or end of mp3s without needing to re-encode the mp3s. I have used it successfully to modify my mp3s that had more than a few seconds of silence at their beginning and/or end.
-
Simple option is change the active output plug-in to wasapi & see if that makes a difference. As either the output is clipping silence or the MP3 decoder is doing it but that's a bit more involved to change around (unless you make a test portable install using the x64 build so the existing installation isn't altered & the x64 build uses a different decoder plug-in compared to the x86 build which would rule out decoder vs the files being played).