yashsingh1/xdaforums huggingface dataset:
[MX Player] ThomasOMalley77:
It's not a problem. It's supposed to be this way. MX Player doesn't have the rights to distribute the codecs. Just be happy that you get a free awesome player, that can handle almost every format out there.

The source code will be available soon enough. Just be patient.
[MX Player] BigMani:
As I notices, I had issues with the codec. In the meantime, it is working. But I don't know why it is working now and why it did not work before.

Maybe I had the same issue as KEYofR has. Here what I noticed:

I found various versions of the libffmpeg.mx.so file:

- /data/data/com.mxtech.videoplayer.pro/lib/ --> which is 6.98 mb, it is the builtin codec shipped with 1.7.20

- /data/data/com.mxtech.ffmpeg.v7_neon/lib --> These are the codecs I've additional installed via google play, it is the same 6.98 mb file

- I had installed the custom codecs for 1.7.17 from this thread with a previous version (it was working then). the original file (7.10 mb) was located on the sdcard, I've deleted it. I did not find this version somewhere else on /data

- I tried to select the codec from this thread for 1.7.20 (7.90 mb). Now I have this file in /data/data/com.mxtech.videoplayer.pro/files/

after selecting the custom codec (of course the .mx.so file, not the .zip) I was asking for restart the player and then I always got the message that the codec was outdated. but looking into the /files folder (thanks KEYofR for this hint) I was not finding the file there.

Once I switched to ES file explorer just after selecting the codec but befor press OK on the question to restart the player. and now I found the codec in the /files folder. and after the restart, it was working fine.

So I assume there is something strage with the MX player pro itself when updating the codec or so. very strange. but now it is working.
[MX Player] Thirumalai.K:
Be gentle. It's not my professional. You are not forced to use my codecs.

If you are not willing to update the codecs, it's up to you.

Have you noticed the change log?

The developer of the MX Player is not a mad to write that the codec v1.7.19 is not compatible with player v1.7.20.

If you still not believe in me, just load the old v1.7.19 codec in mx player 1.7.20. By default MX will try to play in HW mode. So, there won't be any problems. For HW there is no need of codec.

Now Just play a avi (xvid) file in SW mode. Video will be blank. In x264 files, the playback is very laggy in SW.

Now close the player and replace the libffmpeg.mx.so for v1.7.20. If you open the player it will ask to restart the player to load new codec. Do the same and play the videos in SW mode. Now the playback will be smooth.
[MX Player] KEYofR:
I AM using 1.7.20

How many times do I have to say that?

Wow.

Ok now that last part was useful.

So that is how I can prove the actual functionality of the libffmpeg.mx.so file?

Play any xvid file?

All the videos I was using happened to be playable in hw and hw+ modes, so those files were not even invoking the external codec?

That would explain most of my observations.

It wouldn't explain why the sky diver video didn't work yesterday, but, that is an on-line video not locally saved. It's theoretically possible NBC News changed the video on their server since original.

I will find some other videos to test and nail down the behavior. It's looking now that maybe the app is just inconsistent about when it reports an error. If the video did not need the codec, then why did it report an error? If the app always checks the version and always reports if there is discrepency, then why isn't it doing so today? Either the app is inconsistent about doing the check, or the video I was testing with changed over night.. and since it's an on-line video, that is actually possible. So I'll look for others.

Thanks for the clues.
[MX Player] Thirumalai.K:
Thanks for the info. Can you give the details of your mobile & android version.?

In my mobile I am not facing any problem in loading the custom codec.

If you can reproduce the problem, just clear data of mx player as well as codec pack if installed. Then try to load the same. Once mx had some issues. But, fixed by the developer after my bug report. It seems similar problem reappears.
[MX Player] Thirumalai.K:
Again you have misunderstood.

You have told that the player is working even after loading the old codec. For that only I have justified.
[MX Player] KEYofR:
We all understand that.

Please move forward from thinking we must be idiots.
[MX Player] Thirumalai.K:
I never thought like that. If you are thinking so, I am not responsible.

I have even received the reports from those who are tried to load the zip file. I can't assume the capabilities of the person who is reporting over here.

You have told that you don't have problems with old codecs. For that only I have explained from my side. If you are thinking that I am not capable, then just report your problem in official forum rather than posting here.
[MX Player] KEYofR:
I have provided more than enough details to show exactly what versions of what files I am using them and exactly how I am using them, yet you keep repeating that I need to get 1.7.20 because 1.7.19 is incompatible. That possibility is obvious so that is why I dispensed with it i the very first line of my very first post. So what else am I supposed to think?

When you mentioned how to force the external codec to be used by playing specific types of video file, THAT was the first time you said something that actually addressed the observations and questions being presented. Thank you for that at least.
[MX Player] BigMani:
Hi

yes I was able to reproduce the problem now.

I'm using an unbranded Galaxy S4 LTE (I9505) with Android 4.2.2, build I9505XXUBMGA (the last firmware I found here without the new rubbish bootloader [knox]).

The situation is that I'm using QuickPic as app for navigating through images and videos.

I've uninstalled the MX player pro and reinstalled from scratch, latest version via google play.

I launched QuickPic and selected a video where I choose MX player as the videoplayer.

So it was playing the video, but without custom codec and so no audio (DTS).

Now I went to the settings and selected the custom codec. it asked me to restart the player, what I did. After the restart it was giving me a message that the codec is outdated and I should download the lastest. so it was playing the video with the builtin codec (no audio).

So I can reselect the codec (it is not showing me the codec beeing used where I can select it) and repeat the game a few times.

But now comes to the point:

this problem happens only when I use the MX player launched via other apps directly to play a video and then select the custom codec during playback.

I launched the MX player itself and it was showing me a dialog "what's new in 1.7.20". then I selected the custom codec, confirmed for a restart and then I was able to play the video with DTS. And since then, launching videos out of QuickPic is also working fine.

It seems that there is a bug in MX player that it is not possible to set a custom codec until the player itself was launched and the "what's new" dialog was shown. this happens only for people (like me) that are using the player just for video playback but not for navigating.
[MX Player] Thirumalai.K:
Thanks mate. I just wanted the way to reproduce. Finally you have found the root cause & way to reproduce. This is what we expect from you guys. The way to reproduce the error is much important.

But after doing the same, I have received a difference error. Look at the screenshot. Are you getting the same error?

If you are getting some other errors, Is it possible to post the screenshot?
[MX Player] HR7:
Hey guys, my device is Xperia X10 and i'm having trouble to play my downloaded movie from YIFY (if you know) properly without lag. I tried to install the codec to see if there's any improvement on the video but still the same.. Help?
[MX Player] Thirumalai.K:
As I said in the first post, It is compiled from the same source from the developer. I have added only DTS playback support.

So, It will not improve your playback performance.

Not only MX player, Any software player can't do anything with your hardware capability.
[MX Player] BigMani:
Hi

I'm getting exactly the same error message popup "Unsupported device or component files corrupted...". And additional a toast message: "Custom codec is out of date. Please replace it with the new version".

I was thinking that the toast message is more precise so I just quoted this one, sorry for that.

PS: the screenshot is not from my SGS4, it is from my Huawei MediaPad 10 FHD tablet (Android 4.1.2) which is having exactly the same issue and where the same solution is fixing it (just start the player once with the mainactivity).
[MX Player] Thirumalai.K:
[MENTION=2655912]KEYofR[/MENTION] & [MENTION=2088245]BigMani[/MENTION]

There is another popout (not toast) with the msg Codec is out of date".

It will appear when you have the different version of player & codec pack (not custom codec) in the case of non neon devices.

In neon devices, it will appear when you have different version of player (without codec) & neon codec pack.

This made the confusion in your issues. I have never expected that you could have launched from external application before loading the codec.

Look at the screenshot:
[MX Player] Ettepetje:
Thanks ktsamy for the wonderful work you do on these codecs!
[MX Player] hbfreekwan:
thanks, works perfect on my nexus 5!
[MX Player] Picao:
Thanks, the update works on Nexus 7 (2013) with Android 4.4
[MX Player] itasoulas:
confirmed :good:
[MX Player] Jaime360:
Hi, I've been a user of your pro player for a while but now it doesn't work on my new Asus tf701t with Android version 4.3. Please, could you solve this problem?

Thank you very much!
[MX Player] bfettd:
Nexus 10 issues on KitKat?

So I updated to KitKat and suddenly lost DTS capability. Tried re-installing the app and the codec to no avail. Anyone else have this issue? Better still - anyone know the solution?

---------- Post added at 05:27 PM ---------- Previous post was at 05:21 PM ----------

Well this is embarrassing - but the solution was simple: restart! HAHA. Thanks again, KTSamy, you rock!
[MX Player] ThomasOMalley77:
The source code has been posted... :)

Releases · MXVideoPlayer/MX-FFmpeg

Contribute to MXVideoPlayer/MX-FFmpeg development by creating an account on GitHub.

github.com
[MX Player] mom4751:
Now i understand.

Developers compile the latest version of codec only for internal use (develop) and the community cannot be aware that the coming release of MX player will require a new codec version.

So, people who usually keep the codec updated (like USBhost on github) realize this matter only when the new MX version is already out and they display the outdated custom codec message.

However you are right, the player is good, so i have just bought the pro version.
[MX Player] USBhost:
Release 1.49.0 · USBhost/MX_FFmpeg

-| FFMPEG updated as to 2022-08-16

github.com

come one come all to test it if it works.
[MX Player] ThomasOMalley77:
Awesome. Thanks. Will test it later... :)
[MX Player] yaro666:
1.49 works great with latest mxplayer
[MX Player] IronTechmonkey:
Likewise, 1.49 looking good upon quick review. Detected in download folder (which I decline) then manually installed from elsewhere, runs OK in free MX Player 1.49.5 on stock Moto Android 10 and 11.
[MX Player] Venipa:
Doesn't work on mx player pro 1.46.10
[MX Player] Mandrake1er:
Did you try the 2 versions of 1.49.0 codecs releases ?

- https://github.com/USBhost/MX_FFmpeg/releases

- https://github.com/iDNA420/MX-FFmpeg/releases
[MX Player] fred_gaou:
Feature request: add OneDrive folder to read videos from it as if they were locals.
[MX Player] nmdung9x:
New version 1.49.0: https://drive.google.com/file/d/1XdTyc_-JHHFR7Ymy-FarwJzS95WadLyL/view?usp=sharing

Source: https://github.com/MXVideoPlayer/MX-FFmpeg
[MX Player] AntiSpamXChecker:
I wonder if there could be a filter added to these codecs that would tone-map correctly Dolby Vision videos so that even smartphones with "allegedly no support for that could be used to watch such content without issues.
[MX Player] Muhammad0222:
Now mx player pro 1.51 is here and need new codec
[MX Player] krakout:
I'm so, so tired of this. I have disabled updating because of this need...
[MX Player] Cye3s:
mx player pro says my codec too old...
[MX Player] osm0sis:
Paging @USBhost. 😉
[MX Player] skyhirules:
1.49.0 codec works fine for my Pro 1.51.7.
[MX Player] USBhost:
Got it, will look into it tonight.
[MX Player] Sid32:
Like people don't look for updated codecs. Plus Pro gets updated a while after free, so there are usual new codecs avail for pro.

https://github.com/USBhost/MX_FFmpeg/releases
[MX Player] krakout:
It's the "usual" that keeps me from going Pro unfortunately...
[MX Player] Sid32:
Pro is worth the money. Use VLC as a backup player for when Codecs aren't updated.
[MX Player] Andydotlee:
Same here, I updated from 1.44 today to 1.49 and I don’t get the “too old”message anymore. Thanks for the tip
[MX Player] bjorne900:
The same for me. Upgraded from 1.44.0 codec to 1.49.0 codec.
[MX Player] USBhost:
Man you guys made me think there was a codec update not just pro finally using that mx player free uses. baka
[MX Player] yiyi_26:
How I download it?
[MX Player] Sid32:
Page 1, post 1. Grab the AIO one

Releases · USBhost/MX_FFmpeg

MX Player custom codec / https://mx.j2inter.com/download https://github.com/MXVideoPlayer/MX-FFmpeg / Source not mine - USBhost/MX_FFmpeg

github.com
[MX Player] Beeker-gash:
I can’t get the 1.49 version to appear in m player pro. I’d the reason I have to keep updating the codec due to mxplayer updating itself? Seen a few people on GitHub with issues
[MX Player] Mandrake1er:
Be sure that MX Player Pro has access to the directory where your codec file is located.
[MX Player] Beeker-gash:
thanks will try this tonight. i can see the folder but nothing in it. couldnt see the 1.44 codec either thinking back about it
[MX Player] Mandrake1er:
I can remember that there's a problem with Android 11 (not sure of the version number). You have to give access throught the application and also in the settings of the system.
[MX Player] Sid32:
Put the file in the Downloads or Movie folder. And make sure you are using the right version. AIO if you don't know.
[MX Player] redhusker2016:
I have a Nvidia Shield Pro and for some odd reason when I download the zip file it downloads as a bin file and doesn't even show up. I use the downloader app to install. Any other way I can do it?
[MX Player] Sid32:
Download in on a pc or phone and transfer it across.
[MX Player] soclophe:
confirmed 11/21/2022. MXplayer pro does not have ac3 file reading codec
[MX Player] Wacky2bakky:
Quick question, what's latest MX player pro available that currently works with the 1.49.0 codec?
[MX Player] IronTechmonkey:
This sometimes happens with certain OS and browser combinations. You could probably just rename the file but it's probably more comfortable to download a properly named file by another method as suggested.
[MX Player] IronTechmonkey:
As indicated by posts further up this page and on the previous page, in most cases that version is working OK with the newest version of MX Pro. For me on Android 10 and 11, MX Pro version 1.51.8 (which seems to be the latest) is working with 1.49.0 of the codec.

BTW, I could not figure out or find in the threads away to verify which Kodak version is installed so for this test I just reinstalled what I knew to be 1.49. Is there a way to verify which codec is installed from within the player.
[MX Player] Mandrake1er:
The about menu gives you the version of MX player with the installed codecs if there is one.
[MX Player] IronTechmonkey:
D'oh! That was the first thing I checked but somehow I missed it even though it's right there at the top. Thanks.
[MX Player] jmz768:
Can somebody please explain how to update my custom codec for MX Player Pro on my Chromecast?

It tells me to use ARMv7 NEON type custom codec but I see no file with that name available. So after guessing at which file I need and obviously choosing the wrong one, I'm told I need version 1.49.0 ARMv7 NEON codec, but again, no such file with that name exists for download. Which specific file do I want?

Also, if someone could post a step by step guide to getting the right file on my Chromecast, it would be appreciated.

Thanks
[MX Player] Mandrake1er:
Use mx_aio.zip file (AIO means All (codecs) In One file).
[MX Player] Mandrake1er:
I think that ARMv7 NEON is mx_neon.zip file and ARMv8 NEON is mx_neon64.zip file.
[MX Player] kedaitinh12:
I use MXPlayer in android TV but can use your custom codec. In my setting custom codec it said: "use arm7 neon" but when i put custom codec in download folder and app don't detect it. I use latest mx player free version ver
[MX Player] kedaitinh12:
Of course my app have that permission. I remember old ver can detected but new ver can't do that
[MX Player] Mandrake1er:
Did you give the permission trought the app and throught the system ? What is your version of Android ?
[MX Player] kedaitinh12:
Android tv 11. I checked this permission in app and it's say yes
[MX Player] kedaitinh12:
Ah, it's ok now. I change from "only permission when use with app" to "always"
[MX Player] Mat444:
Hi,

Quick question : I use the mx_aio codec to watch a 4K HDR10 video on my Pixel 7 pro. It works great in full screen when there is no media control displayed on screen. But whenever I touch the screen to display the controls, or receive a notification, the image gets darker and noticeably more saturated.

I tried to take screenshots, but it does not render the proper brightness/saturation.

Is this something you have observed ? Is it an expected behavior and is there a workaround ?

Thank you
[MX Player] Mandrake1er:
And when the controls desappear, does it come back to the proper brightness/saturation ? I guess that it's an expected behavior done to better see the controls when you use them.
[MX Player] krakout:
Either that, or (more probably) the image is rendered according to the new colors on it (bright white elements). Happens all the time on TV's with adaptive image settings.

I don't recall, is it possible to change the color of media controls?
[MX Player] Mat444:
Yes, when all overlay elements disappear, it goes back to the proper brightness settings. That would make sense.
[MX Player] Mat444:
Yeah, it's possible that the phone switches between HDR and SDR rendering modes. I will see if I can change the media control buttons color.
[MX Player] krakout:
One way to test that hypothesis is subtitles: do you use them? Bright white subs (perhaps of a big enough size) should give similar results.
[MX Player] Mat444:
Changing the control color to a very dark grey does not change anything, there is still a significant difference between full screen and UI displayed on screen. I took some photos with another phone to show the difference:

1. In full screen mode - brighter, but looks a bit washed out, lacks saturation:

2. As soon as I touch the screen, the image is darker, the skin tone are over saturated

Which one is supposed to be the true HDR rendering in your opinion ?
[MX Player] extream87:
My tcl android tv is working fine installed aio codecs but still dont detect dolby atmos but the sound works... Dolby Atmos still not working?
[MX Player] TotallyAnxious:
I emailed mx player support to add the feature. I've been using Kodi to get Atmos to work. Maybe they'll be more inclined to add feature if they get multiple emails about it.
[MX Player] extream87:
@TotallyAnxious thanks mate kodi working good. My tcl ts 8132 now displays dolby atmos. In Mx player i get dolby atmos logo on tv but not on soundbar
[MX Player] TotallyAnxious:
I did some googling, it looks like proper HDMI passthrough doesn't work with HW+ decoder. So when using hw+ decoder and an HDMI connection causes all audio to be converted to PCM before going through HDMI cable. Though some of the stuff saying this is old.

I'm not gonna be home with my Atmos soundbar for a couple days to test.
[MX Player] TotallyAnxious:
@extream87 Dolby Atmos works with HW decoder. Not HW+. Just tested.
[MX Player] ataman76:
Does the latest version of MX player TV detect August codecs? Because there are no newer ones
[MX Player] Stef_:
yes
[MX Player] Bzoki:
How?
[MX Player] Bzoki:
Hello, I am using the new amazon cube 3gen. prko onkyo tx nr 696 and I can't get any sound except 2.o dolby
[MX Player] Bzoki:
mx player pro 1.51.8 codek mx so neon 1.49.0
[MX Player] jluva420:
Are you saying that you used 1.49.0 with the updated MX player pro 1.51.8? Because I just tried to play DTS movie and it said no sound. I'm just glad we still get updates for this wonderful player. Most older applications give up but not trusty MX player pro. It would be nice if they added Dolby Vision because Justplayers search interface is garbage by comparison....
[MX Player] Tw3ak3r:
I’m using mx player pro 1.57.4 on my 2015 shield and every time I select codec neon64 1.49 that should work it gives me the usual pop up that it needs to restart to load the codec and when you click OK it closes but when I reopen MX player it just freezes up. The shield stays frozen for about 10 seconds on the MX player blue screen before I can close it and then if you restart it again it pops up asking me if I want to use the codec again and it just keeps looping and freezing but never actually loads up with necessary codec pack. I don’t know why it’s doing this I’ve never had these kind of problems before and neither here or on Reddit and any other place to have a red anyone having this exact particular problem.
[MX Player] Mandrake1er:
Did you try to wait (and not close MX Player) to verify if the loaded codec is 1.49 (About menu) ?
[MX Player] Tw3ak3r:
Yes I can wait forever and it just stays frozen on blue screen with mxplayer in the middle but nothing happens, then when I force close it by double tapping circle and close app and relaunch it asks me to load codec again and it just loops same thing. I attached pic of it stuck on blue screen.
[MX Player] Mandrake1er:
OK. Have you tried to use AIO codec file instead of neon64 one ?

I can remember that I already had the same problem during an update, but I don't remember how I solved it.
[MX Player] Krishnendu Naskar:
Nice
[MX Player] Fydodido:
I'm using it on an Android box (Fire Stick 4K+) connected to a Marantz sound receiver. With 5.1 or 7.1 video files, this program only takes 2.0 trace. I don't know how to get the original sound that my files have.

I have the custom CODEC installed, but still on my receiver (Marantz) it detects that I have a 2.0 output when it is actually a Dolby Surround 5.1 file.

I don't know if it has something to do with it, but after entering the custom codec, in the section to choose audio codes, these appear (I don't see Dolby or DTS there)

can you help me? Thank you!
[MX Player] Fydodido:
alguien me puede ayudar con mi problema?

Mod translation: can someone help me with my problem?
[MX Player] Mandrake1er:
Try to select every audio codecs.
[MX Player] Fydodido:
Hola. Sí, he activado todos los códecs de audio y mi receptor todavía detecta solo dos canales 2.0. También he probado con codecs Aio, pero sigue igual.

yo lo tengo asi

Mod translation:

Hello. Yes, I have enabled all audio codecs and my receiver still detects only two 2.0 channels. I have also tried with Aio codecs, but still the same.

I have it like this. Thank you.

Spoiler content hidden.
[MX Player] Badger50:
Greetings. As a friendly reminder, we ask all members to please post in English as stipulated by XDA Rule #4:

Spoiler content hidden.

Thank you for your cooperation, and have a pleasant day.

-Regards: Badger50
[MX Player] Fydodido:
Hello, I translate it with Google translator, but I don't know for what reason, when pasting it, it returns to my language. I think it's because I have the automatic translation of pages, and maybe in that interval it translates what I'm pasting. I'll try to fix it, sorry and thanks for the compassion.