WACUP
Preview Build Discussion => Preview Build Discussion => Topic started by: MourningStar on March 13, 2021, 04:04:18 AM
-
I have my video window sized to the same as my album art (refer to other threads with attached images of my setup). I have the settings to open@video playback and close@video stop. If I stop and replay, the video window has relocated and parked itself at the bottom of the screen. Same if I exit session and start new session.
-
(https://i.imgur.com/RfJfydI.gif)(https://i.imgur.com/RfJfydI.gif)(https://i.imgur.com/RfJfydI.gif)
-
There's no need to bump & it'll be looked at once I've finished triaging & fixing what I can from the initial few days worth of crash reports before I then look at the non-crashing issues.
-dro
-
... it'll be looked at once I've finished triaging & fixing what I can from the initial few days worth of crash reports before I then look at the non-crashing issues.
-dro
geeez, been using wacup since you put it out there and never a crash. wtf are people doing w/this app ?!?!?!?!?! (you need not reply, just venting)
(oh wait - I did have that single issue a few weeks back and you promptly addressed that with a simple 'delete 2 files' fix [thx again], so, I don't really count that.)
-
Press F5 in a modern skin one too many times and you'll have the engine throw a hissyfit (don't actually do this, please)
-
Press F5 in a modern skin one too many times and you'll have the engine throw a hissyfit (don't actually do this, please)
^
shhhhh ... Darren, don't look now but there's one of 'those' people ... :P
-
geeez, been using wacup since you put it out there and never a crash. wtf are people doing w/this app ?!?!?!?!?!
It's quite easy depending on what's being done. Modern skins definitely are more likely to experience an issue due to bugs in the plug-in responsible. There's then behaviours that block the main ui thread & trigger the unresponsive handling (some of which has been resolved e.g. drag+drop a massive folder onto the main playlist used to do that).
There's also issues from some of the other 5.666 plug-ins that are still being used like the local media library plug-in (ml_local) which does weird things at times with it's importing or in_mp3 & it's metadata handling & so on. There's then anything I've introduced with writing new code like 7170 would lock-up when adding files from the browse folder & a title update was also requested which never appeared from beta testers but showed up under the preview build once you have more people using things.
Most I don't think ever have an actual crash issue but if I ignore such things then we end up with what was leveraged against Winamp proper for many years of it being buggy / unstable which was completely true until more focus was put on resolving such things around 5.64 - 5.66x when those public builds also included the beta builds crash reporter (something that should have been a priority much soon).
So be happy you're not having issues & be happy that for those who do & for whom I can understand from the crash report what's going on that I take dealing with crash reports as a higher priority to try to give a good experience as no one likes things crashing & sadly there's still more for me to do to improve things which will come as more gets replaced (ignoring the dips when new code comes in at times).
-dro
-
So be happy ...
I be happy!!!
(https://aws1.discourse-cdn.com/helloforos/original/4X/2/f/9/2f9173ccfc31504d7e2e7625d4cfb4204ebbc7c1.gif)