Skip Navigation

Posts
1
Comments
663
Joined
3 yr. ago

  • The display looks great and mine doesn’t have the stuck pixel or the buggy lines issue you experienced

    They have since fixed that.

    though I do have very noticeable ghosting artifacts

    Unfortunately just the nature of the technology. If you're just reading, DU4:3 works the best, for manga I use the full G:4 mode with screen refresh for every page flip enabled.

    I wrote some custom profiles for each (Default, Book, Manga, Notes, Notes (Landscape) which I have on my desktop, I can send you the scripts if you want.

    Couldn't find a good way to use browsers on it yet since they all smooth scroll instead of jumping in fixed intervals.

  • I left mine running over night with KOReader open, Nextcloud in background, no suspend and it took 20 hours and 10 minutes to go from 100% to 10%.

    As @poweruser@lemmy.sdf.org wrote, there is a pretty significant phantom drain where it loses about 15% per day when suspended.

  • I have used the same tip for a year and it's still fine. It also comes with 2 tip replacement and all of the generic pens for EMR screens work on the Pinenote.

    Can't say much about the battery life but I'm going to leave it running once it's fully charged and report back.

  • I have one, I wrote a small review for it last year: https://domistyle.gitlab.io/pinenote-2024/ (enable autoplay so the videos play).

    You can test Xournal++ and KOReader on any Linux desktop, it's what works best on the PineNote right now.

    They also have an active Matrix group where the main developers are present.

  • So I've resigned to settling for any phone that's cutting edge.

    If you drop the "cutting edge" condition instead, you could grab a Fairphone, which ticks all the other checkboxes.

    Unless you game on your phone, you won't notice a thing between modern high end and low end phones as long as they put enough RAM in.

    Samsung is the opposite of everything you mentioned besides cutting edge.

  • i'm getting coil whine from it and had to live with that until 60 series...

    My 7900 XTX sounds like it's trying to establish a dial-up connection to Satan when running intense compute tasks. So we can suffer together.

  • I don't hate LTT but they are mostly an entertainment channel nowadays, not a review channel.

    Their reviews are focused on sponsored products, sometimes wrong and most of the time don't go into much depth. Not to mention the countless ads, sponsorships and clickbait.

    If somebody likes them, more power to them, but I don't go to LTT when I need information about something.

  • That's the thing I miss the most. We have such insanely powerful hardware now and yet we never exceeded 2009 in destruction tech.

    Teardown scratched that itch a little bit but it lacks proper building physics.

  • I can't speak for client capabilities on Apple devices, but what's your server hardware? CPU or GPU transcoding?

    I have an AMD GPU in my server and have no issues transcoding AV1 and H265 for my lesser capable clients.

    You can also setup Jellyfin in parallel to Plex and give it a whirl.

  • Sir, this is a /c/selfhosted.

  • but half the 4k streaming content is compressed to hell.

    You can up that to 80%. Almost anything coming from Netflix in 4k is severely bitrate starved.

    Then there is the opposite extreme, like the Arcane blu-rays that put animated content in a 100 Mbit/s stream. Completely overkill but I love it.

  • The only game where I thought the story was complete but the DLC proved me wrong.

  • Who is kiss?

  • 2027/2032 is still some time away.

    However, accessibility features provided by third-party applications may be worse in some aspects. Please open a bug report if you have any special requirements that we don’t cover yet! This is an active topic we’re very interested in improving.

    Let them know what you need.

  • I bought a Model 3 SR+ in 2019 because it was pretty much the only decent option, also still driving it.

    BYD and other Chinese brands were not available here yet and German manufacturers were asleep at the wheel.

    The best coming out of Germany at that time were repurposed chassis from ICE cars, with all the flaws that brings. The Leaf lacked water cooling on the batteries.

    The best alternative at that time was a classic Hyundai Ioniq but it had a 28 kWh battery where as the Model 3 SR+ had a 52 kWh battery for 10.000€ more.

    Since you own an e-Golf, just to put some numbers on this. (e-Golf left, Model 3 SR+ right)

    • Efficiency: 168 Wh/km vs 146 Wh/km
    • Battery: 32 kWh vs 52 kWh
    • Fast charging: 39 kW vs 105 kW (later patched to 170 kW peak)
    • Acceleration: 9.6s vs 5.6s 0-100
    • Weight: 1615 kg vs 1700 kg
    • Price: 32.000€ vs 45.000€
    • Charger network: Whatever ionity was doing vs Superchargers

    https://ev-database.org/car/1087/Volkswagen-e-Golf

    https://ev-database.org/car/1485/Tesla-Model-3-Standard-Range-Plus

  • Instead, they maintain the same versions of software on Windows as well until enough time has passed and enough updates have piled up that they do finally re-test everything

    I'm not that involved with their testing procedure but doesn't that put newer cards at a disadvantage?

    They lack any sort of driver optimization if the release drivers are never installed.

  • That makes sense.

    So the best option seems to be to note updates for newer cards down until the automated testing can be done on Linux as well.

  • https://www.youtube.com/watch?v=ovOx4_8ajZ8&t=2746

    I'm not sure I quite understand the issue Steve has with things updating when adding new cards.

    Sure, updates during a single benchmark series is a problem but what is the issue with the system being updated for the next benchmarks?

    Proton/amdgpu/Mesa receiving updates is no different than installing newer "Game Ready" drivers when a new GPU comes out.

    I assume they don't go out of their way to install older (potentially incompatible) drivers on Windows just so they can compare two separate benchmarks.

    Besides that, after disabling Flatpak and rpm-ostree updates in Bazzite, the only remaining variable is Proton. Which should be easily fixed by manually copying a fixed Proton version to their compatibility tools and using that.