Hello,
I am using mencoder to convert my video files to mp4. The command line I am using seems to work great. If subtitles are located in the same directory with the same name as the video file, then they are hardcoded into the video as well. My only problem is trying to find the right resolution and bitrate for the HTC Desire for best possible picture. Does anyone know what the optimal settings are for these two values?
Code:
#!/bin/bash
FILE="$1"
NOEXT=${FILE%\.*}
mencoder "$FILE" -o "$NOEXT".mp4 -sub "$NOEXT".srt -subcp cp1252 -utf8 -vf dsize=640:480:0,scale=-8:-8,harddup -oac faac -faacopts mpeg=4:object=2:raw:br=128 -of lavf -lavfopts format=mp4 -ovc x264 -x264encopts nocabac:level_idc=30:bframes=0:bitrate=800:threads=auto:turbo=1:global_header:subq=5:frameref=6:partitions=all:trellis=1:chroma_me:me=umh
From the example above, I am using 640x480 as the resolution and 800 as the bitrate. With these two values, the picture is not that bad and the file is pretty small. But, from what I have read, the HTC Desire should be able to perform with a resolution of 800x480. Unfortunately, the picture quality on the HTC Desire is terrible when I increase the resolution to 800x480. Should it not be able to handle this resolution? Is my bitrate just too slow for this higher resolution? Does anyone have the perfect combination of bitrate and resolution?
I use 640x480 (480p)
I can't link using this app on the phone but check my second to last post (about Super © in the MKV lip sync thread), it has many details on a similar discussion as well as some test encoded files.
The best resolution depends on the source file but, 800*450 16:9 works excellent since many of the higher quality vids come in this aspect ratio too. I don't change the aspect ratio of the vids unless extremely needed.
Bit-rate/quality is too relative for me to be absolute on, however, check the vids we encoded linked in that thread. The "highest, playable" visual quality seems to be near the 2.3 Mbps 25FPS zone but even 288 Kbps 15FPS settles fine for me, so what do I know. High bit-rate equals larger files being the major limitation as well as it meaning lower battery-life. Generally, the most used mobile HD settings lie in the 700-1000 Kbps range. A very good compromise in my opinion.
Lastly, it depends a lot on the video playback app you are using too. Some will also stretch one or both dimensions of the vids to full-screen without notifying or apply a level of zoom. Yxplayer, for instance, really kills the visual quality off.
-------------------------------------
- Sent via my HTC Desire -
640*480 @ 800 kbps seems about as good quality as I'm gonna get.
It should be able to handle 800x480, at least the Nexus One can. I found this guide for Handbrake that I want to try out for myself
http://www.frankie.bz/blog/tips-and-tricks/convert-video-nexus-one/
-----
Smart Adopter - UK based tech hints, tips, news and reviews
http://smartadopter.wordpress.com
I started to notice a slight lip sync problem with files encoded over 800 kbps. When I lower the bitrate to 700, I seem to get perfect sync every time. This seems to only be an issue with mp4 files (other supported video formats do not seem affected).
it can handle 800x'xxx'. i've used megui to encode x264 vids in an mp4 container and it plays em fine. only variable now is to try and lower the bitrate to see how low i can go with it before noticing a quality drop.
Tsjoklat said:
Hello,
Code:
#!/bin/bash
FILE="$1"
NOEXT=${FILE%\.*}
mencoder "$FILE" -o "$NOEXT".mp4 -sub "$NOEXT".srt -subcp cp1252 -utf8 -vf dsize=640:480:0,scale=-8:-8,harddup -oac faac -faacopts mpeg=4:object=2:raw:br=128 -of lavf -lavfopts format=mp4 -ovc x264 -x264encopts nocabac:level_idc=30:bframes=0:bitrate=800:threads=auto:turbo=1:global_header:subq=5:frameref=6:partitions=all:trellis=1:chroma_me:me=umh
Click to expand...
Click to collapse
Adding the following line after the mencoder line will allow the mp4 file to be streamable in your apache web server:
MP4Box -inter 500 "$NOEXT".mp4
This way I can play all the movies I want w/o having to copy them ever on the phone when I am at home. Awesome.
I tend to use
Code:
/usr/bin/mencoder -ovc x264 "$1" -o "$2".mp4 -of lavf -lavfopts format=mp4 -vf dsize=400:240:0,scale=0:0,expand=400:240:-1::::,harddup -sws 9 -x264encopts crf=24:force_cfr:bframes=0:nocabac:no8x8dct:global_header:bitrate=412 -oac faac -faacopts br=96:mpeg=4:object=2:raw -af volnorm=1 -channels 2 -srate 44100 -delay 0.3
produces very good output at a good size.
$1 = input file
$2 = output name with a .mp4 appended
I have seen in some build.prop there is a line
debug.composition.type=c2d
Or
debug.composition.type=mdp
Or
debug.composition.type=cpu
Or
debug.composition.type=gpu
Can anyone tell me what the c2d and mdp stand for I have trodd searching Google Bing and xda and can't find an answer
Sent from my SPH-D710 using Tapatalk 2
Anybody have anything?
Sent from my SPH-D710 using Tapatalk 2
If you turn on debug.sf.hw you can change the composition type
# with this variable.
#
# cpu (default)
# gpu (default when debug.sf.hw = 1)
# mdp if your hardware supports MDPv4
# c2d if you have c2d support
# dyn use copybit
# asn upcoming kernel interface
#debug.composition.type=
For a project, I need to achieve 500Hz Sampling rate from the Accelerometer. I am using Nexus 7. And at the SENSOR_DELAY_FASTEST mode it has the sampling rate of 200Hz. How can I increase the sampling rate? I have tried to change the MPLSensor.cpp file on Kernel. But I am still a Beginner in this matters. So my first question is , Is it possible to achieve that level of frequency?
I have seen that Nexus 7 has MPU-6050 Accelerometer which is capable of giving output of 1000Hz. But I dont know why I am getting 200Hz.
My lg g3 (rooted)lags terrible when playing some games but when i upgrded to cm 13 they worked perfectly anyways to decrease lag on stock?
low the resolution
try to low the resolution with terminal emulator, type there this code:
su
wm size 1080x1920
wm density 530.
your phone gonna be much faster.
sorry about my english
Skybutu said:
try to low the resolution with terminal emulator, type there this code:
su
wm size 1080x1920
wm density 530.
your phone gonna be much faster.
sorry about my english
Click to expand...
Click to collapse
How do you revert the settings if you do that?
Sent from my LG-D855 using Tapatalk
Requirements: ADB Fastboot and Windows PC
Enable USB debugging in the developer opinions in settings and connect to USB using data cable.
In the search bar on Windows type CMD.
For this tutorial we will be using the Moto G7 Power screen resolution.
In CMD type adb shell wm size 720x1520 and adb shell wm density 319
To go back to stock just type adb shell wm size reset and adb shell wm density reset.
Go to display settings and keep the display on for 30 minutes before you tamper with the display settings or it could lead to a soft brick.
Download GPU Mark benchmark and you will notice it's much smoother and there's a 20ms difference in latency.
My scores:
GPU Mark
720x1520 957600
1080x2300 stock 592800
Geekbench Compute
Open CL: 366
Vulkan: 506 (beat the best score 501)
Original settings for G Power 1080x2300 and 319 DPI.
This should help apps open faster and the UI will feel more fluid.
Gamers will also benefit from increased fps in games like PUBG.
enjoy!
Has anyone else tried this?
You are lowering the display resolution is all that's happening here. Since there is less pixels to display it will be able to render faster in exchange for loss in visual fidelity (resolution).
It's like running a benchmark in 1080p then the same one in 720p. You can make things appear bigger or smaller using the DPI setting.