• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!
  • Fill out your device list and let everyone know which phones you have!    Edit Your Device Inventory

MX Player Custom Codec [AC3,DTS,MLP,TRUEHD, etc..]

Search This thread

Mandrake1er

Member
Mar 5, 2021
33
12
56
Montgeron
The difference between you and me doesn't come from the codec file, but from the fact that I use the free MX Player and you use MX Player Pro (with the same number version 1.36.11). It seems that the free MX Player works with 1.35.0 codec version and MX Player Pro doesn't. What is the out of date message that you get when you try to use 1.35.0 codec version in your parameters ?
 
  • Like
Reactions: Uves and osm0sis

kokoronikui

Member
Feb 13, 2021
34
14
Redmi Note 10 Pro

Attachments

  • IMG_20210618_152622.jpg
    IMG_20210618_152622.jpg
    67.2 KB · Views: 196

Meteormatic

Member
Jun 23, 2018
5
1
Anyone else here using the play store version of Mx player pro 1.36.11 can confirm that the 1.35.0 custom codec is working?
I'm right there with you, i'm using the same version of MX player pro and tried everything to get the 1.35.0 custom codec working, but failed to do so.

- Tried with the "aio" zip
- Tried with the "ARMv7" zip specifically
- Tried removing the .zip file entirely and re-downloading it to different directory

Nothing worked.. :cry:
 

Sid32

Senior Member
Feb 8, 2015
363
203
I'm right there with you, i'm using the same version of MX player pro and tried everything to get the 1.35.0 custom codec working, but failed to do so.

- Tried with the "aio" zip
- Tried with the "ARMv7" zip specifically
- Tried removing the .zip file entirely and re-downloading it to different directory

Nothing worked.. :cry:
Whats the error? What if its unzippped?
 

Meteormatic

Member
Jun 23, 2018
5
1
Whats the error? What if its unzippped?
I don't get an error while adding it.
However, after i add it, I don't have the HW+ option, like i used to have with the codec.
And when i select the HW option, i get some error (can't remember exactly what it was saying and can't check.. im not home at the moment) so i can only use SW. Basically, the behaviour is the same as it is with the default codec.

Didn't have these issues when we were all using the 1.25 version of the codec
 

rsngfrce

Senior Member
May 13, 2012
802
511
NorCal
Apps & Games
There seems to be different versions of the codecs floating around. This is the version of Neon64 (ARM V8) that I am using and is still working with the latest MX Player I have reached (if there isn't an issue with me posting this).
 

Attachments

  • mx_neon64 1.35.0.zip
    5.7 MB · Views: 440

Meteormatic

Member
Jun 23, 2018
5
1
I'm using MiBoxS, therefore i need ARMv7 codec instead. If someone has a working one, please share it 😅
(for MX Player Pro 1.36.11)

Update:
Finally got it working, don't know why i didn't try this in the first place. I just used the actual file.. unzipped, the one specific for Armv7 neon.
Hope someone will find this useful
 
Last edited:

Uves

New member
Jul 21, 2021
2
1
The difference between you and me doesn't come from the codec file, but from the fact that I use the free MX Player and you use MX Player Pro (with the same number version 1.36.11). It seems that the free MX Player works with 1.35.0 codec version and MX Player Pro doesn't. What is the out of date message that you get when you try to use 1.35.0 codec version in your parameters ?
I also had the same problem. You just need to download libffmpeg.mx.so.neon.1.35.0
And rename it this way libffmpeg.mx.so.neon.null
I renamed it in ES files explorer. It's working now. Hope it would work for you too.
 

Attachments

  • Screenshot_20210721-230635.png
    Screenshot_20210721-230635.png
    163.4 KB · Views: 42
  • Like
Reactions: rsngfrce

Top Liked Posts

  • There are no posts matching your filters.
  • 1
    The difference between you and me doesn't come from the codec file, but from the fact that I use the free MX Player and you use MX Player Pro (with the same number version 1.36.11). It seems that the free MX Player works with 1.35.0 codec version and MX Player Pro doesn't. What is the out of date message that you get when you try to use 1.35.0 codec version in your parameters ?
    I also had the same problem. You just need to download libffmpeg.mx.so.neon.1.35.0
    And rename it this way libffmpeg.mx.so.neon.null
    I renamed it in ES files explorer. It's working now. Hope it would work for you too.
  • 1736
    https://github.com/USBhost/MX_FFmpeg is my modified source where i'm building from
    You can download the codecs:
    here ( Google Drive :: All versions )
    here ( GitHub releases )
    Also the XDA download tab is no longer updated as for some reason I cant remove them.

    INSTRUCTIONS
    1. Check which version you need by going to Local Player Settings/Decoder/General
    in the Custom Codec tab it will tell you which one is needed (x86,x86_64,neon,neon64/ARMv8).
    Note: skip step 1 if your using aio (all in one) version
    2. Download the one you need (No need to unzip it)
    3. Go back to Local Player Settings/Decoder/General
    and tap the Custom Codec tab then select the version you downloaded. DONE!
    69
    Frequently Asked Questions (FAQ) :

    What's the difference between MX Player Codec Packs on Google Play and Custom Codec?
    MX Player Codec Pack not only contains ffmpeg library, It contains many other libraries required to work properly. If you download MX Player from Google Play mostly it will contain the required libraries according to your device architecture. You have to install codec packs from Google Play only if MX Player asks to install. Custom codec is just a modified version of the ffmpeg library used in MX Player. It's modified to include support DTS/Dolby(ac3) audio tracks. So, Codec Pack is mandatory if MX Player asks to install it. Custom Codec is optional and It's required only if you want to play the videos with DTS & Dolby (AC3) audio tacks


    Why Custom Codec is not updated even though MX Player is updated?
    In Many occasions MX Player may updated without any changes to ffmpeg library. So, Custom Codec will also remain same. The custom codec version required will be directly forced by the player itself. So no need to worry about it. If it's not compatible MX Player will not load at all.


    How do I know that my Custom Codec is outdated & needs an update?
    Whenever MX Player is updated, It will check the custom codec version loaded. If it's outdated it will show a error message that shows "Custom Codec is out of date. Replace it with the new version". Otherwise there is no need to check this thread for the new Custom Codecs.
    55
    Custom codecs for 1.9.8
    36
    Update 1.13.0 is up!!!


    1.13.0 ARMv8 codec is needed here as well, thank you !

    Please, it any chance to get ARMv7 Neon codec for version 1.13 mx player? I have sony TV and its problem with EAC3 :-/ Need codec for this version.

    It's up on Google Drive now!!! :angel: neon64 is our ARM64
    However I can't seem to upload them to XDA... I guess Brave does not like flash lol oh well.
    Edit: Its up on XDA as well now.