WACUP 1.99.54.24960 crash

[Nukesforbreakfast]

Hello,

I've inexplicably started experiencing WACUP crashes with the 1.99.54.24960 64-bit WACUP build. Any time I try to change songs, or the current song finishes and it tries to go to the next song in the playlist, it hangs and then closes. As far as I can tell, it is not saving any crash dumps because I see none linked under the Advanced -> Error Reporting. I tried using the ProcDump button in the UI as well as running `wacup.exe /procdump` in a CMD window, but it doesn't restart when clicking the button and wacup doesn't launch when trying to run from CMD.

I tried uninstalling and reinstalling, but it seemed to remember the playlist/song information when I started it back up after a new install, so the clean install instructions I found didn't clear everything out as I expected. Are there official clean install instructions somewhere I can follow to try and resolve this, or some other way of trying to capture a crash dump or other diagnostic info?

Thanks!

[dro]

Is it the x86 or x64 build type? Also what version of Windows are you using & does making a portable test install via the installer modes make any difference to how it behaves? Otherwise the simple option is to go to preferences -> plug-ins -> output -> select notsoyasapi from the dropdown if notsodirect is the selected one & if notsoyasapi is the selected on then change the selection to be notsodirect.

If the action to restart or manually run via the procdump mode isn't working at all then that makes me assume the OS is getting in the way of things or procdump can't be obtained or there's a dependency loading issue which is causing the failure (something I'm not seeing).

I don't know what clean install instructions you were trying to follow but if the uninstaller is used then it prompts whether to keep the settings folder or not otherwise it'll do what it can to remove the whole program folder (assuming this wasn't a portable install anyway) & will indicate if there was anything left (not that it should typically relate to settings persisting). Am also assuming it's wacup's resume mode being used & not from a 3rd party plug-in which can & often will use the OS registry so isn't something that the uninstall knows about.

[Nukesforbreakfast]

I'm using the x64 build. I tried switching from notsodirect to notsoyasapi and the behavior was the same. I did uninstall via the installer and selected remove profile info, but when I reinstalled a non-portable install it launched remembering the playlist + current song + current song time. I'll try again and see if I missed something, and I'll try a portable install to see if that changes behavior. Thanks!

[dro]

If the output plug-in change isn't helping then it's likely something else that I'm not seeing / not aware off due to a lack of crash reports. The 24960 build has also had some post-release updates made available since yesterday (3rd) which can be obtained by going to Preferences -> About|Updates -> About tab -> follow the instructions on the button shown to get them though whether it'll help or not I don't know.

[Nukesforbreakfast]

Alright, I tried to perform the in-app update and it crashes before it can open the UAC prompt to apply the update. I've tried uninstalling multiple times selecting "yes" to remove all of the settings data, allowing the installer to automatically restart the PC, and it still remembers the last song, point in time in the song, and the last playlist when I re-install and re-launch WACUP.

If I do the portable install, the issue does not occur. The non-portable install still crashes on the same machine while the portable install of WACUP runs fine. I suspect there's something corrupted laying around somewhere that causes the non-portable install to behave badly. Is there documentation on how I can manually delete all of the files on my local disk and any registry keys that WACUP sets to effectuate a completely clean reinstall?

[Nukesforbreakfast]

By happenstance I managed to reproduce the issue on the portable install as well. It seems to stem from the fact that there's a .mpeg file in a folder of MP3s. It plays the .mpeg fine, but when it attempts to move on from that file in the playlist it crashes WACUP every time. I can't simply remove it from the playlist and move to the next song as when it tries to, WACUP crashes and then reloads remembering the song and its spot in the playlist. I had to remove the file from that location in the filesystem in order to resolve the issue. Would it be useful to provide that file here for testing purposes or is this expected behavior?