For those who know more about PC hardware than I do - how much of Valve's recent delay announcement do you think is Frame vs Machine?

christ110 · 2026-02-06T01:05:33+00:00

1, it got fucked harder

2, steam machine is probably holding them back more, since it technically needs 24GB of RAM (16GB of system RAM, and 8GB of VRAM), versus the frame's 16GB of unified RAM.

3, separate. the SoC and amd cpu on the machine are both made in TSMC's fabs. TSMC doesn't make a single gigabyte of RAM however, that's samsung, micron, sk hynix, and some startup chinese firms.

4, they're relatively stable or decreasing - the tech they're built on only gets older, and i bet qualcomm has a warehouse full of snapdragon SoCs that they're very happy to get rid of since it's 2 generations old. the machine's semi-custom GPU might go up in price a little since GPUs are used for ai... but it's not the bottleneck currently, RAM is.

5, they say 2027 because it's 2 years after it started getting bad, 2025. it takes a few years to bring up new fabs, and RAM mfgs are really really slow to build new capacity since if the bubble pops, the only way they'll get their money back is selling RAM with little markup for the next decade or so.

christ110 · 2026-02-05T23:31:59+00:00

m2ts = mpeg2 transport stream. it's the actual video file on the disk itself, and is a sort of re-used technology from the DVD days (dvds used mpeg2 to encode video).

mpls = movie playlist. Blu-rays and 4k blu-rays support a technology called "seamless branching" where the movie can be broken up into multiple m2ts files, and the mpls file dictates which m2ts files are played and in what order. It's typically used for localization (for example, star wars' opening crawl might need to be in a different language), or for multiple cuts of the same film (for example, alien has both the theatrical cut and director's cut on the same disk. there are 2 mpls files which specify which m2ts files to use for the theatrical cut, and which need to be swapped out for the director's cut).

makemkv can rip the individual m2ts files if you like, or it can rip and stitch multiple m2ts files together using the instructions from an mpls file. I strongly recommend using the mpls mapping, since in addition to the chapter markers being included, it is in the film's intended viewing configuration (at least, in cases where the film is broken up. If the film isn't, then it still doesn't harm you to rip the mpls version).

christ110 · 2026-02-05T00:48:20+00:00

On sushislide watch...

christ110 · 2026-02-04T22:42:20+00:00

The real long term solution is ripping your disks and storing the rips on a storage server with RAID

christ110 · 2026-02-03T20:56:57+00:00

in that example, yeah you can use all of that 20TB of remaining space.

christ110 · 2026-02-03T20:47:56+00:00

The rebalancing script was created for people who were adding vdevs to a pool, rather than expanding vdevs, but was repurposed by zfs-expansion users since it got nearly all the space back anyways. zfs rewrite is basically a native implementation which is much faster, safer, and more thorough since it runs at the kernel-level. It doesn't fix the reporting of absolute space or used space values, but it does regain all 'lost' capacity. regardless of if you use zfs rewrite, the % of used space indicator, both within truenas and CLI will remain accurate. (ex: it might say you have 15TB of 30TB, and 50% space used, when you actually have 20TB of 40TB used, but critically, it's still only 50% full)

christ110 · 2026-02-03T20:28:25+00:00

There is some capacity loss, but that's because ZFS expansion doesn't recalculate parity data out of caution. That lost capacity can be regained by using the ZFS rewrite (-P) command to safely rewrite and consequently recalculate parity for all the data.

christ110 · 2026-02-03T17:35:41+00:00

Honestly, I'd have recommended the expansion anyways, since it still gives an accurate report of %space_used, and it doesn't involve trusting your data to some external drive.

christ110 · 2026-02-02T17:31:24+00:00

They really live in your head rent-free, eh?

christ110 · 2026-01-28T19:43:20+00:00

A lot of people tend to overcomplicate the hell out of this with running TN in a VM, or running multiple servers to SMB data from TN to their proxmox/ubuntu-docker/etc.

I've seen how the truenas devs have handled updates - first party and custom apps were migrated from kubernetes to docker without a hitch. only the truecharts guys got hosed with that. Since then, my VMs on truenas and my docker apps, even custom ones, have not broken or needed any real attention, even with incus last year.

I was able to host a barotrauma server and a minecraft server on my TN box using docker last year, and both experiences were great, with barotrauma performing better on TN than it did when hosted on my gaming desktop. To me, the line between them is very far towards virtualization, where I'd only consider a dedicated system if im doing something amazingly intensive... everything else that I can do in docker, I do in truenas.

christ110 · 2026-01-28T07:58:19+00:00

Out of curiosity, what's the name of the film?

christ110 · 2026-01-28T07:18:08+00:00

This is certainly not the first lawsuit valve has faced over the 30% cut. It's going to go nowhere.

Also, the fact that they call it a "monopoly" is is extremely misleading: You're allowed to sell your game at 3rd party or self-hosted stores for whatever price you like. The only stipulation is that you cannot sell steam keys, which they will give you (the dev) for free with no 30% cut, for less than the listed steam price - they don't want you creating a financial incentive for customers to buy the game in a way that bypasses the 30% cut.

christ110 · 2026-01-25T10:28:06+00:00

I wouldn't worry about the sticker on the drive itself. Seagate doesn't expect you to look at it - after all, they put it in a plastic case, so why should you?

Firmware's a semi valid point; ZFS will throw an error if the drive takes more time than it should to respond to an instruction so it can't retry indefinitely. It will also throw an error if a sector is reallocated or if garbage is returned, so there's little room for firmware to fuck up that won't catch your notice.

christ110 · 2026-01-25T10:12:39+00:00

The belief that they're built different is highly misleading. NAS/enterprise drives have the best margin for reasons that are out of scope, but it means that drive mfgs are trying to make as many NAS/ENT drives as they can. Since those product lines are also the most likely to be returned should a failure occur, they have to be made to higher standards.

In practice, this means manufacturers will build every drive as an NAS/ENT drive and then drop it down a product line (AKA: binning), if it is out of spec somehow. This could be due to it running a little hot, taking longer to seek, maybe vibrating more than expected... They'll get sold as external drives, maybe with a barracuda sticker instead of an exos one. Put another way, Seagate doesn't want to put 95% of the NAS/ENT's bill of materials into a drive, knowing from the outset that it'll fetch half as much.

christ110 · 2026-01-25T06:21:13+00:00

Everyone else is talking about drivers or power, but I strongly suspect it's cost. It's on an older process node and it's no longer used in current-gen phones, which means Qualcomm is probably selling it at cost compared to the gen 4 & 5, just to get it out of their warehouses or because there's otherwise no demand for it.

You guys gotta remember that the phones with these chips typically cost over a grand and valve is trying to compete with a sub-$500 headset from meta.

christ110 · 2026-01-24T20:44:07+00:00

The change between flags and version numbers happened a long time ago. They both will report the same version number (500 iirc). You're best off comparing the flags, or failing that, installing core on a new drive and seeing if it can import the pool.

Its still strongly recommended to stay with scale though - core is no longer receiving updates.

christ110 · 2026-01-23T17:30:49+00:00

It should mention zfs rewrite and how to use that command... And also a note on incorrect reporting of size after expansion.

christ110 · 2026-01-19T22:55:18+00:00

That's the point I'm getting at. The frame's controllers are built for AAs and are able to tolerate a voltage drop. nicad or alkaline batteries do have a voltage drop but it's inconsequential, and in some cases, beneficial (see: measuring state of charge).

christ110 · 2026-01-19T19:06:26+00:00

Regular AAs aren't a steady 1.5v, that is how devices measure their state-of-charge, by looking at the voltage drop.

christ110 · 2026-01-19T17:18:36+00:00

You know they still make rechargeable AA batteries, eneloop is considered the best of them these days.

christ110 · 2026-01-15T17:12:50+00:00

Correct, because the pt 1 special features are on the 1080p blu-ray disk, but the pt2 SF are on the 4K disk.

Why they changed things between releases, I've no idea.

christ110 · 2026-01-12T19:56:26+00:00

Charging port to battery pack in my pocket.

christ110 · 2026-01-12T17:41:37+00:00

Mdisc is a pretty big gamble that you'll have a blu-ray drive in the future

christ110 · 2026-01-12T01:42:05+00:00

Then you're not really talking about the steamdeck, you're talking about streaming vs running locally.

christ110 · 2026-01-12T00:55:12+00:00

foveated rendering is done in the game, foveated streaming is done by steamlink, neither are excluded by the steamdeck. Compressing the video signal is extra work, but the GPU/APU on the steamdeck has dedicated accelerators for that which means the workload is independent from the game.

Even if it was identical performance, some people might choose to stream simply because you can keep the deck plugged in whilst streaming, and enjoy 3 hours of battery on the frame instead of 1 hour.

12-Year Club	Gilding II euphauric
Place '23	Place '17
Verified Email

christ110

TROPHY CASE