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

    • Microsoft's fast coding model MAI-Code-1-Flash comes to Copilot Business and Enterprise by Karthik Mudaliar Microsoft’s recently announced MAI-Code-1-Flash model is now generally available to GitHub Copilot Business and Copilot Enterprise customers. With this support, organizations can have more centralized policy controls and billing while finally being able to use Microsoft’s lightweight, first-party coding model. According to GitHub’s announcement, Business and Enterprise plan administrators must enable the MAI-Code-1-Flash policy in Copilot settings before developers can access the model. Microsoft says that MAI-Code-1-Flash is for fast, iterative coding work rather than the most demanding architectural or debugging tasks. GitHub’s official model comparison page says that the model is great for "general-purpose coding and writing," while it excels at fast, accurate code completions and explanations Microsoft introduced MAI-Code-1-Flash on June 2 as part of a broader collection of internally developed MAI models. GitHub subsequently expanded support to Copilot CLI, the Copilot cloud agent, GitHub.com chat, GitHub Mobile, Visual Studio, JetBrains IDEs, Eclipse, and Xcode, but said support for managed Business and Enterprise customers was still on the way. In Microsoft’s own benchmark testing, MAI-Code-1-Flash scored 51.2% on SWE-Bench Pro, compared with 35.2% for Anthropic’s Claude Haiku 4.5. Microsoft also claimed that the model used up to 60% fewer tokens on SWE-Bench Verified. Do note that these are vendor-run results rather than independent measurements. The model is billed at provider list pricing under GitHub’s usage-based system. GitHub currently lists MAI-Code-1-Flash at $0.75 per million input tokens, $0.075 per million cached input tokens, and $4.50 per million output tokens. For organizations, the main incentive to use MAI-Code-1-Flash is likely to be efficiency rather than maximum capability. A smaller model that responds quickly and limits unnecessary output is quite useful for repetitive agent tasks at scale, especially after GitHub Copilot’s move toward usage-based billing. The "Flash" model is recommended for fast work and not necessarily for huge repositories with loads of context. It's better if teams compare their output with other larger models, especially if they're working on security-sensitive changes and complex, multi-file work.
    • yes AND no the "original" or plain/normal Optiplex 7010 won't be getting any more new firmware updates BUT the Optiplex SFF/SFF Plus {small form factor}, Micro/Micro Plus & Tower/Tower Plus 7010 editions DO get new updates such as this new one   and here are similar guides from the Dell web site for Dell systems: https://www.dell.com/support/kbdoc/en-us/000390990/secure-boot-transition-faq https://www.dell.com/support/kbdoc/en-us/000347876/microsoft-2011-secure-boot-certificate-expiration
    • AT&T has been spying on US citizens with the NSA for decades.. they just know how to keep it more under wraps.. the evil level is still there.
  • Recent Achievements

    • One Year In
      bernmeister earned a badge
      One Year In
    • Week One Done
      Scoobystu earned a badge
      Week One Done
    • Week One Done
      tuben earned a badge
      Week One Done
    • First Post
      OffsetAbs earned a badge
      First Post
    • Reacting Well
      OffsetAbs earned a badge
      Reacting Well
  • Popular Contributors

    1. 1
      +primortal
      459
    2. 2
      +Edouard
      212
    3. 3
      PsYcHoKiLLa
      157
    4. 4
      FloatingFatMan
      71
    5. 5
      Steven P.
      69
  • Tell a friend

    Love Neowin? Tell a friend!