Futureweb

Open Source

The AAC pin is a crate choice

A house note presents rusty_aac as a pure-Rust AAC path beside fdk-aac. The C repository and Android tree remain. A pin is the version this house chose.

The short version

No. The house note is one source for a Rust path. mstorsjo/fdk-aac and Android's external AAC tree still exist. This page does not rerun the note and does not paste its commands.

The pin

The house learn note at the address in the sources presents rusty_aac as a pure-Rust path for AAC, set next to the fdk-aac C library and used inside the house ffmpeg work. This page takes that note as one source. It does not paste the note, and it does not repeat the note's commands. The C library's own repository, mstorsjo/fdk-aac, is a second document: the code the note is an alternative to. Android's external AAC tree is a third public copy of an AAC implementation that ships in a large operating system. A crate version chosen in one project does not edit those trees.The house AAC note.

What a pin decides

A pin decides which crate version a build will fetch. It does not decide that the C library lost a benchmark, and it does not decide that every AAC product on earth has switched. The Vorbis crate was filed on this point: the Rust crate is not the Xiph project. The h264 pin was filed the same way against libx264. The ffmpeg pin was the house project that these codecs sit inside, and that pin is not the ffmpeg.org release. rusty_aac belongs in that series. The series is about not promoting a dependency line into a contest result.The Vorbis crate.

The C library remains the C library

Anyone who needs the bitstream behavior of fdk-aac still has the C repository and the license that repository carries. The Android tree shows the same family of code in a place millions of devices already build. Those facts are independent of whether a Rust port can decode or encode a given profile. This page does not claim a profile list the note would claim, because pasting that list would be rewriting the note. A reader who wants the profile list should open the note and the C repository, not a paraphrase.The h264 pin.

The house link, once

The note is the mechanism that answers the dependency, so it is linked once in this section's sibling above, and nowhere else. A second link to the same host would break the house rule. The answer at the top of the page has no URL. The xml pin was a similar boundary with libxml2: the crate is a choice, the upstream project continues. The alloc pin was a memory crate, not a speed test. Both are on this desk so a reader can see the pattern without this page becoming a catalog of commands.The xml pin.

ffmpeg is the neighboring pin

The house ffmpeg pin was filed as the project that binds several of these codecs. Pointing at it here says rusty_aac is discussed as part of that work, not as a standalone product launch with customers and a price. There is no customer list in the note that this page will invent. There is no performance table in this brief. JetBrains's terminal post, filed today, is a vendor choosing libghostty. This is a house choosing a crate. The shape is similar. The publisher is not.The ffmpeg pin.

Workload conformance is the other open-source filing

The Kubernetes working group announced today is a charter with no test binary yet. The AAC note is a codec path a repository can already name. Both are open-source desk items because both are about a community artifact rather than a company's outage. They do not share code. systemd's Rust boundary was about which programs a project would rewrite. A codec port is one program family, not a init-system policy.Workload conformance.

Who the note is for

The note is for a reader deciding whether a Rust AAC path exists beside the C library, inside the house ffmpeg work. It is not a procurement document for a phone maker, and it is not a security advisory. Android's tree is mentioned so the C implementation has a second public home, not so this page can claim the phone changed. Asked directly, What is the house note's claim? The note's address presents rusty_aac as a pure-Rust alternative path for AAC work that the fdk-aac C library does. This page does not paste the note.

What this page will not paste

Build flags, profile matrices, and any command the note uses to prove a decode are left in the note. The alloc brief already carries the rule that a house page does not become a second copy of a how-to. This one follows it. A reader who wants to build the crate has the repository the note names. A reader who wants fdk-aac has the C repository in the sources. Asked directly, Where does the C library live? The public repository is mstorsjo/fdk-aac. Android also carries an AAC implementation in its external tree. Neither repository is the Rust crate.The alloc pin.

The record

The record is the house note for the Rust-path claim, the mstorsjo repository for the C library, and Android's external tree for a second public AAC implementation. The pin does not retire fdk-aac. The pin does not rank it. The commands stay in the note. The short answer this page will stand on is this: No. The house note is one source for a Rust path. mstorsjo/fdk-aac and Android's external AAC tree still exist. This page does not rerun the note and does not paste its commands.

Sources

The reports this brief is filing. Futureweb did not republish them.

  1. House note
  2. fdk-aac
  3. Android AAC

Questions

What is the house note's claim?

The note's address presents rusty_aac as a pure-Rust alternative path for AAC work that the fdk-aac C library does. This page does not paste the note.

Where does the C library live?

The public repository is mstorsjo/fdk-aac. Android also carries an AAC implementation in its external tree. Neither repository is the Rust crate.

Does a crate pin close Fraunhofer's encoder?

No. A pin records a version a project chose. Fraunhofer's codec and the C repository are unchanged by a Rust crate's version line.

Is this a speed ranking against fdk-aac?

No ranking is filed here. The Vorbis pin was filed the same way: a crate is not the Xiph library, and a pin is not a bake-off.

Where does the house link sit?

Once, in the body, on the note that states the mechanism. It is not in the answer, and it is not a second link to the same host.