![](/static/66c60d9f/assets/icons/icon-96x96.png)
![](https://slrpnk.net/pictrs/image/d9a15e34-516b-4f18-a4c7-171aa9dc1e98.webp)
It’s missing on purpose. There is not enough room for grains.
It’s missing on purpose. There is not enough room for grains.
Does anyone know what the release schedule is for 0.17? It has some features I am interested in.
If it is just “when it is ready” that is fine, I’m just wondering if there is a plan or not.
Ahh yes, let’s introduce floating point rounding errors for one half. Sounds fun.
I’m sure it’s going to get right on that.
Side note. Don’t use hardware acceleration with TDARR. You will get much better encodes with software encoding, which is great for archival and saving storage.
Use hardware acceleration with Jellyfin for transcoding code on the fly for a client that needs it.
If you know what your client specs are, you can use TDARR to reencode everything to what they need and then you won’t have to transcode anything with Jellyfin.
Oscar has a heap of apples.
And the fax machine was invented in 1843. So do with that what you want.
I went through there last summer. It was a total tourist trap.
Which is on an indian reservation, and requires an entrance fee to go look at it.
You are correct that if you are on thee moon and have a cs-133 atom with you is second will take that many transitions. And if you do the same thing on Earth, a second will take the same number of transitions.
But things get weird when you are on earth and observe a cs-133 atom that is on the moon. Because you are in different reference frames, you are traveling at different speeds and are in different gravity wells time is moving at different rates. This means that a cs atom locally will transition a different number of times in a second from your point of view on Earth vs one you are observing on the moon.
And it would all be reversed if you were on the Moon observing a clock back on the Earth.
They already have to account for this with GPS satellites. They all have atomic clocks on them but they don’t run at the same speed as clocks that are on the ground. The satellites are moving at a great speed and are further from the center of the earth than us, so the software that calculates the distance from your phone to the satellite have to use Einstein’s equations to account for the change in the rate of time.
Relativity is weird.
Except the length of a second is different on the moon because of relativity. So even utc is wrong.
This is the big thing. All doing silly things like obscene QR codes does is add training data for future ai to remove them.
What do people think about Rocky Linux for servers?
This is why every calculator should be a RPN calculator.
It should let you choose what location should be sent. Flood their data with junk.
Honestly this just sounds like periodically refactoring everything to remove cruft can be a good thing. Also, it helps you understand how the existing code works if you change it and not break everything.
How does this compare to the AndroidTV client? Are they pretty much the same feature wise?
I personally would not use it for anything that is being saved on your drive. Using cpu encoder is slower but I just let it run over night or whatever and it will be done later.
Save GPU encoding for when you need it smaller right now like when you are transcoding on the fly.
I generally think that for storage/archiving you should use CPU encoding and only use GPU for things like transcoding where real-time results are crucial.
GPU encoding is a lot worse quality than CPU, and you can’t change the settings to what you want. Better to just accept the extra time requirement to get a better result.
Alpha Centauri was awesome, but so were a lot of the other games. Colonization was a lot of fun. Call to Power is the civ game I want a real sequel to. Going way into the future tech was a lot of fun, and being able to build cities at the bottom of the ocean.
Of course, I think the whole franchise has gone downhill since Civ IV, so take my opinion as you will.