vividspecter

joined 1 year ago
[–] vividspecter@lemm.ee 7 points 2 days ago* (last edited 2 days ago) (1 children)

And the software ecosystem, much of which they have funded/developed. In 2015, there was no proton, no DXVK, no vkd3d, and most important, no Vulkan.

[–] vividspecter@lemm.ee 10 points 4 days ago

It's a reverse-cycle AC if you've heard the term. Basically, an AC that can can run in reverse, heating the room.

It's the most efficient form of heating and cooling that we have, since it doesn't create energy, but instead moves it (so its efficiency is greater than 100%).

[–] vividspecter@lemm.ee 3 points 6 days ago

I've seen it go down in some cases on VPNs, so it could be a matter of time (or they'll find a solution again and the back and forth will just continue).

[–] vividspecter@lemm.ee 6 points 6 days ago (1 children)

Youtube isn't just a thing people use to waste time, but a source of educational content. That actually matters, and there isn't a good alternative to much of it.

That being said, I agree that people could at least drop it (or reduce their usage) if they are just using it as a time waster.

[–] vividspecter@lemm.ee 1 points 1 week ago

What headphones in particular are you using? Because with standard AD2P you're limited to mSBC at best, but maybe your device has some proprietary implementation.

You could try with a hardware dongle, but no guarantee that will work either.

At least in the long run it should be fixed by Bluetooth LE audio, but I'm not sure if the Deck properly supports it yet, and it requires new audio devices as well.

[–] vividspecter@lemm.ee 2 points 1 week ago

Pulseaudio has been pretty solid for a while now which is what the steamdeck uses from what i can see online.

It uses Pipewire, but it has pretty close to full API compatibility with Pulseaudio (and Jack) so most applications will "just work" and you get lower and more stable latency in return.

[–] vividspecter@lemm.ee 10 points 1 week ago* (last edited 1 week ago)

On the open source side of things, I'll add that gadgetbridge is pretty rapidly making progress with Garmin devices. Might not be enough if you're deep into the Garmin ecosystem etc, but if you just want something simple and private, it's a good alternative.

I suggest using the nightly f-droid repo as there's new updates multiple times per week.

[–] vividspecter@lemm.ee 2 points 1 week ago

They are right that Garmin sleep tracking is pretty inaccurate though. Not so much the length, but identifying the sleep stages correctly. But yeah, it's like how drinking alcohol fucks your HRV up, it's just showing the issues alcohol can cause.

[–] vividspecter@lemm.ee 10 points 1 week ago* (last edited 1 week ago)

Humans don't work this way, especially knowledge workers. We need breaks to function at our best, and constantly doing work for 8 hours (or more) is not it. Not to mention the health issues that come from constantly sitting.

[–] vividspecter@lemm.ee 14 points 1 week ago

I do about the same amount overall I just don’t get around to it as quickly.

That's the important part. Who gives a fuck when and how you finish your work, as long as you do. We can only be productive for so many hours a day anyway.

[–] vividspecter@lemm.ee 5 points 1 week ago* (last edited 1 week ago)

The drivers for your card needs to support the required extensions, and the hardware needs to support the particular codecs as well. So if you don't have already have encoding/decoding support for the given codec with OGL etc, this won't add it most likely.

The main benefit is that application devs won't need to add multiple hardware decoding/encoding APIs, and can just target Vulkan. Cross platform support in particular is currently a mess due to the different APIs on Windows/Linux/Mac, so this will simplify things greatly. Eventually, driver devs will be able to just support Vulkan too, but that's a long way off.

[–] vividspecter@lemm.ee 5 points 1 week ago (4 children)

As someone who already has a Deck, I'm more keen on this. The Index was very expensive and only had a limited run. Mind you, the Index is expensive in general and I hope they aim for Quest level prices this time around.

 

tl;dr Geometric mean results

 

tl;dr EEVDF CPU scheduler that has replaced Linux's previous default scheduler (CFS), is close to completion. CPU schedulers can have a significant effect on performance and latency of various tasks.

It will be interesting to see how it compares to BORE which is what I use on my desktop systems. There's also the many workload specific schedulers that sched_ext allows for, but it's still not in mainline I believe.

65
Bazzite 3.5.0 Update Released (universal-blue.discourse.group)
 
  • Nvidia 555 Drivers on Bazzite (Nvidia :heart: Wayland)
  • Handheld Daemon Version 3
  • Full Steam Deck OLED Support
 

tl;dr technical about about the upcoming sched_ext interface in Linux 6.11, used for running out-of-tree CPU schedulers on the fly

 
  • Support for asynchronous processing has been implemented. Nodes can choose (or be forced) to be scheduled asynchronously. The graph will not wait for the output of the node to continue processing but it will use the output of the previous cycle (or silence) instead. This adds one cycle of latency but it can avoid having some nodes blocking the processing graph. Non realtime streams and filters now also use this asynchronous processing instead of their own slightly broken version.

  • The concept of node.sync-group was added. This groups nodes with overlapping sync-group together when one of them sets the node.sync = true. This is now used to make sure all nodes are scheduled together when JACK transport is started so that they all see the same transport time.

  • Config parsing errors are reported earlier and much better with line and column numbers where the parsing started to fail.

  • Add support for mandatory metadata when negotiating buffer parameters. This can be used to only negotiate extra buffer planes when certain metadata is negotiated. One use case is the explicit sync support that requires 2 extra fds for the timelines.

  • Explicit sync metadata and support was added.

  • Support was added for making and using multiple data-loops in the server and clients. Support for CPU affinity and priorities was added to the data-loops as well.

  • The log topic debug levels can now be changed at runtime with metadata.

  • The log levels in the pulse server can be dynamically changed with a /core message.

  • The UCM conflicting devices patches were merged.

  • Add snapcast-discover module to stream to snapcast servers.

  • Rework how peers are linked and the counters are updated. Resume the peers when a node is unlinked and not yet processed. This should cause less occasional dropouts in the graph when reconnecting things.

  • Many GStreamer element updates.

  • Many more fixes and improvements.

EDIT: Whoops, looks like a repost.

view more: next ›