yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab 10.1 General] e.mote:
If you're using CRF, why are you specifying bitrate?

No need to specify level, let the encoder (x264) pick the minimum level needed. For 1280x720, that's 3.1.

May be the GT plays 5.1 AAC as a value-add for its player, but the Xoom only plays 2.0.

Yes, most online MKVs can be re-crunched to half or less of their size. But really that's only of concern to the handful of peeps like us, who are already comfortable with (re)encoding videos. Most people just want to watch their downloaded vids on the tab however they can. Video recoding takes time, and most people don't have the patience.

MP4 container is fine, but it's limited to AAC, and sub support is problematic. If you're into animes or foreign films, you'll need to extract the subs, and possibly do hardsub if it requires, say, kanji support. MKV isn't widely supported on Android at this point, but given that most "downloaded" vids are in MKV, it's only a matter of time.
[Galaxy Tab 10.1 General] TECK:
I don't, CFR does it does automatically. I did several small files and --cfr 21 pushed a 2500 bitrate average (from my original movie encoded with --cfr 18) which is perfect for a tablet IMO. About the subs, one thing at the time. :) I don't plan to convert my entire library of movies for tablet, just selected movies I will use while going on vacation, etc. I have the space to store them, I'm just too lazy to do it. :)
[Galaxy Tab 10.1 General] e.mote:
Saw your sample clip. Suggest going with HP rather than BP, viz use the defaults. Also, since target device has only stereo speakers, then 2.0 AAC would save space for same fidelity.

For Tegra 2, I found CRF 22 to be "safe" for high-action content, else, 21.

An alt method is to specify vbv_maxrate & vbv_bufsize, as you have done. I didn't take the time to determine the optimal vbv settings for Teg2, although I do think your 2500 value is too low, and quality would suffer. My brief tests indicate that the Teg2 pegs out when hitting 10Mbs, so if you want to play with it, suggest starting with maxrate 8000 and bufsize 4000 for testing. [BTW, the reason your encodes avg 2.5Mbs is because vbv_maxrate is the limiter, rather than CRF.]

BTW, I'm same as you. I don't plan to convert my MKV library to MP4, just whatever I want to watch. I'll just wait for MKV support to show up.
[Galaxy Tab 10.1 General] TECK:
Ya, I did that... but for some reason, the fake 5.1CH preset in Google Videos sounded better with a 5.1 AAC, compared to 2.0. Weird I know... I was sure it was a real 5.1 channel, until Entropy512 told me it is a fake processing into software.

A 5000 bitrate and higher vbv_maxrate will create lag on an MP4 container, check the original sample I started with. I did not bother to play with the settings too much since the ones I have into latest sample work great and the video is superb IMO. See Arnold's eyes how they shine at 0:10. :)

Still, I trust your judgement... can you play a little also with the sample-orig.mp4 and see what settings you can come up with? I love dealing with a sample, it makes the encoding blistering fast.
[Galaxy Tab 10.1 General] StuMcBill:
It is the mkv file you posted yesterday with no overclocking!

Sent from my Amiga 500 using Workbench
[Galaxy Tab 10.1 General] e.mote:
It probably sounds better than 2.0 (assuming the 2.0 was properly downmixed via DPL2) because Sammy added some software DSP enhancer. Samsung makes PMPs, so it has some chops in this area. Anyway, DPL2 upmixing isn't uncommon, just not for Android players thus far.

My sample Avatar clip (high prof) in the survey avgs 6.6Mbs @ CRF 23. It plays mostly smooth except at the two 10-12Mbs spikes, per bitrate graph below.

http://xdaforums.com/showpost.php?p=15054949&postcount=250

I don't have the source for your clip, so can't say how much degraded the quality is because of the 2500 maxrate, but details were fairly soft, which is what happens with a lower bitrate (higher CRF). My gauge is that your clip roughly equates to CRF 25. As a test, leave off the vbv settings and try it w/ CRF 25 to see if you can tell a difference.

The vbv_maxrate should be close to the peak that the hardware can handle (or not be set at all), since you want it to constrain only the spikes, not the whole movie. That's the CRF's job. The maxrate should never be lower than or same as the avg rate, else it'll be a mostly CBR encode.

You can see this by checking the clip's bitrate variability. Your sample's avg is 2505, and the peak is only 3371, meaning minimal variability.
[Galaxy Tab 10.1 General] e.mote:
Here is the bitrate graph for your sample-megui.mp4. As you can see, it's very flat.

I've downloaded the orig clip, but my bitrate viewer can't load it since it uses VFR (variable framerate). This is a problem with Handbrake (using VFR for CFR source) and apparently with your source's encoder. If it's not already known, most players don't handle VFR well, and is probably the main culprit for playback problems. The high ref=8 (from the level 4.1) can also be an issue.

I've recoded the orig clip by forcing CFR (medium preset, high profile, film tuning, crf 21, no vbv). Notice the bitrate variability in the graph below.
[Galaxy Tab 10.1 General] TECK:
OK, I will give it another try with your settings. Can you upload the newly encoded file to MediaFire?
[Galaxy Tab 10.1 General] e.mote:
Recoded sample @ CRF 21: http://mediafire.com/?87puc5kskcz4ipo

The clip should play smoothly; you may get a single stutter at the 41sec mark (the 9.2Mbs spike).
[Galaxy Tab 10.1 General] TECK:
What do you think about this:

--level 4.1 --tune film --crf 21.0 --vbv-bufsize 18000 --vbv-maxrate 18000
[Galaxy Tab 10.1 General] e.mote:
Let x264 auto-select the level (which for 720p should be 3.1 or 3.0). As said, the Teg2 pegs out at around 10Mbs (10000) by my observation, so suggest trying maxrate 8000 and bufsize 4000 or 2000, ie a 1/2 or 1/4sec buffer. You can also try a 1sec buffer (bufsize = maxrate), but that increases the possibility of the bitrate overshooting the specified maxrate, and causing stutter.

The goal is to determine the highest vbv_maxrate w/o causing stutter. You'll need a bitrate viewer to see where the spikes are. Once you determined the optimal vbv values, then suggest setting CRF 21 all the time.

Or simpler is to use CRF 21 for low-action and 22/23 for high-action content.
[Galaxy Tab 10.1 General] CazeW:
I'm on the latest TouchWiz (KME).
[Galaxy Tab 10.1 General] e.mote:
BTW, I got the bitrate viewer to load the original clip. Turns out it's a bad mux job (remuxed it to MKV w/ MKVToolnix) rather than the VFR. Below are bitgraph comparisons of the original vs CRF 21 vs CRF 25, along with the clips. Note the general bit distributions are the same on all encodes.

The CRF 25 is roughly equiv to your 1st sample, with a slightly lower avg but more efficient bit distribution. To a casual viewer (read: most peeps), it's hard to tell the quality difference between 25 and 21 (overall details are just a bit softer).

Original clip http://mediafire.com/?nn1ki2b247tuupm

CRF 21 http://mediafire.com/?87puc5kskcz4ipo

CRF 25 http://mediafire.com/?7mbqhlzp6bcsdob
[Galaxy Tab 10.1 General] symanuk:
Try MX video player its the only player i found that can realy play loads of formates.
[Galaxy Tab 10.1 General] simple_punk:
@dudleygb

you can also try diceplayer. only tried the trial version but it was able to play 720p mkv animes without any problems.
[Galaxy Tab 10.1 General] rainbow ng:
Still No Luck For 1080p Playback.

720p Work Fine On Dice, MX, Vital and BUZZ.

For 1080p,

BUZZ give u normal sound , pretty picture quality but slower than the sound twice.

Vital and Dice have normal sound, poor picture quality and flake, but sometime for every 30s have 3 seconds playback in extreme perfect condition.

MX playback excellent quality for the first 5 seconds than everything worse.

For CM7 running on P1000, BUZZ,Dice,MX,Vital, All have perfect quality in 1080p playback without any lag. That implies the CPU of PT7500 is not at the MEANWHILE can support 1080P playback. The advertisement of SAMSUNG lie us.

NEVER accept convert the media files by myself to play back on the device meaning the TAB10.1 can playback HD video. I never pay any effort to playback HD 1080p video on Galaxy TAB 7" P1000 with the stock Samsung firmware. P1000 can play HD video without any convertion of codec and not the case for p7500. Before I buy P7500 , I never concern and don`t know anything about ac3 bitrate software hardware decode and why should I know? I am a customer , end user and not a programmer.

In the old day, I install Tubemate on P1000 and download the 1080p music video and playback them without any issues.

Now 720 p annoy us on THE LASTEST P7500. 1080P is impossible at this moment.

SORRY as I really think that the issue should solve by Samsung as it say P7500 can........
[Galaxy Tab 10.1 General] e.mote:
The issue is already solved by Samsung. Unfortunately, it involves buying another (newer) tablet. Succeeding GT products shown at IFA--the GT Note, GT 7.7, and GT 8.9 LTE--all use more powerful (presumably Samsung) SoCs. The Tegra 2 is an interim SoC, used because for this gen because it's what HC 3.0 was developed on.

The Teg2 SoC is an Nvidia part, and apparently Nvidia has sole responsibility for its driver. It's marginal on H.264 HD "scene" content (let's be frank about this), ie it will play some, but not all. That's the way it is. No software player can compensate for hardware shortcomings (although some are better than others).

>I never concern and don`t know anything about ac3 bitrate software hardware decode and why should I know? I am a customer , end user and not a programmer.

If you want to be a know-nothing, then don't play warez videos. Stick to paid solutions. If you want free, then get yourself educated. No rest for the wicked.
[Galaxy Tab 10.1 General] StuMcBill:
I know nothing about these things, but is it possible that Nvidia could release an updated driver for the Tegra2 or does it not work like that?

Sent from my Amiga 500 using Workbench
[Galaxy Tab 10.1 General] StuMcBill:
I know these are not mkv files, but I just found this site: http://www.tools4movies.com/xoom/fullscreen/

Its a load of 720p and 1080p HD video trailers and they play on my tab with the stock player, no probs. (Well the few I have tried anyway)

Just wondered if there was anything that could be learned from the encoding of these files?

Stewart

Sent from my Amiga 500 using Workbench
[Galaxy Tab 10.1 General] e.mote:
Nvidia doesn't release drivers for Android. Teg2 video improvements have come with each HC update. 3.2 was better than 3.1 was better than 3.0.

From some benchmarks, TouchWiz 3.1 has same video perf as 3.2 on other tablets, so apparently Sammy used improved drivers from 3.2 for TW.

>Just wondered if there was anything that could be learned from the encoding of these files?

The files you linked to are dated March, when 3.0 was around. They probably all use baseline profile (BP), as that's the only profile that can be played on the Teg2 and 3.0. BP takes less resources to decode, hence the Teg2 can play 1080p BP, but it eats 20-30% more space than high profile (HP).

There are encoding guides around if you want to try your hands, or "1-click" converters if not. A search should bring up both.

IMO most guides make it more complicated than it should be. There's no need for "secret recipes." For me, a commandline guy, it's basically this:

x264 inputfile.mkv outputfile.mp4

Most converters you see are GUI front-ends that do just the above, plus some audio processing.
[Galaxy Tab 10.1 General] StuMcBill:
Ah OK fair enough. I really don't know much about the subject, just thought I would try and help.

Sent from my Amiga 500 using Workbench
[Galaxy Tab 10.1 General] rainbow ng:
Ok I find that Dice player have the nearest result.

It can actually play 1080p for 5 seconds and than lag 4 seconds and than excellent condition for 5 seconds and again lag 4 seconds; loop.

It is the player seem to be will solve the issue in near future. :-)

I don't mind pay money for the app. If anyone or developer do great job, he WORTH it!

and I appreciate for their job.

However, Samsung LIE us in the advertisement ! The stock videoplayer CAN`T play 1080p ! This is the fact !

For those whose very concern on this point, I stronly recommend hold on until perfect solution released !

If my words make u feel un-comfortable, here I say SORRY to u ! :’(

( remember We both cheated by Samsung)
[Galaxy Tab 10.1 General] hbkmog:
Tegra 2 simply doesn't have the horse power to play 1080p video. Not only mkv, it can't even play YouTube 1080p video smoothly. Plus I don't see the point of playing 1080p anyway as the resolution is lower than that.
[Galaxy Tab 10.1 General] TECK:
+1, 720p is the way to go.
[Galaxy Tab 10.1 General] Coolhanded:
I heard from my advent vega days that it would play 1080p at a lower frame rate. so not 30 but 24 frames per second. cant test cos got rid cos screen was a hunk of junk.
[Galaxy Tab 10.1 General] alextso321:
Use moboplayer??? Cant u?
[Galaxy Tab 10.1 General] zhix:
Strange .. I just read GSMarena's review of Tab 10.1 and they claim no issues with 720p. http://bit.ly/nGvlkl
[Galaxy Tab 10.1 General] cnewsgrp:
Great discussion. I just purchased GT10.1 and have a question

What is the best app to play media wirelessly on my network? Most of my videos are 480p, few are 720 encoded in avi or mkv containers. I have purchase vPlayer and have PlugPlayer
[Galaxy Tab 10.1 General] markdj57:
Diceplayer is the only hardware decoder i think, works well for me though any mkvs need to be encoded to a lower bitrate which is poor. It seems xvid and divx play at 1080p according to gsmarena so must try them...
[Galaxy Tab 10.1 General] da.trute:
not another i cant play videos thread.... do your homework people.
[Galaxy Tab 10.1 General] MANIMOZHI:
No audio sound

I am using mx player. It plays all hd videos upto 720p with audio. But plays 1080p video without audio. Ensure that you have checked the option of "software decoding" in settings.
[TG01 General] Godric8:
vorrei comprare questo: http://www.mytrendyphone.com/shop/toshiba-tg01-cover-41318p.html

do you have the slightest idea how to disassemble?
[TG01 General] chdeul:
My French tutorial: http://toshiba-tg01.forumactif.com/t1205-tuto-demontage-du-toshiba-tg01
[Galaxy Tab 10.1 General] zaphyr:
At my work we're not allowed to use the Android (2.1-2.3) built in email client because it's not encrypted, like the iPhone.

Has this changed in Android 3, or does Samsung provide their own encryption for the Tab?
[Samsung Galaxy S (4G Model)] Jerry D:
Does anyone know why the gps gets activated in the stock camera apps on Bionix Frost and Bionix Black Ice?

Also I can't figure out how to disable it. There seems to be no option to disable it. Can we? If so how.

Thanks
[Samsung Galaxy S (4G Model)] FBis251:
I could've sworn this happened on the stock roms too, but are you talking about gps getting enabled even though you had it off, or the gps icon popping up

Sent from my awesome SGS4G
[Samsung Galaxy S (4G Model)] Jerry D:
I'm talking about it getting enabled even though it is off. And there is no way to turn it off in the app.
[Samsung Galaxy S (4G Model)] thcnme956:
Main settings/location and security/ then uncheck everything in my location. That should do the trick
[Samsung Galaxy S (4G Model)] Jerry D:
Ok..that makes sense now. I recently enabled my location in setting for the Weather Bug app.

THANK YOU
[Motorola Droid X2] Igtenio:
So, there's the problem with the X2 having the volume buttons not work when it's locked. I just got one a couple days ago, and decided to poke around to see if I could get it going. I messed with my old Nexus One and reassigned the Search button to the camera, so I started with the keylayout directory. Well, after some experimenting, I got it going. While you have to press the button for each incremental change in volume, it beats having to turn the device on.

Note: I can't post links due to a low post count. So my lack of helpful links is the forums' fault, not mine. My apologies.

What you'll need before you begin;

1) Root access. The X2 can be rooted with Gingerbreak.

2) A file manager. I use Root Explorer.

2b) If you're manually applying the changes, and you're using a file manager without one built-in, you'll need a text editor. Root Explorer has one, so...figure it out. :P

The Long Method

=Step One=

Navigate to "/system/usr/keylayout". The file we're working with is "tegra-kbc.kl"

=Step Two=

Mount the file system as read/write, make a backup of tegra-kbc.kl(I'm partial to adding a .ori to the end, but that's me), and open tegra-kbc.kl in a text editor.

=Step Three=

Lines six and seven, right below Camera, are the volume buttons we're looking for. We're going to append "WAKE" at the end of the line, to tell the phone to listen when they're pressed. Mine looks like this;

key 115 VOLUME_UP WAKE

key 114 VOLUME_DOWN WAKE

Obviously, it's not too picky about spacing. So the sky and your anal-retentiveness is the limit. :P

=Step Four=

Save the file, set correct permissions if they got mangled somehow(rw-r--r--, for reference), and restart.

The Short Method

=Step One=

Download the needed file. Take any public dropbox file link, and replace the end with "/u/3487229/Android/tegra-kbc.kl"

Look, I'd just give the link, but low post count and all. My apologies.

=Step Two=

Make a backup of, then copy the file over /system/usr/keylayout/tegra-kbc.kl

=Step Three=

Reset any mangled permissions(rw-r--r--, for reference), and restart.
[Motorola Droid X2] MrWilliams2:
Awesome.

10char
[Motorola Droid X2] spr0k3t:
Worked a champ. Was trying to figure out how to do this last night.
[Motorola Droid X2] cmanatam:
Could someone paste the tegra file. I think I may have deleted it while attempting to make a backup. Many Thanks!
[Motorola Droid X2] Elite49:
Just tried this and did not work. Looking at file now, says WAKE after each, restarted and still doesn't work.
[Motorola Droid X2] cmanatam:
This may sound dumb, but I don't think this method "fixed" anything. I accidentally deleted the tegra-kbl.kl file but my volume can be adjusted while locked. The trick is to press volume multiple times rather than holding to adjust. FYI I never got a chance to adjust the file per the OP. Lemme know if this works for anyone else.

ALSO I STILL WOULD REALLY APPRECIATE SOMEONE POSTING THE TEGRA-KBL.KL FILE. THANK!
[Motorola Droid X2] Igtenio:
Does it match the above, where there's at least one space between WAKE and the word preceding it? Also, are the permissions correct?

That's how this works when implemented; you can't just hold down volume, but each click changes the volume by one increment.

I'm not sure how you got to where you are; when I accidently deleted the keylayout file on my Nexus One, none of the physical buttons worked, except the power button to power it on.

That was a fun one to recover from. :P

While I see someone else posted the entire original file in another thread, let me post what mine looks like, for comparison.

Modified tegra-kbc.kl, with volume fix and Search reassigned to Camera;

key 102 HOME WAKE
key 139 MENU WAKE_DROPPED
key 158 BACK WAKE_DROPPED
key 212 FOCUS
key 211 CAMERA
key 115 VOLUME_UP WAKE
key 114 VOLUME_DOWN WAKE
key 217 SEARCH WAKE_DROPPED
key 28 ENTER
key 103 DPAD_UP WAKE_DROPPED
key 108 DPAD_DOWN WAKE_DROPPED
key 105 DPAD_LEFT WAKE_DROPPED
key 106 DPAD_RIGHT WAKE_DROPPED
key 232 DPAD_CENTER WAKE_DROPPED
#
# IKXETNA-128 Verizon UTS tool support
#
key 2 1 WAKE_DROPPED
key 3 2 WAKE_DROPPED
key 4 3 WAKE_DROPPED
key 5 4 WAKE_DROPPED
key 6 5 WAKE_DROPPED
key 7 6 WAKE_DROPPED
key 8 7 WAKE_DROPPED
key 9 8 WAKE_DROPPED
key 10 9 WAKE_DROPPED
key 11 0 WAKE_DROPPED
key 56 ALT_LEFT WAKE_DROPPED
key 42 SHIFT_LEFT WAKE_DROPPED
key 62 ENDCALL WAKE_DROPPED
key 61 CALL WAKE_DROPPED
key 228 POUND WAKE_DROPPED
key 227 STAR WAKE_DROPPED
key 231 CALL WAKE_DROPPED
key 162 POWER WAKE
key 14 DEL
key 57 SPACE
key 52 PERIOD
key 51 COMMA
key 16 Q
key 17 W
key 18 E
key 19 R
key 20 T
key 21 Y
key 22 U
key 23 I
key 24 O
key 25 P
key 30 A
key 31 S
key 32 D
key 33 F
key 34 G
key 35 H
key 36 J
key 37 K
key 38 L
key 44 Z
key 45 X
key 46 C
key 47 V
key 48 B
key 49 N
key 50 M
[Motorola Droid X2] Elite49:
Mine looks just like that, still doesn't work.
[Motorola Droid X2] Igtenio:
@Elite49;

Here's what I'd do, on your device. I know we might be treading old ground, but just to rule anything out, try this;

1) Download the attached file. Lop off the file extension so it's just "tegra-kbc.kl"

2) Copy it, and head over to /system/usr/keylayout. Take the existing "tegra-kbc.kl" and put on a file extension that renders it inoperable(I like .ori, but that's just me).

3) Paste the downloaded "tegra-kbc.kl" into the keylayout folder.

4) Check permissions and ownership. Ownership needs to be root on both group and user, and permissions should be rw-r--r--.

5) Power-cycle.

6) Try it out. The quickest way, with that file, is to hold down the search key. If it's using that key layout file, after a few moments your camera app should come up. If it does, then your volume buttons should also be usable when your device is locked.

If you don't want camera on your search key, here's how you change it back. I only suggest doing this after you've verified your device is using this key layout file. If you do it before, then we're back to square one because we're only testing the volume buttons. This's changing two functions, making it easier to see whether it's a hardware or software issue.

1) Open /system/usr/keylayout/tegra-kbc.kl

2) Find CAMERA. Change the key from 211 to 217.

3) Find SEARCH. Change the key from 217 to 211.

4) Save file, check ownership and permissions, reboot. Ta-da.
[Motorola Droid X2] FattyJJ:
Thanks!

This marks a huge negative off of my list! I think I will keep it now.

-JJ
[HTC Sensation] bigevild:
The update for the Sensation is READY! Everyone is waiting for HTC's HQ's to give the ok to send it!!!"

Hopefully this is for s-off, just received this from Twitter
[HTC Sensation] eXceed:
NICE! Although I can't see it on htc's twitter?
[HTC Sensation] GuestK00431:
Funny enough, Snap!
[HTC Sensation] bigevild:
Yeah just been sent it, hopefully baadnwz can confirm he got the same twitt
[HTC Sensation] bigevild:
A guy called idan firma posted it on Twitter
[HTC Sensation] BonesRed:
Trollaz they gon' trollz?
[HTC Sensation] wadill:
It is there..
[HTC Sensation] Electronic Punk:
What is and where is it?

Amazing post.
[HTC Sensation] o0o Wiggy o0o:
It's nothing and it's nowhere
[HTC Sensation] wadill:
It is on twitter posted by the guy he mentioned.
[HTC Sensation] xl VipeR lx:
Well can someone post a screenshot
[HTC Sensation] bigevild:
Not sure how this guy knows, but from reading another post in these forum. HTC have the update there just getting it ready to send out.
[HTC Sensation] phoenx06:
For which carrier or model?
[HTC Sensation] bigevild:
Didn't you do a screenshot from your thread s-off documentation being ready for update
[HTC Sensation] xl VipeR lx:
Yh I did. I thought he might have one
[HTC Sensation] bigevild:
Not sure just posted what I got on Twitter. I know its not a lot off info but that's all I have. Sorry if people think this is a useless thread
[HTC Sensation] umd:
Couldn't find that guy. Could you give us a link?
[HTC Sensation] bigevild:
Idan fima he is on there, for some reason this forum what let me post links yet
[HTC Sensation] BonesRed:
You couldn't find him because he doesn't exist and these 2 guys with less than 15 posts between them, The OP who started this thread as his first post, are trolls. Please let's all stop feeding the trolls and go back to our lives.

If they don't produce some proof in their next post, I say that a mod should close this thread immediately. And if possible check the trolls IP's and ban their regular XDA accounts / IP Addresses.

Edit: Also Idan Firma does not exist but Idan Fima does, and it says it's some photographer with very few likes on Facebook.
[HTC Sensation] xl VipeR lx:
Ok. Could you screenshot it. Save it in paint. Attach it to a post. Or use image shack to upload it direct into the forum using the forum code and posting that in quick reply