5.8 Beta Bugs Thread

[Prelim]

Been using WASAPI output plugin on Win7 since release, no problems with playback so far.

The only bug I've found so far is that every time i change songs manually/enqueue the WASAPI volume output resets back to something extremely quiet (close to 1%)

Really annoying.

THIS!

very annoying indeed, otherwise I would prefer WASAPI plugin

[FixTheSize!]

I have seen this mentioned twice i other threads, with no real response / solution. I am a windows 10 user - laptop. I just downloaded the latest 5.8 3660 version. The display is so tiny as to be completely illegible. Even using the 2x (Ctrl+D) "trick" - that only increases the playlist size - along with font if I change that. None of the headings or main/eq button sizes are large enough to see. I'm not geriatric, nor blind. Nigh on 20 years ago, with the old versions, I was able to increase the size of all components - and the buttons would increase in size as well.

I prefer to use the Classic skin, but have experimented with all 4 in this version - all having the same size/legibility issues of the components.

I don't have this issue with any other programs on this computer...

This makes it extremely difficult and frustrating to use. ...and I've always been quite fond of the player!

THANKS!

[NJK]

go back to 5.6 and problem is solved.
since there is no development team ,issues won't be solved anytime soon.

[MrSinatra]

I don't have any 5.8 size issues, but I use Bento.

Are the issues skin specific?

[NJK]

I don't have any 5.8 size issues, but I use Bento.

Are the issues skin specific?

as i also have no issues with the default modern skin
but on a windows 7 laptop i can change size in the old green skin but not on my windows 10 pc.

the bento skin is also sizeable but the default old skin is limited on windows 10

[FixTheSize!]

go back to 5.6 and problem is solved.
since there is no development team ,issues won't be solved anytime soon.

Perfect - solved the problems. This is why change is bad!

I don't have any 5.8 size issues, but I use Bento.

Are the issues skin specific?

As I stated, I experimented with all 4 skins, and some basic options. I am not a tech-wizard, and don't fiddle behind the curtains as you guys seem wont to do though. NJK's solution was just dandy.

[MrSinatra]

My read is the problem with 5.8 ur having is unique to u, since others with 5.8, like myself, are not having it. Doesn't mean there isn't some niche case at play here tho.

[musicf8]

I think this is all about if you are using a larger DPI scale instead of 100% which is standard (e.g. using 200% on a 4K display). If so, then it is a winamp/skin problem. Wacup does have modified skins that fix most of the issues for a higer DPI scale

[MrSinatra]

That sounds good, but why would 5.666 fix that?

[musicf8]

¯\_(ツ)_/¯
Misread that going back to the stable release fixed it, I figured it was a DPI issue, but sounds like it was a skin/install issue

[yarrmateys]

i'm unsure why, but recently after i leave winamp 5.8 running overnight it will freeze, requiring me to kill it through task manager. sometimes this freezing will even affect the system and cause huge lag and freezing until winamp's off. in the task manager its memory use goes over 1.2 gb, which may be some sort of memory leak. it seems to happen with a very large playlist (1890 entries in the m3u8 file, total nearly 125 hours of music), maybe this is related, since i don't think it happens to smaller ones. this is on windows 7 in case this matters.

[MrSinatra]

i don't think thats an especially large playlist...

i have had similar issues tho with many versions of winamp... u could install the time restore plugin to save ur spot and set the computer to reboot once a day, might help.

[yarrmateys]

no need to reboot the pc, shutting winamp down is enough since it clears out all the garbage data from the cache. the problem only happens once the memory leak happens and winamp's memory use spirals out of control until it gets around the 32 bit memory limit.

it may be related to inactivity, one time while i had it running for around half a day the ram use also got to 1.2 gb but it still worked, it seems it freezes only after prolonged inactivity, like when i leave it running overnight. maybe it's pagefile related, though i'm unsure why would it use it since i have 32 gb of ram and most of the time 50-60% of it is free.

[MrSinatra]

ok, so automate a batch file to close and restart winamp, and with the time restore plugin u won't lose your place.

i would like a winamp plugin that monitors winamps memory usage, and alerted the user when the mem usage leaks / gets abnormally high and or restarts winamp if that occurs.