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

[Mandrake1er]

@x2k13 : It can depend also on the device.​

@kokoronikui : What is the 'out of date' message that you get ?​

 

[kokoronikui]

@x2k13 : It can depend also on the device.​

@kokoronikui : What is the 'out of date' message that you get ?​

Getting this message when I try to load it

 

[Mandrake1er]

Maybe you could try to rename your codec file replacing '1.35.0' by 'null'.

 

[rsngfrce]

Getting this message when I try to load it

I am using a pro version above 1.37 and have no problem with the 1.35 codec. Are you sure you are properly loading the neon64 version?

 

[dhruvdave]

I am using 1.38.1 and cutom codec is working properly.

 

[kokoronikui]

Maybe you could try to rename your codec file replacing '1.35.0' by 'null'.

How should I rename it?

libffmpeg.mx.so.neon64.null ?

 

[Mandrake1er]

How should I rename it?

libffmpeg.mx.so.neon64.null ?

Yes, give it a try.

 

[kokoronikui]

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?

 

[Sid32]

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?

Mine are working.

 

[ImFilippo]

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?

Working too.

 

[Mandrake1er]

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?

Did you try to uninstall, reboot and reinstall ?

 

[Sid32]

Did you try to uninstall, reboot and reinstall ?

Or deleting the codec, well moving them somewhere else abd downloading them again?

 

[Meteormatic]

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..

 

[Sid32]

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..

Whats the error? What if its unzippped?

 

[Meteormatic]

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]

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).

 

[Meteormatic]

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

 

[Uves]

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.

 

[Mandrake1er]

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.

Good ! It's what I proposed to kokorunikui.
Pleased to know that it can work.

 

[Uves]

Good ! It's what I proposed to kokorunikui.
Pleased to know that it can work.

Yes