Latest WACUP beta release is build #6840 (December 31st 2020)

Latest WACUP public preview is build #6840 (December 31st 2020)

Recent Posts

Pages: [1] 2 3 ... 10
1
It depends on the metadata tag format & what it supports as to how many options there can be.

Currently I'm using whatever is found first but with a preference for the front cover as that's more likely to exist. Reading in the other bits of artwork isn't much more work.

The pain is how to do it in the ui when especially with modern skins involved, there's no easy solution at the moment to allow them to distinguish let alone cycle between them (unless I've missed something with gen_ff's handling of artwork). That's why I've not actively done anything as other than the alt+3 dialog & the artwork window (aimed for classic skins but can be used with modern), where it's generally wanted it can't be leveraged for now.

-dro
2
I am confused. I can assign (embed) a unique image to every track in a album. Sometimes I assign the cover to the first track and the back cover to the last track and each song a page from the booklet. However, I did not know one could assign (embed) more than one image per track.
3
I've determined what I believe to be the cause of the performance regression & I'm now back to being able to run WACUP's Milkdrop build at the specified FPS without it being a factor lower. Am hoping to release a newer preview build with the fix later this week.

-dro
4
Not sure if you're still following this or not but I've just spent the past 4hours tonight trawling back over all of the changes from 2.30 back to around 2.26k (from around October 2019 based on the commit logs) & I've not found anything obvious within the plug-in that could explain a drop in performance when there's less blocking code running now than before (I also should have realised that 2.26k was massively older compared to the current previews).

However I have noticed that the fps limiter doesn't seem to be right with a number of builds after that old one (e.g. 30fps runs at 22fps) so it's either due to the change in the compiler used (which was a change made around that time) & it's something about that which is causing the issue or I've broken something within my handling of vis render calls (irrespective of the input plug-in) within the WACUP core itself.

I'll be looking into this more as the "30fps runs at 22fps" thing is definitely odd especially with small window sizes where there's no obvious reason for a limitation in what's going on.

-dro
5
Wishlist / Feature Requests / Re: Artwork : Display front cover instead of first image
« Last post by Aminifu on January 16, 2021, 11:49:30 PM »
Beginning with version 2 of the mp3 standard it is very flexible with regards to the type and number of images that can be embedded. However in practice only one image is ever usually embedded. Winamp v 5.666.3516 and so far WACUP only recognizes 1 embedded image. It is usually the embedded image tagged as the cover.

Years ago there was a Winamp plug-in that could read and display multiple embedded images in mp3 files. Unfortunately it stopped working and I don't remember what it was called. Maybe some old timers who read this will remember what it was. Even better, have a copy that dro could look at when he has the time.
6
Preview Build Discussion / Re: Strange phenomenon - annihilated main and playlist windows
« Last post by Mits on January 16, 2021, 04:57:09 PM »
Well, Microsoft with billions of dollars invested and an army of devs didn't find an idiot-proof solution yet, so it would be preposterous to assume you could do it in a jiffy by yourself... The only realistic and sane advice is "everything should be made as simple as possible, but not simpler."
7
Wishlist / Feature Requests / Re: Artwork : Display front cover instead of first image
« Last post by Mits on January 16, 2021, 04:51:40 PM »
I was never aware that you could embed more than one picture in a music file. I did some research and it seems it's not provisioned in the mp3 specifications. For example, a nice small utility that embeds pictures (https://archive.codeplex.com/?p=mp3artembedder) implies that only one is possible.

Therefore, I assume that the mp3 producer used an automated tagger tool which embedded the wrong picture from a list of albumart scans. I think the only remedy is to find the correct cover and re-embed it by using the File Info - Artwork tab (Alt+3) in Wacup.
8
General Discussion / Re: High res audio player
« Last post by Mits on January 16, 2021, 04:34:28 PM »
Dear RudieV, I have not yet delved in the Windows 10 audio stack (and don't intend to, I'm Win7 for life), but from my long experience in Win7, unless you use ASIO or WASAPI output, Windows will get in the way and won't let you by default output anything other than 16/44 unless configured so. 24/96 is possible, even 5.1 and 7.1, Dolby 24/96 or DTS (see https://windowsreport.com/get-dts-sound-pc/) but higher-res is totally out of the question with Directsound.

IMHO it's not productive for the Wacup developers to compare Wacup performance and capabilities with that of fourth-party players like MusicBee. I can too name a dozen apps, free and paid, that can play DSD properly, but please consider that we are all here to help make Wacup come to at least the level of Winamp, when I presume it will finally get out of beta.

Therefore, please report first if what you want to is feasible with Winamp 5.666 (patched). If it's not, there are numerous known and unknown scenarios for what may be wrong in your case.

Finally, don't assume that the DAC drivers, however expensive it is, are written properly - in the audio world the norm is a patchwork of fixes upon fixes.
9
General Discussion / Re: Play/Open Folder Issue
« Last post by Mits on January 16, 2021, 03:58:45 PM »
Dear Morningstar, I was trying to understand your problem and specifically what you mean by "playing random files in a folder" - how do you actually randomize them, and for what purpose?

And most importantly, but very OOT, from your screenshots I understand that you keep your music in the default "This PC" locations (in C:\Users\<yourusername>), which is IMHO very bad practice. When running Win10, all user files in default user locations (Documents, Music, Pictures etc) should be considered as at risk and potentially expandable if a Windows Update goes wrong. Thousands of such cases have been reported and more people are still searching and/or mourning for their files. The best practice is to reorganise your folders so that your personal files are outside C:\Users .

This is one of the main reasons I'm staying away from Win10 for the foreseeable future (a few more years by god's will) and I also advise so my dearest friends. As I said, very OOT but critical for our mental health :-)
10
General Discussion / Re: Extra plugins you may need
« Last post by Mits on January 16, 2021, 03:38:25 PM »
Thanks for the info! By listing them I presume you have tested them as fully working in the December build and for portable installations too?

Since it seems you're a plugin expert, have you any idea what is the condition for a 3rd party plugin to be accepted by Wacup as legit and be listed as a candidate plugin in Preferences? I am trying to test the MAD input plugin (indispensable imho for any music player) as well as the old WASAPI-NT plugin in case it works better than the not-so-yasapi bundled, but they are not even listed as installed (and yes, I have the 'Allow 3rd party plugins'checkbox checked).

Thanks in advance for any tips!
Pages: [1] 2 3 ... 10