Originally posted by Michael
View Post
Announcement
Collapse
No announcement yet.
Chrome 107 Released With HEVC Hardware Decoding, Other Additions
Collapse
X
-
Originally posted by RejectModernity View PostChromium on wayland is still a shitshow. At least on KDE it can't go over 60fps plus vaapi and Vulkan don't work.
It's why i switched to Sway, with floating windows. kwin is a mess.
Comment
-
Originally posted by numacross View Post
What's wrong with using "effect" as a verb in this context? It's listed in most online dictionaries.
Affect-EFFECT--760x400.jpg
- Likes 1
Comment
-
Originally posted by tildearrow View PostThat's only when video-sync is not set to audio.
Originally posted by tildearrow View PostFew kernels are compiled with a 100Hz timer. The majority run at 250Hz or 300Hz, with some low-latency kernels running at 1000Hz (e.g. Ubuntu/Debian lowlatency).Code:sid@shiney:~$ grep -r ^CONFIG_HZ /boot/config-5.15.0-52* /boot/config-5.15.0-52-generic:CONFIG_HZ_250=y /boot/config-5.15.0-52-generic:CONFIG_HZ=250 /boot/config-5.15.0-52-lowlatency:CONFIG_HZ_1000=y /boot/config-5.15.0-52-lowlatency:CONFIG_HZ=1000
Thanks! I always appreciate being updated!
I've been using Linux since 1994, compiled my own kernel with modules disabled for faster boot... One of the things I always did was set CONFIG_HZ to 1000, starting in October 1996 when I got my Cyrix M1 PR120+ and started hacking on X-MAME. One of the things I did was add sleeping in the frameskip code so that I could run 4 different arcade games at once on the X desktop. With the busy-waiting it stuttered badly until I increased CONFIG_HZ to 1000, but back then almost all software expected CONFIG_HZ to be 100, so anything that did timings based on jiffies ran 10x too fast, or waited 1/10th as long as it should. One of my desktop clocks ran fast, DOSEMU ran fast, and my SmartMedia card reader had a lot of timeout warnings on the kernel log lol. We've come a long way since those days.
Anyhow I've had this discussion a lot of times over the years and I've slowly accepted that CONFIG_HZ was never going to be anything other than 100 on x86 for performance reasons, but it was higher on some other arch's, ie it was 1000 on MIPS. I'm glad to see the default is 250 on X64 now. Anyone know when Ubuntu made this change?Last edited by linuxgeex; 26 October 2022, 11:49 AM.
Comment
-
Originally posted by OneTimeShot View PostARGHH! HEVC support: no!!!! I thought that non-free codecs were going to die on the Internet. Now we're going to be stuck with another 10 years of MPEG payments...
The timing kind-of matches with the EU anti-trust investigations. I guess this means that AV1 is now dead - there isn't enough benefit to warrant using AV1 over HEVC anymore...
- Likes 1
Comment
Comment