[Q] H.263 / 3GPP2 / MPEG4 Video camera - Touch Diamond, MDA Compact IV General

H.263 / 3GPP2 / MPEG4
Which one is best to use to record video?
I am not really concerned about life size, but smaller can't hurt.
I am mainly looking for :
1) Smoothness in the recorded video when played back.
2) Highest quality.
Also, is CIF resolution the highest the phone supports?
I have a Sprint Diamond running Juicy 2.5

I see everyone voting for MPEG4, why MPEG4? Any insight on that?

best quality/low size. playable on most things. newest codec.

where you got 3gpp2 on diamond i have only two options

Related

Slow video playback

Is anyone having problems with video playback?
WMV files they are played very slow (loosing a lot of frames). With MP4 I got best results but not the best. Any suggestions??
Thanks
WMV
I can't even get the above files to play
are you using Media Player? as video playback has always been awful on Medial Player on every pocket pc or smartphone ive everhad.
install TCPMP and video playback will be perfect, and will play any file you throw at it
http://forum.xda-developers.com/showthread.php?t=380387&highlight=tcpmp+diamond
Thanks for the tip keyz86. I'll try it.
no problem, glad to help a fellow Dimondarian
won't play
loaded the TCPMP but everytime I try and start it i get the attached error, using diamond help
keyz86 said:
no problem, glad to help a fellow Dimondarian
Click to expand...
Click to collapse
Dimondarian Cool hehehe
Has anyone been able to play a full resolution file without skipping?
I am using CorePlayer now but if another player works better, please say so.
With Coreplayer I benchmark about 85%, which is not good enough.
I believe the Diamond should be able to get 100%.
I found that an encoded mp4 file would play about the same as the original avi xvid file...
What do you use to encode videos specifically for the Diamond?
Come on!! Post your results!
tretre said:
What do you use to encode videos specifically for the Diamond?
Come on!! Post your results!
Click to expand...
Click to collapse
What video settings do you use with coreplayer ?
DirectDraw, GDI or what ?
This is what i get:
With these configs.:
But with some other videos i have i get only 88% speed and some frame drops and tearing.
Doesnt the Diamond has a good video hardware.
Imo, it shouldnt lag at all.
Ive read somewhere that it doesnt use the hardware correctly since the drivers were not fully implemented. Not sure if its true.
Still looking for a good solution... any more help?
Coreplayer is still choppy ...
Yeah, I wasn't able to get WMVs to play using this, either.
I think what we need to have a look at is which encoding, resolution, bitrate, fps, etc are optimal for the diamond using core player.
I'm experimenting a bit. Will report back in a bit...
I've just got my Ignito (diamond) a couple of days ago, but I've got a long history of video playback on hand helds. Since this is my first time post, and I happen to have a bit of time on my hands.... I'm going to convert a file into a series of different resolutions and settings to see which one will perform the best. I know the objective is to get a full res one to play, but I'll see what I can come up with.
Also, I'm using the default ROM at this time.
With Coreplayer you should use the 'QTv' display option - this is hardware accelerated and beats 100% benchmark on every AVI I have tried. If you get a blank display using this mode, you are using an old version and need to update.
Alright. After trying a bunch of different codecs, encoders, video and audio formats at various resolutions I came the conclusion that for now, full resolution video is just not possible without jerky movements during continuous motion or fast action scenes.
My eyes are very sensitive and I get really irritated if playback is not perfectly smooth.
So far what works the best in achieving this kind of natural playback is AVI as the output container with XviD video codec at 480 x 360 resolution, and mp3 audio. I set the video and audio bitrates to match whatever the source video was (min 864 kbps and max 1008 kbps for video and 192 kbps for audio).
Even then, CorePlayer is a must with the following settigns: QTv On, TytnII driver mode On and Smooth Zoom On.
Every now and again CorePlayer will show only a purple screen during playback when QTv mode on. At that point I usually do a soft reset and it starts working again.
This issue may be resolved with an upcoming release of CorePlayer (1.3) but until then, the solution above works exceptionally well.
I'd be very interested in anyone else is having success in other ways...
320 by 240 versus 640 by 480
I have done some playing with conversion and have found that the Diamond (currently) does not support the 640 by 480 settings with a good bitrate. The BEST conversion I have found (using Coreplayer to play back the files) is using the BETA Version of the Pocket Divx Encoder (http://www.pocketdivxencoder.net/EN_index.htm) and using the HTC Diamond Template (NON VGA!!!!, there is a VGA and non VGA) that team has developed. They have done an excellent job!
The output settings -
Dimensions 320 by 240
Video Quaility - "36" ... 584 kb bitrate
Hopefully an update by HTC or coreplayer will be released to fully utilize the resolution that the Diamond SHOULD be able to support, but for a clear, non jerky playback, this is my 2 cents
im able to play those axxo dvdripson using coreplayer without any sort of convertion....
I want to share my experience. I am using core player and trying to recode unprotected high-definition TV shows (original resolution of 1920x1080) that I've recorded on Windows Media Center (.dvr-ms files) to watch on my Sprint Diamond. Unfortunately .dvr-ms are poorly supported, and the only program I've found to recode is TMPGEnc 4.0 Xpress.
I am using Core Player version 1.2.5 build 4506, and my video output is QTv Display with the Tytn II driver mode enabled.
Like everyone else here, I have had horrible results when converting the shows to DivX at 640x360 at any usuable bitrate (above 500 kbps). Benchmarking in Core Player yielded a playback speed of 66% or so (completely unacceptable, obviously). So I played around with the resolution and bitrate, and finally settled on the following:
Format: DivX
resolution: 512x288 (maintains the 16:9 aspect ratio of the original)
Video bitrate: 850 kbps
Frame rate: 29.97 fps (progressive)
Audio: MP3
Audio bitrate: 80 kbps, 48kHz sample rate
With those settings, I have a 104% playback benchmark with around 25 dropped frames compared to several thousand played, and about 29.5 fps. Basically, it is completely smooth audio and video.
I was still PO'd that I had to sacrifice so much resolution and bitrate on a supposed media device, so I played around with other formats. WMV was awful. MPEG-2 was awful, and avi was passable, but no better than DivX. I also decided to try h.264 (MPEG-4 AVC). Here are the settings I used:
Video Format: MPEG-4 AVC (saves as .mp4)
Resolution: 640x360 (still maintaining the original 16:9 AR)
Video bitrate: 1000 kbps
frame rate: 29.97 fps (progressive)
Audio format: AAC
Audio bitrate: 96 kbps, 48kHz sample rate
Core Player absolutely choked on this. It was unwatchable, and the benchmark revealed a playback speed of 50%. Dropped frames were higher than played frames (!) and framerate was 13 fps. Obviously not successful.
But, before I deleted the file, on a whim I decided to try Windows Media Player and...it was completely FLAWLESS playback. Absolutely beautiful, smooth motion, no audio stuttering, slow and fast pans were the best I've ever seen on a WM device.
Why??? Is there something I'm missing about this that someone can elaborate on? Is this the fabled "hardware acceleration" that I've read so much about? I should note that WMP had a hard time on a 320x240 .wmv file, so I can't really understand how it is able to play a 640x360 .mp4 file so smoothly. In any event, I have found my perfect file format, and, surprisingly, it doesn't involve Core Player in any way.
-R
The thing is that HTC didn't release any kind of SDK for Diamond or Touch Pro and companies like CoreCodec have hard time trying to figure out how to use the HW acceleration but they are trying very hard to improve the situation so maybe with time they will be able to use the HW for now the only way we wan't to watch videos with HW acceleration is only WMP which means recoding or atleast remuxing files.
Cheers
P.S. Could you post exact specs of the .mp4 file? What kind of AVC it was and things like that.
in regards to the WMP hardware acceleration.
is it better on battery life than having coreplayer trying its hard out to render a video. even if its a small 320x vid that plays at 120%. Does that mean that the cpu is running near max?

Best suited video resolution / kbits for TD?

I made a new video with myself with my Samsung HD Camera. It records with 50 FPS and in 16:9 - 1280x720p. I was wondering what the best results would be to convert to for the Touch Diamond. If I choose 25fps from 50fps originally, the video doesnt seem smooth enough.
And if I just choose to make it, say 320x180 and 50 fps at 1000kbit, it lags alot on my phone. What can I do? Its coded with WMV 9 codec.
Try to encode with 30fps, and 640x480 wmv9 WITH hardware acceleration (search for video encoder on forums )

What video encoder/settings do you use?

After a lot of experimenting I've settled on Mediacoder as encoder: free, fast, from everything to everything. The only big disadventage is that it isn't very easy to use (altough the Web UI is ok).
These are the settings I use. I've chosen them because they produce the smallest file/quality compromise while retaining smooth plaback. Also you don't need a special player to view it, WM/the HTC player can do it (altough that might only be since the diamond2 since I use gen.Y's D2 rom)
Container: MP4
Video codec: H.264 (x.264 encoder)
Bitrate: 256 Kbps 2-Pass (target bitrate/average bitrate will produce same sized file faster altough with bit less video quality, since I usually only transcode short music clips etc. and have a fast computer I use 2-pass, but if you want to encode 6 hours of movies you might want to select average bitrate)
Resolution: 640x480
Profile: Baseline - Level 3.0
Audio codec: AAC (Nero encoder)
Bitrate: 96 Kbps
Profile: LC-AAC (make sure you use this, most players can't play HE-AAC yet, e.g. Apple can only do it since iTunes v9, iPhone OS 3.1 and the iPods of fall 2009)
As I said: smooth playback, small filesize and good quality...
Sometimes I have a file which doesn't play really smooth, but lowering the bitrate to 200 Kbps usually fixes that. That is also usually the bitrate I choose for video if I have a really large file and/or want to be sure the file (e.g. film) plays smooth. In my experience lowering the resolution helps a bit on smooth playback, but doesn't really help much. The only reason I use a lower resolution is because I like [email protected] Kbps better than [email protected] Kbps (200 Kbps differs a bit from case to case). Remember: the bitrate gets "divided" over all the pixels so more pixels => less bits per pixel. The only reason to use a higher resolution is because it's sharper but you don't usually see that on such a small screen and low bitrate.
Another thing: I really recommend using x.264 as an encoder rather than the nVidia CUDA encoder. Altough it is waaay faster it also produces worse quality results, especially at low bitrates. So if you have the time: use x.264. If you have the power and space: use the CUDA H.264 encoder.
What do you use?
try handbrake... its free
Pacman15 said:
try handbrake... its free
Click to expand...
Click to collapse
Well, that doesn't sound very good to me...
AVI: AVI is a rough beast. It is obsolete. It does not support modern container features like chapters, muxed-in subtitles, variable framerate video, or out of order frame display. Furthermore, HandBrake's AVI muxer is vanilla AVI 1.0 that doesn't even support large files. The code has not been actively maintained since 2005. Keeping it in the library while implementing new features means a very convoluted data pipeline, full of conditionals that make the code more difficult to read and maintain, and make output harder to predict. As such, it is now gone. It is not coming back, and good riddance.
OGG/OGM: HandBrake's OGM muxer is just as out of date. It hasn't been actively maintained in years either, and it too lacks support for HandBrake's best features. ... This one is not coming back either. ...
XviD: HandBrake, these days, is almost entirely about H.264 video,... Meanwhile, XviD's build system causes grief...
Click to expand...
Click to collapse
Ok, avi I can understand. Anyone who combines AVI with H.264 is just being stupid. But OGM? Xvid? Sound to me more like: we were to lazy to update our requirements and now they're out of date and awfull so we're just removing them...
Removing Vorbis and Xvid from your encoder... Whut?

[Q] LG P990 Video Problem

Hello Community,
so I gat the following problem:
The phone should show and record 1080p and 720p videos. No problem with recording, but I gat a problem with playing a video. Every 1280x720 / 1680x1050 / 1920x1080 video is constantly laggy, but the sound works perfect.
640x360 videos are working perfect, no matter what codec.
The sample videos in 1920x1080 are working perfect, so I think it's a problem with the codecs, but all videos are H264, so what's the problem here?
I hope you can help me!
Thanks,
Max
ps: found no topic about that thing, I hope it's not already existing!
I think tegra 2 doesn't support it (yet?)
Sent from my Optimus 2X using XDA Premium App
aren't they in mkv container? if that's the case, then it's normal... no mkv support yet
sorry but you both failed at my answer.
The LG P990 does support 1920x1080! As I mentioned above the sample videos are working perfectly, but other videos in 1920x1080 are laggy , even when it's the same codec, so what's the problem here?
what do you mean with mkv container?
For all who have the same problem:
I gat the answer now:
The H264 Profile of the video files must be baseline, otherwise your video will lag
You can convert to h264 baseline for example with the program SUPER
Regards,
Max
the problem is the encoding profiles used to create the videos you try to play
You dont mention where these videos come from or if you encoded them yourselves, but video are much more than just the codec.
When videos are encoded there are many different encoding settings that can be used, settings like bitrate, resolution, macroblocks, cabac, reference frames, b-frames, etc. etc. - for H264 these different settings is arranged into something called profiles and levels. Levels go from 1 up to 5.1 and profiles is called baseline, main and high
Each level and profile describe the set of encoding settings that can be used.
Read more details here:
http://en.wikipedia.org/wiki/H.264/MPEG-4_AVC
Different types of content for playback on different kinds of units allows different profiles and levels, like HDTV specifies a maximum profile level to be used and Bluray another maximum profile level to be used. The idea is then that manufacturers of Bluray hardware decoders design their hardware codecs to support up to the maximum profile level for Bluray (which is High L4.1)and the content creators can encode their Bluray videos to the same specifications and thereby ensure that the content can be played on Bluray players.
The Tegra2 chipset support recording and playback of content up to 1080p, but that is only a specification of the resolution - you also have to know which maximum profile levels of encoding specifications it support before you can encode video properly for the Tegra2 chipset. And since it isnt designed for Bluray but for mobile use, it doesnt support the same high encoding specifications as Bluray but only a lower profile level.
The maximum supported profile level for the Tegra2 is 1080p Baseline L4.0 or 720p Baseline L3.1
If you download pirated HD movies, then most of these are encoded with similar or even higher specifications as Bluray movies - these will not play on a Tegra2 chipset.
And if you encode yourself, then you have to ensure that the settings you choose in the encoding application does not exceed the specifications supported by the Tegra2 chipset.
In short - if you download movies you can never be sure it will play because you have no control of how it was encoded. If you want to make sure videos will play, you have to encode them yourself and make sure to use the correct settings.
The videos you have that doesnt play right, will have to be reencoded with correct settings to play.
Edit: I see you found an answer while I was writing this
thanks for the answer
just something to add: The baseline things just getting important when the resolution is higher than 640x480 , my LG P990 can display all videos with all codecs and baselines with 640x480 but 1920x1080 for example will lag So these films are not a problem, because mostly they are 640x480 for mobile phones and not higher, that your Card isn't full with 2 vids
so what program would be best to convert a video to, as stated above :-
The maximum supported profile level for the Tegra2 is 1080p Baseline L4.0 or 720p Baseline L3.1
I normally use Total video Converter but cant find any of the L4.0 ect setting on it.
Kickasskev said:
so what program would be best to convert a video to, as stated above :-
The maximum supported profile level for the Tegra2 is 1080p Baseline L4.0 or 720p Baseline L3.1
I normally use Total video Converter but cant find any of the L4.0 ect setting on it.
Click to expand...
Click to collapse
going to bump this, would be awesome to know exactly what setting and a program to use.
Kickasskev said:
so what program would be best to convert a video to, as stated above :-
The maximum supported profile level for the Tegra2 is 1080p Baseline L4.0 or 720p Baseline L3.1
I normally use Total video Converter but cant find any of the L4.0 ect setting on it.
Click to expand...
Click to collapse
I'll bump again just in hope

Best settings for MAX Video performance?

Hey!
What are your preferred settings and video players to get maximum graphics quality?
For example to view HQ Movies Files or use with streaming apps.
In direct comparison, my HTC 10 does with the VLC-Player and same videofile much better results on display.
Any helpful ideas?
:cyclops:

Categories

Resources