Only had my Desire HD about 3 weeks, rooted last week, installed Lg Camera Pro.....but as I know absolutely ZERO when it comes to any kind of camera/camcorder stuff...what is the best setting for best possible video quality?
Options under video resolution are:
640 x 480
704 x 576
720 x 480
800 x 480
960 x 720
1280 x 720
Then I have video encoder options:
Default
H.263
H.264
MPEG4
Then: Video file Format
MPEG4
3GP
File size at the end of the recording is not an issue, as I have a big SD card and don't record to much video, but when I do record I want it to be the very very best possible.
Any help - very very much appreciated.
cheers
Matt
Hi matt
For me, the best possible video output is 800x480 with MPEG4 as format. Stable 50fps under bright place and still manage to maintain 20+ fps in low light. Recording in full HD is nice, but limited to 30fps at most and low audio bitrate. Also, try to adjust the sharpness to -1 or -2. It will improve the fps. There's also a thread for DHD camera guide I guess. For better compression, I choose the H.264 format.
Related
I just realised the the TP2 can record VGA (640x480) video. I played with the camera settings and found that if video recording format is set at MPEG4, the resolution can be set at up to VGA quality. If the recording format is set at H264 or H263, the resolution would only goes up to QVGA.
I would have preferred H264 over MP4. But at least I now know that TP2 can record VGA video. Hopefully future updates of the HTC camera app would add H264 VGA recording.
Are there other MSM7200 devices that can do H.264 at 640x480 at any reasonable framerate? I ask because as I understand it, it's pretty processor intensive to compress that amount of data...
Lord_BlackAdder said:
I just realised the the TP2 can record VGA (640x480) video. I played with the camera settings and found that if video recording format is set at MPEG4, the resolution can be set at up to VGA quality. If the recording format is set at H264 or H263, the resolution would only goes up to QVGA.
I would have preferred H264 over MP4. But at least I now know that TP2 can record VGA video. Hopefully future updates of the HTC camera app would add H264 VGA recording.
Click to expand...
Click to collapse
so is this only for the msm7200 or also for the 7201a
Lord_BlackAdder how you do it?? explain please step by step, i already try all the settings in video recording and nothing, only the small resolution, no alternatives to change
hello..
i have a sprint touch pro 2.
i used to have the stock sprint wm6.5 rom installed. and it used to take okay-quality videos.
yesterday, i flashed energy rom, and since then, the quality is so bad. i use the same format (mp4 VGA), but the one on the energyrom is bad. a 10 second video on the sprint rom is around 1+mb.. on energyrom, it's only around 200kb. whats wrong with this?
thanks
Recorded a video last night and uploaded it to Youtube but Im not impressed with the quality.
Checking the settings its set to 640x480 (VGA) but the video is awfully blocky. I was under the impression that VGA recording on the TP2 was rather good.
Am I expecting too much from the device or is there something amiss here?
Does noone have any input on this? Is the linked video what I should expect from TP2 video footage?
What settings did you use?
I use Resolution L (320x240) and Capture Format MPEG4
Comes out fine for me.
Capture Format: MPEG4
Resolution: VGA (640x480)
Its blocky both on the Youtube conversion and on the phone itself.
Could it simply be a result of poor recording venue?
If there is low light this will make a difference. But test and see. Try the slightly lower resolution (because then it can cope with better compression and may be less blocky). Would be interested if anyone else has different settings. Cheers.
I have a issue with the video recorder in CM7. I had this in RC1v2 and also in latest nightly, don't know in versions before that.
I can't use the high and youtube resolution setting. I can select them, but when I press the record button nothing happens. The other settings, for example wide, do work.
Is this normal? If not is there a sollution to solve this?
I installed Nordic rom and reinstalled CM7 latest nightly, that didn't solve my issues.
However changing the frame rate for the encoder profiles (in media_profiles.xml) to 24 did. (this was a suggestion in the developers forum). Now I can use all resolution settings.
My defy has red lens.
During testing I also noticed that the standard bitrate for the high and wide recording setting are really high.
For a 640x480 (high) mp4 video it is 10000 kb/s
For a 848x480 (wide) mp4 video it is 8000kb/s
This a lot higher then most good looking xvid 720p movies I have , which are around 2000 kb/s.
I now use 1300 kb/s (high) and 1500 kb/s (wide) which seems to give usable results but with a lot smaller videos.
Which settings do other people use/suggest?
Try the newest LG Cam (free) from market an set it to these parameters:
video resolution: 848x480
video encoder: mpeg4
video file format: mpeg4
video bitrate: 8
video framrate:24
audio encoder: ACC
audio samplerate: 44100
audio bitrate: 62900
and check force autofocus before capture
This works great on mey Defy (red lense)!
After much experimentation, I have found that the epic prefers 5:3 aspect ratio. If you want the maximum in clarity and optimized file size for your videos, here are the settings I came up with. Adding more to either bitrate wont help the quality.
Customized MP4 Movie (*.mp4) template in Freemake
Video Code: MPEG4 (NOT h.264 or x264)
Frame Size: 1000x600 (5:3 ratio)
Video Bitrate: 1280
Video framerate: 24
Encode Passes: 2
Audio Codec: AAC
Audio Bitrate: 160
Sample rate: 44100
Audio Channels: 2
Disable Audio: No
A/V Sync: Default
These settings work great on my Arnova 10b (Capacitive) and my Touchpad. They would also work great in an iPad or XBOX. I used the high resolution to fill the screen of my Arnova without stretching. It works fine on my Epic.
Here the question: Why 5:3? Any other aspect ratio does not actually fill the screen. If you make a 800x600 (4:3) video, you will find that the player does not actually fill the screen. Thoughts?
The screen resolution is 800x480, which is 5:3...
Just make the video 800x480, and it won't have to do any scaling.
Interesting. Gonna check my videos and see what res I have them in, because they look awesome as it is.
LunaticWolf said:
The screen resolution is 800x480, which is 5:3...
Just make the video 800x480, and it won't have to do any scaling.
Click to expand...
Click to collapse
I did that resolution... It worked great for my epic.. I settled on the resolution I used because it worked awesome on all my devices.. even my touchpad. The cost in file size is almost nothing between the two resolutions.
Ok, I have a 720p video.. it looks amazing at its normal resolution of 1280x720.. no cropping that I can notice..
I'm an editor by trade.
What you're looking for is H.264 in .mp4. I tend to go for a video bitrate that hangs out around 1.5mbps and AAC stereo audio at 160kbps, 44.1kHz. There are quite a few artifacts in the shadows, but for watching a movie on an airplane it'll suffice.
The key to both a sharp picture and long battery life is to properly prepare the video. When your video is under or over 800px wide the Epic has to perform scaling to make it fill the screen (or sacrifice filling the screen if it is under). This scaling is an additional calculation it must perform, which hits the battery, and is a transformation on a lossy codec - a quality killer. If you have the render power (48 i7 cores and segmented processing makes for fast work) you can always hit it with mild sharpening for that extra pop.
Export your video at 800 pixels wide by whatever makes the correct aspect ratio. It's a bit of simple algebra, set up a proportion, cross-multiply, divide, and bang.
ex:
(1280/720)=(800/x)
1280x=720*800
1280x=576,000
x=450
800x450 <-- use this for any 16x9 broadcasts
(1.85/1)=(800/x)
1.85x=800
x=432
800x432 <-- use this for movies presented in 1.85:1, 2.35:1, and 2.40:1.
If it's 4x3 export at 640x480.
I just scale up to 4k. Looks pretty good =D
Is there any tweak for full hd (1920x1080) video playback on wave??
But this makes really no sense...
Display is 480 x 800 Pixel...
I think als TV output is 480 x 800 Pixel ?
Will check.
Anyway. Wave must shrink/scale Video for playback...
Why not use PC... there are more then 10000000 Tools for convert Videos...
Best Regards
adfree said:
But this makes really no sense...
Display is 480 x 800 Pixel...
I think als TV output is 480 x 800 Pixel ?
Will check.
Anyway. Wave must shrink/scale Video for playback...
Why not use PC... there are more then 10000000 Tools for convert Videos...
Best Regards
Click to expand...
Click to collapse
It doesn't make you sense? for example galaxy s support full hd video playback and display is also 480x800 pixel...
It doesn't make you sense?
Click to expand...
Click to collapse
At the moment you have NOT full access to change all internal bada OS parts... Read about apps_compressed.bin or the OSP thingies with *.so extension...
So you have 2 choose between:
A.: galaxy s
B.: do nothing and wait... wait and wait...
or C... if Wave not play your Video, then convert before on PC.
Your choice.
Oh forgotten, you could research by yourself... maybe I have something overseen.
Best Regards
Rastafarian- said:
It doesn't make you sense? for example galaxy s support full hd video playback and display is also 480x800 pixel...
Click to expand...
Click to collapse
But Galaxy S have (micro?) HDMI output, right? So it is possible to get 1080p on Full HD TV. And Wave have only TV-Out analog PAL 576 lines/NTSC 480 lines. And also 4 GB limitation on SD card - FAT32 file system. And finally, there is no difference in video quality on Wave's screen (800x480!) between 720p with high bitrate (4-5 Mbps) and 720p with bitrate ~900 kbps after transcoding (I tested it). Artefacts are invisible on Wave's screen, only on monitor or TV with full resolution of 720p you'll see the video isn't good. But on Wave's display it's clean.
PS. Wave won't play video with too high bitrate (higher than 5-7Mbps, I don't remember exactly, I've checked this on some video samples).