Hi, I have a problem with the encoding USSD because I have a Chinese encoding how to fix it ?
Related
Hi,
I want to change my android device to only support EFR speech codec and to disable other codecs. How can i do it?
many thanks in advance
I have problem with more encoded Opus track in MKV container with MX Player Pro (tested with Android 5 and 6)
one example with problem: OPUS 224Kbps VBR
( another without problem to compare: Opus 192Kbps VBR )
I not know english word to explain audio effect.. it's a vibrate each 2sec for less 0.5sec.
I not reproduce the problem if enable HW OPUS audio codec (but HW not support 5.1).
No problem on MPC-HC or VLC with PC.
I reproduce the same probleme with KODI on Android 5
I add this new MKV test file with x264 video (not all device can read x265 for test)
MKV x264-OPUS 224kbps VBR
-VLC can read without problem on Windows and Android (but not found other player can read without problem this x264 mkv)
baudav said:
I have problem with more encoded Opus track in MKV container with MX Player Pro (tested with Android 5 and 6)
one example with problem: OPUS 224Kbps VBR
( another without problem to compare: Opus 192Kbps VBR )
I not know english word to explain audio effect.. it's a vibrate each 2sec for less 0.5sec.
I not reproduce the problem if enable HW OPUS audio codec (but HW not support 5.1).
No problem on MPC-HC or VLC with PC.
I reproduce the same probleme with KODI on Android 5
Click to expand...
Click to collapse
It looks like a FFmpeg side issue & the latest version also has issues. That's why the issue is there with KODI.
Probably VLC might have implemented some workarounds.
The issue is forwarded to our developer team & they are looking into the issue.
baudav said:
I have problem with more encoded Opus track in MKV container with MX Player Pro (tested with Android 5 and 6)
one example with problem: OPUS 224Kbps VBR
( another without problem to compare: Opus 192Kbps VBR )
I not know english word to explain audio effect.. it's a vibrate each 2sec for less 0.5sec.
I not reproduce the problem if enable HW OPUS audio codec (but HW not support 5.1).
No problem on MPC-HC or VLC with PC.
I reproduce the same probleme with KODI on Android 5
Click to expand...
Click to collapse
It looks like a bug on mkvmerge or ffmpeg.
We will add a workaround on the next version which can be enabled optionally.
Hi,
for the update
- https://github.com/mbunkus/mkvtoolnix/issues/2099
- https://trac.ffmpeg.org/ticket/4178
after extract opus track with ffmpeg, and add it with ffmpeg, it's GOOD.
I not understand all word in explanation, but initial opus track is not very good (even if reading has no problem)
If mxplayer can read without problem it's good; but if I correct my file it's better.
baudav said:
Hi,
for the update
- https://github.com/mbunkus/mkvtoolnix/issues/2099
- https://trac.ffmpeg.org/ticket/4178
after extract opus track with ffmpeg, and add it with ffmpeg, it's GOOD.
I not understand all word in explanation, but initial opus track is not very good (even if reading has no problem)
If mxplayer can read without problem it's good; but if I correct my file it's better.
Click to expand...
Click to collapse
We will add a workaround for this. But, it is not supposed to be used for all audio tracks. So, it will be made as optional.
DVB-T2 recorded with DIGIPORTY in HD. The video list shows this after the video file name:
DVB TEL
This error message is displayed after start play:
This audio codec
EAC3
is not supported.
Please add this codec, thanks.
I just thought i would share this, as it's been bugging me on Miui that the Google Assistant didn't always speak results like what is the weather forecast.
https://support.google.com/websearch/forum/AAAAgtjJeM4MwaLxKImwEc/?hl=en
change the value of mm.enable.qcom_parser in build.prop to 245389 (3183219 as mentioned in the article is for another device that supports different codecs) fixes the issue as mentioned in the google bug report for the Xiaomi a1.
I've attached a magisk module that is a modified Camera2 api enabler script. It enables Camera 2 api, adjusts noise cancelation to fluencepro, adds EIS entry for Google camera and turns off noise cancellation for voice recordings
Edit: modified Magisk package to the value @Stoffl_ calculated, 245389, for the mido. Thanks
Thanks, will try this as the TalkBack issue has bugged me for a while.
A better explaination of what is happening - based on that information we can probably work out the right number for the Redmi Note 4x to disable the ogg hardware codec until its updated - The above number may be correct, but we probably just need to get the original number, and just change the bit for Ogg to off for the moment.
http://en.miui.com/forum.php?mod=viewthread&tid=1465017&page=2#pid21050310
21#
01:04, Jan-10-2018 | From PC |
This post was edited by Theliel at 18:09, Jan-09-2018
Is not exactly in that way.
In first instance, the issue is only present in qualcom SoC (not Mediatek) Nougat, Oreo work fine.
In second place, qcom_parser number is a mask, representing all supported codecs directly in hardware (not software). Each SoC support different codecs.
For Mi4c:
Codecs: DivX DivXHD AVI AC3 ASF AAC QCP DTS 3G2 MP2TS
mm.enable.qcom_parser=3379827
3379827 = 1100111001001001110011
Each bit represent a codec, if you set a bit to 1, you enable hw support to that codec. A more simpe example, imagine only 3 codecs and in the exact order: mp3 ogg acc
111 enable all codecs = 7
001 enable only aac = 1
101 enable mp3 and aac, disable ogg = 5
You can't use the same value to each device, because each device support a different array of codecs. The real issue is only with qcom hw lib/codec ogg (container, real codec is opus), that is the audio returned by google. Devices without hw support of ogg or with ogg disabled, work fine in most Nougat.
In my investigations, ogg is placed in 15th position in most of all qcom devices.
So, for default Mi4c:
3379827 = 1100111001001001110011 | Work fine, hw is not used anyway, not supported
Default Mi6 Nougat:
1048575 = 11111111111111111111 | Dont Work
1032191 = 11111011111111111111 | Work perfecly
If you force all devices to 3183219 (for example), yes, you are disabling ogg bit, but you are disabling a lot of other codecs too, is not recommended, not a solution.
The real solution is a newer driver/codec to solve hw codec. Temporal fix is ONLY flip ogg bit to disable hw support and use only software, without touching the others bits. Each device, have a different hw arraw codec, so you shouldn't use the same value to all, is a big mistake
Click to expand...
Click to collapse
So..if I understand this correctly...
My Redmi Note 4X Global on Global stable Rom 9.0.5.0 build.prop has currently the following values
Code:
#codecs:(PARSER_)AAC AC3 AMR_NB AMR_WB ASF AVI DTS FLV 3GP 3G2 MKV MP2PS MP2TS MP3 OGG QCP WAV FLAC AIFF APE
mm.enable.qcom_parser=261773
261773 decimal = 111111111010001101 in binary
According to the post above and the comments in my build prop bit 15 should be Ogg support.
111111111010001101 means Ogg is enabled
So the correct value to disable Ogg HW support would be 111111111010000101 = 261765
Correct ?
Hmmm .... this is very interesting - but also probably error prone. With SlimROM v1.17, I have this "mm.enable.qcom_parser=1048575" (i.e., 1111 1111 1111 1111 1111). It seems that everything is turned on! But it is not clear what one will be disabling if any alteration is made.
Turns out the bits should be read from right to left, whoops.
http://en.miui.com/forum.php?mod=redirect&goto=findpost&ptid=1465017&pid=21367895
And the starting zero bits aren't counted, which would explain why number of codecs and bits didn't match up in my example.
I'm now using 229005 and so far google assistant talkback is working.
*edit*
I had the dumb and counted wrong
111011111010001101 = 245389 is working, weather and time talkback functional!!
Only OGG hardware encoding should be disabled, everything else is should be on default rom setting.
Why is not playing HEVC Mi10P in HW? (YUNDOO Y8, RK3399)
In FTMC player it plays in HW-mode.
Format : V_MPEGH/ISO/HEVC
Codec ID : V_MPEGH/ISO/HEVC
Width : 1 920 pixels
Height : 1 080 pixels
Frame rate : 23.976 fps
Writing application : mkvmerge v8.2.0 ('World of Adventure') 64bit
Writing library : libebml v1.3.1 + libmatroska v1.4.2
Bug report:
BillyBonesX99 said:
Why is not playing HEVC in HW? (YUNDOO Y8, RK3399)
In FTMC it plays in HW mode.
Format : V_MPEGH/ISO/HEVC
Codec ID : V_MPEGH/ISO/HEVC
Width : 1 920 pixels
Height : 1 080 pixels
Frame rate : 23.976 fps
Writing application : mkvmerge v8.2.0 ('World of Adventure') 64bit
Writing library : libebml v1.3.1 + libmatroska v1.4.2
Bug report:
Click to expand...
Click to collapse
FYI,
Not all HEVC files are same. Most of the devices support only HEVC Main profile. Kindly provide the full metadata whenever you report a bug. It will help us to provide you with a better solution.
In many devices, Force trying the hardware accelerated decoding of 10bit video may result in crashes. So, MX Player will try the hardware acceleration only if the 10bit profiles are explicitly supported. Based on the bug report, your system doesn't report the HEVC Main10 support. So, MX Player has rejected the HW & HW+ decoders. If you are sure that your chipset supports the hardware acceleration of Main10 profile and the same is implemented on your device as well, kindly enable the same in the HW+ Video Codecs on the Settings » Decoder. It will allow you to force try the Main10 profile even if the device doesn't support it explicitly.
Hope this information will be helpful to you.
MXPlayer said:
FYI,
If you are sure that your chipset supports the hardware acceleration of Main10 profile and the same is implemented on your device as well, kindly enable the same in the HW+ Video Codecs on the Settings » Decoder. It will allow you to force try the Main10 profile even if the device doesn't support it explicitly.
Click to expand...
Click to collapse
OK, I turned on "HW+ Codecs" (H265 10-bit) and HEVC Mi10P started playing in "HW" hardware mode (Mikagura Gakuen Kumikyoku BD1080). :good: