usbhost / mx_ffmpeg Goto Github PK

not working with mx player pro 1.25.5
Need a update 👍👊

For arm64-v8a which is the preferred codec?

I have found both libffmpeg.mx.so.neon64.1.49.0 and mx_neon64.zip works.

What is the difference between these two versions?
There is a big difference in size. One is 12MB another one is 6MB.

The dav1d is quite outdated in the Repo.
Any reasons for not upstreaming the files?

Hi,

Can you please upload the latest Custom Codecs for Mx Player 1.35.1.

Also I had issues with the last Custom Codec you uploaded 1.32.0 (armv7a) with the embedded subtitles not showing up in the videos but the external subtitles worked.

Thanks

Can you build A12 Armv8 Neon. i've tested each of the zips it says "cant find custom codec please use 1.35.0 Armv8 Neon" i have tested each one of the neons same issue

Mx player pro doesn't support MKS extention subtitles.

Hi,

MX Player Pro v1.46.10 got released and since then the custom codec v1.44.0 has stopped working.

Please provide an updated one.

Thanks.

Play store updated and 1.44.0 is not valid it's updated to 1.49.0

Google Store has updated mxplayer to version 1.44, when will it be released?

I have the same version of mx player on both my firestick 4k and my chromecast with google tv along with the same codec 1.49.0. When navigating to HW+ audio codecs AC3 and EAC3 appear on the firestick mx player app but not the chromecast with google tv mx player app. They are the only two options missing. Because of this dolbly digital works on the firestick and not the chromecast. I cannot get dolby to work when playing files in mx player on the chromcast but it always works with the 4k firestick even though everything is configured identical on the hardware and software level. Even with vlc on the chromecast I am able to geet dolby. I Don't understand why this is? Idk where else to report this so sorry if this is not the appropriate place to do so.

Is it possible to release a beta codec pack for mxplayer with ac4 support?

There is an experimental build of ffmpeg which now supports AC4

The tree for this can be found
https://github.com/richardpl/FFmpeg/tree/ac4

admin can you make 1.41.2 aio file I know I can rename the file of 1.35.0 to 1.41.2 but if possible

I have trying to update mx player version 1.44 custom codecs. When i start mx player it shows option that new codecs find update . When i click on update it freeze and when i close app and start again it show some components are curropted.pleaae resolve my issue.because i do not use any ither media player

I would like to understand one thing:
Let's take the Teclast M40 Pro as an example...
The tablet is equipped with Android 12 stripped down to the bone. To levels where there are NO HW codecs even for h263 and VP9.
On MXPlayer, in HW+ it does not give me HW acceleration grey text on anything.
On Emby, it tells you that the render in use is FFMPEG (normaly is ExoPlayer2).
So, these custom codecs take advantage of HW acceleration by using commands like "ffmpeg.exe -hwaccel cuda -hwaccel_output_format cuda" but for Mali ARM GPUs and would go to solve the problem of no codecs at all in the android system?
Or are they interfacing systems with the codecs already installed in Android?
Thanks

Hi there,

Could you make the custom codec available for armv8 neon please? OnePlus 9 Pro.

Thanks
Mark

After load latest custom codec mx_aio.zip or mx_neon.zip I can't use HW+ decoder for:
File format .m2ts BluRay copy on USB HDD Drive
Video Stream, SMPTE VC-1, Profile "Advanced", 1920x1080, 23.97602

This 1.25 version is not accepted by MX player.
I need Armv8 Neon 1.32 .
So please try n give me this.

Hi,

MX Player v1.49.0 got released and since then the custom codec v1.44.0 has stopped working.

Whenever I tried it giving a crash and works perfectly when I disabled it.

Please provide an updated one.

Thanks.

I'm cloning this repo to make some modifications to customize. However, I've noticed that some CVEs which were confirmed and fixed by FFmpeg do not get patched in this repo. To enhance the availability of my project as far as possible, I will appreciate it if any of the CVE below do exist in this repo as well, so that I can fix these security issue myself by applying the corresponding patch.
Here are the CVEs I found in this repo unpatched, but get fixed in FFmpeg:

CVE-2020-20446 in ffmpeg/JNI/ffmpeg/libavcodec/aacpsy.c's function void psy_3gpp_analyze_channel (FFPsyContext *ctx,int channel,const float *coefs,const FFPsyWindowInfo *wi), with patch here for your reference.

CVE-2020-35964 in ffmpeg/JNI/ffmpeg/libavformat/vividas.c's function int track_header (VividasDemuxContext *viv,AVFormatContext *s,uint8_t *buf,int size), with patch here for your reference.

CVE-2020-22015 in ffmpeg/JNI/ffmpeg/libavformat/movenc.c's function mov_write_video_tag (AVFormatContext *s,AVIOContext *pb,MOVMuxContext *mov,MOVTrack *track), with patch here for your reference.

CVE-2020-20453 in ffmpeg/JNI/ffmpeg/libavcodec/aacenc.c's function int aac_encode_frame (AVCodecContext *avctx,AVPacket *avpkt,const AVFrame *frame,int *got_packet_ptr), with patch here for your reference.

Hi,

No matter what I do I cannot update my custom codec past version 44. My Note 4 is not accepting the higher versions and I am unable to play HEVC. I am running the payed version of MX player via Google play store. Do you have any idea why this happens and how can I overcome this issue. Please do not tell me to buy a new phone as it will be unacceptable!

I want to enable Passthrough in Exoplayer for rk3368 based android box .Your code supports the passthrough in our box please give me a solution to use it in exoplayer

When I switch to a custom codec - 1.32.0 ARMv7 NEON, as my MX player app requested, subtitles are not visible anymore. When I go back to a standard one - subs reappear flawlessly.
Could you help me, please?

Hello,
Thanks for this package!
I am experiencing some weird issues while using these codecs with MX player on my projector (Xgimi Z6X) with audio channel mapping in DTS mode -- center and right channels are swapped, left-read is gone completely etc + consistent audio delay. None of these issues are present with Dolby encoded material.

I was wondering whether it's due to some old bugs in ffmpeg and dav1d? I can see this codec package uses fairly old versions, so I tried building my own with updated ones, but ffmpeg fails to configure with:

dav1d >= 0.5.0 not found using pkg-config

(Actual dav1d in my system is 1.0.0).

I tried building dav1d statically, installing from packages etc -- no avail. So after couple hours of different failing paths I gave up.
Building on Ubuntu 22, using android-ndk-r21e as some tools used in your build process were removed from more recent NDKs.

Maybe you can update all versions to make a more modern codec pack? Thanks so much for your time!

Hi,

I'm using the MX Player Pro in version 1.51.8 ARMv7 Neon. It seems it does not recognize the zip file which I've put into the Downloads folder. Am I doing something wrong there?

I tested the same on my android phone and it works fine.

Have MX Player Pro installed on a Samsung Tab A7 (android 11). It won't recognize (install) any of the new 1.44.0 codecs. Is the problem on my end or is it with MX?

Which version can use on nplayer ?

@USBhost
91e9799 will not actually upgrade the dav1d library used. In the config-ffmpeg.sh script, only the dav1d header files are referenced. The only external library passed to the linker is libmxutil. So, I believe, dav1d and other dependency library symbols are resolved from libmxutil. If you use header files from newer dav1d versions, you will end up with a broken FFmpeg library as FFmpeg will be built for a newer version of the dav1d library but the actual one resolved through libmxutil will be the older one. That's why it's crashing. Even if it works, you will not get any benifits of the newer dav1d library as the underlaying library is still older one.

I think the better way to upgrade dav1d library is to build it as a static library and pass appropriate linker flags so that will be a part of ffmpeg library.