the hoarding wyrmling
@wyrmling.bsky.social
Avid Scalie Computer Enthusiast.
NPR Artist / Data hoarder / Aspiring pencil user
NPR Artist / Data hoarder / Aspiring pencil user
Rest peacefully
December 9, 2025 at 3:02 AM
Rest peacefully
It is a tad late and I seem to have mixed up LLVM with LLDB here, but they're very quite closely related.
VSC will automatically pull & use "CodeLLDB" as an extension on unix-based systems when trying to launch its integrated debugging tools on a supported language.
VSC will automatically pull & use "CodeLLDB" as an extension on unix-based systems when trying to launch its integrated debugging tools on a supported language.
December 8, 2025 at 11:54 PM
It is a tad late and I seem to have mixed up LLVM with LLDB here, but they're very quite closely related.
VSC will automatically pull & use "CodeLLDB" as an extension on unix-based systems when trying to launch its integrated debugging tools on a supported language.
VSC will automatically pull & use "CodeLLDB" as an extension on unix-based systems when trying to launch its integrated debugging tools on a supported language.
It is also how a lot of language-agnostic debugging with things like call stacks, breakpoints and variable watching is done, which then gets neatly integrated into your IDE of choice.
December 8, 2025 at 11:31 PM
It is also how a lot of language-agnostic debugging with things like call stacks, breakpoints and variable watching is done, which then gets neatly integrated into your IDE of choice.
Many such cases
December 4, 2025 at 2:55 AM
Many such cases
I'm frankly not low-level enough to understand much of these specifics, considering that HDR already is functional on KDE (I'm on it *right now*) but it is still a clear sign to me that HDR is still something Valve is prioritizing, even if they're simply funding it, and not themselves developing.
November 30, 2025 at 2:49 PM
I'm frankly not low-level enough to understand much of these specifics, considering that HDR already is functional on KDE (I'm on it *right now*) but it is still a clear sign to me that HDR is still something Valve is prioritizing, even if they're simply funding it, and not themselves developing.
2) Regarding HDR; although Valve still hasn't shown any signs of updating KDE in newer versions of Steam OS yet, kernel-level color-management work sponsored by Valve to better facilitate HDR was recently signaled as ready for the Linux 6.19 merge window
www.phoronix.com/news/Linux-C...
www.phoronix.com/news/Linux-C...
Valve-Backed Color Pipeline API For Linux Is Finally Ready For Upstream
For those Linux desktop users in the US needing another reason to be thankful this Thanksgiving, a huge and long-awaited accomplishment is ready for merging to the kernel: the Color Pipeline API that ...
www.phoronix.com
November 30, 2025 at 2:49 PM
2) Regarding HDR; although Valve still hasn't shown any signs of updating KDE in newer versions of Steam OS yet, kernel-level color-management work sponsored by Valve to better facilitate HDR was recently signaled as ready for the Linux 6.19 merge window
www.phoronix.com/news/Linux-C...
www.phoronix.com/news/Linux-C...
I did my best to compile my findings with regards to this into a comment on the closest matching issue on Valve's SteamOS Issue tracker:
github.com/ValveSoftwar...
In effect, this means the Steam Deck cannot play back Atmos audio from streaming platforms, only BluRay rips with TrueHD.
github.com/ValveSoftwar...
In effect, this means the Steam Deck cannot play back Atmos audio from streaming platforms, only BluRay rips with TrueHD.
![A screenshot of the GitHub Issue comment linked in the post, containing the following text:
I may have some developments regarding this. I've been exploring using my Deck as a HTPC watching movies with Atmos audio, but have been running into issues regarding pass-through as well.
(apologies beforehand that this comment might be a bit of a mess)
Passthrough seems to work okay with mpv without having to mess with the pipewire service.
You'll need to set --audio-device to your HDMI device's alsa entry (found with --audio-device=help), plus --audio-spdif with whatever codec it is you're trying to pass through. With that
(Jellyfin Media Player just happens to do all of this for you automatically, as long as you enable it's pass-through options in the settings)
It will sometimes stop working if you mess around too much, but exiting to the game view and going back to desktop seems to kick it back into working order.
However, codec passthrough support seems spotty across docks.
I originally used a third-party JSAUX dock, which only seemed to pass through lossy codecs to my receiver (presumably a bandwidth issue).
However, I managed to lend the official dock too, which doesn't seem to have this issue, but instead refuses to pass through only eac3, aka Dolby Digital Plus.
Here's my results, including ones from a laptop connected straight to the reciever to make sure it truly can pass all of these formats through:
[Table indicating that the JSAUX Dock cannot pass through TrueHD or DTS-HD Master Audio, while the Official Dock can pass through all codecs besides Dolby Digital Plus]
The lack of Dolby Digital Plus passthrough on the official dock is obviously quite perplexing, and hopefully something that could be addressed with a firmware update](https://cdn.bsky.app/img/feed_thumbnail/plain/did:plc:tvewszksog52rknhlrtjuczc/bafkreig4dxypgilz5pcwg3xccwrdi6pnacpatpuaunm4r2zbtkkbqmpuw4@jpeg)
November 30, 2025 at 2:49 PM
I did my best to compile my findings with regards to this into a comment on the closest matching issue on Valve's SteamOS Issue tracker:
github.com/ValveSoftwar...
In effect, this means the Steam Deck cannot play back Atmos audio from streaming platforms, only BluRay rips with TrueHD.
github.com/ValveSoftwar...
In effect, this means the Steam Deck cannot play back Atmos audio from streaming platforms, only BluRay rips with TrueHD.