In WACUP v1.0.12.5586's playlist editor, is there a way to hide the paths?

[ant]

I only let WACUP "read metadata only when file(s) are played" since I have way too many songs on my decade old 64-bit W7 HPE SP1 PC's SATA 7200 RPM HDD. https://i.ibb.co/Dt0xS3y/screenshot.gif for a screen shot/capture of it in action.

Thank you for reading and hopefully answering.

[Aminifu]

Use the Advanced Title Formatting section on the Titles|ATF tab in the preferences to enter a string for controlling what is displayed in the playlist editor. In the same section, click on "ATF Help" for information on how to format an ATF string.

This works best for files that contain the metadata for the info you want to use. Otherwise, you with need to create a complicated string using the filename variable.

[ant]

Use the Advanced Title Formatting section on the Titles|ATF tab in the preferences to enter a string for controlling what is displayed in the playlist editor. In the same section, click on "ATF Help" for information on how to format an ATF string.

This works best for files that contain the metadata for the info you want to use. Otherwise, you with need to create a complicated string using the filename variable.

I am currently using the defaults as shown in my screen shot/capture attached.

DrO said he needs to fix this issue as in his forum: https://getwacup.com/community/index...2.html#msg5432 since the regular Winamp versions never had this problem.

[Aminifu]

Since you already had an answer for your issue from the developer of WACUP, it makes absolutely no sense to me why you would post the issue in the Winamp forum.

Since you are too lazy to edit your files and add the necessary artist and title metadata, you can try MP3Tag to see if it can correctly add the metadata for you. I know what you're thinking...you have so many files it could take weeks to edit them all manually.

The number of files you have is just an excuse not to do the work. I currently only have 6614 files and it took me 3 months to add or correct the metadata in them (artist, title, album name, release date, genre, etc.). It was worth the effort, since I can now display info about my songs in all kinds of ways. I use the media library, so I can also search for stuff using many various filters.

I told you in my previous post you will need a much more complicated ATF string if you only have the filename to work with.

The string you tried will not work since your files don't contain the %artist% metadata. If you delete the first part of that string (i.e. [%artist% - ]) then just the filename without the leading path information will be displayed.

[ant]

But ID Tag metas doesn't have path locations.

[Aminifu]

If your files' internal metadata do not contain the artist and song title (in this case), then the filename is used. The filename as far as Winamp/WACUP is concerned includes the path locations.

[ant]

Before upgrading to WACUP, Winamp v5.666 didn't do that. It only showed their filenames without paths. I wanted the old behavior hence why DrO is going to fix it.

[Aminifu]

Have you looked at the ATF Help info? I believe it was/is your Winamp that was/is broken and not WACUP. What I have described is the way ATF strings have always worked for me, since I started using them several years ago.

Anyway, do and believe what you want. I give up.

[Aminifu]

ant, I owe you an apology. I'm sorry that I didn't believe what you reported. In 20+ years of using Winamp, I never used drag & drop folders with the option to "Read metadata only when file(s) are played". So I was unaware of the title generation behavior in that case.

I should have investigated further (like dro did) before deciding you were in error.

[ant]

ant, I owe you an apology. I'm sorry that I didn't believe what you reported. In 20+ years of using Winamp, I never used drag & drop folders with the option to "Read metadata only when file(s) are played". So I was unaware of the title generation behavior in that case.

I should have investigated further (like dro did) before deciding you were in error.

No worries. It happens to me too. Yeah, this is a very rare minor comestic case scenario. Maybe I was the first one to notice and report it? Hopefully, DrO can fix it for the next release.