Latest WACUP public preview for x86 & x64 is build #22656 (September 12th 2025) (x86 & x64 changelogs)
Latest restricted WACUP beta release is build #22656 (September 12th 2025) (x86 & x64 changelogs)

« previous next »
Pages: [1]   Go Down

Author Topic: my wacup  (Read 5463 times)

richard johnson

  • Newbie
  • *
  • Posts: 4
    • View Profile
my wacup
« on: March 18, 2021, 09:12:26 PM »
it crashes 7 times in a row
sent crash reports
i am a artist writer ilive of my wacup had one form or the other 98 99
i just dont want to loose library history ect i have 40000 plus songs
1ooooo hours music most number for nameif i loose personal info start over
i cool with that NEED WACUP TO WORK
I DO NOT LIKE ANY OTHER WANT TO BE WINAMP
please let me know whats up cant write code
had computer late 80
thank for doing this i was out for a few 1st thing i did look for winamp no where
smash computer then wacup appeared  i was not in jail VEGAS IT SUCK ME UP
THANK U IF THIS IS NOT THE WAY TO DO THIS
TELL I KNOW THIS IS PUBLIC
Logged

richard johnson

  • Newbie
  • *
  • Posts: 4
    • View Profile
Re: my wacup
« Reply #1 on: March 18, 2021, 09:18:19 PM »
TRIED SAFE MODE CRASH
REPORTS IN ZIPE
Logged

richard johnson

  • Newbie
  • *
  • Posts: 4
    • View Profile
Re: my wacup
« Reply #2 on: March 18, 2021, 09:49:30 PM »
fixed it
Logged

Eris Lund

  • The Skin Guy, Official Modern Skin tech support
  • Beta Tester
  • Hero Member
  • *****
  • Posts: 320
    • View Profile
    • Eris Lund's Github
Re: my wacup
« Reply #3 on: March 18, 2021, 09:51:10 PM »
How'd you fix it?
Might be good for others to know
Logged
Maker of Plugins, I suppose.
gen_native:
https://github.com/0x5066/gen_native
vis_sdl2:
https://github.com/0x5066/WinampVis
(I know, creative names)

dro

  • Admin / WACUP Developer
  • Administrator
  • Hero Member
  • *****
  • Posts: 5397
    • View Profile
    • WACUP (Winamp Community Update Project)
Re: my wacup
« Reply #4 on: March 18, 2021, 10:26:52 PM »
All I can tell from an initial look at the 2 crash reports is that something was attempting to be played via in_mp3.dll & it's caused the notsodirect output plug-in to effectively lock-up. Knowing what was done to fix it even it's just doing something like changing the output plug-in used would be helpful. I'd also appreciate a bit more information about what was going on at the time of the crashes if possible.

-dro
Logged
Pages: [1]   Go Up
« previous next »