You’ll be pleasantly surprised. Updates in the coming weeks.
> In the coming weeks, we will relicense all of our source-available tools, including Tart, Vetu and Orchard under a more permissive license. We have also stopped charging licensing fees for them.
A carefully timed sequence will guide Orion through the final stages of descent:
7:33 p.m.: Orion’s crew module will separate from the service module, exposing its heat shield for the spacecraft’s return through Earth’s atmosphere, where it will encounter temperatures of about 3,000 degrees Fahrenheit.
7:37 p.m.: Following separation, Orion will perform an 18 second crew module raise burn beginning to set the proper entry angle and align the heat shield for atmospheric interface.
7:53 p.m.: When Orion reaches 400,000 feet above Earth’s surface while traveling nearly 35 times the speed of sound. The crew is expected to experience up to 3.9 Gs in the planned entry profile. This moment marks the spacecraft’s first contact with the upper atmosphere and the start of a planned six-minute communications blackout as plasma builds around the capsule.
8:03 p.m.: Around 22,000 feet in altitude, the drogue parachutes will deploy, slowing and stabilizing the capsule as Orion nears splashdown.
8:04 p.m.: At around 6,000 feet, the drogues will release, and the three main parachutes will deploy, reducing Orion’s speed to less than 136 mph.
8:07 p.m.: Slowing to 20 mph, Orion will splash down in the Pacific Ocean off the coast of San Diego, completing the Artemis II crew’s return to Earth and a 694,481-mile journey.
From there, teams from NASA and the U.S. military will extract the crew from Orion and fly them via helicopter to the USS John P. Murtha.
Within two hours after splashdown, the crew will be extracted from Orion and flown to the USS Murtha. Recovery teams will retrieve the crew, assist them onto an inflatable raft, and then use helicopters to deliver them to the ship. Once aboard, the astronauts will undergo post‑mission medical evaluations before returning to shore where awaiting aircraft will take them to NASA’s Johnson Space Center in Houston.
YouTube live stream (begins at 6:30 p.m. US/Eastern):
The README mentions Plex and Emby, but those don't support m3u, so you need to use a proxy which makes an m3u source appear like a local tuner such as:
There is also threadfin, which I found a bit more friendly than XTeVe.
Above system works pretty well but had trouble with encode/decode speed somewhere. Tried with N100 cpu and still had the same result...probably user error somewhere but none of the options seemed to work. No issues with UHF so kept using that.
As someone who also operates fleets of Macs, for years now, there is no possible way this bug predates macOS 26. If the bug description is correct, it must be a new one.
Sure, but less grain is often worth it. There's a reason why fast lenses exist. The high quality lens being used here can probably still resolve 20 MP adequately even wide open.
I had that lens. It’s soft as fuck around the edges open.
Peak sharpness is about f/8. They should have had the D5 on aperture priority auto iso, pushed the exposure comp either way and then just fired at f/8 and let the camera make the decisions.
But they are astronauts not photographers :)
The modern Z lenses are far better and sharper open but much larger generally.
In 1976, 14-year-old Chris Espinosa rode a moped to his job demonstrating computers made in Steve Jobs’s childhood home. The company has changed a bit since then.
HN's submission form removes the query string with the share code:
I think it should work at the user config level too:
> If project-, user-, and system-level configuration files are found, the settings will be merged, with project-level configuration taking precedence over the user-level configuration, and user-level configuration taking precedence over the system-level configuration.
https://github.com/cirruslabs/tart/blob/main/LICENSE
https://tart.run/licensing/
reply