The last syllable is usually pretty subtle, like the br- in bread, but very quietly voiced. I’d say I hear it maybe 75% of the time I hear the word. Currently in Yorkshire, via SW England, London and NW England. The syllable is a lot less subtle in a West Yorks accent!

Did you learn French at GCSE level? Possibly there’s a relationship between that and pronouncing the re like that in French-derived words. Cadre is another example. If it is related to learning French, then it’s probably on the decline as French teaching is on the decline and foreign languages are no longer compulsory at GCSE.

In some of the accents around here, blood, wood and food do rhyme, more or less.

British English voices those letters in most accents. I think the two silent letters is just a North American thing.

Similar to herb.

Do we have to bring this up again? It’s just boring.

systemd is here and it isn’t going anywhere soon. It’s an improvement over SysV, but the core init system is arguably less well-designed than some of the other options that were on the table 10 years ago when its adoption started. The systemd userspace ecosystem has significantly stifled development of alternatives that provide equivalent functionality, which has led to less experimentation and innovation in those areas. In many cases those systemd add-on services provide less functionality than what they have replaced, but are adopted simply because they are part of the systemd ecosystem. The core unit file format is verbose and somewhat awkward, and the *ctl utilities are messy and sometimes unfriendly.

Like most Red Hat-originated software written in the last 15 years, it valiantly attempts to solve real problems with Linux, and mostly achieves that, but there are enough corner cases and short-sighted design decisions that it ends up being mediocre and somewhat annoying.

Personally I hope that someone comes along and takes the lessons learned and rewrites it, much like Pulseaudio has been replaced by Pipewire. Perhaps if someone decides it needs rewriting in Rust?

The WiFi card is probably a Realtek 8852AE, which has become very common in laptops since 2021. Unfortunately Realtek driver support tends to lag quite a bit.

If you want to run Ubuntu Desktop 22.04, then you’re probably best off waiting a few weeks for the Ubuntu Desktop 22.04.4 point release. It’s due sometime this month. It will boot and install an “HWE” (Hardware Enablement) kernel and drivers, that are based on the kernel from Ubuntu 23.04, and therefore should work out of the box with your WiFi card.

While it’s possible to upgrade an existing Ubuntu 22.04 installation with the latest HWE kernel, doing it by downloading the relevant packages on another machine and moving them across using a USB stick is going to be somewhat frustrating if you’ve not done it before. You’ll certainly learn a few things, but it may not be an enjoyable experience. I’m a grizzled Linux veteran, and I’m pretty sure I’d end up forgetting to download one or more packages and having to swap back and forth between machines.

In the meantime, I would just continue to use Ubuntu 23.04. In fact, if it was me, I would probably just stick with 23.04, upgrade to 23.10 and then subsequently 24.04 when they become available. What you do once you’re on the 24.04 LTS release is up to you. By that time, other distros will probably also work out of the box too.

At least for me, there is a big difference between naming things at home and naming things for work.

Work “pet” machines get systematic names based on function, location, ownership and/or serial/asset numbers. There aren’t very many of them these days. If they are “cattle” then they get random names, and their build is ephemeral. If they go wrong or need an upgrade, they get rebuilt and their replacement build gets a new random name. Whether they are pets or cattle, the hostnames are secondary to tags and other metadata, and in most cases the tags are used to identify the machines in the first instance, because tags are far more flexible and descriptive than a hostname.

At home, where the number of machines is limited, I know all of them like the back of my hand, and it’s mostly just me touching them, whimsical names are where it’s at.

Ungulates. Because who doesn’t like a hoofed animal?

My client machines are even-toed ungulates (order Artiodactyla) and my servers/IoT machines are odd-toed (order Perissodactyla). I’m typing this on Gazelle. My router is called Quagga, both after the extinct zebra subspecies and the routing protocol software (I don’t use it any more but hey, it’s a router).

Biological taxonomy is a great source of a huge number of systematic (and colloquial) names.

I could well be wrong about the AAC passthrough, and I should have hedged that statement with “allegedly” as I’ve not tested it myself.

To your other point though, I disagree - there are plenty of ways you could pass through an unchanged AAC bitstream, but still mix in other sounds when required. For example, having the sender duck the original bitstream out temporarily and send a mixed replacement bitstream while the other sound is playing. Or (and this would only work if you control the firmware on the receiver, but if you’re using Apple headphones with an Apple device, that’s not a problem) sending multiple bitstreams to the receiver and letting the receiver mix them.

I can only comment on my experience with my own equipment and ears, but in my experience, 990Kbps LDAC is noticeably more transparent than 256Kbps AAC for Bluetooth audio.

I can fairly reliably guess whether or not I remembered to switch my Sony XM4s out of multipoint mode the last time I used them (when in multipoint pairing mode LDAC is not supported and 256Kbps AAC is usually what gets negotiated). The difference is small, but over a few minutes of listening, the sonic signature when it’s using AAC is just a little bit “off” and my ears don’t like it as much.

Could I ABX the difference using the usual ABX setup with short samples of music I’m not familiar with? Probably not. Can I tell the difference over an extended period using music I know well, and that I often listen to uncompressed? Yes, pretty easily.

LDAC is not a particularly sophisticated codec, but it doesn’t have to be when it has a 990Kbps bitrate. It’s also possible that the FDK-AAC codec that I think both Pipewire and Android use for real-time AAC encoding is not the best tuned for 256Kbps CBR. AIUI in 256Kbps CBR mode, FDK-AAC has a hard low-pass filter at 17KHz, and I can still hear above 17KHz.

Yeah, I agree.

I bought them for their noise cancelling primarily, and they’re excellent at that, but otherwise they’re not great. The un-EQed frequency response is terrible for headphones in their price range: flabby, wildly over-exaggerated bass and no mids at all. Running without EQ I can barely hear lyrics - every singer sounds like they’re mumbling underwater. I’ve had $20 IEMs with better tonal balance. They respond well to EQ but the on-board EQ doesn’t have enough frequency bands to even come close to fixing them. Wavelet on Android doing EQ duty makes them listenable. Even when you do EQ them properly, they still sound a bit dull and lifeless.

No idea how they got so much praise when they were launched. The power of marketing budgets I guess. For a while I was gaslighting myself thinking I had a faulty pair or maybe there was something going wrong with my hearing, but having heard another pair, and doing comparisons with my other headphones - most of which are far cheaper - I realised that no, they’re just not very good as headphones.

It is worse than uncompressed, but 990Kbps LDAC is the closest codec to totally transparent I’ve heard for Bluetooth audio. AptX HD is nearly as good to my ears, and is better than 660Kbps LDAC. The differences are very small though, especially when compared with the differences on the analog side, e.g. the amp, and particularly the headphone design.

Apple side-steps the problem by, at least when you’re listening to Apple Music, simply sending the AAC stream as-is to the headphones and has them decode the audio. I don’t know why that isn’t a more common approach.

I’m still somewhat bemused that we’re talking about Bluetooth codecs at all. It surely can’t be that difficult technically to get 1.5Mbps actual throughput on Bluetooth and simply send raw 16-bit/44.1Khz PCM. 2.4Ghz WiFi is capable of hundreds of times that speed. Bluetooth has been stuck at the same speeds for decades.

I have a Radsone ES100 Bluetooth DAC/headphone amp, and that supports LDAC, multipoint, and doesn’t compromise the LDAC bitrate when you have multipoint enabled. You can even leave it plugged in as a USB DAC and still use multipoint BT with LDAC, and it switches smoothly between the sources depending on which device started playing a stream most recently.

I was distinctly underwhelmed by the BT implementation when I got my Sony XM4s, it’s kinda weak by comparison.

The UI font in MacOS is called SF Pro. If you have access to a Mac you can simply copy the .otf font files over to Linux (they are in /System/Library/Fonts on MacOS) and install and use them there.

If you don’t have access to a Mac, Google Roboto Sans is a very similar design (it was the default Android UI font for several years) and if it’s not already installed by your Linux distro, it’s freely downloadable.

MacOS font rendering is dreadful on non-Retina/HiDPI displays. If you want similar rendering on Linux, turn font hinting off, and set antialiasing to greyscale only, no subpixel rendering. It will look very similar, if not identical, to modern MacOS.

For non-Retina displays I vastly prefer FreeType’s subpixel antialiasing and “slight” hinting to what MacOS does.

Have you tried turning off Wi-Fi power management on the Deck? The Deck’s Wi-Fi is normally pretty good, but the Wi-Fi power management occasionally has issues with some combinations of router chipset and router settings, which can cause symptoms like what you’re experiencing.

Full instructions are here: https://seekingtech.com/how-to-disable-wi-fi-power-management-on-steam-deck/

Nvidia drivers have (slightly) more timely support for the latest cards, and more mature support for non-3D uses of the GPU, especially scientific computing. To a large extent they are the same code as the Windows drivers, and that has positives in terms of breadth and maturity of support.

For everything else, the AMD drivers are better. Because they are a separate codebase from the Windows drivers, and are part of the de-facto Linux GPU driver stack Mesa, they integrate much better into the overall Linux experience, especially around support for Wayland. Unless you have an absolutely bleeding-edge card, they “just work” more often than the Nvidia drivers. If you like doing serious tinkering on your Linux system, then the AMD drivers being fully integrated and having the source available is a major win. Also, it used to be that the Nvidia drivers did a much better job of squeezing performance out of the hardware, but today there’s very little in it, and the AMD drivers might even be a little more efficient.

I’ve got both AMD and Nvidia GPUs currently in different machines, and I much prefer the Linux experience with AMD. I don’t think I’ll be buying another Nvidia GPU unless the driver situation changes significantly.

FWIW I don’t stream so I can’t comment on the exact situation, but I have used the video encode hardware on AMD cards via VAAPI and it was competent and much faster than x264/x265 on the CPU. I think OBS has a plugin to use VAAPI (which is the “standard” Linux video decode/encode acceleration interface that everyone but Nvidia supports).