I have made a review of this phone in Swedish but Google Translate should translate it good enough for you to understand. Have a look here:
https://translate.google.se/transla...i-mi-max-recension-3gb-32gb.133656/&sandbox=1
dannejanne said:
I have made a review of this phone in Swedish but Google Translate should translate it good enough for you to understand. Have a look here:
https://translate.google.se/transla...i-mi-max-recension-3gb-32gb.133656/&sandbox=1
Click to expand...
Click to collapse
Thanks for the review. Is there any way to modify the dpi on this phone? I'm not very familiar with the MIUI so I don't know if there's a built in tool similar to what Samsung and Huawei have in their latest ROMs.
LE: Answered in your review. Nice to know it works .
albireox said:
Thanks for the review. Is there any way to modify the dpi on this phone? I'm not very familiar with the MIUI so I don't know if there's a built in tool similar to what Samsung and Huawei have in their latest ROMs.
Click to expand...
Click to collapse
No built in function. It can be done without root with ADB but some things can look a little weird even though it still functions. 400 DPI was the lowest I could go without breaking things too much graphically. Stock DPI is 440.
Sent from my Mi Max
dannejanne said:
No built in function. It can be done without root with ADB but some things can look a little weird even though it still functions. 400 DPI was the lowest I could go without breaking things too much graphically. Stock DPI is 440.
Sent from my Mi Max
Click to expand...
Click to collapse
So you're saying that an equivalent "View Mode" function from the Mate8 is not present on the Mi Max... That's a little disappointing :|
albireox said:
So you're saying that an equivalent "View Mode" function from the Mate8 is not present on the Mi Max... That's a little disappointing :|
Click to expand...
Click to collapse
Yes. It's a bit disappointing indeed. What helped me to be satisfied enough was to download a custom font from its theme store named "SlatePro-Condensed" which is smaller than the stock one. It's also closer to Roboto in looks.
Sent from my Mi Max
dannejanne said:
No built in function. It can be done without root with ADB but some things can look a little weird even though it still functions. 400 DPI was the lowest I could go without breaking things too much graphically. Stock DPI is 440.
Sent from my Mi Max
Click to expand...
Click to collapse
you say stock dpi is 440? but the specs says otherwise.
To anyone who want to adjust dpi for Mi Max, you should root your phone and modify this line in build prop: "persist.miui.density_v2=440", change "440" to the value you like.
Does this phone support HEVC x265 playback in mxplayer with HW/HW+ instead of SW?
Also can it easily play a 1080p 10bit Hevc file with 5mbps or higher bitrate? Or it stutters or shows artifacts?
husaintaherali said:
Does this phone support HEVC x265 playback in mxplayer with HW/HW+ instead of SW?
Also can it easily play a 1080p 10bit Hevc file with 5mbps or higher bitrate? Or it stutters or shows artifacts?
Click to expand...
Click to collapse
From CM13 media_codecs.xml:
Code:
<!--
Decoder capabilities for 8952
_________________________________________________________________
| Codec | W H fps Mbps MB/s | Encode Secure-dec |
|__________|_________________________________________|___________________|
| h264 | 1920 1088 60 50 489600 | Y Y |
| hevc | 1920 1088 60 50 489600 | N Y |
| mpeg4 | 1920 1088 60 40 489600 | Y N |
| vc1 | 1920 1088 30 45 244800 | N Y |
| vp8 | 1920 1088 30 50 244800 | Y N |
| divx3 | 1920 1088 30 20 244800 | N N |
| div4/5/6 | 1920 1088 30 50 244800 | N N |
| h263 | 864 480 30 2 48600 | Y N |
| mpeg2 | 1920 1088 30 80 244800 | N Y |
|__________|_________________________________________|___________________|
-->
<!--
Encoder capabilities for 8952
____________________________________________________
| Codec | W H fps Mbps MB/s |
|__________|_________________________________________|
| h264 | 1920 1088 30 20 244800 |
| mpeg4 | 1920 1088 30 40 244800 |
| h263 | 864 480 30 2 48600 |
| vp8 | 1920 1088 30 20 244800 |
|____________________________________________________|
-->
looks like shouldn't be a problem for the hardware?! Correct me if I am wrong...
nijel8 said:
From CM13 media_codecs.xml:
Code:
<!--
Decoder capabilities for 8952
_________________________________________________________________
| Codec | W H fps Mbps MB/s | Encode Secure-dec |
|__________|_________________________________________|___________________|
| h264 | 1920 1088 60 50 489600 | Y Y |
| hevc | 1920 1088 60 50 489600 | N Y |
| mpeg4 | 1920 1088 60 40 489600 | Y N |
| vc1 | 1920 1088 30 45 244800 | N Y |
| vp8 | 1920 1088 30 50 244800 | Y N |
| divx3 | 1920 1088 30 20 244800 | N N |
| div4/5/6 | 1920 1088 30 50 244800 | N N |
| h263 | 864 480 30 2 48600 | Y N |
| mpeg2 | 1920 1088 30 80 244800 | N Y |
|__________|_________________________________________|___________________|
-->
<!--
Encoder capabilities for 8952
____________________________________________________
| Codec | W H fps Mbps MB/s |
|__________|_________________________________________|
| h264 | 1920 1088 30 20 244800 |
| mpeg4 | 1920 1088 30 40 244800 |
| h263 | 864 480 30 2 48600 |
| vp8 | 1920 1088 30 20 244800 |
|____________________________________________________|
-->
looks like shouldn't be a problem for the hardware?! Correct me if I am wrong...
Click to expand...
Click to collapse
But has anyone tried hevc on the phone in mxplayer?
Because even if hardware is capable the software might not be. In oneplus 3 hevc is supported in hardware but plays SW mode only not HW mode, which is better for playback.
husaintaherali said:
But has anyone tried hevc on the phone in mxplayer?
Because even if hardware is capable the software might not be. In oneplus 3 hevc is supported in hardware but plays SW mode only not HW mode, which is better for playback.
Click to expand...
Click to collapse
Then that would be problem with mxplayer, not the phone, right? Considering both devices are so new more likely mi max will lack the support too.
nijel8 said:
Then that would be problem with mxplayer, not the phone, right? Considering both devices are so new more likely mi max will lack the support too.
Click to expand...
Click to collapse
No. If manufacturer of the phone implemented support for hevc then mx player can easily play it. Its the fault of xiaomi if they didnt do it.
Changing fonts?
Anyone have a method to change the fonts on this phone? I had installed a utility in my Zenfone 2 but that doesn't work here. In the Zenfone, I would go into Display - Fonts and change the font but this option doesn't come up here even after installing the .apk
Stock google font sucks
husaintaherali said:
But has anyone tried hevc on the phone in mxplayer?
Because even if hardware is capable the software might not be. In oneplus 3 hevc is supported in hardware but plays SW mode only not HW mode, which is better for playback.
Click to expand...
Click to collapse
I've tried on Miui 8...HEVC format is supported on Mi Max....no lag or anything...works perfect on mx player...and im using sw mode...
husaintaherali said:
But has anyone tried hevc on the phone in mxplayer?
Because even if hardware is capable the software might not be. In oneplus 3 hevc is supported in hardware but plays SW mode only not HW mode, which is better for playback.
Click to expand...
Click to collapse
The libs are there but it doesn't support a Hevc (H265) high profile (HDR 10 bit). I didn't try with MX, tried with stock & Kodi (15.2). As MX use also its own libs someone should try it.
nijel8 said:
From CM13 media_codecs.xml:
Code:
<!--
Decoder capabilities for 8952
_________________________________________________________________
| Codec | W H fps Mbps MB/s | Encode Secure-dec |
|__________|_________________________________________|___________________|
| h264 | 1920 1088 60 50 489600 | Y Y |
| hevc | 1920 1088 60 50 489600 | N Y |
| mpeg4 | 1920 1088 60 40 489600 | Y N |
| vc1 | 1920 1088 30 45 244800 | N Y |
| vp8 | 1920 1088 30 50 244800 | Y N |
| divx3 | 1920 1088 30 20 244800 | N N |
| div4/5/6 | 1920 1088 30 50 244800 | N N |
| h263 | 864 480 30 2 48600 | Y N |
| mpeg2 | 1920 1088 30 80 244800 | N Y |
|__________|_________________________________________|___________________|
-->
<!--
Encoder capabilities for 8952
____________________________________________________
| Codec | W H fps Mbps MB/s |
|__________|_________________________________________|
| h264 | 1920 1088 30 20 244800 |
| mpeg4 | 1920 1088 30 40 244800 |
| h263 | 864 480 30 2 48600 |
| vp8 | 1920 1088 30 20 244800 |
|____________________________________________________|
-->
looks like shouldn't be a problem for the hardware?! Correct me if I am wrong...
Click to expand...
Click to collapse
You are wrong. It's Qualcomm QDSP6 V56 same as one on Snapdragon 810. Libs are there but they quality is a questionable along with implementation.
Only thing I can confirm is that it doesn't want to play H265 high 10 bit mixed in mkv container I have at all, while my old phone with CM12.1 plays it with software decoding without of problems.
Edit:
& there are also VP9 software (Google) & hardware (QC) decoder libs in firmware, just checked with Aida but didn't test do they actually work.
Edit n°2:
Only software H265 High 10bit works in MX player, HW+ & new HW+ doesn't work.
Related
I successfully installed TCPMP (TCPMP-0.72RC2-ARM-REV31.CAB) but I'm having a problem.
While running the movie 10-15 sec, it start running slow. I tried changing the video & audio setting but NO LUCK.
I'm running .mkv files (videos are in MicroSD card)
=====================================
Video Frame width: 640
Video Frame Height: 272
Video Frame Rate: 25 frames/second
Audio Channels: 1(mono)
Audio Sample Rate: 24khz
===============================
Video Frame width: 720
Video Frame Height: 400
Video Frame Rate: 25 frames/second
Audio Channels: 2(stereo)
Audio Sample Rate: 24khz
=====================================
Software crash everytime I try to run BR-Rip .mkv movie such as
Video Frame width: 1280
Video Frame Height: 544
Video Frame Rate: 25 frames/second
Audio Channels: 2(streo)
Audio Sample Rate: 24khz
If you have any info how to fix the problem plz reply it
Any changes? Has anything improved?
I have been told that 720p High profile is smooth and OK.
True?
Totally smooth. I was testing it last night with Youtube embeded videos using the stock google browser at 720 and it was great. I even hooked up the HDMI to take a look at it on the big screen. About time.
Sorry, for not being precise.
I meant stuff like mkv files, etc.
720p. in High Profile
I just tried an mkv I originally had to use Handbrake to encode that's 720p/AC3 audio using Moboplayer. Soft decoding was choppy but Hard decoding played it flawlessly! Unfortunately... no sound.
Rockplayer didn't perform as well.
How would 3.1 affect High Profile playback? My understanding is its purely a Tegra 2 hardware issue. 3.1 might bring better handling of wrappers and software decoding but it can't add hardware decoding capabilities that aren't designed in already.
mhausig said:
How would 3.1 affect High Profile playback? My understanding is its purely a Tegra 2 hardware issue. 3.1 might bring better handling of wrappers and software decoding but it can't add hardware decoding capabilities that aren't designed in already.
Click to expand...
Click to collapse
LOLWUT. Tegra 2 supports HD, 720p and 1080p (recording and playback) with lot of codect and formats (mp4,mkv / divix, h.264). Just read about it on official site. NVidia says this.
Also, use mort for tegra 2 with special codecs
Read again, he said "High Profile".
And Tegra 2 can't handle it.
I don't understand this whole "high profile" issue, but I am now watching a movie on my xoom encoded using the Handbrake Apple TV2 profile and the video's specs are 1280x688/23fps/4241kbps........pretty damn nice picture.
fromdetroit7 said:
I don't understand this whole "high profile" issue, but I am now watching a movie on my xoom encoded using the Handbrake Apple TV2 profile and the video's specs are 1280x688/23fps/4241kbps........pretty damn nice picture.
Click to expand...
Click to collapse
Basically, the profiles determine how many compression features can be used to produce a smaller size with equal (or comparable) quality than a higher size version. The higher the profile, the more complex compression features it have and is harder on CPU/GPU decoding.
You can re-encode a video using a basic profile and it will play smooth, the quality can be the same as a high profile version, but the file size can get bigger too.
The point here is that to ensure a smooth video playback on Nvidia Tegra 2 a re-encode is needed and this is what some people hate, they just want to be able to do a simple copy-paste (or drag-drop) of videos without worrying about re-encoding. This also happens because most of the videos found in Internet are encoded in high profile.
Sure, other people doesn't mind doing re-encoding and they are fine doing that.
I'd have thought that all Apple presets are limited to main or baseline profile, but apparently the "AppleTV 2" preset (from HB 0.95) uses high profile. It also removed the vbv rate limitation.
AppleTV: -e x264 -q 20.0 -a 1,1 -E faac,copy:ac3 -B 160,160 -6 dpl2,auto -R Auto,Auto -D 0.0,0.0 -f mp4 -4 -X 960 --loose-anamorphic -m -x cabac=0:ref=2:me=umh:b-pyramid=none:b-adapt=2:weightb=0:trellis=0:weightp=0:vbv-maxrate=9500:
bv-bufsize=9500
AppleTV 2: -e x264 -q 20.0 -r 29.97 --pfr -a 1,1 -E faac,copy:ac3 -B 160,160 -6 dpl2,auto -R Auto,Auto -D 0.0,0.0 -f mp4 -4 -X 1280 --loose-anamorphic -m
The big diff between 1 & 2 is that the -x blah:blah:blah setting is removed in the latter, which basically disables a bunch of compression settings to conform to main/baseline.
In simpler terms, if you're using the AppleTV 2 preset, you're using high profile, which means that the Teg2 can at least handle some 720p high profile. I suspect that smoothness will depend on the content, if the Teg2 is as marginal as many indicate. The acid test would be trying to encode Avatar at [email protected]
BTW, the above preset specifies a second (AC3) audio track. If you only need the main audio track, remove the second to reclaim some space, and more importantly, to increase the probability of smooth playback.
e.mote said:
I'd have thought that all Apple presets are limited to main or baseline profile, but apparently the "AppleTV 2" preset (from HB 0.95) uses high profile. It also removed the vbv rate limitation.
AppleTV: -e x264 -q 20.0 -a 1,1 -E faac,copy:ac3 -B 160,160 -6 dpl2,auto -R Auto,Auto -D 0.0,0.0 -f mp4 -4 -X 960 --loose-anamorphic -m -x cabac=0:ref=2:me=umh:b-pyramid=none:b-adapt=2:weightb=0:trellis=0:weightp=0:vbv-maxrate=9500:
bv-bufsize=9500
AppleTV 2: -e x264 -q 20.0 -r 29.97 --pfr -a 1,1 -E faac,copy:ac3 -B 160,160 -6 dpl2,auto -R Auto,Auto -D 0.0,0.0 -f mp4 -4 -X 1280 --loose-anamorphic -m
The big diff between 1 & 2 is that the -x blah:blah:blah setting is removed in the latter, which basically disables a bunch of compression settings to conform to main/baseline.
In simpler terms, if you're using the AppleTV 2 preset, you're using high profile, which means that the Teg2 can at least handle some 720p high profile. I suspect that smoothness will depend on the content, if the Teg2 is as marginal as many indicate. The acid test would be trying to encode Avatar at [email protected]
BTW, the above preset specifies a second (AC3) audio track. If you only need the main audio track, remove the second to reclaim some space, and more importantly, to increase the probability of smooth playback.
Click to expand...
Click to collapse
Thanks, both posts were great break downs that helped me understand better.
Guy I am talking to says he is using Mobo Player and this is the video he tried. Apparently before update to 3.1 it was not that smooth. He says it is like switching from software decode to hardware decode.
If this serenity trailer is not the filr format we are all talking about, please supply me with a link to an mkv High Profile file, so I can ask him to download and try again.
General
Complete name : E:\PLIKI\Download\Serenity - HD DVD Trailer.mp4
Format : MPEG-4
Format profile : Base Media
Codec ID : isom
File size : 80.0 MiB
Duration : 2mn 19s
Overall bit rate : 4 802 Kbps
Movie name : Serenity - HD DVD Trailer
Performer : Universal Pictures
Genre : Trailer
Recorded date : 2005
Encoded date : UTC 2007-05-30 05:20:31
Tagged date : UTC 2007-05-30 05:20:31
Cover : Yes
Video
ID : 1
Format : AVC
Format/Info : Advanced Video Codec
Format profile : [email protected]
Format settings, CABAC : Yes
Format settings, ReFrames : 4 frames
Codec ID : avc1
Codec ID/Info : Advanced Video Coding
Duration : 2mn 19s
Bit rate mode : Variable
Bit rate : 4 675 Kbps
Maximum bit rate : 10.8 Mbps
Width : 1 280 pixels
Height : 720 pixels
Display aspect ratio : 16:9
Frame rate mode : Constant
Frame rate : 23.976 fps
Color space : YUV
Chroma subsampling : 4:2:0
Bit depth : 8 bits
Scan type : Progressive
Bits/(Pixel*Frame) : 0.212
Stream size : 77.8 MiB (97%)
Writing library : x264 core 55 svn-655
Encoding settings : cabac=1 / ref=3 / deblock=1:0:0 / analyse=0x3:0x13 / me=hex / subme=6 / brdo=1 / mixed_ref=1 / me_range=16 / chroma_me=1 / trellis=1 / 8x8dct=1 / cqm=0 / deadzone=21,11 / chroma_qp_offset=0 / threads=1 / nr=0 / decimate=1 / mbaff=0 / bframes=3 / b_pyramid=0 / b_adapt=1 / b_bias=0 / direct=1 / wpredb=1 / bime=1 / keyint=250 / keyint_min=25 / scenecut=40 / rc=2pass / bitrate=4675 / ratetol=1.0 / rceq='blurCplx^(1-qComp)' / qcomp=0.60 / qpmin=10 / qpmax=51 / qpstep=4 / cplxblur=20.0 / qblur=0.5 / ip_ratio=1.40 / pb_ratio=1.30
Encoded date : UTC 2007-05-30 05:20:31
Tagged date : UTC 2007-05-30 05:20:35
Audio
ID : 2
Format : AAC
Format/Info : Advanced Audio Codec
Format profile : LC
Codec ID : 40
Duration : 2mn 19s
Bit rate mode : Variable
Bit rate : 128 Kbps
Maximum bit rate : 149 Kbps
Channel(s) : 2 channels
Channel positions : Front: L R
Sampling rate : 48.0 KHz
Compression mode : Lossy
Stream size : 2.12 MiB (3%)
Encoded date : UTC 2007-05-30 05:20:34
Tagged date : UTC 2007-05-30 05:20:35
Any ideas as to how it plays scene HD MKVs?
Here's a sample MediaInfo for one:
General #0
Complete name : F:\TV.SHOW.S01E02.720p.HDTV.X264-DIMENSION.mkv
Format : Matroska
File size : 1.09 GiB
PlayTime : 43mn 41s
Bit rate : 3581 Kbps
Encoded date : UTC 2011-05-12 19:59:44
Writing application : mkvmerge v3.0.0 ('Hang up your Hang-Ups') built on Apr 19 2010 11:58:49
Writing library : libebml v0.7.7 + libmatroska v0.8.1
Video
ID : 1
Format : AVC
Format/Info : Advanced Video Codec
Format profile : [email protected]
Format settings, CABAC : Yes
Format settings, ReFrames : 8 frames
Codec ID : V_MPEG4/ISO/AVC
Duration : 42mn 22s
Bit rate : 3 306 Kbps
Width : 1 280 pixels
Height : 720 pixels
Display aspect ratio : 16:9
Frame rate : 23.976 fps
Color space : YUV
Chroma subsampling : 4:2:0
Bit depth : 8 bits
Scan type : Progressive
Bits/(Pixel*Frame) : 0.150
Stream size : 980 MiB (88%)
Writing library : x264 core 102 r1666 d058f37
Encoding settings : cabac=1 / ref=8 / deblock=1:-2:-2 / analyse=0x3:0x113 / me=umh / subme=9 / psy=1 / psy_rd=1.00:0.00 / mixed_ref=1 / me_range=24 / chroma_me=1 / trellis=1 / 8x8dct=1 / cqm=0 / deadzone=21,11 / fast_pskip=0 / chroma_qp_offset=-2 / threads=16 / sliced_threads=0 / nr=0 / decimate=1 / interlaced=0 / constrained_intra=0 / bframes=5 / b_pyramid=2 / b_adapt=1 / b_bias=0 / direct=3 / weightb=1 / open_gop=0 / weightp=2 / keyint=250 / keyint_min=25 / scenecut=40 / intra_refresh=0 / rc_lookahead=40 / rc=2pass / mbtree=1 / bitrate=3306 / ratetol=1.0 / qcomp=0.60 / qpmin=10 / qpmax=51 / qpstep=4 / cplxblur=20.0 / qblur=0.5 / ip_ratio=1.40 / aq=1:1.10
Language : English
Audio
ID : 2
Format : AC-3
Format/Info : Audio Coding 3
Mode extension : CM (complete main)
Codec ID : A_AC3
Duration : 42mn 22s
Bit rate mode : Constant
Bit rate : 384 Kbps
Channel(s) : 2 channels
Channel positions : Front: L R
Sampling rate : 48.0 KHz
Bit depth : 16 bits
Compression mode : Lossy
Stream size : 116 MiB (10%)
So... update to 3.1 did not change anything?
mkv (h.264) High Profile do not work - so IT IS TEGRA?
has anyone thought this could be a limitation of Android?
here is the media format support from android dev guide
H.263 3GPP (.3gp) and MPEG-4 (.mp4)
H.264 AVC Baseline Profile (BP) 3GPP (.3gp) and MPEG-4 (.mp4). MPEG-TS (.ts, AAC audio only, not seekable, Android 3.0+)
MPEG-4 SP 3GPP (.3gp)
VP8 WebM (.webm)
Click to expand...
Click to collapse
Tegra 2 definitely can decode more formats than android support
Not sure if you guys are aware but new video player released on market that adds lot of new codecs with hardware support this is great for my Nexus S
I know SGS2 pretty much supports most codecs but i dont think it supports DTS this player will play your MKV moves with DTS with full hardware support.
Not software like rockplayer, mobo..ect
Its a paid app but has 3 day trial version
https://market.android.com/details?id=com.inisoft.mediaplayer.trial
The native player supports DTS.
Sent from my GT-I9100 using Tapatalk
Not with the DTS MKV I just tried.
Hmmm, that's strange. I d/l the second dts mkv now, same, it plays flawlessly WITH audio.
now I no my android player better than any other bit of software on android, I have tried every player and know when I see a decent player, this one is pretty decent.
I have a test video I have kept on my phone for 12 months now, a full high profile 1080p copy of a band of brothers episode. Prior to the SG2 nothing I played it on could handle it my HD2, Ipad or Ipad2. When I first got my Sg2 i found that most of the players (that played MKV) would play it but most without sound. Those with sound played it fairly well but if you tried to skip through the film things would go awry.
This player takes a few seconds to skip but it get there and plays in sync - awesome. now this v1.0, looking forward to some more optimisations, this is now my #1 video player, better than rock, mobo, act1, vitl, vplayer and others.
good find, have a thankyou from me.
How peculiar - just tried another video with DTS audio and once again, no sound.
stoolzo said:
this is now my #1 video player, better than rock, mobo, act1, vitl, vplayer and others.
good find, have a thankyou from me.
Click to expand...
Click to collapse
Yup this is the only player so far that actually plays video/audio even when not supported by native OS with actual HArdware support.
Rock player Mobo and every other video player will only play what the OS supports with hardware. So if you dont have DTS support native those players will only play those files with software and play back will be sloppy and quality wont be as good
now with this it will play perfect..with hardware support.
David Horn said:
How peculiar - just tried another video with DTS audio and once again, no sound.
Click to expand...
Click to collapse
not sure ...Ive tested a few and works fine
David Horn said:
How peculiar - just tried another video with DTS audio and once again, no sound.
Click to expand...
Click to collapse
can you provide a link anywhere to this video or upload a small snippet somewhere, perhaps use gspot and post the codecs used?
Dice is chomping through everything I throw at it.
Dice is cool, but can't say it is playing really flawlessly, for example, on a 720p mkv Band of Brother ep02, you can see slight but noticeable stutters, though then again, it indeed is the only player that can play out video/audio in sync while all others failed...
mi3x said:
Hmmm, that's strange. I d/l the second dts mkv now, same, it plays flawlessly WITH audio.
Click to expand...
Click to collapse
are you sure that it is DTS and not AC3??? I tried 2 different mkv-files with DTS audio and could not get any sound... DicePlayer is working, but lags too much... Any other solutions?!
I was checking a 1080p/6ch DTS (1.5 MBit) mkv clip before and while Diceplayer (1.1.1) does play the audio right, it stutters the video like every 2 seconds, unusable.
Rockplayer decodes the 6ch audio in software mode, but the video is superlaggy.
Mobo is superslow and without sound.
Video is playing smoothly in system player... without sound.
I have two apps that decode the audio properly and with little CPU usage (DICE and Rockplayer), and one that decodes video properly and with little CPU usage (System). Unfortunately, it's either or.
Kinda sucks...
Tried my Inception 1080p DTS sample that plays smooth without audio in the stock Video player. It plays with audio in DicePlayer but stutters like mad and is not watchable.
there be be an issue with the way it has been encoded, then again it cannot have a high bitrate as that would make the file over 4 gig and you wouldnt be able to play that due to the FAT32 limit on file sizes. Perhaps you could share the file size, bit rate and codec information of the file you are playing.
If it plays well on the standard player it will likely be H264 mp4, could be main or high profile.
stoolzo said:
there be be an issue with the way it has been encoded, then again it cannot have a high bitrate as that would make the file over 4 gig and you wouldnt be able to play that due to the FAT32 limit on file sizes. Perhaps you could share the file size, bit rate and codec information of the file you are playing.
If it plays well on the standard player it will likely be H264 mp4, could be main or high profile.
Click to expand...
Click to collapse
There's no issue with the encoding as it plays fine on my media center and computer. The full movie is of course well over the FAT limit, but that shouldn't matter for the sample, right. It's a 1080p MKV [email protected]
Here's the mkvinfo output of the sample file:
Code:
+ EBML head
|+ EBML version: 1
|+ EBML read version: 1
|+ EBML maximum ID length: 4
|+ EBML maximum size length: 8
|+ Doc type: matroska
|+ Doc type version: 2
|+ Doc type read version: 2
+ Segment, size 90069522
|+ Seek head (subentries will be skipped)
|+ EbmlVoid (size: 4044)
|+ Segment information
| + Timecode scale: 1000000
| + Muxing application: libebml v1.0.0 + libmatroska v1.0.0
| + Writing application: mkvmerge v4.4.0 ('Die Wiederkehr') built on Oct 31 2010 21:52:48
| + Duration: 61.604s (00:01:01.604)
| + Date: Mon Nov 22 20:44:54 2010 UTC
| + Segment UID: 0xbc 0xee 0x26 0x58 0x42 0x96 0x31 0x6b 0xb9 0x0c 0x7b 0x5f 0x16 0x6d 0xc2 0x59
|+ Segment tracks
| + A track
| + Track number: 1
| + Track UID: 1
| + Track type: video
| + Lacing flag: 0
| + MinCache: 1
| + Codec ID: V_MPEG4/ISO/AVC
| + CodecPrivate, length 40 (h.264 profile: High @L4.0)
| + Default duration: 41.708ms (23.976 fps for a video track)
| + Video track
| + Pixel width: 1920
| + Pixel height: 800
| + Display width: 1920
| + Display height: 800
| + Content encodings
| + Content encoding
| + Content compression
| + Algorithm: 3 (header removal)
| + Settings: length 1, data: 0x00
| + A track
| + Track number: 2
| + Track UID: 2917809285
| + Track type: audio
| + Codec ID: A_DTS
| + Audio track
| + Sampling frequency: 48000
| + Channels: 6
| + Content encodings
| + Content encoding
| + Content compression
| + Algorithm: 3 (header removal)
| + Settings: length 4, data: 0x7f 0xfe 0x80 0x01
|+ EbmlVoid (size: 1123)
|+ Cluster
720p [email protected] w/AC3 audio plays perfectly fine in the stock player by the way.
I see you have cropped the video but that shouldnt make any difference, to be honest though if it plays on your stock I see nothing to worry about, I have several video players installed, I always check stock, then dice then rock to see which it plays best on. Stock is actually pretty good and has half decent codec support I find.
i agree with stoolzo. there is 4g limit on android devices. player is not my best partner. any player is not perfect. but i perfer to standard player. when video formats don't play on my phone, convert it. it is so easy.
alexcarterkarsus said:
Dice is cool, but can't say it is playing really flawlessly, for example, on a 720p mkv Band of Brother ep02, you can see slight but noticeable stutters, though then again, it indeed is the only player that can play out video/audio in sync while all others failed...
Click to expand...
Click to collapse
try diceplayer 1.1.6 ( not free ).
it play 1080p Band of Brothers ep02 with almost no shutter.
1080p Kill.Bill Sample clip test video
http://www.youtube.com/watch?v=ANf4oCNSxn0
just download a mkv dts video to play on diceplayer 1.1.2, video play good but no sound. what do i? need to download latest diceplayer or not? help plz?
Ok, so I split a movie in parts <4GB using mkvmerge (faster than recompress) and put it on the sd card. I also copied one part to internal mem to exclude the"slow sd" factor. Dice plays a bit choppy from both. However, the cpu never goes higher than about 40% when decoding. (goes for both Dice and stock players btw)
So as it's probably not a bandwidth or cpu bottleneck, what can it be?
Sent from my GT-I9100 using XDA Premium App
I've just started transencoding from 1080p to 720p (bit rate around 1500-2000) for playback on my transformer (i'm using moboplayer and mxplayer). The playback is ok but not quite as smooth as I would like (and is being handled by software).
I found this thread:
http://forum.xda-developers.com/showthread.php?t=1060825
-
that suggest things are simply broken (no video palyer will use hardware decoding) and that I should reencode the streams without b-frames (which will make them significantly larger).
-
I'm currently using mencoder but the guide suggest handbreak. Before I go through the exercise
I have a couple of questions:
Woudl things work better if I use mpeg-2 instead of h.263 ?
-
Will ICS make things better (i.e, should I not go with the larger non-b frame encodings) and just wait till ICS release in a few weeks?
-
Have there been any updates ?
-
Sadly my phone (razr) seems to be faster than my tablet and has no issues playing these videos (though if it uses hardware decoding the sound is way out of sync - by minutes - but if i use software decoding they are in sync - not sure why).
-
I've tested both avi containers and kmv containers - I think I prefer avi as it is smaller (though again I have to double check if the encodings were done with the same set of options)
jake21 said:
I've just started transencoding from 1080p to 720p (bit rate around 1500-2000) for playback on my transformer (i'm using moboplayer and mxplayer). The playback is ok but not quite as smooth as I would like (and is being handled by software).
Click to expand...
Click to collapse
FYI you can tell it to handle with h/w.
The players I tried refused to play it with h/w. Is there another way to force hardware decoding ?
goodintentions said:
FYI you can tell it to handle with h/w.
Click to expand...
Click to collapse
Try BS player lite.
Sent from my PC36100 using Tapatalk
try using h.264 not 263,
try remuxing the stream rather than recoding http://forum.xda-developers.com/showthread.php?t=1102922
its far quicker
bs lite coudlnt' play it using hardware deocding either:
First test file:
mencoder -mc 0 in.mkv -vf crop=1920:800:0:140 -af volume=10:0 -nosub -oac mp3lame -lameopts abr:br=256 -ovc xvid -vf scale=1280:720 -xvidencopts bitrate=1200 -o test3.avi
file test3.avi
test3.avi: RIFF (little-endian) data, AVI, 1280 x 720, 23.98 fps, video: XviD, audio: MPEG-1 Layer 3 (stereo, 48000 Hz)
Second test file:
mencoder in.mkv -af volume=15:0 -of lavf -oac mp3lame -lameopts abr:br=256 -ovc x264 -x264encopts preset=veryslow:tune=film:crf=15:frameref=15:bitrate=1500:fast_pskip=0:threads=auto -vf scale=1280:-10 -o test.mkv
--
mkvinfo test.mkv
+ EBML head
|+ EBML version: 1
|+ EBML read version: 1
|+ EBML maximum ID length: 4
|+ EBML maximum size length: 8
|+ Doc type: matroska
|+ Doc type version: 2
|+ Doc type read version: 2
+ Segment, size 1484420071
|+ Seek head (subentries will be skipped)
|+ EbmlVoid (size: 147)
|+ Segment information
| + Timecode scale: 1000000
| + Muxing application: Lavf53.3.0
| + Writing application: Lavf53.3.0
| + Segment UID: 0x77 0x2f 0xa7 0xdf 0x88 0x3d 0xd1 0xfd 0x43 0x75 0x02 0x94 0xad 0x96 0x87 0x0a
| + Duration: 6792.096s (01:53:12.096)
|+ Segment tracks
| + A track
| + Track number: 1
| + Track UID: 1
| + Lacing flag: 0
| + Language: und
| + Codec ID: V_MPEG4/ISO/AVC
| + Track type: video
| + Default duration: 41.708ms (23.976 fps for a video track)
| + Video track
| + Pixel width: 1280
| + Pixel height: 720
| + A track
| + Track number: 2
| + Track UID: 2
| + Lacing flag: 0
| + Language: und
| + Codec ID: A_MPEG/L3
| + Track type: audio
| + Audio track
| + Channels: 2
| + Sampling frequency: 48000
| + CodecPrivate, length 12
|+ Tags
| + Tag
| + Targets
| + Simple
| + Name: ENCODER
| + String: Lavf53.3.0
|+ Cluster
jake21 said:
bs lite coudlnt' play it using hardware deocding either:
Here is the command line I used to generate the file:
mencoder in.mkv -af volume=15:0 -of lavf -oac mp3lame -lameopts abr:br=256 -ovc x264 -x264encopts preset=veryslow:tune=film:crf=15:frameref=15:bitrate=1500:fast_pskip=0:threads=auto -vf scale=1280:-10 -o test.mkv
--
mkvinfo test.mkv
Click to expand...
Click to collapse
There's your problem; the mkv container is not supported for hardware decoding. With the current firmwares, I seem to recall only .mp4 is supported.
Here's my re-encode script that I use (I use ffmpeg ; I used to use mencoder, but it's weakness with non-avi formats pushed me to ffmpeg)
Code:
#!/bin/bash
# first argument is input file,
# second argument is output file or directory
# optional third argument is crf, lower is better quality, but I've had issues with large motion screens and values lower than 22
# optional 4th arg is audio bitrate, include k.
threads=2
[email protected]
# debug
#ffmpeg="echo ffmpeg"
ffmpeg="ffmpeg"
if [[ $3 = "" ]] ; then
VRATE="22"
else
VRATE="$3"
fi
if [[ $4 = "" ]] ; then
ARATE="96k"
else
ARATE="$4"
fi
#if [ -d "$2" || -L "$2" ] ; then
if [ -d "$2" ] ; then
echo $1 | grep "\." > /dev/null ; TRET=$?
if (( $TRET == 0 )) ; then
# name as a dot
oname="$2/`echo $1 | rev | cut -f 2- -d. | rev`.mp4"
else
oname="$2/$1.mp4"
fi
else
echo $2 | grep "\." > /dev/null ; TRET=$?
if (( $TRET == 0 )) ; then
# name as a dot
oname="`echo $2 | rev | cut -f 2- -d. | rev`.mp4"
else
oname="$2.mp4"
fi
fi
# tune Values available: film, animation, grain, stillimage, psnr, ssim, fastdecode, zerolatency.
# new ffmpeg crashes with -profile baseline
$ffmpeg -i $1 -acodec libfaac -ac 2 -ab $ARATE -vprofile baseline -vcodec libx264 -x264opts threads=$threads:level=31:keyint=250:keyint_min=25:bframes=0:crf=$VRATE $oname
The script is fairly simple, but I still find it quite useful. Note, don't do "script infile.mp4 . " as that will over write your source file, and I note I don't check for that. Maybe ffmpeg might, but it's a silly enough issue that I'm not fixing that.
I've never had an issue with mx player nor mobo player not doing hardware decoding (even via smb streaming with es file manager) , however since 3.11.1 on revolver, mobo player force closes when I quit, but I think that's a mobo player issue, as it often locks up my Galaxy-S with hardware, or software encoding in the latest version.
[update; ble the provided script did not work with ubuntu 11.10; I think they changed the switches for ffmpeg as it could not parse the switches after x264 nor baseline switch].
Ok thanks. Surprise the first example I have above, which is an avi file, did not work either
--
I'll look at what you have - i have to figure out how to scale down the image to 720p (from the man page it looks like ffmpeg does not support -vf scale=1280:-1)
-
Before I go to the effort of learning how to use ffmpeg; do you know if ICS will resolve this issue ?
[btw I have the same force-close issue with mobo on razr and transformer]
nobeagle said:
There's your problem; the mkv container is not supported for hardware decoding. With the current firmwares, I seem to recall only .mp4 is supported.
Here's my re-encode script that I use (I use ffmpeg ; I used to use mencoder, but it's weakness with non-avi formats pushed me to ffmpeg)
Code:
#!/bin/bash
# first argument is input file,
# second argument is output file or directory
# optional third argument is crf, lower is better quality, but I've had issues with large motion screens and values lower than 22
# optional 4th arg is audio bitrate, include k.
threads=2
[email protected]
# debug
#ffmpeg="echo ffmpeg"
ffmpeg="ffmpeg"
if [[ $3 = "" ]] ; then
VRATE="22"
else
VRATE="$3"
fi
if [[ $4 = "" ]] ; then
ARATE="96k"
else
ARATE="$4"
fi
#if [ -d "$2" || -L "$2" ] ; then
if [ -d "$2" ] ; then
echo $1 | grep "\." > /dev/null ; TRET=$?
if (( $TRET == 0 )) ; then
# name as a dot
oname="$2/`echo $1 | rev | cut -f 2- -d. | rev`.mp4"
else
oname="$2/$1.mp4"
fi
else
echo $2 | grep "\." > /dev/null ; TRET=$?
if (( $TRET == 0 )) ; then
# name as a dot
oname="`echo $2 | rev | cut -f 2- -d. | rev`.mp4"
else
oname="$2.mp4"
fi
fi
# tune Values available: film, animation, grain, stillimage, psnr, ssim, fastdecode, zerolatency.
# new ffmpeg crashes with -profile baseline
$ffmpeg -i $1 -acodec libfaac -ac 2 -ab $ARATE -vprofile baseline -vcodec libx264 -x264opts threads=$threads:level=31:keyint=250:keyint_min=25:bframes=0:crf=$VRATE $oname
The script is fairly simple, but I still find it quite useful. Note, don't do "script infile.mp4 . " as that will over write your source file, and I note I don't check for that. Maybe ffmpeg might, but it's a silly enough issue that I'm not fixing that.
I've never had an issue with mx player nor mobo player not doing hardware decoding (even via smb streaming with es file manager) , however since 3.11.1 on revolver, mobo player force closes when I quit, but I think that's a mobo player issue, as it often locks up my Galaxy-S with hardware, or software encoding in the latest version.
Click to expand...
Click to collapse
I could not get the provided script to work (ffmpeg would not accept the args). I did a little searching and saw one suggestion to install everythign from source and build - BUT the test encodings I made last night worked on both the phone and tablet using hardware encoding. On the phone mx player was fine; on the tablet mx player would only use software encoding but bs lite (which seemed pretty nice) worked fine and indicated it was using hardware decoding.
So I think I'm mostly set. the only issue I have is that sometimes mencoder dies on some streams with floating error when it reads the initial header - so I guess I should track that one down - when I get home tonight I'll post the args I used that worked and then ones that result in floating point error (on some streams).
Thanks for the help !
When I record a video on my G6 (from T-mobile) and set the video resolution to FHD 16:9 60fps, the resulting MP4 video files have an incorrect frame rate. I see 59.51fps, instead of the expected 60.00 or 59.94. The result of this is that any video that's more than a few seconds long has audio/video getting out of sync, and the de-sync gets worse further into the video.
Here is the (trimmed) output from the ffprobe utility (from the ffmpeg project):
Code:
> ffprobe take1.mp4
ffprobe version 2.8.11-0ubuntu0.16.04.1 Copyright (c) 2007-2017 the FFmpeg developers
libavutil 54. 31.100 / 54. 31.100
libavcodec 56. 60.100 / 56. 60.100
libavformat 56. 40.101 / 56. 40.101
libavdevice 56. 4.100 / 56. 4.100
libavfilter 5. 40.101 / 5. 40.101
libavresample 2. 1. 0 / 2. 1. 0
libswscale 3. 1.101 / 3. 1.101
libswresample 1. 2.101 / 1. 2.101
libpostproc 53. 3.100 / 53. 3.100
Input #0, mov,mp4,m4a,3gp,3g2,mj2, from 'take1.mp4':
Metadata:
major_brand : mp42
minor_version : 0
compatible_brands: isommp42
creation_time : 2017-10-22 01:04:08
location : [redacted]
location-eng : [redacted]
Duration: 00:02:43.91, start: 0.000000, bitrate: 24154 kb/s
Stream #0:0(eng): Video: h264 (High) (avc1 / 0x31637661), yuv420p(tv, bt709/bt709/smpte170m), 1920x1080, 23980 kb/s, SAR 1:1 DAR 16:9, 59.51 fps, 90k tbr, 90k tbn, 180k tbc (default)
Metadata:
creation_time : 2017-10-22 01:04:08
handler_name : VideoHandle
Stream #0:1(eng): Audio: aac (LC) (mp4a / 0x6134706D), 48000 Hz, stereo, fltp, 155 kb/s (default)
Metadata:
creation_time : 2017-10-22 01:04:08
handler_name : SoundHandle
I was able to fix the time stamps (PTSs) using the mkvmerge utility, but that isn't the best solution. This does seem like an actual bug. Here's hoping that anyone from LG's engineering team checks this subreddit!