Search Results
7/3/2025, 2:56:01 PM
>>105783881
>h264 10bit
Presumably you meant H.265/HEVC? H.264/AVC 10-bit is quite rare and I doubt whether MSFT provided support for this capability in their decoder.
>the libavcodec-based DirectShow filters do, thoughbeit - like LAV Filters
WMP uses Media Foundation transforms by default, so you'll have to install a codec of that type.
https://www.codecguide.com/media_foundation_codecs.htm
You'll handle vidya, at least, but not the .ASS subtitles - WMP doesn't support that unless you have xy-VSFilter installed (choose either the pinterf or Masaiki fork - the latter actually uses libass as the backend).
It's a DirectShow filter, though, so you have to make WMP use DirectShow filters for media playback. Assume that you'll have to install additional filters for video/audio playback (like the aforementioned LAV filters - just install the K-Lite Codec Pack as a one-stop solution) if the built-in stuff can't handle the coding.
All you have to do is rename all of your vidya's extension to .video - WMP won't recognize this as an extension that is supported by Media Foundation, so it will try to fall back to DirectShow.
>you may also turn off Media Foundation support for specific file extensions like mp4, mkv and whatnot, but since it's global-wide and there are applications that are dependent on the framework, it's not feasible as it will break video playback for these cases
But with all that tinkering you might as well just use MPC-HC (bundled in K-Lite) as a player. It actually has libass support implemented from within.
>TL;DR: stop using WMP - use any other media player that supports 10-bit stuff and ASS subtitles
>h264 10bit
Presumably you meant H.265/HEVC? H.264/AVC 10-bit is quite rare and I doubt whether MSFT provided support for this capability in their decoder.
>the libavcodec-based DirectShow filters do, thoughbeit - like LAV Filters
WMP uses Media Foundation transforms by default, so you'll have to install a codec of that type.
https://www.codecguide.com/media_foundation_codecs.htm
You'll handle vidya, at least, but not the .ASS subtitles - WMP doesn't support that unless you have xy-VSFilter installed (choose either the pinterf or Masaiki fork - the latter actually uses libass as the backend).
It's a DirectShow filter, though, so you have to make WMP use DirectShow filters for media playback. Assume that you'll have to install additional filters for video/audio playback (like the aforementioned LAV filters - just install the K-Lite Codec Pack as a one-stop solution) if the built-in stuff can't handle the coding.
All you have to do is rename all of your vidya's extension to .video - WMP won't recognize this as an extension that is supported by Media Foundation, so it will try to fall back to DirectShow.
>you may also turn off Media Foundation support for specific file extensions like mp4, mkv and whatnot, but since it's global-wide and there are applications that are dependent on the framework, it's not feasible as it will break video playback for these cases
But with all that tinkering you might as well just use MPC-HC (bundled in K-Lite) as a player. It actually has libass support implemented from within.
>TL;DR: stop using WMP - use any other media player that supports 10-bit stuff and ASS subtitles
7/2/2025, 7:52:51 AM
>>105767265
>nobody here has ever been on lkml because nobody here can read
I've been on the lkml many times and I can read. Still don't understand the fuck what they are going on about though.
>nobody here has ever been on lkml because nobody here can read
I've been on the lkml many times and I can read. Still don't understand the fuck what they are going on about though.
6/29/2025, 3:08:56 AM
>>105738925
It's just a hashing algorithm.
A hash is just a unique value created by a mathematical algorithm. It's used to verify that information hasn't been changed which is useful for security/privacy and troubleshooting/debugging.
If the data has been changed in any way, no matter how small, it will have a different hash.
So you can verify that you've downloaded the full file with no malicious or unintended modifications by taking the hash of what you've downloaded, and comparing it with the hash on the website.
You don't *need* to check the hash of anything you download, but it's not a bad habit to get into if you care about security. Generally files with large sizes are hosted on unofficial mirrors, and bad actors could try to upload their own compromised files into those mirrors, or make their own mirror to host those compromised files.
I would definitely do it for any important software like your operating system. Windows PowerShell should come with commands for checking the hash of a file, look up how to use them.
It's just a hashing algorithm.
A hash is just a unique value created by a mathematical algorithm. It's used to verify that information hasn't been changed which is useful for security/privacy and troubleshooting/debugging.
If the data has been changed in any way, no matter how small, it will have a different hash.
So you can verify that you've downloaded the full file with no malicious or unintended modifications by taking the hash of what you've downloaded, and comparing it with the hash on the website.
You don't *need* to check the hash of anything you download, but it's not a bad habit to get into if you care about security. Generally files with large sizes are hosted on unofficial mirrors, and bad actors could try to upload their own compromised files into those mirrors, or make their own mirror to host those compromised files.
I would definitely do it for any important software like your operating system. Windows PowerShell should come with commands for checking the hash of a file, look up how to use them.
Page 1