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

[levcekslo]

That does not work for everyone.

Work For me.

 

[AntiSpamXChecker]

Work For me.

What appears to work for the moment is stopping the settings for automatic apps updates from the Play Store on the Android TV and then install and use v1.26.7 with the 1.25 codec - which worked OK for me. I don't understand why the hell this app was updated if it botched the subtitle support for embedded subtitles in MKV files.

 

[JFK1975]

Thx for your work. I downloaded update to pro version these days which is 3.2.8. unfortunately Codec 1.3.2 won't work with.

 

[x2k13]

Thx for your work. I downloaded update to pro version these days which is 3.2.8. unfortunately Codec 1.3.2 won't work with.

I have exactly the same version, with working codec 1.32.0, just armv7. I used the AIO .zip.

 

[Mandrake1er]

Just force MX Player to use 1.25.0 codec version by renaming the files in aio zipped file '1.25.0' by '1.32.0' . You'll get the embedded subtitles.
The problem comes from the 1.32.0 codec, not from the app.

To be clear :
- Download 1.25.0 aio zipped codec
- Rename the files '1.25.0' by '1.32.0' inside the zipped file
- Use this codec with the last version of MX Player

 

[AntiSpamXChecker]

Just force MX Player to use 1.25.0 codec version by renaming the files in aio zipped file '1.25.0' by '1.32.0' . You'll get the embedded subtitles.
The problem comes from the 1.32.0 codec, not from the app.

To be clear :
- Download 1.25.0 aio zipped codec
- Rename the files '1.25.0' by '1.32.0' inside the zipped file
- Use this codec with the last version of MX Player

This DOES NOT work for everyone, I have a Sony 4K Android TV and if I install the 1.32 version of the app, it DOES NOT ACCEPT version 1.25 of the codec (as it is, renamed in archives or as a renamed direct file). It keeps asking for the new version - and the new version does not work well with the subtitles. Period. The codec compiler needs to work better on the ARM V 7 NEON version of this codec or else we get stuck with this irritating issue.

 

[Mandrake1er]

I'm not sure that you tried what I recommend :
- use the 1.25 aio zipped version of the codec (the name of the file you have to download is mx_aio.zip), not the other ones (mx_neon.zip, mx_neon64.zip, mx_x86.zip or mx_x86_64.zip)
- inside this file (mx_aio.zip), you have different files with 'xxx.1.25.0' names (because it's the 1.25.0 version of the codec)
- rename these files by 'xxx.1.32.0' (with that, MX player will read it as the 1.32.0 version of the codec)
- use this file (mx_aio.zip with the renamed files inside) with MX player.

What does mean for you that the app is 'asking for the new version' ?

 

[AntiSpamXChecker]

I'm not sure that you tried what I recommend :

Clearly, it's a waste of time for me to explain again - I have used the 1.2.5 aio zip and file - renamed the files inside it to 1.32 and the player DID NOT accept the codec files - it kept asking for the new version of the codec - the app figured out the files have been merely renamed and not compiled as a new version - which can only mean that there is also an internal code in the file that specifies the codec version - it's not just in the name of the file. I am not a n00b - in my device, the player just refuses to work with or install the old codec on the new version 1.32.8 of the player.
It's not your fault, but I wish the codec compiler did a better job about all the files in the archive.

 

[Mandrake1er]

If it can help : I renamed the files inside the zipped file using Winrar, and used directly the zipped file as codec. I'm quite sure that is what you did.
I understand that the 1.34.5 version of the free player (mine) and the 1.32.8 version of the PRO player (I guess it's yours) don't check similarly the codec version. It could also depend on the devices.

 

[TotallyAnxious]

Clearly, it's a waste of time for me to explain again - I have used the 1.2.5 aio zip and file - renamed the files inside it to 1.32 and the player DID NOT accept the codec files - it kept asking for the new version of the codec - the app figured out the files have been merely renamed and not compiled as a new version - which can only mean that there is also an internal code in the file that specifies the codec version - it's not just in the name of the file. I am not a n00b - in my device, the player just refuses to work with or install the old codec on the new version 1.32.8 of the player.
It's not your fault, but I wish the codec compiler did a better job about all the files in the archive.

Works fine here.

 

[Mandrake1er]

Works fine here.

Which version of the player do you use, please ?

 

[TotallyAnxious]

Which version of the player do you use, please ?

 

[Mandrake1er]

Thanks.
Did you rename the file in the mx_neon64(1.25.0).zip file ('1.25.0' by '1.32.0') ?

 

[TotallyAnxious]

Thanks.
Did you rename the file in the mx_neon64(1.25.0).zip file ('1.25.0' by '1.32.0') ?

 

[Mandrake1er]

Thanks.
I assume that you can see embedded subtitles on screen.
Then this solution works also for version 1.32.8 of MX Player Pro on your device.

 

[dhruvdave]

Mx player updated to 1.35.0 and custom codec is out of date.

 

[skyhirules]

I really don't understand why should all the users in this topic struggle to find a way to use the custom codec, instead of a simple update from the developer to make it functional!?
Hello!!! Is the OP listening at all???

 

[Mandrake1er]

You could probably take benefit from looking at the release dates on GitHub ...

 

[rsngfrce]

Considering the fact that the codec is an unofficial workaround for an issue that was imposed on MX Player by the Play Store, I don't think it is fair to place too many demands on the devs for issues that arise with it. The OP doesn't even mention the purpose of it, but answers many questions.

 

[OFShuvo]

I need 1.35.0 codec file...