• penquin@lemm.ee
    link
    fedilink
    arrow-up
    6
    ·
    11 months ago

    I just want kde on Wayland not to have blury font with fractional scaling. It’s just unusable. Once that’s fixed, I’m all set to use it as my daily driver.

    • aname@lemmy.one
      link
      fedilink
      arrow-up
      0
      ·
      edit-2
      11 months ago

      I have fractional scaling on current plasma wayland and don’t have blurry font. Is this a specific usecase?

      • penquin@lemm.ee
        link
        fedilink
        arrow-up
        1
        ·
        11 months ago

        Just your regular 27" 4k monitor. If I set it to 200%, everything is fine, but things are huge. I have to have it on 175%, and that makes the font very blurry. Also, any window decorations that are not default plasma get blurry, too. I’ve already posted about it in the kde instance and zamunda (a KDE dev) said it was fixed in plasma 6. So, I guess I’ll just wait it out.

  • GnuLinuxDude@lemmy.ml
    link
    fedilink
    arrow-up
    5
    ·
    11 months ago

    I’m really looking forward to Plasma6. I know gnome has its fans but I am really just a reluctant user. Every day gnome works against me and I have to resort to workarounds.

    Do I want to navigate, inspect, and manipulate my files quickly? I use dolphin.

    Do I want to have a convenient panel to get a very quick glance of my currently running programs as well as a place to pin my most commonly used ones? That’s an extension.

    Do I want sub-windows to always block their parent window, preventing me from interacting with the parent further? No solution.

    Do I want desktop icons? Do I want excessive notifications from common tasks my computer is doing instead of from my own programs?

    I have more complaints but I think I am making myself clear. Overall I do like gnome and it has good performance, but there are so many annoying aspects. KDE is itself not perfect. There’s enough reasons for me to continue using gnome over kde5. But that’s why I hold out hope for plasma 6.

    • RickyRigatoni@lemmy.ml
      link
      fedilink
      arrow-up
      6
      ·
      11 months ago

      Anybody else really hate how a lot of gnome programs have settings that are hidden in the optional gnome-tweaks program instead of putting them in the control panel or program preferences? I swear gnome3 is the only DE that genuinely despises its users.

    • TeryVeneno@lemmy.ml
      link
      fedilink
      arrow-up
      0
      arrow-down
      1
      ·
      11 months ago

      What are your reasons to use gnome over kde? Most of the things you mentioned are reasons I use gnome over kde so I’m curious to know other perspectives.

      • GnuLinuxDude@lemmy.ml
        link
        fedilink
        arrow-up
        1
        ·
        11 months ago

        Overall I do think KDE is more cluttered. So I like Gnome’s streamlined appearance (even if it omits too much). I also think the desktop compositor and shell are really well made, (i.e. mutter and gnome-shell), so I don’t really have performance complaints.

  • Eager Eagle@lemmy.world
    link
    fedilink
    English
    arrow-up
    2
    ·
    edit-2
    10 months ago

    I really want to use wayland - and even though maybe I shouldn’t I still do on my laptop - but man… on Plasma 5 that thing is borked. And I’m not even running on NVIDIA.

    Whenever the system wakes up from sleep or an external display reconnects all open windows are gone and the system enters a weird state which forces me to reboot. How was “all windows are lost when the compositor crashes” not something fixed in the early days, is beyond me. That must make even developing for Wayland unnecessarily difficult/annoying.

  • pathief@lemmy.world
    link
    fedilink
    arrow-up
    1
    ·
    edit-2
    11 months ago

    I can only hope plasma6 has serious improvements on Wayland compatibility with nvidia drivers because plasma5 is unusable.

    Yes, I know it works on your machine. It doesn’t work on mine :P

    • devfuuu@lemmy.world
      link
      fedilink
      arrow-up
      1
      ·
      edit-2
      11 months ago

      Completely agree. I keep trying to open a new session on a clean new user regularly to check if it works and it is absolutely horrible. 3 days ago after updating the system and seeing some new latest kde versions coming in, tried again and noped the out of it in a few minutes. The fonts and scalling in so many places are very bad.

      I keep reading about great improvements in the 6 version and am really hopeful for it to be usable.

      Or the problem is just that no developers have normal regular laptops that are 14’’ at 1080p and can’t imagine that proper scaling at 125% and 150% needs to work out of the box.

      Edit: I don’t even have nvidia hardware, it’s just regular intel stuff. Can’t imagine the struggle of nvidia folks.

    • kadu@lemmy.world
      link
      fedilink
      arrow-up
      1
      ·
      11 months ago

      Nvidia’s latest driver patched several issues with Wayland sessions - perhaps the experience will be a tiny bit better now

    • merthyr1831@lemmy.world
      link
      fedilink
      English
      arrow-up
      1
      ·
      11 months ago

      Hopefully Fedora and others forcing users onto Wayland is going to help push Wayland devs to fixing the stuff that’s breaking compatibility for everyone still stuck on X11.

      • SquigglyEmpire@lemmy.world
        link
        fedilink
        arrow-up
        1
        ·
        11 months ago

        Wayland is just a protocol, issues need to be fixed by devs of the apps/toolkits that have still haven’t migrated over unfortunately.

      • pathief@lemmy.world
        link
        fedilink
        arrow-up
        0
        ·
        11 months ago

        Yeah, I share the feeling. Not sure if the problem lies on Wayland or Nvidia but hopefully if Wayland becomes the standard they’ll address the elephant in the room!

        • loutr@sh.itjust.works
          link
          fedilink
          arrow-up
          1
          ·
          11 months ago

          Wayland is just a set of protocols, which work fine (albeit with limitations) when implemented properly. So if KDE’s implementation of its share of the APIs works correctly with Intel and AMD GPUs, but not with Nvidia ones, the culprit is extremely likely to be the latter.

  • deadcream@kbin.social
    link
    fedilink
    arrow-up
    0
    ·
    11 months ago

    I wonder if they consulted Plasma devs about it. Sure they said that they aim to make Wayland ready for Plasma 6, but it didn’t sound like it was an actual plan for 6.0. After all they got their hands full with Qt 6 porting, and there are still major roadblocks with completing Wayland support, while 6.0 is about to have its alpha release already.

    Knowing Fedora devs however, I suspect they didn’t. They switched to Plasma Wayland by default several Fedora releases ago, when it was in no way ready. I guess I will switch to a different distro when this time comes.

    • Zamundaaa@discuss.tchncs.de
      link
      fedilink
      arrow-up
      4
      ·
      11 months ago

      Yes, they did. Neal has been pushing for Wayland by default upstream for a while, and getting that in for Plasma 6.0 was and is the plan.

    • magikmw@lemm.ee
      link
      fedilink
      arrow-up
      1
      ·
      11 months ago

      Or do what I do and don’t update for half a year. The previous version is supported for a month after the release the next-next version.

      • deadcream@kbin.social
        link
        fedilink
        arrow-up
        0
        arrow-down
        1
        ·
        11 months ago

        It’s still not enough time for KDE devs to fix all major issues with Wayland. It requires at least another two years in the oven.

        • magikmw@lemm.ee
          link
          fedilink
          arrow-up
          3
          ·
          11 months ago

          Maybe. Depends on the usecase. I’ve been running wayland for a year or so without trouble. Using moonlight to another machine for gaming and such.

            • ByteSeb@beehaw.org
              link
              fedilink
              arrow-up
              0
              ·
              11 months ago

              Well, on Linux, lack of codec support makes it such a pain to work with it. Basically useless (unless you buy the Premium version).

              On Windows, I always had weird rendering errors and crashes.

              Other than that, it’s really good. Love the fusion system.

              • Paranoid Factoid@beehaw.org
                link
                fedilink
                English
                arrow-up
                0
                arrow-down
                1
                ·
                11 months ago

                Fusion is what I hate most! Lol I come from Ae and the Adobe suite before I switched. And while I’m comfortable with node based systems, Fusion just isn’t all that compared to all the plug-ins for Ae. Or Blender, which is also fantastic for motion graphics. Fusion does a great job animating titles though.

                Resolve requires a whole production pipeline to use it properly. From ingest, organization, cutting, and post for audii, color, and graphics. It’s best suited to broadcast or features. Or, advertising.

    • jlow (he/him)@beehaw.org
      link
      fedilink
      arrow-up
      0
      ·
      11 months ago

      Doesn’t the Linux version of Resolve only read/import (or export? I can’t remember) .mov or something that makes it more or less unusable? Has that changed?

      • Paranoid Factoid@beehaw.org
        link
        fedilink
        English
        arrow-up
        0
        arrow-down
        1
        ·
        edit-2
        11 months ago

        Yeah. On Win and Mac, it imports anything. But on Linux, the paid Studio version will import x264/x265 with mp3 or PCM (wav) audio. Not AAC. People don’t like that. Lol

        But you’d be insane to edit with these interframe formats. And most commercial editors would auto-convert ingested x264/265 to an intraframe format like Apple ProRes or Avid DNxHR anyway. They’re essentially containers for jpeg or png frames instead of compressing collections of frames. Much easier to scrub the timeline that way, though the files are huge.

        On Linux, Resolve (both free and Studio) imports DNxHR with PCM audio and edits that like butter. ffmpeg easily converts prosumer camera x265/aac output to DNxHR. Or Shuttle encoder, if you want a GUI. And most pro cameras output ProRes, ProRes RAW, or DNxHR directly.

        Also, Resolve on Linux will ingest all Blackmagic RAW file formats, if you have a Blackmagic camera. And the little BMPCC 4k is still a steal at $1200 or so. As long as you light your subject properly, that little camera shoots gorgeous photography.

        Resolve is a pro tool. But a project takes time to set up. For little things, I’d go with Blender’s VSE, which is full featured but has a terrible interface, or kdenlive, which is a Windows Movemaker like toy, but has a normal interface you’d expect from an NLE.

        • jlow (he/him)@beehaw.org
          link
          fedilink
          arrow-up
          2
          ·
          11 months ago

          Thanks for the writeup, that’s far more advanced than what I need to do in my work sometimes __ But cool that it looks like there are options on Linux.

          • Paranoid Factoid@beehaw.org
            link
            fedilink
            English
            arrow-up
            1
            ·
            11 months ago

            I do this for a living. Most people shooting family vids or youtube vlogs/video essays would find Kdenlive perfectly well suited to their needs. It does simple transforms, titling, adjustments, etc. And it looks like a normal NLE. When you hit a wall with it, the move to a commercial program will be easy.

        • justJanne@startrek.website
          link
          fedilink
          arrow-up
          0
          ·
          edit-2
          11 months ago

          Sadly even Resolve Studio doesn’t support h264 all-intra as used in Sony’s XAVC-I and XAVC-S-I on Linux, which sucks.

          With XAVC-I CineEI Slog footage the metadata is enough that Resolve treats it as Raw (in fact, it’s more flexible than braw). So losing this functionality really hurts.

          • Paranoid Factoid@beehaw.org
            link
            fedilink
            English
            arrow-up
            1
            arrow-down
            1
            ·
            edit-2
            11 months ago

            Ouch, that does hurt. Sorry, dude!

            You could use gpu passthrough with iommu and qemu to a virtual system and run Win. A real PITA. I know.

            I’d bitch about that on the blackmagic Resolve forum. That’s a serious hit to your workflow. Call out Dwaine, he works there and does Linux support. Nice guy.

            • justJanne@startrek.website
              link
              fedilink
              arrow-up
              1
              ·
              11 months ago

              I still hope it’s just a driver or configuration issue, for now I just dual boot for resolve, but that’s obviously not a long term solution.

              • Paranoid Factoid@beehaw.org
                link
                fedilink
                English
                arrow-up
                2
                arrow-down
                1
                ·
                edit-2
                11 months ago

                I mean, I dunno about you but for me this is money. I make money with these tools. I prefer Linux for privacy reasons, but I’m not religious about it when it comes to money. We all gotta eat.

                The Blackmagic folks might help. Especially if you paid for Studio. I don’t work there and can’t make promises, but I’d definitely make a stink about that. At least get a formal statement from them on Sony support in Linux.

                My in-house is an old GH5s w/ a Shogun. But if the client pays, I prefer to rent an URSA mini. So I haven’t hit this.

                Really wish I could help more.