CC-BY
this specification document is based on the
EAD stands for Encoded Archival Description, and is a non-proprietary de facto standard for the encoding of finding aids for use in a networked (online) environment. Finding aids are inventories, indexes, or guides that are created by archival and manuscript repositories to provide information about specific collections. While the finding aids may vary somewhat in style, their common purpose is to provide detailed description of the content and intellectual organization of collections of archival materials. EAD allows the standardization of collection information in finding aids within and across repositories.
The specification of EAD with TEI ODD is a part of a real strategy of defining specific customisation of EAD that could be used at various stages of the process of integrating heterogeneous sources.
This methodology is based on the specification and customisation method inspired from the long lasting experience of the Text Encoding Initiative (TEI) community. In the TEI framework, one has the possibility of model specific subset or extensions of the TEI guidelines while maintaining both the technical (XML schemas) and editorial (documentation) content within a single framework.
This work has lead us quite far in anticipating that the method we have developed may be of a wider interest within similar environments, but also, as we imagine it, for the future maintenance of the EAD standard. Finally this work can be seen as part of the wider endeavour of European research infrastructures in the humanities such as CLARIN and DARIAH to provide support for researchers to integrate the use of standards in their scholarly practices. This is the reason why the general workflow studied here has been introduced as a use case in the umbrella infrastructure project Parthenos which aims, among other things, at disseminating information and resources about methodological and technical standards in the humanities.
We used ODD to encode completely the EAD standard, as well as the guidelines provided by the Library of Congress.
The EAD ODD is a XML-TEI document made up of three main parts. The first one is,
like any other TEI document, the
For MX Player, this custom codec pack restores playback capability for unsupported audio formats like —formats commonly found in high-definition video files. Without this pack, many videos will play silently or show an error message.
Mx Player is a media player app that allows users to play a wide range of video and audio files on their Android devices. Developed by J2 Interactive, Mx Player has become one of the most popular media players on the market, with millions of downloads worldwide.
: MX Player was the first Android player to support multicore decoding, which can increase performance by up to on dual-core devices compared to single-core decoding. Processor Optimization
Community-developed custom codec packs built using the FFmpeg library. These packs can be downloaded manually and installed within MX Player, effectively restoring support for all major audio formats. Mx Player 1.13.0 Armv7 Neon Codec
The 1.13.0 codec pack brings several optimizations to your media player:
MX Player 1.13.0 with the is a time-tested combination for users running older Android hardware. It provides excellent performance, hardware decoding, and format coverage without the bloat of modern app versions. While no longer supported by the developer, it remains a favorite among retro-enthusiasts and offline media consumers.
This is where the Custom Codec feature comes in. A custom codec is a package that adds these missing audio decoders back into MX Player. It's not a standalone app; it works with the MX Player app itself to add licensed capabilities. The specific variant needed is , tailored for the 32-bit NEON-enabled processor. For MX Player, this custom codec pack restores
Enable “Install from unknown sources” in your Android settings (varies by device and Android version).
With this codec, users can avoid the common "Audio format not supported" or "Video freezes while audio plays" errors. It safely expands playback infrastructure across dense file types:
Even with the correct setup, you might encounter problems: Developed by J2 Interactive, Mx Player has become
Restores full decoding for AC3, DTS, MLP, and EAC3 audio tracks.
Understanding the MX Player 1.13.0 ARMv7 NEON Codec: Installation and Optimization Guide
: It enables the player to decode a wide variety of formats (e.g., .mkv, .avi, .flv, .mp4) that might otherwise struggle on standard decoders. Advanced Audio Support
How to Fix EAC3 Audio Not Supported in MX Player - Free-Codecs.com
If MX Player does not automatically prompt you to use the codec after downloading it, you can install it manually: : Obtain the correct file (typically mx_neon.zip or a version-specific file). Open Settings : Launch MX Player and go to Settings > Decoder Locate Custom Codec : Scroll to the bottom and tap Custom codec Select File : Navigate to your folder and select the downloaded