Playing a file is crashing WACUP after my update to Windows 10 2004

[PimpUigi]

The only things I were doing was double checking the Nexuscast stream info. Making sure the ip, port number, address, and title were all typed right. Perhaps it's because Edcast dll's are in the directory or something. I will try a clean install (though retaining my Winamp.ini because I don't remember everything I've set by any means)

OK, still crashed, roughly at the same time as this Modify Post timestamp.
Crashed again with a clean winamp.ini just to be thorough. So now I'm out of ideas. : (

[dro]

Looking a bit closer I've just noticed it's not using the lame_enc.dll that WACUP requires & is instead using one from 2003 found in the C:\WINDOWS\SYSTEM32 folder. So that'll explain it going all weird & I'll need to add some extra checks to avoid using non-WACUP builds of that dll.

Other than removing the old lame_enc in the system directory (assuming that was only an edcast 'addition') to hopefully allow the wacup version to be used, it'll need a newer build of the plug-in to be able to do as I note above.

-dro

[PimpUigi]

Will the AAC encoding method work to let people listen from their iPhones via Safari, or Android from Chrome?
If so I'll just switch to the AAC encoder. It doesn't crash.

[dro]

Dunno about iphone/safari but android/chrome should work from my prior testing.

-dro

[PimpUigi]

Our listeners are reporting it's working. Thank you so much for helping with me navigate these issues!

[dro]

That's useful for me to know it's ok for iphones & hopefully that should be more stable

-dro

[PimpUigi]

Seems like it was frozen and just sent a crash report a minute ago.

[dro]

Can you try changing to use the Not So Direct output plug-in as it locked up somewhere in the 5.666 DirectSound output plug-in.

At least it shows it wasn't anything like an obvious resource / memory leak for the just over 2 days it had been running.

-dro

[PimpUigi]

It crashed again last night, I was too tired at the time to post. Up and running for 7 hours and 40 minutes now without issue. I don't think it sent a crash report either, next time I will make sure it does.

[dro]

Had you changed the output plug-in being used?

-dro

[PimpUigi]

Yeah, this is the way the window looks when I open the prefs.

[dro]

Rightio, just wanted to be sure

-dro

[PimpUigi]

Just had Wacup crash on me after at least four days of uptime. I think a crash report sent this time. Just letting you know, hoping it helps with research into why.

[dro]

According to the crash report, it was running for a bit longer than that

WACUP process running time: 9 days + 21:47:09

It seems it got into a weird state with the output plug-in being queried for information whilst another request was in-progress. There's also something indicating maybe the audio driver failed but I'm not sure if that was due to the lock-up or the lock-up was due to it. I'll try & make some changes to hopefully better deal with what I'm seeing in the crash report.

Still almost 10 days is good going compared to how it had been

-dro

[PimpUigi]

I'm glad that info was in there. It did feel like it was a more manageable uptime. : )
Perhaps I'll look for an updated audio driver if one exists.