marmarama @ marmarama @lemmy.world

Posts

0

Comments

39

Joined

2 yr. ago

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.

That's only true if China gets no further than attempting an amphibious landing on Taiwan. If China succeeds in creating a bridgehead on the island, then many of the same land-based weapons and systems that the US is currently supplying to Ukraine, or that Ukraine would like to have, come into play, including 155mm artillery, rocket artillery, tanks, air defence missiles, and land-based multirole aircraft like the F-16.

From a war planning point of view, unfortunately you can't assume that China's amphibious landing would fail. In fact, I think it's more likely that China would succeed in establishing some kind of foothold on the island in the early stages of a future Taiwan war than not. If the amphibious force is large enough, it would be very difficult to eliminate all the landing craft, especially if there is a successful misdirection.

This is without considering that North Korea could also simultaneously launch a land-based attack on South Korea to dilute any US response in either theatre.

The real meat shields in the war in Ukraine are Russian conscripts. At least Ukrainian conscripts have the conviction that they are defending their country's internationally recognised borders.

The US (and the rest of NATO) is being cautious for a reason, and it's not because they're using Ukrainians as "meat shields."

NATO stocks of war materiel were at historically low levels before February 2022, and it's difficult for the US to commit fully when China is sabre-rattling over Taiwan. That's Xi's (and Kim Jong-Un's, to a lesser extent) gift to Putin. Sabre-rattling keeps the US from engaging fully in Ukraine, even though China won't be ready to invade Taiwan for several years yet.

Unfortunately for Ukraine, it'll be several years before NATO materiel stocks start to grow above 2022 levels, but they will grow.

The question is, will they grow fast enough?

Personally I'm predicting world war in 2027-28 unless the West pulls its finger out.

Smells like two instances behind the load balancer, one is fine with the JWT, one is not.

Like it or loathe it, the BBC is the UK's most important broadcaster by a country mile.

If the BBC's internal procedures are shown to be reasonable and to have been followed, which it appears so far to have been the case, then I don't see anyone jumping ship about this.

People do dumb stuff all the time, some of which may or may not be illegal. It isn't an employer's responsibility until the employer finds out about it. What matters is the response and, so far at least, it appears the BBC has done fairly well this time, although perhaps more effort could have been made after the initial followups made by the BBC to the original complaint were ignored.

I pulled them from the table at https://en.wikipedia.org/wiki/Casualties_of_the_Russo-Ukrainian_War#Total_casualties which seems to be kept fairly up-to-date with the reasonably credible claims, including the Meduza estimates. Original references are in the Wikipedia article.

I added the 30000 upper bound as a fudge for the Ukrainian military deaths because the one somewhat credible estimate from the US that table lists only covers up to May 2023. While Ukraine has been on the offensive since then, I don't think increasing the KIA numbers by more than 50% in 2 months is credible even under the circumstances.

Most Fediverse users are Western. The Western world has plenty of media diversity, and you can find virtually every viewpoint you can imagine represented there. Open criticism of government, all the way to the top, is a normal part of everyday life, and media outlets regularly criticise each other, and themselves, for bad takes and poor journalism.

Because of the diversity of media opinion, it is harder to push an agenda, so mainstream Western media does it, by and large, with substantial subtlety, building trust first, and seeding ideas over long periods of time.

Russian and Chinese media aimed at a Western audience seems brash and full of bad takes by comparison. It is rarely, if ever, critical of itself or of its own government, and also rarely provides any independently verifiable evidence for its claims. To a Western audience used to Western media, it appears so one-sided that it is laughable. That is why it is easy for people in the West to dismiss it as propaganda.

You could probably write a PhD thesis on why media outlets in China and Russia find it difficult to play the Western media game, but I think the main issue is this: If you live in a society that doesn't itself value diversity of opinion and thought, it is difficult to produce media for a society that does value that without it seeming off-kilter. It's a bit like the difference between being fluent in another language and "feeling" the language. To a native speaker listening to it, the difference is really obvious.

If pro-Russian media come up with a decent methodology to independently estimate Ukrainian losses, then I'm sure some discussion can be had around that.

Don't expect the opposition to do the work for you.

Somewhere between 9000 and 42000 civilians depending on estimates, and probably 20000-30000 military, again depending on estimates.

Converted-to-Bluetooth Stadia controller.

It's actually a really nice controller. The ergonomics are great for my big meaty hands, it's got some weight to it and feels really solidly built. The heft means the vibration really has some kick to it. The battery life is really good too - it was specced for having Wi-Fi on all the time, so now it's running only a little Bluetooth LE radio, the battery is massive. Even when it runs down, the charge rate is quick - full in about half an hour, and then good to go for weeks. Again, probably because it was specced for Wi-Fi, the radio circuitry is way above average and the range is stupid - I can control a Steam Deck from two rooms away, through two solid brick walls, something none of my other controllers can do.

The sticks are accurate and don't drift, the buttons are pretty good, and the D-Pad is a bit stiff but perfectly serviceable. My one significant complaint is that the springback on the triggers is way too light, which makes it difficult to be subtle with the triggers, a little annoying for driving games.

Still, if you see one at a sensible price, they're a steal.

Bit of a nitpick, but the comparison with the reversing of the MS Office formats is a bit tenuous, and somewhat revisionist.

Competitors and open-source applications were reverse-engineering the Office file formats long before Apple iWork was a thing, and arguably no-one really gets it right because in order to get it perfect you'd have to reproduce the Office application layouting engine exactly, bug-for-bug. Even Microsoft doesn't get it 100% from release to release.

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).