Database Info

Video recording - little question

I'm thinking about buying i9003. I was wondering if someone could tell me the video recording length that I can shot with an sd of 8gb at 720p. Also any other number card size would be good to have an idea. Thank you in advance.

Cellulario the video recording on this phon is quite amazing this phone records videos at HD 720p.
i'm attaching media info of a small video i made with my phone.
Code:
General
Complete name : L:\DCIM\Camera\video-2011-07-21-08-18-11.mp4
Format : MPEG-4
Format profile : 3GPP Media Release 4
Codec ID : 3gp4
File size : 17.2 MiB
Duration : 12s 52ms
Overall bit rate : 12.0 Mbps
Video
ID : 2
Format : MPEG-4 Visual
Format profile : [email protected]
Format settings, BVOP : Yes
Format settings, QPel : No
Format settings, GMC : No warppoints
Format settings, Matrix : Default (H.263)
Codec ID : 20
Duration : 12s 52ms
Bit rate mode : Variable
Bit rate : 12.0 Mbps
Maximum bit rate : 19.8 Mbps
Width : 1 280 pixels
Height : 720 pixels
Display aspect ratio : 16:9
Frame rate mode : Variable
Frame rate : 29.124 fps
Minimum frame rate : 2.688 fps
Maximum frame rate : 37.037 fps
Color space : YUV
Bit depth : 8 bits
Scan type : Progressive
Compression mode : Lossy
Bits/(Pixel*Frame) : 0.446
Stream size : 17.1 MiB (99%)
Language : English
Audio
ID : 1
Format : AAC
Format/Info : Advanced Audio Codec
Format profile : LC
Codec ID : 40
Duration : 11s 648ms
Bit rate mode : Constant
Bit rate : 66.15 Kbps
Channel(s) : 1 channel
Channel positions : Front: C
Sampling rate : 16.0 KHz
Compression mode : Lossy
Stream size : 90.0 KiB (1%)
Language : English

the video recordin has cont. autofocus and it works lyk a charm
Sent from my GT-I9003 using XDA App

How many minutes can I squeeze into 8gb?

Cellulario said:
How many minutes can I squeeze into 8gb?
Click to expand...
Click to collapse
dude can't you do the calculations ur self ?
13 min of video aprox size 17MB now u do the rest of the calculation
edit : 1000mb = 1gb
8000mb = 8gb

Yesterday I shoot video on birthday. It create more than 200 mb file in 2 min 30 sec video. Then I have to convert that to 30 mb file for facebook upload :-/
Sent from my GT-I9003 using Tapatalk

[TESTING] Infuse 4G Video Recording & Playback Tests With Stock & Custom Roms

　
Infuse Video Camera Recording Tests With Stock And Custom Roms​
For those of you who are interested in the quality of your homemade video recordings and playback
please read on. Check out these tests which were made with all the stock and custom roms.
(these tests were conducted using a tripod and good indoor lighting)
Stock Froyo 2.2 Rom: Excellent very smooth, virtually no hesitation or lag during recording and playback of moving objects on preview screen.
(Ultimate Unbrick - Return to Stock)
Froyo 2.2.1 Custom Roms:Excellent very smooth, virtually no hesitation or lag during recording or playback of moving objects on preview screen.
(Infused 1.5.3, Infused 1.6.0, Refuse 1.7, Bionix Infinity 2.0)
Basically all the Froyo 2.2.x based custom roms all have the same results. Excellent video recording quality, smooth and virtually no noticeable hesitation or lag while recording and playback of homemade video. (I have tested different formats, 720p, 640x480 etc.)
Gingerbread Based Roms: Testing Rogers Gingerbread 2.3.x based Infuse i997 custom roms such as Infuse 2.1, CyanogenMod 7 and Hellraiser with i9000 Gingerbread based roms the video recording and playback quality with these roms were very poor with constant jerkyness, hesitation and lag due to only capturing up to 15fps like many cheaper cell phones do.
(even tried "CWM_UXKG3-rooted-de-odexed-updated_no_bootloaders_v2 & Odin_UXKG3_rooted_no_bootloaders_v2" GB roms with same results.)
These same recording/playback tests using Froyo based roms have no jerkyness, hesitation or lag due to capturing the full 30fps as advertised in the Infuse i997 specifications. (very noticable differences when comparing)
The Real Test: Record video while in Froyo based rom, flash any Gingerbread based rom, record video in gingerbread based rom then playback and compare the two videos. (this will take some time to test but for those who care enough about video recording quality it will be worth while)
You can easily see this hesitation/jerkyness while in a Gingerbread rom and the lack of hesitation/jerkyness while in Froyo roms by just starting up the camera app, switch to video camera and turning the phone in landscape mode moving slowly from left to right / right to left then speeding up little by little while looking thru viewfinder at objects on your table or desk without even starting the actual video recording.
It took me over 3 hours to conduct all these tests, I wanted to be sure that I tested the Froyo stock and custom roms and all the Rogers Gingerbread based custom roms available for Infuse i997.
These tests were all conducted in the exact same lighting conditions indoors with good lighting and using a tripod.
All recording and playback tests were made with homemade videos, not movies or other videos downloaded from the web.
It would be very interesting to find out other peoples video recording and playback results and experiences under similar conditions with these Froyo/Gingerbread based roms.
I have a strong suspicion that until the DEVS get their hands on the stock AT&T retail Gingerbread rom made for Samsung Infuse i997 we will need to choose between the stock Froyo/custom Froyo roms with excellent quality homemade video recordings and playback or the much faster Gingerbread based custom roms with all the extra bells and whistles (features and options) but lacking the video record and playback quality we have in Froyo based roms.
All the DEVS here in this Infuse 4G forum are constantly working and striving to improve these custom roms for our phones and have done and are doing an excellent and wonderful job. (thanks!)
So it’s up to each of us to choose which roms to use and how important quality video recordings and playbacks are to us.
Many people here may not use the camera in the phone much at all so video recording quality is not important to them
however for those of us who do a lot of video recording with our phone and want the very best possible quality this can
and will be of great importance.
I would really like to read other people’s opinions and comments about this.
If you are interested in seeing the technical details & results with exact framerates you might want to test
using "MediaInfo". It's excellent way to test & compare results between Froyo & Gingerbread based roms.
It's fast and easy to use. It adds mediainfo into explorer's shell options.

Other than visual inspection.. Watching the vids...have you torn apart the vids and looked for specific differences in codecs, bitrate etc?
Sent from my GT-I9000 using XDA App

Video Bitrate & Codecs
00mred00 said:
Other than visual inspection.. Watching the vids...have you torn apart the vids and looked for specific differences in codecs, bitrate etc
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
I wish I were technically oriented enough to check for specific codecs & bitrate differences but unfortunatly I am not. However I am trying to learn.
It seems to me as if not only the frame rates (just visually speaking) seems to drop to a low enough level so most anyone conducting tests like this could easily see and compare differences, but even just looking into the viewfinder without recording anything it seems like either frame rates get dropped and/or the screen is not refreshing itself as it normally does with Froyo based roms.
Right now I am using GTG's Infuse 1.5.3 which is a Froyo based custom rom, it may not be the latest and greatest of all custom roms for the Infuse i997 but since quality video recording is a must-have for me it's my first choice as of now.
It's approx. 2X faster than stock Froyo rom and has a lot of extra features and options compared to stock.
I just hope that the DEVS get the complete FULL AT&T Stock Infuse GB rom soon so perhaps it can also do quality video recordings just as good if not better than AT&T Froyo based roms.
Hopefully one of these days I will have learned enough about these things so I could make a more informed and techincal explaination to all these tests I made.
I really love photography, especially now since the Infuse is so good at video recording, just about as good as many camcorders and I always have my phone with me wherever I go.
Thanks for your comment.

Looks like u answered my question about the video recording its a Rogers rom issue I take it..I'm running a gb rom on my infuse and a froyo rom on my wife's infuse and compared the 2 cause I'm always using my camera to record my lil girls.. the froyo rom records twice as fast as gb roms..frames per second..like u I have tried all gb roms too and have had the same issue which really sucks..love the bells and whistles of gb but hate the recording so I keep going back to infused 1.5.3 froyo.but thanks for answering my question cause I was getting really frustrated with it..also I work for Att and a gb update is coming very soon..read it today on our internal stuff..

Looks Like I am NOT Alone!
Task775 said:
Looks like u answered my question about the video recording its a Rogers rom issue I take it..I'm running a gb rom on my infuse and a froyo rom on my wife's infuse and compared the 2 cause I'm always using my camera to record my lil girls.. the froyo rom records twice as fast as gb roms..frames per second..like u I have tried all gb roms too and have had the same issue which really sucks..love the bells and whistles of gb but hate the recording so I keep going back to infused 1.5.3 froyo.but thanks for answering my question cause I was getting really frustrated with it..also I work for Att and a gb update is coming very soon..read it today on our internal stuff..
Click to expand...
Click to collapse
So you are running the same rom as I am, it looks like you have done your homework about this as well as I have. (testing video recordings).
Well at least now I know that I am not the only one who has noticed this video recording issue which by the looks of it is not much of a issue for most people here in this forum. So far I have not read any posts here which mentions this video recording issue. (except yours)
I guess that most people here just do not pay much attention to the video quality which our Samsung Infuse is capable of or don't use the camera part very often to notice the differences in frame rates. (big difference)
Personally one of the main reasons for getting the Infuse 4G for me was the video recording quality it can produce.
(for the price we pay for the Infuse it better have excellent video recording quality)
I am certain that after the DEVS get their hands on a 100% stock AT&T Gingerbread rom that within a couple days more or less this video recording issue will be a thing of the past and we can move up to Gingerbread custom roms and have at least as good quality video recordings if not better than these Froyo based custom roms which we are using now.
Thanks for your comment!

There is a program was used with the EVO to show in that case (same type of suspicions) that there was actually no difference.
I will see If I can find it...
it was mmpeg something or another I believe

For reference, here's a MediaInfo dump of a video I took on June 09 (on a Froyo ROM):
Code:
General
Complete name : C:\video-2011-06-09-17-08-30.mp4
Format : MPEG-4
Format profile : 3GPP Media Release 4
Codec ID : 3gp4
File size : 249 MiB
Duration : 2mn 53s
Overall bit rate : 12.1 Mbps
Video
ID : 2
Format : AVC
Format/Info : Advanced Video Codec
Format profile : [email protected]
Format settings, CABAC : No
Format settings, ReFrames : 1 frame
Format settings, GOP : M=1, N=30
Muxing mode : Container [email protected]
Codec ID : avc1
Codec ID/Info : Advanced Video Coding
Duration : 2mn 53s
Bit rate mode : Variable
Bit rate : 12.0 Mbps
Width : 1 280 pixels
Height : 720 pixels
Display aspect ratio : 16:9
Color space : YUV
Chroma subsampling : 4:2:0
Bit depth : 8 bits
Scan type : Progressive
Stream size : 248 MiB (99%)
Language : English
Material_Duration : 173098
Material_StreamSize : 260103689
Material_FrameCount : 5201
Audio
ID : 1
Format : AAC
Format/Info : Advanced Audio Codec
Format profile : LC
Codec ID : 40
Duration : 2mn 52s
Bit rate mode : Variable
Bit rate : 60.3 Kbps
Maximum bit rate : 68.9 Kbps
Channel(s) : 1 channel
Channel positions : Front: C
Sampling rate : 16.0 KHz
Compression mode : Lossy
Stream size : 1.24 MiB (0%)
Language : English
Material_Duration : 172900
Material_StreamSize : 1295557
Although it's not specified in the container, the video plays at 30 frames per second.

Infuse 4G Video Recording
00mred00 said:
There is a program was used with the EVO to show in that case (same type of suspicions) that there was actually no difference.
I will see If I can find it...
it was mmpeg something or another I believe
Click to expand...
Click to collapse
Well you just about made my point, I am writing about homemade recordings, and the format the camera uses for video recording is NOT MPG.
Our cameras record video in 3GP video format.
I know that there is nothing wrong with the playback of avi/mpg/mpeg4/mkv/divx formats. The playback using those formats are excellent, but those are not the formats our phones use to record homemade videos.
When we download or watch videos or movies from internet and different sources like YouTube or if we encode DVDs and play them on our phones they all play perfectly well with close to 30 FPS.
It's just like I said in the original posting, the HOMEMADE videos which we record on our phones are not up to par at all if we use the current Gingerbread based roms.
With Froyo based roms these Homemade videos are just about as as good as watching HD movies on TV. (sometimes better).
Make the test yourself. I have Avatar the full movie (AVI format) on my external sdcard and it plays 100% perfect on either Gingerbread or Froyo based roms. (but its not a homemade video recorded on the phone)...

Have you guys tried comparing the videos on a computer instead of just playing them back on the phone? Maybe the issue is with video playback only and not with the actual recording.

Oops, this post was in error...

Also a mediainfo dump from a gingerbread recording could be helpful.

MediaInfo Dumps
gtg465x said:
Also a mediainfo dump from a gingerbread recording could be helpful.
Click to expand...
Click to collapse
Ok below is a mediainfo dump from your Infuse 2.1.0 custom GB rom.
------------------------------------------------------------------------------
General
Complete name : 1.mp4
Format : MPEG-4
Format profile : 3GPP Media Release 4
Codec ID : 3gp4
File size : 12.9 MiB
Duration : 1mn 0s
Overall bit rate : 1 796 Kbps
Video
ID : 2
Format : AVC
Format/Info : Advanced Video Codec
Format profile : [email protected]
Format settings, CABAC : No
Format settings, ReFrames : 1 frame
Format settings, GOP : M=1, N=30
Muxing mode : Container [email protected]
Codec ID : avc1
Codec ID/Info : Advanced Video Coding
Duration : 1mn 0s
Bit rate mode : Variable
Bit rate : 1 732 Kbps
Width : 720 pixels
Height : 480 pixels
Display aspect ratio : 3:2
Frame rate mode : Variable
Frame rate : 14.990 fps
Minimum frame rate : 5.181 fps
Maximum frame rate : 15.625 fps
Standard : NTSC
Color space : YUV
Chroma subsampling : 4:2:0
Bit depth : 8 bits
Scan type : Progressive
Bits/(Pixel*Frame) : 0.334
Stream size : 12.4 MiB (96%)
Language : English
Material_Duration : 60174
Material_StreamSize : 13026738
Material_FrameCount : 901
Audio
ID : 1
Format : AAC
Format/Info : Advanced Audio Codec
Format profile : LC
Codec ID : 40
Duration : 1mn 0s
Bit rate mode : Variable
Bit rate : 61.2 Kbps
Maximum bit rate : 70.0 Kbps
Channel(s) : 1 channel
Channel positions : Front: C
Sampling rate : 16.0 KHz
Compression mode : Lossy
Stream size : 448 KiB (3%)
Language : English
Material_Duration : 60255
Material_StreamSize : 459307
------------------------------------------------------------------------------------------
Below is a mediainfo dump from your Infuse 1.5.3 custom Froyo rom.
-------------------------------------------------------------------------------
General
Complete name : 2.mp4
Format : MPEG-4
Format profile : 3GPP Media Release 4
Codec ID : 3gp4
File size : 13.0 MiB
Duration : 31s 184ms
Overall bit rate : 3 505 Kbps
Video
ID : 2
Format : AVC
Format/Info : Advanced Video Codec
Format profile : [email protected]
Format settings, CABAC : No
Format settings, ReFrames : 1 frame
Format settings, GOP : M=1, N=30
Muxing mode : Container [email protected]
Codec ID : avc1
Codec ID/Info : Advanced Video Coding
Duration : 31s 184ms
Bit rate mode : Variable
Bit rate : 3 440 Kbps
Width : 720 pixels
Height : 480 pixels
Display aspect ratio : 3:2
Frame rate mode : Variable
Frame rate : 29.919 fps
Minimum frame rate : 25.641 fps
Maximum frame rate : 33.333 fps
Standard : NTSC
Color space : YUV
Chroma subsampling : 4:2:0
Bit depth : 8 bits
Scan type : Progressive
Bits/(Pixel*Frame) : 0.333
Stream size : 12.8 MiB (98%)
Language : English
Material_Duration : 31217
Material_StreamSize : 13407780
Material_FrameCount : 933
Audio
ID : 1
Format : AAC
Format/Info : Advanced Audio Codec
Format profile : LC
Codec ID : 40
Duration : 31s 70ms
Bit rate mode : Variable
Bit rate : 60.4 Kbps
Maximum bit rate : 70.1 Kbps
Channel(s) : 1 channel
Channel positions : Front: C
Sampling rate : 16.0 KHz
Compression mode : Lossy
Stream size : 228 KiB (2%)
Language : English
Material_Duration : 31135
Material_StreamSize : 234157
--------------------------------------------------------------
As you can see, its a big difference, I am really surprised that I have not yet seen anyone writing anything about this.
(unless I missed something)
It's not just your custom roms, its ALL the Rogers based custom GB roms which I tested for hours today, (even the CM7 has the same problem) then I tested Froyo stock/Froyo custom and saw a world of difference even without checking it out in mediainfo.
Hope this helps! (looking forward to a custom GB rom which has 25-29fps)
Have a great day and keep up the good work with all the custom roms.

Comparing videos on computer
gtg465x said:
Have you guys tried comparing the videos on a computer instead of just playing them back on the phone? Maybe the issue is with video playback only and not with the actual recording.
Click to expand...
Click to collapse
I have tried that too gtg, I even copied 4-5 different homemade videos which was recorded on GB based custom rom from phone to computer and they all have the same flaw (dropping 1/2 the frames).
I did the same thing with homemade video recorded when on a Froyo based custom rom and the results were nothing short of stunning. BIG difference.
If you make a homemade video recording of a person sitting on a chair and basically not moving around much or moving very slowly except for talking
then it may be a bit more diffiult to test and compare.
I found the best way to conduct recording tests is to have the subject walk back and forth left to right of the camera 5-6 times approx. 6-8 ft from the camera in at least average lighting and while holding the camera real still.
(tripod is best)
Another good test is if you can PAN the camera left to right / right to left slowly and gradually picking up speed as you view small objects on a desk or table.
I have about 6 full length movies on my phone and all play flawlessly. (GB or Froyo)
Even the playback on GB custom roms play back flawlessly if using homemade videos recorded with Froyo rom installed. So the playback is not the problem at all. (my adult videos play flawlessly too )

Thanks for making the text color the same as the background...
Sent from my SGH-I997

Misterjunky said:
Well you just about made my point, I am writing about homemade recordings, and the format the camera uses for video recording is NOT MPG.
Our cameras record video in 3GP video format.
I know that there is nothing wrong with the playback of avi/mpg/mpeg4/mkv/divx formats. The playback using those formats are excellent, but those are not the formats our phones use to record homemade videos.
When we download or watch videos or movies from internet and different sources like YouTube or if we encode DVDs and play them on our phones they all play perfectly well with close to 30 FPS.
It's just like I said in the original posting, the HOMEMADE videos which we record on our phones are not up to par at all if we use the current Gingerbread based roms.
With Froyo based roms these Homemade videos are just about as as good as watching HD movies on TV. (sometimes better).
Make the test yourself. I have Avatar the full movie (AVI format) on my external sdcard and it plays 100% perfect on either Gingerbread or Froyo based roms. (but its not a homemade video recorded on the phone)...
Click to expand...
Click to collapse
haha...I made no reference to what we were recording in...the name of the program we used to get the media dump was mpg something another

Mediainfo
00mred00 said:
haha...I made no reference to what we were recording in...the name of the program we used to get the media dump was mpg something another
Click to expand...
Click to collapse
If you want a media dump here is what most others are using.
"Mediainfo" here is the link just incase you want to try it out:
http://surfnet.dl.sourceforge.net/p.../0.7.48/MediaInfo_GUI_0.7.48_Windows_i386.exe
Its excellent, fast and easy to use.. It adds mediainfo into explorer's shell commands.

Misterjunky said:
If you want a media dump here is what most others are using.
"Mediainfo" here is the link just incase you want to try it out:
http://surfnet.dl.sourceforge.net/p.../0.7.48/MediaInfo_GUI_0.7.48_Windows_i386.exe
Its excellent, fast and easy to use.. It adds mediainfo into explorer's shell commands.
Click to expand...
Click to collapse
I will check it out! need to find the 64 bit version though

I'm looking into the issue. Hopefully it can be fixed by editing mediaprofiles.xml, but I'm suspecting it might be a kernel issue, or even worse, an issue in one of the libs. It's clear that the Gingerbread firware shipping on Rogers Infuses was not ready for prime time. Hopefully the AT&T Gingerbread release doesn't have all of these problems.

Thanks for sharing your research and findings Misterjunky. I shot video* last week on vacation and was thinking "I don't remember that jerkiness??".
Now I know what to do to resolve (v1.5.3)...since I'm going backpacking for 6 days post Labor day and desire the excellent video capabilities of my Infuse 4G (I carry extra, cheap ebay batteries which seem to work very well).
*Currrent Infused V2...soon to be V1.5.3 (time to do some reading on how to go backwards...I'll figure it out, if nothing else I can return to stock then upgrade from there...I know how to do that ).
thanks again

re: video recording issue
gtg465x said:
I'm looking into the issue. Hopefully it can be fixed by editing mediaprofiles.xml, but I'm suspecting it might be a kernel issue, or even worse, an issue in one of the libs. It's clear that the Gingerbread firware shipping on Rogers Infuses was not ready for prime time. Hopefully the AT&T Gingerbread release doesn't have all of these problems.
Click to expand...
Click to collapse
Here is an idea which may be helpful to you before you start digging into the problem.
Why not ask someone who purchased a Rogers Samsung Infuse i997 which was shipped
with Gingerbread rom from the factory and and ask them to do a mediainfo dump to see
if the 100% stock retail Rogers i997 also has this issue with video recording.
It might be a good place to start.

[STICKY] Tegra K1 support

Hi Devs, any plans to include support for the Tegra K1 soc? I just bought a Xiaomi Mipad and MXPlayer is proving to be flaky with frequent crashes and closing. It also shows strange behavior when playing back HI10p videos, the native player on the Mipad fails to play Hi10p but MxPlayer can be invoked to use HW or HW+ on the Hi10p videos. However I see colors bleeding in the video so I presume that MXplayer is forcing the Tegra K1 to play Hi10p as 8 bit h264 as the effect looks similar on my set top box.
Just an FYI for those hoping the Tegra K1 would be fast enough to play back Hi10p 1080p video in software mode it still stutters. If you need some debug logs etc then pls send me instructions to get those.

Kantana said:
Hi Devs, any plans to include support for the Tegra K1 soc? I just bought a Xiaomi Mipad and MXPlayer is proving to be flaky with frequent crashes and closing. It also shows strange behavior when playing back HI10p videos, the native player on the Mipad fails to play Hi10p but MxPlayer can be invoked to use HW or HW+ on the Hi10p videos. However I see colors bleeding in the video so I presume that MXplayer is forcing the Tegra K1 to play Hi10p as 8 bit h264 as the effect looks similar on my set top box.
Just an FYI for those hoping the Tegra K1 would be fast enough to play back Hi10p 1080p video in software mode it still stutters. If you need some debug logs etc then pls send me instructions to get those.
Click to expand...
Click to collapse
Just an update I tested Hi10p and h265 with VLC and it looks like the Tegra K1 can hw accelerate Hi10p but not h265, however both codecs @ 1080p plays smoothly with VLC on the Mipad. Devs pls update the MXplayer for the Tegra K1 soc

Ok, have narrowed down the cause of crashing and closing to the launcher. If HW+ is enabled this will happen 50% of the time. If I enable HW+ but not check the boxes for local or network play it will start the video normally in HW mode. But there is no audio and I need to manually choose HW+ mode. If it doesn't crash to the launcher then audio will play. I get regular MX player has stopped when I exit MXplayer after using HW+.
I see the same behavior for Diceplayer so assume that it also uses the same methods for hardware acceleration. VLC beta has no issues even with full acceleration and YUV color space. Devs pls look into this and if you need diagnostic or logging info we can assist as there are some MiPad owners out there that are testing this unit right now:
http://forum.xda-developers.com/showthread.php?p=54045235

Kantana said:
Ok, have narrowed down the cause of crashing and closing to the launcher. If HW+ is enabled this will happen 50% of the time. If I enable HW+ but not check the boxes for local or network play it will start the video normally in HW mode. But there is no audio and I need to manually choose HW+ mode. If it doesn't crash to the launcher then audio will play. I get regular MX player has stopped when I exit MXplayer after using HW+.
I see the same behavior for Diceplayer so assume that it also uses the same methods for hardware acceleration. VLC beta has no issues even with full acceleration and YUV color space. Devs pls look into this and if you need diagnostic or logging info we can assist as there are some MiPad owners out there that are testing this unit right now:
http://forum.xda-developers.com/showthread.php?p=54045235
Click to expand...
Click to collapse
If your video plays well in HW mode but not getting audio means the audio codec is not supported by your device.
You can enable SW audio from Settings 》 Decoder to play audio through ffmpeg. Video will be decoded by the hardware as usual.
---------- Post added at 06:14 PM ---------- Previous post was at 06:07 PM ----------
@Kantana
Use mx log collector app immediately after crash to collect the logs and attach here...!!!

That could be true since the audio is DTS which is not supported normally. However I can play back the video with audio from the system video player which implies that both video and audio are supported by the hardware.

Ok here is the first crash when HW+ has been enabled and used. When I exit Mxplayer then it will generate this crash. Logs attached

Here is the 2nd crash when HW+ has been enabled and ticked for local and network. I click on the file and choose mxplayer to play the file, it starts then crashes.

The system details for these 2 crashes:
=========================
Manufacturer: Xiaomi
Model: MI PAD
Brand: Xiaomi
Version: 4.4.2 (REL)
Build: Xiaomi/mocha/mocha:4.4.2/KOT49H/KXFCNBF2.0:user/release-keys
Kernel: Linux version 3.10.24-g5858f73 ([email protected]) (gcc version 4.7 (GCC) ) #1 SMP PREEMPT Fri Jun 27 10:07:03 CST 2014
CPU: 4 core(s) 2.22 GHz
CPU architecture: 7
CPU features: swp half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt
Board platform: tegra
Instruction set: armeabi-v7a (+armeabi)
Resolution: 1536 x 2048
Available screen size (DIP): 768 x 999 (smallest: 768)
Tablet: true
Screen size: X-Large
Density: 2.0 (320)
Font scale: 1.0
Hardware main button: false
Locale: en_US
Total memory: 1982052 kB
Free memory: 249704 kB
=========================
=========================
Manufacturer: Xiaomi
Model: MI PAD
Brand: Xiaomi
Version: 4.4.2 (REL)
Build: Xiaomi/mocha/mocha:4.4.2/KOT49H/KXFCNBF2.0:user/release-keys
Kernel: Linux version 3.10.24-g5858f73 ([email protected]) (gcc version 4.7 (GCC) ) #1 SMP PREEMPT Fri Jun 27 10:07:03 CST 2014
CPU: 4 core(s) 2.22 GHz
CPU architecture: 7
CPU features: swp half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt
Board platform: tegra
Instruction set: armeabi-v7a (+armeabi)
Resolution: 1536 x 2048
Available screen size (DIP): 768 x 999 (smallest: 768)
Tablet: true
Screen size: X-Large
Density: 2.0 (320)
Font scale: 1.0
Hardware main button: false
Locale: en_US
Total memory: 1982052 kB
Free memory: 151892 kB
=========================

Kantana said:
Hi Devs, any plans to include support for the Tegra K1 soc? I just bought a Xiaomi Mipad and MXPlayer is proving to be flaky with frequent crashes and closing. It also shows strange behavior when playing back HI10p videos, the native player on the Mipad fails to play Hi10p but MxPlayer can be invoked to use HW or HW+ on the Hi10p videos. However I see colors bleeding in the video so I presume that MXplayer is forcing the Tegra K1 to play Hi10p as 8 bit h264 as the effect looks similar on my set top box.
Just an FYI for those hoping the Tegra K1 would be fast enough to play back Hi10p 1080p video in software mode it still stutters. If you need some debug logs etc then pls send me instructions to get those.
Click to expand...
Click to collapse
I am in the same problem,Mipad,the system player is ok to run the video,but with MX,the HW+ mode usually crashed,when using HW mode,there is a chance the audio have problem,I need to use the SW mode for the audio.
I checked the video type that have the HW+ and no audio problem,they are H264 and AC3,strange thing is that some other video in the same type is ok to run with HW+ Mode,i am sure the video itself is no problem,i have checked it with my nexus 7 PAD.
Maybe it is the system's problem

07-10 20:52:55.872 12496 12679 F libc : invalid address or address of corrupt block 0x731648e8 passed to dlfree
07-10 20:52:55.872 12496 12679 F libc : Fatal signal 11 (SIGSEGV) at 0xdeadbaad (code=1), thread 12679 (.videoplayer.ad)
On both logs there is a fatal error from libc
@bleu8888
Can you look at the issue?
---------- Post added at 01:01 AM ---------- Previous post was at 12:30 AM ----------
@kantana @donkeyear
I have discussed with the developer about your issue.
As I said libc fatal error may be due to a compiler error.
In another device we had similar crashing which is fixed in the latest test build by using the latest compiler.
Can you test the latest test build from the following link & report here. It will be helpful to resolve the issue.
https://sites.google.com/site/mxvpen/translation/test-build

ktsamy said:
07-10 20:52:55.872 12496 12679 F libc : invalid address or address of corrupt block 0x731648e8 passed to dlfree
07-10 20:52:55.872 12496 12679 F libc : Fatal signal 11 (SIGSEGV) at 0xdeadbaad (code=1), thread 12679 (.videoplayer.ad)
On both logs there is a fatal error from libc
@bleu8888
Can you look at the issue?
---------- Post added at 01:01 AM ---------- Previous post was at 12:30 AM ----------
@kantana @donkeyear
I have discussed with the developer about your issue.
As I said libc fatal error may be due to a compiler error.
In another device we had similar crashing which is fixed in the latest test build by using the latest compiler.
Can you test the latest test build from the following link & report here. It will be helpful to resolve the issue.
https://sites.google.com/site/mxvpen/translation/test-build
Click to expand...
Click to collapse
No luck, still crashing randomly with test build. If HW+ is enabled it's crashing 50% of the time. It looks stable with HW+ off but sometimes no sound even with files where the audio codec is supported in hardware eg mp3 or ac3. When I enable HW+ then same random crashing.

Kantana said:
No luck, still crashing randomly with test build. If HW+ is enabled it's crashing 50% of the time. It looks stable with HW+ off but sometimes no sound even with files where the audio codec is supported in hardware eg mp3 or ac3. When I enable HW+ then same random crashing.
Click to expand...
Click to collapse
I have already conveyed this issue.
We had same issue when Tegra 3 was released. But, even NVidia people where unable to fix. Finally it was fixed by a volunteer on ffmpeg.
The developer will try to resolve the issue as soon as possible....!!
Till that use SW audio by default if you are encounter audio issues in HW mode
---------- Post added at 01:38 AM ---------- Previous post was at 01:36 AM ----------
@Kantana
Can you collect a log when you face audio issue in hw mode?

ktsamy said:
I have already conveyed this issue.
We had same issue when Tegra 3 was released. But, even NVidia people where unable to fix. Finally it was fixed by a volunteer on ffmpeg.
The developer will try to resolve the issue as soon as possible....!!
Till that use SW audio by default if you are encounter audio issues in HW mode
---------- Post added at 01:38 AM ---------- Previous post was at 01:36 AM ----------
@Kantana
Can you collect a log when you face audio issue in hw mode?
Click to expand...
Click to collapse
Hi ktsamy, here are the logs from playing a video in HW mode with no audio:
=========================
Manufacturer: Xiaomi
Model: MI PAD
Brand: Xiaomi
Version: 4.4.2 (REL)
Build: Xiaomi/mocha/mocha:4.4.2/KOT49H/KXFCNBF2.0:user/release-keys
Kernel: Linux version 3.10.24-g5858f73 ([email protected]) (gcc version 4.7 (GCC) ) #1 SMP PREEMPT Fri Jun 27 10:07:03 CST 2014
CPU: 4 core(s) 2.22 GHz
CPU architecture: 7
CPU features: swp half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt
Board platform: tegra
Instruction set: armeabi-v7a (+armeabi)
Resolution: 1536 x 2048
Available screen size (DIP): 768 x 999 (smallest: 768)
Tablet: true
Screen size: X-Large
Density: 2.0 (320)
Font scale: 1.0
Hardware main button: false
Locale: en_US
Total memory: 1982052 kB
Free memory: 151352 kB
=========================
Format : Matroska
Format version : Version 2
File size : 2.18 GiB
Duration : 44mn 1s
Overall bit rate : 7 084 Kbps
Encoded date : UTC 2012-10-11 10:07:06
Writing application : mkvmerge v2.9.0 ('Moanin'') built on May 22 2009 17:46:31
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 : 5 frames
Codec ID : V_MPEG4/ISO/AVC
Duration : 44mn 1s
Bit rate : 6 439 Kbps
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.291
Stream size : 1.94 GiB (89%)
Writing library : x264 core 128 r2216 198a7ea
Encoding settings : cabac=1 / ref=5 / deblock=1:-1:-1 / analyse=0x3:0x113 / me=umh / subme=7 / psy=1 / psy_rd=1.00:0.00 / mixed_ref=1 / me_range=16 / chroma_me=1 / trellis=1 / 8x8dct=1 / cqm=0 / deadzone=21,11 / fast_pskip=1 / chroma_qp_offset=-2 / threads=12 / lookahead_threads=2 / sliced_threads=0 / nr=0 / decimate=1 / interlaced=0 / bluray_compat=0 / constrained_intra=0 / bframes=3 / b_pyramid=2 / b_adapt=2 / b_bias=0 / direct=3 / weightb=1 / open_gop=0 / weightp=2 / keyint=250 / keyint_min=23 / scenecut=40 / intra_refresh=0 / rc_lookahead=40 / rc=2pass / mbtree=1 / bitrate=6439 / ratetol=1.0 / qcomp=0.60 / qpmin=0 / qpmax=69 / qpstep=4 / cplxblur=20.0 / qblur=0.5 / vbv_maxrate=50000 / vbv_bufsize=50000 / nal_hrd=none / ip_ratio=1.40 / aq=1:1.00
Language : English
Default : Yes
Forced : No
Audio
ID : 2
Format : AC-3
Format/Info : Audio Coding 3
Mode extension : CM (complete main)
Format settings, Endianness : Big
Codec ID : A_AC3
Duration : 44mn 1s
Bit rate mode : Constant
Bit rate : 640 Kbps
Channel(s) : 6 channels
Channel positions : Front: L C R, Side: L R, LFE
Sampling rate : 48.0 KHz
Bit depth : 16 bits
Compression mode : Lossy
Stream size : 202 MiB (9%)
Language : English
Default : Yes
Forced : No

It looks like an issue of hw+ decoder.
I ordered a MiPad and now waiting.

bleu8888 said:
It looks like an issue of hw+ decoder.
I ordered a MiPad and now waiting.
Click to expand...
Click to collapse
Well this has taught me to not take anything for granted with chinese tablets. They appear to have so many bugs on release and not subtle ones but major functions. You'll have a ball working around all these oversights. I'm quite pleased with the Mipad subject to them fixing these bugs.

Kantana said:
Well this has taught me to not take anything for granted with chinese tablets. They appear to have so many bugs on release and not subtle ones but major functions. You'll have a ball working around all these oversights. I'm quite pleased with the Mipad subject to them fixing these bugs.
Click to expand...
Click to collapse
> Well this has taught me to not take anything for granted with chinese tablets.
Understatement of the year
Still, per your original post, it's kinda disappointing to hear that the Tegra K1 doesn't have enough power to play Hi10p 1080p with SW mode.
I looked at the K1's specs sheet, and with a quad core A15 2.3Ghz, I would have thought for sure it was enough power...

CDB-Man said:
> Well this has taught me to not take anything for granted with chinese tablets.
Understatement of the year
Still, per your original post, it's kinda disappointing to hear that the Tegra K1 doesn't have enough power to play Hi10p 1080p with SW mode.
I looked at the K1's specs sheet, and with a quad core A15 2.3Ghz, I would have thought for sure it was enough power...
Click to expand...
Click to collapse
It's hard to tell until devs update their apps to optimize for the Tegra K1. Software is never optimal for high bitrates. The Hi10p I am testing is 7.2Mbit/s average but in certain scenes it goes over 10Mbit/s. MXplayer and Dice player are for sure using software, if I invoke HW+ mode it speeds up but I see color blotches all over the picture similar to when playing Hi10p on unsupported hardware or codecs.
VLC beta I have it all set for hardware acceleration and the playback is perfect but the amount of heat generated and battery drain leads me to suspect it is only partially accelerated.
Once the devs optimize for the Tegra K1 we'll have a clearer picture on the capabilities of the Tegra K1.
As an aside even with h265/HEVC it was easier to play smoothly since lower bit rates:
Format : Matroska
Format version : Version 1
File size : 824 MiB
Duration : 43mn 29s
Overall bit rate : 2 649 Kbps
Writing application : DivXMKVMux 9.8.10.8454
Writing library : libDivXMediaFormat 4.0.0.0578
Video
ID : 1
Format : HEVC
Format/Info : High Efficiency Video Coding
Codec ID : V_MPEGH/ISO/HEVC
Duration : 43mn 29s
Width : 1 920 pixels
Height : 1 072 pixels
Display aspect ratio : 16:9
Frame rate mode : Constant
Frame rate : 23.976 fps
Language : English
Default : Yes
Forced : No
Audio
ID : 2
Format : AAC
Format/Info : Advanced Audio Codec
Format profile : LC
Codec ID : A_AAC
Duration : 43mn 29s
Channel(s) : 6 channels
Channel positions : Front: L C R, Side: L R, LFE
Sampling rate : 44.1 KHz
Compression mode : Lossy
Language : un
Default : Yes
Forced : No

Kantana said:
It's hard to tell until devs update their apps to optimize for the Tegra K1. Software is never optimal for high bitrates. The Hi10p I am testing is 7.2Mbit/s average but in certain scenes it goes over 10Mbit/s. MXplayer and Dice player are for sure using software, if I invoke HW+ mode it speeds up but I see color blotches all over the picture similar to when playing Hi10p on unsupported hardware or codecs.
VLC beta I have it all set for hardware acceleration and the playback is perfect but the amount of heat generated and battery drain leads me to suspect it is only partially accelerated.
Once the devs optimize for the Tegra K1 we'll have a clearer picture on the capabilities of the Tegra K1.
As an aside even with h265/HEVC it was easier to play smoothly since lower bit rates:
Format : Matroska
Format version : Version 1
File size : 824 MiB
Duration : 43mn 29s
Overall bit rate : 2 649 Kbps
Writing application : DivXMKVMux 9.8.10.8454
Writing library : libDivXMediaFormat 4.0.0.0578
Video
ID : 1
Format : HEVC
Format/Info : High Efficiency Video Coding
Codec ID : V_MPEGH/ISO/HEVC
Duration : 43mn 29s
Width : 1 920 pixels
Height : 1 072 pixels
Display aspect ratio : 16:9
Frame rate mode : Constant
Frame rate : 23.976 fps
Language : English
Default : Yes
Forced : No
Audio
ID : 2
Format : AAC
Format/Info : Advanced Audio Codec
Format profile : LC
Codec ID : A_AAC
Duration : 43mn 29s
Channel(s) : 6 channels
Channel positions : Front: L C R, Side: L R, LFE
Sampling rate : 44.1 KHz
Compression mode : Lossy
Language : un
Default : Yes
Forced : No
Click to expand...
Click to collapse
VLC reders clearly because by default it uses RGB 32bit video chroma while MX Player uses RGB 16bit by default. RGB 32bit need more processor power. That's why it leads to heat up issue. You can use RGB 32bit in MX Player too by changing the Settings 》 Decoder 》 Color format to RGB 32bit.

ktsamy said:
VLC reders clearly because by default it uses RGB 32bit video chroma while MX Player uses RGB 16bit by default. RGB 32bit need more processor power. That's why it leads to heat up issue. You can use RGB 32bit in MX Player too by changing the Settings 》 Decoder 》 Color format to RGB 32bit.
Click to expand...
Click to collapse
Tried that but it didn't help for Hi10p. Both HW and HW+ mode gives the blotchy/blocky renders with pink tint. I've attached a screen capture from MX player and one from VLC. SW mode doesn't have this issue on MX player but it will stutter.

H265 is played in HW on the Mipad, but still no Hi10p support in hardware. The stock video player plays h265.

GPU Video Playback issues - Screen shuttering and vertical lines

Hello,
i have a new SM-T585 with Android 6.0.1 (EU) NON-Root and problems with some .ts videofiles frome my TV-Headend-Setup.
When i try to play those files with H/W Accleration (MX-Player, BS Player, Kodi) i get vertical lines and screen shuttering (the whole screen with menue). When I try to play those files with SW-Mode the artifacts are gone but i have poor fps-performance.
Here is one example of the .ts.
Code:
dropbox.com/sh/8bt23ajttypy9p0/AABUFOE11zmFQr-C5YWPwbR2a?dl=0
Has anyone of you made the same experiences?
Code:
General
ID : 12 (0xC)
Complete name : /Volumes/Data/Benutzer/Dropbox/Samsung Tablet Screen Tearing/Sky-Sport-News-HD-Live-Sky-Sport-News-HD_-Spatreport.2017-03-25.ts
Format : MPEG-TS
File size : 60.9 MiB
Duration : 1mn 54s
Start time : UTC 2017-03-25 21:43:24
Overall bit rate mode : Variable
Overall bit rate : 4 395 Kbps
Country : DEU
Timezone : +01:00:00
Video
ID : 1023 (0x3FF)
Menu ID : 108 (0x6C)
Format : AVC
Format/Info : Advanced Video Codec
Format profile : [email protected]
Format settings, CABAC : Yes
Format settings, ReFrames : 4 frames
Codec ID : 27
Duration : 1mn 54s
Bit rate : 3 984 Kbps
Width : 1 920 pixels
Height : 1 080 pixels
Display aspect ratio : 16:9
Frame rate : 25.000 fps
Standard : Component
Color space : YUV
Chroma subsampling : 4:2:0
Bit depth : 8 bits
Scan type : MBAFF
Scan order : Top Field First
Bits/(Pixel*Frame) : 0.077
Stream size : 54.3 MiB (89%)
Color range : Limited
Color primaries : BT.709
Transfer characteristics : BT.709
Matrix coefficients : BT.709
Audio
ID : 1027 (0x403)
Menu ID : 108 (0x6C)
Format : AC-3
Format/Info : Audio Coding 3
Mode extension : CM (complete main)
Format settings, Endianness : Big
Codec ID : 129
Duration : 1mn 54s
Bit rate mode : Constant
Bit rate : 192 Kbps
Channel(s) : 2 channels
Channel positions : Front: L R
Sampling rate : 48.0 KHz
Compression mode : Lossy
Delay relative to video : -695ms
Stream size : 2.62 MiB (4%)
Language : German

reformhaus85 said:
Hello,
i have a new SM-T585 with Android 6.0.1 (EU) NON-Root and problems with some .ts videofiles frome my TV-Headend-Setup.
When i try to play those files with H/W Accleration (MX-Player, BS Player, Kodi) i get vertical lines and screen shuttering (the whole screen with menue). When I try to play those files with SW-Mode the artifacts are gone but i have poor fps-performance.
Here is one example of the .ts.
Code:
dropbox.com/sh/8bt23ajttypy9p0/AABUFOE11zmFQr-C5YWPwbR2a?dl=0
Click to expand...
Click to collapse
It seems to be issue with your system decoders itself. It it's so, It's suppose to be fixed on OEM side. Not App Developer side.

Oppo Find X2 Pro HDR Video Record

Hi,
Is someone able to determine from the below metadata from a video shot on an Oppo Find X2 Pro in 'Live HDR' mode why it doesn't trigger any HDR mode playback on capable devices such as an LG OLED?
Is the video some kind of fake or generic HDR or is there missing entries in the metadata that tell the device it's being played back on to enable HDR mode, or something codec-related? The Find X2 Pro is advertised as being able to shoot 10-bit HDR video.
Video
ID : 1
Format : HEVC
Format/Info : High Efficiency Video Coding
Format profile : Main [email protected]@Main
HDR format : SMPTE ST 2086, HDR10 compatible
Codec ID : hvc1
Codec ID/Info : High Efficiency Video Coding
Duration : 1 min 8 s
Source duration : 1 min 8 s
Bit rate : 50.0 Mb/s
Width : 3 840 pixels
Height : 2 160 pixels
Display aspect ratio : 16:9
Frame rate mode : Variable
Frame rate : 29.553 FPS
Minimum frame rate : 14.805 FPS
Maximum frame rate : 30.323 FPS
Standard : NTSC
Color space : YUV
Chroma subsampling : 4:2:0
Bit depth : 10 bits
Bits/(Pixel*Frame) : 0.204
Stream size : 408 MiB (99%)
Source stream size : 408 MiB (99%)
Title : VideoHandle
Language : English
Color range : Limited
Color primaries : BT.2020
colour_primaries_Original : BT.709
Transfer characteristics : BT.709
Matrix coefficients : BT.2020 non-constant
matrix_coefficients_Original : BT.709
Mastering display color primaries : R: x=0.000000 y=0.000000, G: x=0.000000 y=0.000000, B: x=0.000000 y=0.000000, White point: x=0.000000 y=0.000000
Mastering display luminance : min: 0.0000 cd/m2, max: 0 cd/m2
mdhd_Duration : 68455
Codec configuration box : hvcC

My understanding was that the HDR video applied the high dynamic range processing to each photo (like HDR photos) but was not actually filming in HDR format.