Announcement

Collapse
No announcement yet.

GNOME 3.36 Is Looking To Be Another Nice Evolutionary Upgrade To The GNOME Desktop

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Sin2x
    replied
    treba
    Thanks a lot, that's much better. Still begs the question of why the official Gnome blog post states differently.

    Leave a comment:


  • treba
    replied
    Originally posted by Sin2x View Post

    According to the Gnome blog post, you are wrong, my friend:

    Due to the VP9 encoder being too CPU-intensive, the built-in screen recorder changed back to the VP8 encoder.

    And if you would still insist that VP9 is buggy, please provide the evidence and the corresponding bug report.
    From the MR (https://gitlab.gnome.org/GNOME/gnome...requests/954):
    This reverts commit d183f13456991d12ea57ad14ba38a1f7407d0037. Switching to the vp9 encoder seemed like a good idea at the time but unfortunately it also has the major drawback, that it leaks a serious amount of memory every time it is used. See https://gitlab.gnome.org/GNOME/gnome...56#note_692743 for more details.

    Leave a comment:


  • Pajn
    replied
    Sounds like a really nice release. Both in form of user visible changes and for quality of the project moving forward.

    Between other internal refactors that are now possible, it will also facilitate the introduction of an input thread in the native backend, so the pointer cursor is no longer frozen on stalls.
    This has been such a frustration for a long time. While we still need to wait for it to actually be done it's nice to see that things have started moving and are within reason. Older communication from gnome developers have been more in line of "We would have to rewrite the whole of gnome and by caring about stalls you are just an annoying jerk anyway".

    Leave a comment:


  • DanL
    replied
    Originally posted by 144Hz View Post
    The best just got better!
    You're jumping the gun there. The weekly KDE blog post won't be until this weekend.

    Leave a comment:


  • DanL
    replied
    Originally posted by Sin2x View Post
    Why not allow the choice between VP8 and VP9 in screen recording instead of enforcing the former?.
    Because the users shouldn't worry their pretty little heads about such things. Just believe in the GNOME devs to make all your decisions and you will soon be inside a wonderful walled garden. Okay, it's not as nice as the Apple garden, but what do you want for free?

    And if you would still insist that VP9 is buggy, please provide the evidence and the corresponding bug report.
    You mean you want 144Hz to say something fact-based and informative, and not just blindly cheerlead for GNOME all day? Good luck with that...

    Leave a comment:


  • josh_walrath
    replied
    Typo: peeking*, not peaking

    Leave a comment:


  • Sin2x
    replied
    Originally posted by 144Hz View Post
    Sin2x because of bugs in vp9. Bugs that no one plan to fix for now.
    According to the Gnome blog post, you are wrong, my friend:

    Due to the VP9 encoder being too CPU-intensive, the built-in screen recorder changed back to the VP8 encoder.

    And if you would still insist that VP9 is buggy, please provide the evidence and the corresponding bug report.

    Leave a comment:


  • 144Hz
    replied
    Sin2x because of bugs in vp9. Bugs that no one plan to fix for now.

    Leave a comment:


  • 144Hz
    replied
    tildearrow been running 3.35.x for a while now.

    Leave a comment:


  • Sin2x
    replied
    Why not allow the choice between VP8 and VP9 in screen recording instead of enforcing the former? Gnome fails at freedom of choice yet again, seemingly it's their modus operandi.

    Leave a comment:

Working...
X