Latest WACUP public preview for x86 & x64 is build #24496 (May 8th 2026) (x86 & x64 changelogs)
Latest restricted WACUP beta release is build #24496 (May 8th 2026) (x86 & x64 changelogs)

Recent Posts

Pages: 1 ... 6 7 [8] 9 10
71
Ok I make the following test :

Installation in portable version of 99 47 23960, 99 49 and 99 50 in 3 different folders. Skin Classic Default

No change in preferences. I only import some mp3 and mp4 in the media library (the same for the 3 test), I play a mp4 and a mp3 after.

In 99 47, the video windows close after the end of the mp4 and play the mp3. Il 49 and 50 the video windows stay open.... So the change is between 47 and 49 version...
72
There are "smart views" in wacup's local library plug-in as that's what they were coded to replicate so I don't know why you're saying there aren't...

My fault !!!! I made a mistake at my first test, i understand now, I start the software and try the skin and putting windows on my various screen and I try smart view which was grey... I look on the net, find someone who explained that you had to take a dll from winamp. But I did all this BEFORE adding some media into the local libraty (So of course the Add View it was "grey"... !)

So, i'm going to test with a brand new install, it's possible that my video windows which do not close problem come from the winamp ;dll I imported...  I let you know asap. Thanks.
73
I think I didn't express myself clearly, so I'll use a translator this time. What I meant was that Not So Direct is my preferred output option given the lack of logarithmic volume in the WASAPI output. In any case, this is a matter of personal preference. As you said, every output option has its pros and cons.

Actually, I also didn't mention earlier that I experienced stuttering, especially when I lowered the buffer from the default of 2000 to about 1000 to see if it would make a difference with the crashes. In fact, before it crashed, I noticed significant stuttering. Maybe check if it has something to do with buffering

74
What about using the /procdump mode is still causing issues for you as that should be able to catch failures otherwise good or bad behaviours shouldn't be altered whether that debugging mode is being used or not.

The OP has also mentioned that changing the output plug-in makes no difference to them.

As for the comment about WASAPI being better, imho that's not true when all of the output plug-ins can & do have issues for some setups & as I'm currently working on debugging a stuttering issue related to a crash fix that was introduced with the notsodirect plug-in for 24472 (something that 24360 didn't have but instead would cause it to crash) could be behind your problem. It's also way there are other output plug-ins provided & yes for some setups wasapi might be the better solution but directsound is generally a more compatible fix for what is being targetted sans the problems with it which have been being worked through.
75
I am experiencing the exact same issue since the last update (1.99.49.24360). However, after the new May 4th update nothing changed, and instead of happening only shortly after launch, it happens with a new playlist, so when I open a file from my media library with a 50% chance.

No error reporting gets triggered and running with /procdump or in safe mode still causes issues. Switching from Not So Direct to the WASAPI output did fix this issue, though, so I'd suggest looking into that, also because it's the best output you can choose at the moment.
76
It'll need a new build as the input plug-in is seemingly working fine but with the alt+3 aspect there's a problem with how the core is handling the look-up for filepaths ending like "nsfe::NSF,16,,,0,,0" which is already meant to be dealt with to extract it out as 'nsfe' but something is going awry which I've still to debug further (but have a simple change for that which is better to do anyway). I can't replicate the normal atf handling failing to get the metadata unless you've got those items in the local library & if so then you'll need to try refreshing them as the metadata from that is used instead of always going to the file.

[edit]
I can do it as part of a post-release update patch instead of needing to involve a complete so that'll go up in the next few days.
77
I'll have to look into why title is missing as I hadn't noticed it tbh as my playlist items seemed to be showing it whereas it's only via the alt+3 dialog that it's obviously failing to fill the fields when there is the handling to return it like with artist & few other metadata values (which seem to be returned as expected from an initial look).
78
Thank you, the issue has been fixed in the latest builds. A question: Is it possible to show the track names in the playlist? I tried using the ATF formatting but it only shows the %artist% and %filename% tags (it seams that the plugin doesn't return the tag %title%)
79
There are "smart views" in wacup's local library plug-in as that's what they were coded to replicate so I don't know why you're saying there aren't...
80
I was using Winamp in my clubs since the 90's... Never found another music program with floating windows which can open a video windows on a specific screen when a video file is in the playlist ans close the windows when the video ends (My playlist have MP3 AND MP4...) so stay with it even when it was no more supported.

A friend told me to try Wacup a few mouth ago and it's just the winamp spirit in 2026 ! You can easily try it in portable mode. The only problem (easy to hack) is that there is no smart views in the Wacup media library (But you just have to take a dll from Winamp and copy it in Wacup and you have smart views so not a real problem). Great software !
Pages: 1 ... 6 7 [8] 9 10