[Q] Xoom video/media player capabilities (curious) - Xoom Q&A, Help & Troubleshooting

Nvidia lists the following specs on their website for the Tegra2 :
Video decode
H.264
VC-1 AP
MPEG2
MPEG-4
DivX 4/5
XviD HT
H.263
Theora
VP8
WMV
Sorenson Spark
Real Video
VP6
Audio decode
AAC-LC
AAC+
eAAC+
MP3
MP3 VBR
WAV/PCM
AMR-NB
AMR-WB
BSAC
MPEG-2 Audio
Vorbis
WMA 9
WMA Lossless
WMA Pro
Can anyone confirm that the xoom can decode these?
Can the Xoom/honeycomb media player read subtitles (in) .mkv or .srt, sub/idx files?

The xoom can handle those, but only very specific versions of those. For example, don't try playing a 720p high profile h.264 video, because it won't play. So if you torrented a 720p video for example and it was an mkv file, not gonna play since they are almost all high profile h.264. You can convert them to baseline h.264 and it will play up to 1080p, but converting is annoying and takes time.

I am not sure what is out there on torrents, but I have some MKVs that I encoded and they have a bitrate of around 3mbit. According to this general tips section:
http://forum.xda-developers.com/showthread.php?t=969029&highlight=720p
The Xoom is supposed to be able to play video as long as the bitrate is under 20Mbit. The post references this:
https://supportforums.motorola.com/message/330326#330326
which says that realistically as long as the bitrate is under 4Mbit you should be fine.
The MKVs that I am trying to play, which are well under 20mbit and under 4mbit, skips like crazy and is unwatchable.
If I look at vmstat (via adb shell) while I am playing a movie using rock player in software decoding mode, the CPU goes to 100% (presumably in the kernel that android is using each core gets 100%, so there is a total of 200% available -- half ends up in system and half in user land):
procs memory system cpu
r b free mapped anon slab in cs flt us ni sy id wa ir
2 0 74440 58584 254928 30112 158 1005 0 99 0 30 99 0 0
1 0 74564 58588 255036 30124 466 2263 0 99 0 22 99 0 0
1 0 68392 58880 261072 30128 367 2742 0 99 0 32 99 0 0
1 0 67136 58968 262216 30180 684 3604 0 99 0 32 99 0 0
2 0 67004 58976 262456 30180 224 1635 0 99 0 13 99 0 0
3 0 66632 58912 262756 30180 272 1721 0 99 0 10 99 0 0
3 0 60564 59724 266896 30160 414 2212 3 99 0 19 99 1 0
3 0 25136 60136 294812 30196 603 3372 0 99 0 76 9 0 0
4 0 25012 60128 294512 30184 472 2458 0 99 0 88 6 0 0
5 0 25020 60128 294448 30184 390 2121 0 99 0 99 3 0 0
3 0 24540 60128 294440 30164 265 1631 0 99 0 99 1 0 0
4 0 24416 60128 294576 30164 353 1768 0 99 0 93 6 0 0
4 0 24912 60128 293108 30140 332 1747 0 99 0 99 5 0 0
3 0 24788 60128 293076 30140 300 1604 0 99 0 99 3 0 0
While looking at hardware decoding mode, the system usage drops way down:
procs memory system cpu
r b free mapped anon slab in cs flt us ni sy id wa ir
2 0 54116 58928 262524 30140 170 933 0 99 0 10 99 0 0
3 1 63780 58932 262520 30276 1119 4809 0 99 0 24 99 6 0
7 0 50184 59544 264332 31072 3493 19967 6 99 0 99 98 14 0
4 0 5620 59852 311776 31124 455 4765 2 99 0 61 18 0 0
3 0 5124 59868 311872 31064 368 4590 0 99 0 33 23 0 0
4 0 5124 59860 313024 30952 322 4625 0 99 0 39 44 0 0
3 0 4760 59860 313060 30936 390 5172 0 99 0 45 25 0 0
3 0 5256 59860 313032 30900 358 5475 0 99 0 38 30 0 0
3 0 4884 59868 312992 30876 336 5202 0 99 0 31 35 0 0
4 0 4636 59868 312856 30816 307 5036 0 99 0 34 36 0 0
3 0 5504 59904 312876 30816 378 5095 0 99 0 36 37 0 0
4 0 5504 59912 312884 30664 363 5046 0 99 0 33 44 0 0
3 0 4512 59924 312808 30656 288 4796 0 99 0 27 29 0 0
4 0 5256 59928 312908 30408 287 4927 0 99 0 32 38 2 0
3 0 5008 59928 312808 30404 367 5779 0 99 0 44 28 0 0
1 0 5132 59944 312820 30224 490 3432 0 99 0 36 74 0 0
But the playback remains fairly choppy. So all we need is the great devs at Rockplayer to stick the right code in for hardware decoding.
Presumably the native player uses hardware decoding which is why it is able to play video with framerates around 4mbit.

http://mediainfo.sourceforge.net/en
Download that and after installing, open it up and drag your mkv file into the window. Bet you that those videos are high profile h.264 which is the reason for the choppiness.
The reasons your processor max out in software mode is that its using the CPU to play the file. It drops down using hardware acceleration because its the GPU playing the file.

I used mediainfo to get the bitrate, which is under 4Mbit, which is under the limit that is quoted on the Motorola website. The fact that they may be a specific "media profile" in whatever converter you are using makes no difference -- only the bitrate is important.
Also, as mentioned in my post, I understand that the CPU drop is due to the use of hardware rendering. We still have to wait for either specific Xoom GPU support in Rockplayer or optimized code changes in Rockplayer.

Also, it appears that the native movies app is able to play my MKV files. It plays them much smoother, but they are still too choppy and the sound doesn't come through. The audio track on this is an AC-3 48KHz, 384Kbps audio stream.

No. You dont understand. The profile is everything. Bitrate means nothing. Tegra 2 is not capable of playing high profile hd h.264. The video you are trying to play is probably a high profile h.264 mkv file. There are various profiles for h.264 video. The Tegra 2 can play baseline profile. Almost all media is in high profile.
Do this for me, drag the media file you are trying to play into MediaInfo, and then go to View>Text. Then select the entire Video section and copy it and then paste it in here.

Thanks guys.
The sad thing is a cheap single core tablet with limited memory like the Archos 101 can play any video I throw at it without needing to convert them. The Archos 101 even plays DTS and AC-3 audio. Most of my videos are 720p HD and the only thing it doesn't play is 1080p. However, the Archos 101 is not perfect.
I was really hoping that the Xoom (or one of these other tablets) could at least come close to performing as well. How is it a company like Archos can make a cheap tablet perform so well (media wise) and these higher end tablets fall short?

kmd1970 said:
Thanks guys.
The sad thing is a cheap single core tablet with limited memory like the Archos 101 can play any video I throw at it without needing to convert them. The Archos 101 even plays DTS and AC-3 audio. Most of my videos are 720p HD and the only thing it doesn't play is 1080p. However, the Archos 101 is not perfect.
I was really hoping that the Xoom (or one of these other tablets) could at least come close to performing as well. How is it a company like Archos can make a cheap tablet perform so well (media wise) and these higher end tablets fall short?
Click to expand...
Click to collapse
software, honeycomb is buggy, its hardly optimized. no one really knows what the tegra 2 is capable of yet.
the facts are simple, there no tegra 2 device capable of playing high profile h264 right now.
tegra 2 devices are just now making it to market and its new untested unproven hardware.
secondly there are only two devices released or pseudo released(in the case of the adam) that even use this hardware. not alot of info to go on here.
at this point ask anyone here and they can't give you any 100% accurate answer, because we simply don't know. its ALL speculation at this point.
you have two camps on this issue. one camp, the hardware people claim that because both the adam and xoom use tegra 2 and can't play h264 high profile that its a hardware limitation.
the second camp takes the side that because this is new hardware, it needs proper software and drivers to handle the decoding and that this is the reason for the poor playback. this camp believes it will be fixed down the line with an update.
the second camp is the more feasible scenario. anyone that knows anything about hardware and software understands that hardware is worthless without good software.
let me give a prime example everyone knows video encoding takes time. if you want to encode a 20 minute video lets say you use handbrake and encode the video using your cpu in 14 minutes. but wait, whats this? you have a $500 nvidia graphics card in your system? its a big arse paper weight right now ain't it?
lets fix that, lets get the proper software and drivers and encode that same 20 min video by offloading to this powerful gpu. done in 5 minutes.(*actually times vary based off settings and actually hardware)
get the picture?
however, this does NOT mean that the tegra 2 is without fault. it could be the hardware and its simply not capable of high profile and never will be. we simply don't know, because we don't have any good information from nvidia or motorola or notion ink. we don't know what its true capabilities are.
all we know is that the tegra 2 with the current available devices and software cannot play high profile h264.
all the rest is speculation.

..........

From an XBMC developer:
http://forum.xbmc.org/showpost.php?p=735285&postcount=41
Tegra2 can't hw decode h264 [email protected] or above. I know because I have one (Tegra2 dev kit). That really limits the video content to SD. Too bad, it's a nice chip except for that.
Click to expand...
Click to collapse
This guy worked on porting XBMC to iOS and has videos like this:
Code:
Format/Info : Advanced Video Codec
Format profile : [email protected]
Format settings, CABAC : Yes
Format settings, ReFrames : 9 frames
Muxing mode : Header stripping
Codec ID : V_MPEG4/ISO/AVC
Duration : 1mn 52s
Bit rate : 6 478 Kbps
Nominal bit rate : 5 660 Kbps
Width : 1 280 pixels
Height : 720 pixels
Display aspect ratio : 16:9
Frame rate : 23.976 fps
playing like this:
http://vimeo.com/20636064
on the ipad.
Same file playing on two different Tegra 2 tablets:
http://www.youtube.com/watch?v=lXWu6m33EP0&feature=player_detailpage#t=231s

... with the amount of Tegra2 for the next month,
i think we could download all videos in tegra2 useable formats (720p/1080p) and nvidea will also adress this topic, so i am not worried about ...

muyoso said:
From an XBMC developer:
http://forum.xbmc.org/showpost.php?p=735285&postcount=41
This guy worked on porting XBMC to iOS and has videos like this:
Code:
Format/Info : Advanced Video Codec
Format profile : [email protected]
Format settings, CABAC : Yes
Format settings, ReFrames : 9 frames
Muxing mode : Header stripping
Codec ID : V_MPEG4/ISO/AVC
Duration : 1mn 52s
Bit rate : 6 478 Kbps
Nominal bit rate : 5 660 Kbps
Width : 1 280 pixels
Height : 720 pixels
Display aspect ratio : 16:9
Frame rate : 23.976 fps
playing like this:
http://vimeo.com/20636064
on the ipad.
Same file playing on two different Tegra 2 tablets:
http://www.youtube.com/watch?v=lXWu6m33EP0&feature=player_detailpage#t=231s
Click to expand...
Click to collapse
take his with a grain of salt. all he said was i have a tegra 2 dev kit and tegra 2 can't do the high profile h264.
whats this even mean? is there something in this dev kit that actually lists what the tegra 2 is capable of hardware wise? whats in this dev kit, whats the real reason it won't play.
ill take him for his word when pigs fly out of his ass.
http://developer.nvidia.com/tegra/tegra-devkit-features
its just hardware, no magical software to be had there. which means what? hes got the same software we do.
also id like to point out that there is a VAST difference between making android support another codec so it can play a video and making android offload to the gpu using drivers. key word there folks, drivers.
back to the cuda example, two things are needed to tango. first you need the proper nvidia drivers. and secondly, you need an application designed to work with those drivers in order to have it successfully utilize the gpu. xbmc can only proved the app to interface with what exists, they can't do anything else.
ps:
al gore invented the internet.

Is there like a cut off date for peoples denial about tegra 2's shortcomings? Like a year from now when it still can't play video [email protected] h.264, will people still be claiming its a lack of software?
Davilla did massive testing of the tegra 2. You think there were drivers from apple for the ipad? No.
Look, there may be a software solution if the tegra 2's cpu is powerful enough to decode hd h.264, but there is massive evidence that it will never hardware decode that video. I think its an important enough shortcoming to inform people about and not lead them on with some promise of future software.
Sent from my SPH-D700 using XDA App

Any official info from NVidia about this H.264 high profile hardware decoding capability?
Anyone reached NVidia?

e.mote said:
Most Honeycomb tablets announced will have a Tegra2 in it, and video playback is an important component, so I'm confident the issue will be addressed, if not from Nvidia, then from a 3rd-party commercial media player like Coreplayer.
Click to expand...
Click to collapse
Please, not that Coreplayer for Android rumor again. (I've been waiting for too long)

It's not really CoreCodec's fault. Android has been a pretty fast moving target, and my guess is that Nvidia hasn't been exactly timely with software support for the Tegra2, else the VS G-Tab would've had decent playback by now.
My reading of the tea leaves is that we'll probably see CP either around the Honeycomb mass launch or a bit after. Anyway, it'll come when it'll come.
Now, VLC, I think will be a fair bit longer in coming,
http://ivoire.dinauz.org/blog/index.php?post/2011/02/02/VLC-on-Android

muyoso said:
The xoom can handle those, but only very specific versions of those. For example, don't try playing a 720p high profile h.264 video, because it won't play. So if you torrented a 720p video for example and it was an mkv file, not gonna play since they are almost all high profile h.264. You can convert them to baseline h.264 and it will play up to 1080p, but converting is annoying and takes time.
Click to expand...
Click to collapse
From Xoom office website, we know that Xoom supports AAC, H.263, H.264, MP3, MPEG-4, ACC+ Enhanced, OGG, MIDI, AMR NB, AAC+. If u want to play video on Xoom, the video format and video coding must be correct.
So I suggest u convert your MKV files to Mp4 H.264 1280*720 for playing.
I did a test, and I can't find any diffirence between 1080P and 720P, SO I recomend convert video to 720P, and the converted file size is small. therefore, u can transfer more video to Xoom.

For those use HandBrake, attachment is the [email protected] preset for playback in Tegra2

muyoso said:
The xoom can handle those, but only very specific versions of those. For example, don't try playing a 720p high profile h.264 video, because it won't play. So if you torrented a 720p video for example and it was an mkv file, not gonna play since they are almost all high profile h.264. You can convert them to baseline h.264 and it will play up to 1080p, but converting is annoying and takes time.
Click to expand...
Click to collapse
MKV is a container format, which supports holding unlimited number of video, audio, picture or subtitle tracks inside a single file, can’t be played on the Motorola Xoom. only the video format and video encoding are right, Xoom can be play it.
So, not because Xoom can't play 720P high profile h.264 video, but the video format is wrong. I suggest u convert MKV 720p h.264 video to MP4 720P H.264 for playing on Xoom.

Related

Raphael Video Encoding Thread

NOTE: USE OF THIS THREAD AND INFO ASSUMES YOU HAVE LEGAL AUTHORITY TO USE / ENCODE ALL SOURCE MATERIALS. I AM A US CITIZEN AND A SOLDIER, AND HENCE FALL UNDER JURISDICTION OF MANY ORGANIZATIONS, TO INCLUDE THE FEDERAL CENSORSHIP CLUB (FCC) AND THE DOUCHEBAGS MOLESTING CONSUMERS ACT. NO QUESTIONS WILL BE FIELDED REGARDING RIPPING, DOWNLOADING, OR PIRATING OF SOURCE MEDIA, REGARDLESS OF THE INQUIRER'S NATIONALITY. - Fathead, P.I.
This thread will be about video encoding, with the end product being the Raphael. My current Device, Radio and ROM are in my sig and updated for reference.
The premise of this guide: Using freely available (NON-WAREZ) CODEC and software, the user will be able to create video with audio playable on a HTC Touch Pro. The video will be of a watchable quality and small in file size.
Some of you may be familiar with my work on SEGA Dreamcast with GypPlay, DC-Divx, DC-VCD standard, and XDP (X-Rips, Inc. Dreampassport, English translation of DP 2 and above)
- Fathead, P.I.
----- START OF THEOREY -----
If you're like me, the first thing you asked yourself after buying your Fuse was "HOLY ****! I can run 4x the storage on this thing that my old Wizard could!" Yes, 16 GB of Micro-SD goodness is freakin' sweet. But how to use it? You can only listen to so much music per week, even with Napster To Go. You can only play so many games. (I'm further reduced due to lack of a usable joy pad for Pocket Nester.) Why not throw some movies on this joker?
----- VIDEO FORMAT -----
The first thing most people want to know is "What resolution and format should I use?" I am a longtime fan of Divx. I have used it to successfully create video content for low end devices, specifically the SEGA Dreamcast. Creating or downsampling content for a mobile phone gives us a considerable edge over bigger-screen counterparts. Before we jump into the configuration of settings and knob-dicking with software, let's figure out just what kind of video we want to produce.
FRAME RATE
Most content you find will come in one of 3 frame rates:
30 FPS (VHS / NTSC Broadcast / DVD / Blu-Ray(?) )
25 FPS (PAL)
23.976 FPS (Actual frame rate used to record cinema and produce much media)
The first thing you need to realize is that many things initially encoded in 30 FPS can be converted back to 23.976 FPS with no loss of fluidity or data. If your source is a webcam, skip the scaling to 23.976 and drop down to frame decimation. If your source is film, you're in luck. The other frames are just dummy frames that waste a little data. Deleting those frames frees up more video data to better express the picture information in the other 23.976 frames. This trick allows you to:
A. Use a lower bitrate (and hence smaller file) for the same picture OR
B. Get a better picture at the current bitrate
To figure out the frame rate, load up your file in V-Dub and go to File - File Information. The Data Rate box in the Video Stream area will tell you current bit rate, while frame size will give you resolution and frame rate. If you have a 23.976 FPS source, continue. If you have a 30 FPS source that you think should be 23.976 FPS (Film, etc) :
1. Load up the file in V-Dub.
2. Go to the Video drop down menu. Select Frame Rate (CTL+R is shortcut)
3. Change the Frame Rate on the source to 23.976 FPS.
If you continue to have audio sync issues with this method, leave the file at 30 FPS and continue.
Now we are going to look at frame decimation. Frame decimation drops every X frame while keeping the audio sync'd. The end result is a file X the frame rate of the source. While this is noticeable on large screens, on the Touch Pro / Diamond Screens (and probably even the HD), it shouldn't be an issue at all. You can play with this option. It is more noticeable on film, but I cannot see a difference at all on animated sources.
I use the decimate by 2 option in VDub. Video -> Frame Rate (CTL+R shortcut) and select Decimate video frame rate by 2. Our output video is now half the frame rate of our source. The end result is we can:
A. Get a better picture with the current video bit rate OR
B. Lower the video bit rate to get the same picture in a smaller size.
I use option B. Another big advantage here is that the device is trying to decode half the frames. A general rule about audio and video playback: The lower the bit rate you ask the device to handle, the less work it has to do to decode and display the video, and less battery power will be used.
RESOLUTION
Most content you will find is around 640 x 480. DVD sources usually come around 720x480. Blu-Ray would be above that, but possibly scaled down. We are going to watch this movie on a 3 inch screen. Guess what that means? If we never found a video about 320x240, or comparable widescreen resolution, It wouldn't matter. At all. Stepping up to 640x480 is just going to quadruple the amount of pixels we are trying to express on a limited budget.
A handy tool I use in V-Dub is the 2:1 reduction filter (high quality). To kick kit on, go to Video -> Filters (CTL+F). Click add, and it should be the first filter you can choose. This cuts your resolution by half. As a rule of thumb, If I've got a source that's around 640x480 (or 16:9 equiv) or higher, I hit it with the 2:1. You'll find oddball sources like 480 x 360, you can give it a shot, but it might not be worth it. Again, lower resolution means less pixels to express both in bit rate and in reproduction (playback).
Pausing here again, tired as hell.
THE SOFTWARE I USE
Video Editing / Audio and Video Compression and Mux - Virtual Dub. Totally free. I usually refer to this as VDub.
Home
Download
Audio Compression CODEC - LAME MP3 - Free and versatile.
Home
Compiled Binaries
Use the ACM Binary here for Windows and Virtual Dub
Video Compression CODEC / PC and SP/PPC Player - Divx - Decoder, player, mobile player, and MOST of the Encoder are FREE. DO NOT POST ABOUT CRACKING THIS.
Home / CODEC and PC Player
MOBILE (PPC and SP) Player
One more for good measure...
Okay, replies and requests, go!
Am I correct in thinking that videos should be encoded in 640 x 480 ?
*RESERVED*
cucusoft
i use Cucusoft Ultimate DVD + Video Converter Suite
mpeg-4
video bitrate 600kbit/s
framerate, depends from 23.976 to 25 (not important)
videosize 480x368
format 4:3
audio aac
128kb/s
samplerate 48000k
2 chanels stereo
it works fine, no framedrops
played with coreplayer 1.25 build 4506
I just use the standard 700mb divx movie in .avi
I use the free divx player V0.91
Smaller would be sweeter.
Taking a break for a bit, added some new material. Internets in the hotel are barely functional.
I'll be focusing on getting files down to smaller levels. The theorey should give you enough information to start dramatically cutting your file sizes. I've been moving my Boondocks DVD over to Divx 6.8 movies. Averaging 40 megs per episode.
I have been using spb mobile dvd for a few years now. It is very easy to use can convert straight from a dvd or a video file and supports vga res.
Will have to check that one out, have been thinking about backing up my DVD's to mobile, will be traveling about 26 - 30 weeks out of the year and need some boredom killers.
Gonna score some sleep and SEGA time, later all.
Added some new info, taking a pre breakfast nap.
i use slysoft clonedvdmobile. output at vga res and filesize around 700mb seems to run fine for me...although its not free, its well worth the money
Brendo said:
i use slysoft clonedvdmobile. output at vga res and filesize around 700mb seems to run fine for me...although its not free, its well worth the money
Click to expand...
Click to collapse
This is a great bit of software. It also utilises all 4 cores on my Q6600. Another fantastic program is DvDFab which can transcode DVD to Divx/Xvid/MP4 etc on the fly, or dump the Video TS to your HD.
Going to have to check all this out. Have many a DVD that needs ripped. Wonder if any of those have a frame decimation feature. I like my 30 - 40 meg per episode cartoons.
Based on some comments in other threads, I've tried a couple of freeware programs to try to encode in the format that works so well with WMP (MP4, H.264, 640x368, 1000 Kbps, AAC @ 96Kbps): DVD Decrypter + SUPER for one and AutoMKV for the other. However, I haven't been fully successful with either, so I'm hoping that someone who uses these tools can clue me in on the appropriate settings and procedures for encoding.
The combination of DVD Decrypter and SUPER creates very nice movies for playback on the Fuze. Unfortunately, DVD Decrypter keeps the VOB structure from the DVD and SUPER follows suit, which means that a movie will be broken into several pieces at arbitrary points: unsatisfactory, to say the least. The SUPER support forum mentions a way to join inputs into a single output, but following what I understood those instructions to say did not, in fact, result in a combined file.
AutoMKV is very convenient, as it is a single program (or at least UI) to both rip and encode. Unfortunately, I haven't found the settings that generate output that is comparable to the SUPER output -- WMP won't play any of the files I've managed to create so far.
Anybody use these successfully and can share how they do it? TIA.
amerisoft, works very well for me so far, except an occasional blank screen
Just wanted to add...
I don't bother encoding video anymore. Sure, a full-blown 50 minute xvid show might be 400meg. However, the touch pro does not have any issue playing such files back.
Makes life much easier!
I'd agree. I've loaded up a couple of 700MB XVIDs and had no problem playing them.
For some reason, my Sprint Touch Pro has issues playing back even reasonable quality video. For instance, 640x480 video at 1200k (MP4) is a little choppy in WMP, and almost -everything- is extremely choppy in TCPMP, no matter how it's encoded, including 350MB 45-minute XVid TV shows.
AndyCR said:
For some reason, my Sprint Touch Pro has issues playing back even reasonable quality video. For instance, 640x480 video at 1200k (MP4) is a little choppy in WMP, and almost -everything- is extremely choppy in TCPMP, no matter how it's encoded, including 350MB 45-minute XVid TV shows.
Click to expand...
Click to collapse
As I understand it, it's a driver issue. (This is what I've gathered across numerous postings here; someone please correct me if I've gotten something wrong.) The Qualcomm chipset in the TP/Fuze has an efficient driver called Qtv, but Qualcomm charges for a license. WMP appears to incorporate the driver, so it's able to handle moderately challenging videos. 1200 Kbps might be a little more than it's capable of displaying smoothly, but people have reported that 1000 Kbps plays well. On my one trial with DVD Decrypter + SUPER, that was the case for me, too -- full resolution and smooth motion for a video ripped from a DVD with the specs I reported in my earlier message in this thread.
TCPMP, on the other hand, does not include the Qtv driver, so in order to get smooth playback you have to reduce the size, resolution, or frame rate.
Coreplayer has a reverse-engineered partial driver for Qtv. As a result, it falls between TCPMP and WP in capabilities. It is claimed that version 3.0 of Coreplayer will have full Qtv support.

HELP NEEDED: 5.1 Audio Test

Asking for help from anyone who has a 5.1 audio setup to his/her PC.
At issue is ffmpeg's bug in incorrectly mapping channel order from AC3 (and perhaps other formats) to AAC. Before, you had to remap the channels using an intermediate app like sox. But my current testing (on a 2-speaker setup) shows that there isn't an issue. Confirmation from a 5.1 setup is needed.
Attached below are 4 audio test clips: 5.1 WMA, 5.1 AC3, 5.1 AAC (from WMA clip), 5.1 AAC (from AC3 clip). The clips tell you which channel the sound is supposed to come out of, eg "front left".."front right"..etc. The LFE channel will be a mumbling sound coming out of the subwoofer.
I would appreciate it if someone with a 5.1 audio setup would test all 4 clips, and tell me if the channel orders are correct for all four. The clips are only 9 secs long apiece. Thanks in advance.
They all play correct for me.
I appreciate the assist.
I still get wrong order when converting 5.1 AAC to 5.1 AC3.
which ffmpeg version are u using?
Mapped fine here, too.
Someone sent me a PM asking which build of ffmpeg I'm using (for the correct AC3->AAC mapping). Not sure if I sent a reply, so I'm cc'ing a copy here.
I'm using the Zeranoe build. This is from AC3 to AAC. I didn't test the other way. (If one way comes out OK, the other should as well, but you never know.)
http://ffmpeg.zeranoe.com/builds
ffmpeg version N-31031-gf211d9d, Copyright (c) 2000-2011 the FFmpeg developers
built on Jun 26 2011 22:50:39 with gcc 4.5.3
configuration: --enable-gpl --enable-version3 --enable-memalign-hack --enable-runtime-cpudetect --enable-avisynth --enable-bzlib --enable-frei0r --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libfreetype --enable-libgsm --enable-libmp3lame --enable-libopenjpeg --enable-librtmp --enable-libschroedinger --enable-libspeex --enable-libtheora --enable-libvorbis --enable-libvpx --enable-libx264 --enable-libxavs --enable-libxvid --enable-zlib
libavutil 51. 10. 0 / 51. 10. 0
libavcodec 53. 7. 0 / 53. 7. 0
libavformat 53. 4. 0 / 53. 4. 0
libavdevice 53. 1. 1 / 53. 1. 1
libavfilter 2. 24. 0 / 2. 24. 0
libswscale 2. 0. 0 / 2. 0. 0
libpostproc 51. 2. 0 / 51. 2. 0
The AAC was created by converting the AC3 to 6-channel WAV, then piped to NeroAACEnc external encoder.
ffmpeg -i inputfile -vn -acodec pcm_s16le -ac 6 -f wav - -map 0.1 | neroAACEnc -q 0.4 -ignorelength -if - -of out.m4a

[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.

Rogers Infuse records video at 15 fps!

Hey guys i'm posting this thread to reply to a thread in the dev's section.
Since i'm a new member with under 10 posts i cannot reply to the thread in that section. Here's the thread url:
http://forum.xda-developers.com/showthread.php?t=1237907
Misterjunky wanted to know if the Rogers i997 phones with Gingerbread 2.3.3 were having the same low fps recording issues as others that have complained about it.
I am here to confirm that yes, i bought the phone last week and it does in fact record video only at 15 fps, even at 1080p.
This is very frustrating!
Thank you for letting us know!
I hope we can get ot fixed
Yep, I notice the same problem. After i rooted my phone and install infused 2.1.0 and did a highest resolution recording today, notice that it is it has latency slow fps. Absolutely horrible.
Hi all,
Another Rogers User here with the same low fps issue when recording movies. I also am replying here since I can't post in the developer forum.
Had the infuse for about a month, but just recorded my first video on it yesterday and noticed the clearly low fps.
Stock infuse, no roms.
Good to know that it isn't a regression we introduced.
The media capabilities of the Rogers firmware are clearly crippled - no MHL, low FPS for video.
Same here, Rogers stock 2.3.3 ... getting half frames
Sent from my SAMSUNG-SGH-I997R using XDA App
Thanks!
I Just wanted to stop by here to thank everyone here for reporting
this video recording bug in the stock Rogers Infuse Gingerbread rom.
Now we all know that this bug has nothing to do with the the customization or
improvements of the stock Rogers Gingerbread roms which the DEVS have
been working on but instead this video recording bug was in the stock
Gingerbread rom to start with.
If you guys want to check out all the technical details of your homemade
video recordings, here is a link to MediaInfo which most the devs use:
http://forum.xda-developers.com/attachment.php?attachmentid=705197&d=1314737293
for Misterjunky
Rogers Stock Infuse 4G
sorry im late.
for 480
General
Complete name : C:\Users\archer\Desktop\video-2011-09-11-14-51-51.mp4
Format : MPEG-4
Format profile : 3GPP Media Release 4
Codec ID : 3gp4
File size : 7.11 MiB
Duration : 32s 370ms
Overall bit rate : 1 844 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 : 32s 331ms
Bit rate mode : Variable
Bit rate : 1 784 Kbps
Width : 720 pixels
Height : 480 pixels
Display aspect ratio : 3:2
Frame rate mode : Variable
Frame rate : 15.063 fps
Minimum frame rate : 14.493 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.343
Stream size : 6.86 MiB (96%)
Language : English
Material_Duration : 32397
Material_StreamSize : 7205362
Material_FrameCount : 487
Audio
ID : 1
Format : AAC
Format/Info : Advanced Audio Codec
Format profile : LC
Codec ID : 40
Duration : 32s 370ms
Bit rate mode : Variable
Bit rate : 60.2 Kbps
Maximum bit rate : 67.2 Kbps
Channel(s) : 1 channel
Channel positions : Front: C
Sampling rate : 16.0 KHz
Compression mode : Lossy
Stream size : 235 KiB (3%)
Language : English
Material_Duration : 32435
Material_StreamSize : 240924
for 720
General
Complete name : C:\Users\archer\Desktop\video-2011-09-11-14-50-41.mp4
Format : MPEG-4
Format profile : 3GPP Media Release 4
Codec ID : 3gp4
File size : 24.3 MiB
Duration : 33s 151ms
Overall bit rate : 6 137 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 : 33s 64ms
Bit rate mode : Variable
Bit rate : 6 088 Kbps
Width : 1 280 pixels
Height : 720 pixels
Display aspect ratio : 16:9
Frame rate mode : Variable
Frame rate : 15.062 fps
Minimum frame rate : 14.286 fps
Maximum frame rate : 15.873 fps
Color space : YUV
Chroma subsampling : 4:2:0
Bit depth : 8 bits
Scan type : Progressive
Bits/(Pixel*Frame) : 0.439
Stream size : 23.9 MiB (99%)
Language : English
Material_Duration : 33131
Material_StreamSize : 25168331
Material_FrameCount : 498
Audio
ID : 1
Format : AAC
Format/Info : Advanced Audio Codec
Format profile : LC
Codec ID : 40
Duration : 33s 151ms
Bit rate mode : Variable
Bit rate : 59.9 Kbps
Maximum bit rate : 66.9 Kbps
Channel(s) : 1 channel
Channel positions : Front: C
Sampling rate : 16.0 KHz
Compression mode : Lossy
Stream size : 241 KiB (1%)
Language : English
Hi all , please see below link for 30fps fix. http://forum.xda-developers.com/showthread.php?t=1271876
Confirmed working on my Rogers infuse 4g stock 2.3.3 rom. Note the lib files are 2 months newer than other lib files -- to me this indicates it's off a new version, possibly 2.3.4 . No worries to. If ud like to be on safe side like me, before u copy as per instructions, rename the original files with underscore at the end -- this was u keep originals as ...
Sent from my SAMSUNG-SGH-I997R using XDA App
This fixed the fps issue on my stock rogers infuse as well. It seems to be working. I made backups of the files (only 3 of them, whereas there were 4 new files).
Thanks to all the folks who contributed to the fix
Sent from my SAMSUNG-SGH-I997R using XDA App
Awsome!
Now to find where someone can post a Stock Rogers dump i can use to restore my own phone...
....Never mind, Found one!
(Had to mash 2 return to stock programs together, but it works! http://forum.xda-developers.com/showthread.php?t=1315362)
Why the hell did you bump this?
duhhhh
Naphthoylindole said:
Why the hell did you bump this?
Click to expand...
Click to collapse
Probably cause i JUST GOT THE PHONE!
Good for you, now go do some other things that lead to a month ban.
Naphthoylindole said:
Good for you, now go do some other things that lead to a month ban.
Click to expand...
Click to collapse
Bumping a 3 week old thread can get u banned??
Sent from my SAMSUNG-SGH-I997 using XDA App
I couldn't get the method to work, whenever I try to copy the 4 files into that directory (via Root Explorer) I get a error window saying it cant be done because that directory is system read only. Any thoughts?
My Infuse is from Rogers, and yes I have root from this method: http://forum.xda-developers.com/showthread.php?t=1197248
Edit: OK the problem is fixed. While in the folder with the original files I pressed the "mount R/W" button at the top of Root Explorer and tried to paste the four modded files but got that "read only" error. For some reason doing it to the system folder first, then going to the lib folder and doing it there made it work. The video recording is simply epic!

[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.

Categories

Resources