Winamp CD Case Beta 8


Recommended Posts

OK here is something I noticed when using it... for Ogg Vorbis files, see the following example of a song.

Title: Synergy - Hello Strings

Artist: Armin van Buuren

Album: Universal Religion 2004 (Armada at Ibiza)

In the notifier, the title should appear as shown above, but all I can see is Synergy (it seems to ignore everything after 'Synergy')

Hope you can fix it! ;)

Edited by rbet

rbet,

I've uploaded a new build that has a workaround to deal with this kind of title (with "-") and Ogg Vorbis files (WCC reads tags directly from mp3 so the "-" is not an issue anymore).

The upcoming beta 7 will probably read Ogg Vorbis tags directly too.

Please, try it: http://www.closetosoftware.com/wcctheme2.zip

Hey Carlos. I have beta 5 installed with the 6 as well (copying exe files) but for some reason the cover doesnt automatically update. I always have to double click in order for the cover to update. If it dont click it it'll just show the "escape is my reality" cover.Here's a screenshot to show you the problem.

before i double click

desktop2wm.jpg

after i double click

desktop21fm.jpg

Also, in my main music folder (where winamp plays from) I dont see a folder for my covers.

It seems that you have one folder with a lot of songs.

Anyway, try to change the "Read cover" setting. Go to "Options>Read cover" then:

1) remove any setting from the right list

2) select "Artist - Album.jpg" from the left list then press "Add>" button

3) select "Any image" from the left list then press "Add>" button

If you use ID3v2 tags to store covers add "ID3v2 tag" too.

Now you can download covers and they will be saved following the same pattern of "Read cover" ("Artist - Album.jpg").

Only 1 of the skins seems to work for me....I get this error after I click apply (chooseing Aero, Case or Milk):

Error occured: 380

Description: Invalid property value

Module: frmBack

Function: Form_Load

Happens with Foobar and Winamp. But the skin Glow doesnt do that and displays the Album text properly...

(I installed Beta5 and then used the updated files from the .zip u have given)

:)

I can confirm Rogue's experience; I am getting the same error on startup. Using beta 7 of WCC and Winamp v5.092...

EDIT: I found that in Skin Manager>Text, the 'Reduce Size By' Field was by default at 33333 pixels... I reduced it to 33 pixels and I no longer get the error (using the Case skin).

And, the hyphen problem is gone! :D

Edited by rbet
I can confirm Rogue's experience; I am getting the same error on startup. Using beta 7 of WCC and Winamp v5.092...

EDIT: I found that in Skin Manager>Text, the  'Reduce Size By' Field was by default at 33333 pixels... I reduced it to 33 pixels and I no longer get the error (using the Case skin).

And, the hyphen problem is gone!  :D

585985691[/snapback]

Ahhhh, thnx for that, all working fine now :D

rbet and Rogue,

Due to your great feedback I was able to track the bug.

WCC internal converter (from twip to pixels) was not considering values with comma (e.g. 33,33).

Now it read them properly and you can freely use such values to make fine adjustments.

Thank you very much!

You can download the new build here (as always): http://www.closetosoftware.com/wcctheme2.zip

It works with Foobar2000 (0.8.3 not the beta), but u need the winamp spam component (Winamp API Emulator or somat).

Works fine here anyway :)

585985873[/snapback]

Rogue,

Can you explain how to use Winamp CD Case and foobar?

I have some users asking for it and maybe your solution can help them.

Thank you in advance!

Rogue,

Can you explain how to use Winamp CD Case and foobar?

I have some users asking for it and maybe your solution can help them.

Thank you in advance!

585985965[/snapback]

Sure, all they need to do is download this and extract it into Foobar2000/components/ and then restart Foobar. It then creates a process called Winamp.exe and all the info about songs go to that, and this program and many others use that info :) I got it from using a mIRC script, but ive found it works well with allot of other programs :)

(u can also configure its output via the components window in preferences in foobar)

Hope that helps :)

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • I think it depends on what you're looking for to do, and the time you have to spare. With my Dwarf 3, I easily spend 3-4 hour sessions; half an hour driving to an un-light polluted place, unpacking and setting up the smart scope + tripod for equatorial tracking, mucking around with settings, maybe shoot some calibration frames, spending a few hours shooting, merging with past photo sessions, etc. It's crazy how time flies and I often get home later than I expected. It's something I still need to set aside a good part of an evening to do, all in all. For one session, where you often need like four for best results when it comes to deep space objects. With practice, I can probably begin cutting time here but I think where smart scopes find their home is among people who love to shoot the night sky but don't have the spare time to go deep with the "navigator level" attunement to the night sky itself. Having said this, _if_ you have even more time to spend on this hobby, it will probably be even more rewarding to do it more by hand and learn the skies and the details of how it all works.
    • I misread the title and thought Teams itself would be redesigned. Imagine having this one as a native WinUI app.
    • Dell, HP PCs ran into endless reboot, BitLocker recovery loops but Windows 11 isn't to blame by Sayan Sen Last month Neowin reported on a major issue on Dell systems wherein a bug in its official support tool was leading to endless blue screen of death (BSOD) and restarts. Following our report, Dell officially acknowledged its SupportAssist-related crash issue, confirming that the culprit is not Microsoft's operating system but rather a faulty version of its own remediation software. In a newly published support advisory, Dell stated that version 5.5.16.0 of Dell SupportAssist Remediation and Alienware SupportAssist Remediation can trigger blue screen errors and unexpected system restarts. The company notes that the problematic component operates independently of the main SupportAssist application, meaning users should not remove the primary SupportAssist software when troubleshooting the issue. According to Dell, the crashes are linked specifically to the SupportAssist Remediation service, which is bundled with SupportAssist OS Recovery Tools, and as such it has since released an updated version, 5.5.16.1, which is said to resolve the problem. Affected users are advised to first verify whether version 5.5.16.0 is installed by checking the Installed Apps section in Windows Settings. If so, Dell recommends updating SupportAssist OS Recovery Tools through either SupportAssist's "Update Software" feature or Dell Command Update. Dell also advises users to back up important data before performing the update and to ensure systems remain connected to power throughout the installation process. If you are still having issues though make sure to report to the Dell support forum. As it turns out though Dell is not the only PC maker currently dealing with update-related headaches as HP is also facing a separate but probably equally frustrating issue involving recent Windows Secure Boot updates that were released with recent Windows 11 Patch Tuesdays. Similar to Dell, HP also put up its own support article where it explains the issue. The company says that affected devices could hit a brick wall when booting as they run into a BitLocker recovery loop after the April 2026 updates. The problem appears to affect systems wherein the new UEFI Secure Boot CA 2023 certificates fail to apply properly. As such affected users will find themselves entering their recovery key over and over again despite the system otherwise functioning normally. HP says such PCs should be updated to the latest available BIOS version and configured with the necessary Secure Boot certificates before installing Microsoft's Windows 11 Patch Tuesday updates. Systems that are already experiencing the problem may require BIOS configuration changes to restore normal boot behavior. Admins can find information regarding that in the support article here on HP's official website.
    • Getting further away from the artistic study of mental disease that was the first game... (which never needed any sequels to begin with) But I get it, a company has to make money. And the second was at least visually impressive, if not in any other way.
    • If its the devs fault you would think Unreal would help M$ take full advantage of Unreal and work with them to fix the performance issues. Otherwise they are catching unwarranted bad press.
  • Recent Achievements

    • One Month Later
      DJC50PLUS earned a badge
      One Month Later
    • Week One Done
      DJC50PLUS earned a badge
      Week One Done
    • Proficient
      Eric Biran went up a rank
      Proficient
    • Dedicated
      Conjor earned a badge
      Dedicated
    • Week One Done
      Windows Guy earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      493
    2. 2
      PsYcHoKiLLa
      246
    3. 3
      Steven P.
      72
    4. 4
      +Edouard
      69
    5. 5
      neufuse
      68
  • Tell a friend

    Love Neowin? Tell a friend!