• 1 Post
  • 25 Comments
Joined 1 year ago
cake
Cake day: June 11th, 2023

help-circle

  • I’ve been using WinBTRFS for quite some time without issues. It seems a lot of people recommend NTFS. But be aware, if you plan on using it for things like games, NTFS will absolutely break at some point. It is not compatible with Proton and will break things like updates for Steam. It always has for me up until very recently. Valve also says the same about using NTFS for games. I’m not sure this can be fixed with the NTFS driver unless they do workarounds like renaming things automatically because some things Proton does are not compatible with the filesystem spec.














  • Just to clarify, I use Pop!_OS and not Fedora Ublue. I looked at their Wiki because they are the only ones who had documentation on how they made hw accel work with Flatpak and Nvidia specifically. More exaclty I was led there by this Reddit post.

    AFAIK it should work fine with AMD since Firefox can use the VA-API FFmpeg Flatpak to provide hw accel which should work fine with AMD GPUs. This does however not support Nvidia GPUs, which is why you have to expose the driver in the sandbox and force Firefox to try to use it etc.


  • Mesa drivers for opengl, vulkan, etc. are likely already installed, what you need to install are the mesa-va and mesa-vdpau drivers for video acceleration. Other than that, you just need to make sure the GPU doesn’t stay in power saving mode when you play.

    Thanks, I’ll make sure to install those for sure then.

    Btw, video acceleration with Nvidia mostly works if you use this.

    You know, I actually tried, and I couldn’t get hardware acceleration working in the Firefox Flatpak for the love of god. I tried everything, all the guides, looked at the Ublue documentation how they did it etc. and in the end I decided it’s just not worth it because playback worked fine without, just with a wee bit higher CPU usage.



  • I reported basically this issue a few months back with another Lenovo device. Sadly there was no other activity towards resolving this.

    Maybe you can bring in some new information if you can confirm, that you have the same issue.

    In essence the hover recognition distance greatly reduces when touch input is present causing these jumps to happen with the palm because when writing any lifting off the pen will reactivate touch.



  • Well yes sure, but remember AV1 decoding only became standard like 1-2 GPU generations ago. Encoding only this generation. iPhones only got support with the 15 Pro so it will be another generation before it trickles down to the base models. And what about the hundreds of millions of Android phones in Asia and the likes with dirt cheap SoCs. Pretty sure they don’t have dedicated AV1 decoding hardware for a long time.

    So that’s a TON of hardware being made slow and inefficient if everything were to be AVIF tomorrow. Not saying AVIF decoding will be a big hurdle in the future but how long until all this hardware browsing the web has been replaced? That’s why I think somethings that’s efficient and fast on CPUs without any specialised hardware is more suited for a replacement.


  • Well yes, however without acceleration JPEG XL is many times faster. Also if you only have a CPU for example.

    It’s also highly parallelizable compared to AVIF which also matters a lot considering the amount of cores is growing with the likes of ARM and hybrid architecture CPU.

    AVIF also fairs badly with high fidelity and lossless encoding, has 1/3 the bit depth and pretty small dimension limits for something like photography.

    I don’t think AVIF is per se a bad format. I just think if I want to replace a photo oriented format I’d like to do that with one that’s focused on „good“ photos and not just an afterthought with up- and downsides.