Messages

1

General Discussion / Re: Procrustes question

« on: April 18, 2025, 06:34:17 AM »

Hi Glamrlama,

Where is the default location of the speed control UI when behind other windows? Top, bottom, left, right, middle, or other screen location? When visible are you able to move it to where it is least likely to be completely covered by another window? If so, does it keep the new location between sessions?

Last question. 

Where can I download Procrustes v1.20a from? All the links I'm able to find are no longer working.

2

Skins / Re: Quinto Black CT

« on: April 17, 2025, 01:56:02 AM »

That appears to work! As I've said before, you're the man!

Thank you for your research and figuring this out.

3

Skins / Re: Quinto Black CT

« on: April 16, 2025, 01:14:12 AM »

Yeah, PeterK. is not happy with dro or the moderator at Winamp. I can quickly reposition the cover flow window if it changes, so I'll live with it for now.

4

Skins / Re: Quinto Black CT

« on: April 15, 2025, 03:48:15 AM »

Hi ariszlo,

Thank you for the info.

I had already installed Quinto Black CT v4.4 for Winamp after deleting the v4.3 folders. I still have Winamp installed, mostly for nostalgia. I deleted the Winamp studio.xnf file before running v4.4 for the first time.

I installed v4.4 for WACUP today after deleting the v4.3 folders. I did not remove the WACUP studio.xnf file, but I did delete it's skin section for v4.3 before running v4.4 for the first time.

So far the v4.4 skin works fine on Winamp and WACUP. I do see one difference from v4.3. I use the album cover flow feature. If I position the feature's window with it's background visible and then hide the background when switching skins or ending a session, the window returns to it's default position when switching back or starting a new session. If I leave the background visible, the position I put the window in stays the same. I was able to hide the window's background in v4.3 when switching skins or starting a new session without affecting the position I put in window in. I don't know if this is a bug or a  change in the way the feature works. Either way, it's a minor thing.

I prefer to run Milkdrop in a window behind the album cover flow albumart instead of it's normal background.

5

Skins / Re: Quinto Black CT

« on: April 11, 2025, 02:26:09 AM »

Do I also have to remove the studio.xnf file?

I don't know but as far as I can judge probably not.

Hi ariszlo,

As dro stated, it has been a long standing requirement to remove the studio.xnf file and let it be re-built when updating Quinto Black CT. It would be nice if that was no longer needed.

Do you have a way of directly contacting Peter? I tried via the last email address I have for him. No reply as far.

6

Skins / Re: Quinto Black CT

« on: April 10, 2025, 05:14:01 PM »

Hi dro,

Studio.xnf without the previous line breaks has been working normally. Thank you for responding to this thread and the text editor suggestion. I've been using notepad for my manual editing of studio.xnf, when needed. I can use another text editor to deal with the change of line breaks.

I removed the studio.xnf.backup file between WACUP sessions. It was recreated after the next session. As you know, studio.xnf is updated after a session if needed, like if the modern skin was changed during the session. Both studio.xnf and the backup file now appear to have no line breaks. Without the line breaks, it takes longer to find sections in the file when I need to edit stuff. I seldom need to edit stuff (since I seldom change the modern skins I'm using), so having to take more time was not a problem, more of a minor nuisance.

It is best not to manually edit the file anyway. I have learned over the years that if not very careful, it is easy to mess it up.

7

Skins / Re: Quinto Black CT

« on: April 10, 2025, 12:21:15 AM »

Eh? I've not changed the format of that file afaict since it's still being written out by the gen_ff plug-in (which is the part I hook into to be able to make a backup of the file but it's format shouldn't be different otherwise things wouldn't be able to be read back in correctly).

...

A few beta versions ago, the line breaks in the file in my configuration changed. I assumed you were responsible for it. This is another reason why it is never good to assume. I think I can find around the date it happened if you want to know. I think it was when the backup copy first appeared. I made a copy of the file with the old line breaks format. I can post a copy of both, if it would help you see what I'm talking about.

8

Skins / Re: Quinto Black CT

« on: April 09, 2025, 04:41:05 PM »

Hi,

Do I also have to remove the studio.xnf file?

Dro has changed the format of the studio.xnf file. This makes it much harder to manually enter the configuration info for other modern skins that have not changed. I really like Quinto Black CT, but I use other modern skins and it is very inconvenient to have to reconfiguration the arrangements of these skins every time Quinto Black CT is updated.

9

Wishlist / Feature Requests / Re: Options for the Lyrics Plug-in

« on: March 27, 2025, 04:37:56 AM »

Ok, I better understand why you have things implemented the way you have. If you decide to add the options mentioned, they could be a useful addition instead of what I asked for. After I add or correct the metadata in my files, I make them read-only to prevent inadvertent changes. So, a mode to store lyrics in the files themselves would not be useful for me.  I don't need to prune the entire cache, I just wanted to prevent the empty files. What would be considered too large a cache?

Sometime I use playlists that only contain instrumental songs. It would be just as fast to disable the lyrics plug-in in this case, than enabling an option to not create text files. Those that mix file files with and without lyrics in the same playlist will have to find their own solutions for not wasting directory name space on intentional empty files.

I have been deleting the empty files to force re-querying for lyrics in case they may be found later, when the same files are played again. I understand why you don't want to trigger multiple online look-ups. I think it would be worth the resources used if lyrics are found later. I will stop deleting the empty files, if you think the re-querying will lead to crashes or other processing errors in WACUP. Wasting directory name space is worth it if it prevents WACUP processing errors, imo.

During a session, I have been adding the song titles above the start of the lyrics in the text files, after they finish playing. From time to time, there are errors in the lyrics found online that I have been correcting manually. During a session, I make notes of which files need corrections and these titles help me find these files faster in between sessions, when I make the corrections.

Reasonable people can always disagree on the best way to handle things. Whether I agree with your design decisions or not, I want you to know that I appreciate all you have done and continue to do that makes WACUP better than Winamp was, imo. I don't expect WACUP to do everything the way I would like things done. Expect for real bugs, I learn to work with the ways things are done in WACUP and the skins. In case of skins, I sometimes make small changes in some of their image and script files, when possible, to have them look and work more to my liking, for my personal use.

10

Wishlist / Feature Requests / Options for the Lyrics Plug-in

« on: March 25, 2025, 08:11:32 AM »

Hi dro,

As you know your lyrics plug-in (gen_lyrics.dll) creates text files for every song file that is played. These text files contain the song lyrics if lyrics are found online and are zero length files if no lyrics are found. Can you add to this plug-in's configuration options, an option to not create a text file if no lyrics are found? Can you also add an option to not create text files, even if lyrics are found?

Also, these files are given alpha-numeric names that have no clear relationship to the songs. Can you include the metadata %title% in the text file name or include the %title% on a separate line at the top of the included text when lyrics are found? If the song file doesn't contain the %title% metadata, then the file name could be used.

11

Visualisations / Re: Martins collection of milkdrop presets

« on: March 01, 2025, 08:20:16 PM »

Hi Nitorami,

I really enjoy using your Milkdrop presets. Thank you for this package of updates. They do run better with the Nvidia graphics card I'm using. I'm using version 2.39 of Milkdrop that comes with the current x86 beta build #21066 of WACUP.

12

General Discussion / Re: How To Recover Off-Screen Modules

« on: February 14, 2025, 06:09:47 AM »

Hi dro,

Thank you for having the beta version of WACUP now make backups of the studio.xnf file. I had been making manual backups from time to time. It is better to have a backup automatically made each time WACUP is ran.

13

General Discussion / Re: Swap Left and Right Channels ...

« on: January 04, 2025, 08:37:04 PM »

Hi,

Sounds like I need to look into the Peace EQ. The AC3Filter code is limited to 5.1. I have been holding back on moving to a 7.1 speaker system because of that. 

Thank you for mentioning it!

14

General Discussion / Re: Swap Left and Right Channels ...

« on: January 04, 2025, 03:57:45 AM »

Ok, no problems. I have a 5.1 speaker system and wanted a custom way to direct the stereo channels to all my speakers.

Happy New Year!

15

General Discussion / Re: Swap Left and Right Channels ...

« on: January 04, 2025, 03:02:56 AM »

The configuration can be as complicated or simple as you want. The simplest way to just swap channels is to set the mixing matrix on the Mixer panel as follows: enter 1.0 in the R column of the L' row, 1.0 in the L column of the R' row and 0 in all the other matrix boxes; and disable the Delays. Uncheck all the options on the Options panel, disable the AGC and set the output format to match that of your source files. You should set all the boxes on the Gains panel to 0 and disable the DRC.

I suggest you read how it works and experiment with different settings.

Oh, I forgot to mention that this output plug-in directs it's output to another output plug-in. I use the Not So Direct v1.7.11 (out_notsodirect.dll) plug-in.