Hacker Newsnew | past | comments | ask | show | jobs | submit | dist-epoch's commentslogin

"Mythos, find me a bug in LUKS. I know there is one in there".

Both Intel/AMD CPUs produced in the last 5 years or so support full transparent (to the OS) memory encryption. So cold boot attacks are a thing of the past if you enable this feature (it's typically disabled because it reduces RAM speed by about 0.5%).

The impact on performance is more along the lines of 1-2% on AMD (though it likely varies by generation (I did extensive benchmarking on Renoir wrt throughput/latency/gpu). But yes small enough to be insignificant unless you run LLMs or game on the iGPU. I imagine that it also uses marginally more power.

AMD also has a second encryption mode where the OS decides what gets transparently encrypted, it doesn't have to be everything. But that mode is poorly documented (or at least the documentation isn't accessible to peasants like me)


Recent news is that this isn't shipping on some consumer-grade CPUs from AMD. There, made it explicit enough there's no room for conversation. Here's the link:

https://arstechnica.com/security/2026/06/users-cry-foul-afte...


AMD backtracked on that strategy: https://www.techpowerup.com/350142/amd-to-restore-tsme-memor...

Future AGESA updates will still include memory encryption for all processor models. It's one of the rare instances of consumer backlash creating a clear and immediate response.


No synth generates sawtooths by literally drawing a saw tooth in PCM. The distorsion you get if you do that is not subtle at all.

Proper audio resampling should not be identifiable. Of course, the OS mixer probably doesn't do proper (CPU expensive) resampling.

But a quality audio player should account for this and do it's own.


If you're not on a US-based IP, you should check out https://src.infinitewave.ca/

It is an incredible resource to see the quality of the resampling algorithms used by the actual production software likely used in any digital audio workflow.

You will see that while the best are indeed almost 100% transparent, many are not.


> If you're not on a US-based IP, you should check out https://src.infinitewave.ca/

There is also https://src.hydrogenaudio.org/ (with no IP based restrictions, AFAIK).


Currently giving me: "Internal Server error reading database"

I remember using Adobe Audition for resampling audio, this site shows I had good intuition

your software is among the best, but not pitch black best :)


Yeah, we use Secret Rabbit Code for ours, though we have access to the sox code now and that is "perfect". We might change to that as the default sometime this year.

I'm also one of those audiophile crazies that obsesses over which metals to use in cabling, power filtering, swapping opamps, and builds their own DACs, amps, and speakers

"proper" resampling was expensive in 1997 when Intel was introducing fixed sampling AC'97, but was below noise floor of CPU load meter in 2007 when Microsoft released Vista killing hardware mixing.

The whole audiophile industry is built on stuff which doesn't make any sense

My favourite: "audiophile-grade" audio players which allocate a single continuous buffer of RAM into which they load/decode the whole .WAV/.FLAC file, because supposedly the CPU "jumping" between "fragmented audio" causes audible "jitter".

Of course, they don't know that what looks like continuous memory to user-code is probably discontinuous in kernel/physical RAM.

Didn't check in many years, I wonder if they created kernel level players to account for that, to have "true continuous memory"


Don't forget: "most players use malloc to get memory while new is the c++ method and sounds better."[1]

[1] https://www.audioasylum.com/messages/pcaudio/119979/


> My favourite: "audiophile-grade" audio players which allocate a single contignuous buffer of RAM into which they load/decode the whole .WAV/.FLAC file, because supposedly the CPU "jumping" between "fragmented memory" causes audible "jitter".

Thanks for the laugh... this is absolutely bonkers. In case anyone is wondering, before sound hits our ears it has to go through a digital to analog conversion, which takes place on hardware independent of the CPU, operating with its own clock and buffers etc.


Am486DX/100 was enough to decode and listen an MP3 at 22KHz (and maybe mono?) and was more than enough to listen for 44/16/2 PCM. It's 31 y.o. today.

I remember playing 44khz 16-bit stereo MP3s encoded at 128 kbit/sec on a 133 Mhz 486.

It gobbled like 90% of the CPU and I had to make sure I gave it a pretty large buffer so it didn't stutter when an app claimed CPU for more than a second, but it worked.


In addition to that, while it is possible to hit a delay and run out of buffer because memory access is slow (the most obvious would be if the input got swapped to disk at an inopportune moment), but the audible effect is really obvious. This isn't some subtle "oh my music sounds ineffably worse" effect, it's "my computer is glitching and my music is unlistenable."

audiophiles (https://forums.stevehoffman.tv/threads/turntables-with-pace....) also claim that turntables can be rated on "timing, rhythm, and pace" in which supposedly the timing of the music can be affected by the turntable's mass and other properties.

How this would occur without also producing grossly audible pitch distortion never seems to be discussed.


I can tell when my CPU usage spikes because it causes a hum through my speakers, so this does not seem that far-fetched.

It's just means you have a shitty audio tract with not enough shielding. Move to SPDIF/TOSLINK.

I have an external audio card, if I put it on a laptop I can hear the modem-like sounds. I wonder why it is so sensitive, should not DAC produce strong signal that cannot be easily affected by radio waves?

Also my headphones are extremely sensitive. I can touch the ring and sleeve of a jack with a finger, and touch a metal bed frame with a tip and I hear quiet clicks as I move the tip along the metal. Sometimes I do not even need to touch the jack with a finger. It doesn't work with small objects like a knife though.


Bad grounding everywhere. This is insanely basic stuff.

the radio waves could be interfeering with the signal before it gets amplified

The latter is probably true, but the former does actually happen, and it's easy to accidentally do--lossless or not.

Red blood cells can't reproduce and are "mule" cells - bags of hemoglobin. They are not really alive, so maybe not exactly what you were thinking of.

article says it's mostly for agents, users will not be directly involved

> At the same time, an agent can make thousands of micropayments without friction, while asking a person to approve each payment would be impossibly burdensome.

but yes, they will need wallets

but it's also optional, you do not want to buy these paid for requests, you do not need a wallet


WHATWG, who sets the HTML standard:

> The central organizational membership and control of WHATWG – its "Steering Group" – consists of Apple, Mozilla, Google, and Microsoft.


same thing that happened to Japan/US: they financialized their economy, companies moved from making things to pushing papers and outsourcing the making to China

https://en.wikipedia.org/wiki/Commodity:

> The wide availability of commodities typically leads to smaller profit margins and diminishes the importance of factors (such as brand name) other than price.

I'm not aware of many commodities which have only 3 world-wide sellers.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: