WMP12 win7 7100, Stop WMP12 from touching folder.jpg files


Recommended Posts

If you get rid of the reserved system file 'albumartsmall.jpg' for whatever reason, then at any later point when small thumbnails are shown (shell, Media Center, Windows Media Player) you may trigger the album art extractor which will refresh the folder.jpg/albumartsmall.jpg pair.

There's no reason to just make a "folder.jpg" file unless you are deliberately trying to cause this. :)

How can I try to trigger the extractor? I been playing around in WMP and MCE and myFolder.jpg files are ok and have not been resized.

  • 2 weeks later...

Honestly, I am really tired of this problem.

Why can't someone just add a "Don't screw with my album art under any circumstance whatsoever because I have a larger brain than you, dear computer" checkbox, or make it a registry change if you don't want to expose it to the masses...

So if I am understanding this correctly, the way to prevent this from happening is to remove or in most cases, not create the folder.jpg files and make sure the high-res art work is embedded in the music files. I really HATE WMP12. Version 11 was good, but this problem with album artwork has to change. This isn't 2001 with 15" monitors. Even iTunes downloads it's artwork in 600X600 resolution.

I am thinking of removing WMP and going to Media Monkey for ripping and organization and WMC for playing music files. MS has dumbed down WMP way to much for my liking.

Yes, you should probably consider "folder.jpg" and "albumartsmall.jpg" reserved file names that would be a horrible plan to touch. Inserting the art into the files would be the correct plan.

This should generally have been consistent since day one... more people are enjoying album art these days so it's more noticeable.

Do yourself a favor and remove WMP and install Winamp 552 Pro. It is far superior than WMP, just about anything is. :rolleyes:

Do yourself a favour, and don't troll threads where it isn't warranted, this is about WMP within the Windows 7 Beta, not a debate about the relative merits of WMP and Winamp.

As for the topic, someone needs to pop into the WMP design team, and tell them that 800x600 went out of fashion 10 years ago. Low res album art looks awful on high resolution displays, and why Microsoft feel that there is some need for it to fiddle with your album art anyway, lord only knows.

  • 1 month later...

Any news here? Just did a new scan with MP11 on VISTA and MP replaced many folder.jpgs. Then after that started my xbox360, opend MediaCenter and after selecting the folder where all my mp3s are MediaCenter did even a better job nearly all .jpgs are now replaced...

I hope this will be not the case in the Windows 7 final...

Christian

  • 2 weeks later...
Yes, you should probably consider "folder.jpg" and "albumartsmall.jpg" reserved file names that would be a horrible plan to touch. Inserting the art into the files would be the correct plan.

This should generally have been consistent since day one... more people are enjoying album art these days so it's more noticeable.

This topic is insane. How hard is it to understand that it's a horrible policy to allow WMP12 to degrade a user's pre-existing album art?!? I don't mind WMP12 filling in the gaps for me where I don't already have album art but ruining all of your high resolution art just by running the program is ridiculous!

And Zach, I have to say, you've been rather unhelpful in this thread. The OP has stated how this happens, other people have confirmed it, and still more complain about the problem on a simple Google search. There's nothing to debate here, WMP is doing something it shouldn't be doing and this needs to be changed.

Microsoft wants people to use WMP, right? WMP is consistently hated by a lot of people, right? Well maybe MS should just shut up and listen to people who want to use it but can't because it does something wrong.

This topic is insane. How hard is it to understand that it's a horrible policy to allow WMP12 to degrade a user's pre-existing album art?!? I don't mind WMP12 filling in the gaps for me where I don't already have album art but ruining all of your high resolution art just by running the program is ridiculous!.
You know there is an option in WMP to fill in missing gaps only, right?
This topic is insane. How hard is it to understand that it's a horrible policy to allow WMP12 to degrade a user's pre-existing album art?!? I don't mind WMP12 filling in the gaps for me where I don't already have album art but ruining all of your high resolution art just by running the program is ridiculous!
The biggest culprit should generally be folder.jpg without a matching albumartsmall.jpg .
And Zach, I have to say, you've been rather unhelpful in this thread. The OP has stated how this happens, other people have confirmed it, and still more complain about the problem on a simple Google search. There's nothing to debate here, WMP is doing something it shouldn't be doing and this needs to be changed.
I apologize for any misperceptions. I believe my earlier comments about folder.jpg evidently being a reserved file name is probably the most interesting point to note.

I apologize if my attempts to help people understand this concern a little more clearly are in any fashion misconstrued. folder.jpg is a reserved file name according to everything you and I are seeing here. My comments might be illuminative or might not be, but it seems like you should:

* only update the art within the file directly

* not count on folder.jpg being 'your' file

The biggest culprit should generally be folder.jpg without a matching albumartsmall.jpg .

I apologize for any misperceptions. I believe my earlier comments about folder.jpg evidently being a reserved file name is probably the most interesting point to note.

I apologize if my attempts to help people understand this concern a little more clearly are in any fashion misconstrued. folder.jpg is a reserved file name according to everything you and I are seeing here. My comments might be illuminative or might not be, but it seems like you should:

* only update the art within the file directly

* not count on folder.jpg being 'your' file

I understand that's what people should do to avoid this problem, and it's good to know that and have it documented so thank you, but at the end of the day this is still a problem.

And, yes, there is supposedly an option to only fill in the gaps but others are reporting it's not working so I'm not even going to let WMP access the internet or touch my files.

The settings in question do not affect the reserved file name 'folder.jpg', hence my comments.

Your comments are interesting and important, but that's not the way the player works and there is pretty much no mechanism to do so. It's a good suggestion... but it doesn't work that way. :( This is why my two points:

* only update the art within the file directly

* not count on folder.jpg being 'your' file

are probably highly relevant.

Plus if you update the art within the file, it's more portable. :)

  • 2 months later...
A simple Process Monitor review of the player shows

[HKEY_CURRENT_USER\Software\Microsoft\MediaPlayer\Preferences]

"LargeAlbumArtSize"=dword:00000320

"SmallAlbumArtSize"=dword:00000190

might be interesting. They will not affect everything. They max out at 800(x800). Use at your own risk.

i need to bump this thread as i have run into the folder.jpg issue in this thread and think i may have a solution.

if you add the below values it appears that WMP will NOT generate new folder.jpg OR AlbumArtSmall.jpg files. IF folder.jpg (or AlbumArtSmall) already exist(s), it does not resize it but mearly sets the HIDDEN and SYSTEM attributes. so if you have a folder.jpg and/or an albumartsmall.jpg file at 1500x1500, it will leave them alone (except for hiding them...).

[HKEY_CURRENT_USER\Software\Microsoft\MediaPlayer\Preferences]

"LargeAlbumArtSize"=dword:ffffffff

"SmallAlbumArtSize"=dword:ffffffff

can anyone out there verify this? i tired with a brand new database and a few albums. a quick outside verification would be great. thanks.

  • 2 years later...

i need to bump this thread as i have run into the folder.jpg issue in this thread and think i may have a solution.

if you add the below values it appears that WMP will NOT generate new folder.jpg OR AlbumArtSmall.jpg files. IF folder.jpg (or AlbumArtSmall) already exist(s), it does not resize it but mearly sets the HIDDEN and SYSTEM attributes. so if you have a folder.jpg and/or an albumartsmall.jpg file at 1500x1500, it will leave them alone (except for hiding them...).

[HKEY_CURRENT_USER\Software\Microsoft\MediaPlayer\Preferences]

"LargeAlbumArtSize"=dword:ffffffff

"SmallAlbumArtSize"=dword:ffffffff

can anyone out there verify this? i tired with a brand new database and a few albums. a quick outside verification would be great. thanks.

I know this thread is old but I just had to say that this registry setting works!! I've been looking for years for a way to correct the whole shrinking album art issue and for anyone who cares, this is it!! Thanks!!

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

    • No registered users viewing this page.
  • Posts

    • Simple answer is yes, you will still get the Windows updates and as long as browser is up to date, you will be good. Only thing secure boot does is protect you against boot level threats and make it harder to install other OS's. I've been looking into this pretty thoroughly lately myself as wifes computer has secure boot disabled plus my other, older computers that run Linux, don't have secure boot enabled. Have seen all kinds of questions about this on the Linux Mint and MX Linux forums. Just don't suddenly enable secure boot now.
    • How many other companies will follow Ford's lead? Or, have they already gotten lazy and become enslaved to AI--and now can't figure out how to get out of that mess.
    • Why would any self-respecting intelligent person follow any recommendation by Donald's GOP administration? With almost two years of fabrications, deceit, and blatantly illegal behavior, why believe them now? They had best be gone after the November 2026 election, so we'll wait and see.
    • AltSendme 0.4.1 by Razvan Serea AltSendme is a minimal, cross-platform application designed for fast, secure, and private peer-to-peer file transfers. It allows users to send files or entire directories directly between devices without relying on cloud servers, accounts, or any personal information. Everything is encrypted end-to-end using modern protocols like QUIC and TLS 1.3, ensuring both strong security and low-latency performance. Transfers are verified with BLAKE3 for data integrity, and interrupted downloads automatically resume, making the experience reliable even on unstable connections. You can transfer anything—images, videos, documents, and more. Integrity checks are performed on both ends, so your files are automatically verified for correctness during both sending and receiving. AltSendme works seamlessly across local networks or long-distance links, capable of saturating multi-gigabit connections for extremely fast delivery. With built-in NAT traversal and encrypted relay fallback, it connects devices almost anywhere. The app integrates with the Sendme CLI and will soon support mobile and web platforms. Fully free and open-source, AltSendme offers a lightweight, privacy-first alternative to traditional cloud-based services, removing size limits, upload costs, and unnecessary data exposure. AltSendme 0.4.1 changelog: Release Highlights Self-hosted relays: Run your own iroh relay so transfers don't rely on public infrastructure. Includes a full deployment template in deploy/relay/ with Docker Compose for a VPS and configuration examples for production use. Fly.io support: One-click deploy template for Fly.io, including a quick-start config (fly.dev.toml) for testing without a custom domain, plus production setup with Let's Encrypt and your own hostname. Relay settings UI: New Settings → Network panel to choose how AltSendme connects: automatic public relays, custom self-hosted URLs (with optional auth token), or disabled. Test connections, verify latency, and see live relay status in the footer. Disable relays: Turn off relay servers entirely when you only need same-network transfers (e.g. LAN). Direct connections only. No relay hop required when devices can reach each other. Android graduates from beta: Android is now part of the regular release cycle alongside desktop. APKs ship with each version (universal, arm64, and armv7). Other improvements Private relay access control via shared auth token Relay fallback notifications when a custom relay is unreachable Broadcast mode toggle in sharing settings Android release build fixes (split-per-ABI APKs, universal APK preservation) UI polish: mobile safe-area insets, dropzone layout, transfer progress animation Bug fixes for minification-related serialization issues and system tray icon loading What's Changed feat(relay): add relay status functionality and settings UI (a120cdf) feat(relay): implement custom relay server configuration and verification (51276c7) feat(relay): add configuration for private relay access and enhance observability features (48fbabf) feat(relay): enhance relay URL validation, display connection status (d4fffa0) feat(relay): add RelayChangeGuard component and enhance relay-related translations (16ba514) feat(broadcast): add toggle setting for broadcast mode in sharing UI (ca6d977) fix(relay): correct QUIC discovery port, pin image, templatize fly.dev (52a2ba5) fix: More broken serialization due to minification (67491a9) fix(android): preserve true universal APK across per-ABI builds (e9f256f) fix(ui): conditional safe-area insets padding on mobile (1182f0e) refactor(transfer): CircularRing component animation fix (944572b) chore(android): drop x86 and x86_64 release APKs, keep universal+arm64+armv7 (34ada0b) Download: AltSendme 0.4.1 | ARM64 | ~9.0 MB (Open Source) Download: AltSendme for MacOS | Android Links: AltSendme Home Page | GitHub | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • You are mostly right about the ephemeral nature of it. As I mention in the article, if you dont add a second device or take a backup of your account before uninstalling it, then yes you will lose access to your account. That said, in terms of actual user experience when you sync multiple devices your message history carries across and there's also a Saved Messages chat like there is on Telegram to send messages and attachments between your installs. But yh, what you point out are correct and its not trying to emulate Messenger or Telegram.
  • Recent Achievements

    • Week One Done
      flexorcist earned a badge
      Week One Done
    • One Month Later
      Woland13 earned a badge
      One Month Later
    • Week One Done
      Woland13 earned a badge
      Week One Done
    • One Year In
      bernmeister earned a badge
      One Year In
    • Week One Done
      Scoobystu earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      495
    2. 2
      +Edouard
      225
    3. 3
      PsYcHoKiLLa
      150
    4. 4
      Steven P.
      75
    5. 5
      FloatingFatMan
      71
  • Tell a friend

    Love Neowin? Tell a friend!