• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Forget 30fps cap. Fix our video camera first.

This is a hardware issue, so there's not much HTC can do to drastically improve image quality. For any camera (SLR, P&S, or cell phones), it's all about sensor size per megapixel. The iPhone 4 and EVO both have the same size sensors (1/3.2") yet the EVO needs to fit 8 megapixels compared to iPhone's 5 megapixels in the same area. There just isn't enough light reaching each pixel on such a dense chip. HTC should have stepped it up and used a 4-6 megapixel sensor instead of cheapened out with an 8.

That is why high end compact cameras use 10 megapixel sensors whereas cheapo $50 cameras use 14 megapixels.

This is was on the right track, but not correct. Cramming more pixels on the same physical-sized sensor does not reduce the quality of the image. Yes, it's true that less light reaches each pixel but the decrease is not enough to create a noticeable difference in overall signal/noise ratio. The problem with super dense sensors is that it's a WASTE of extra pixels when the resolution of the sensor exceeds the resolving power of the glass in front of it. Pinhole cameras, like those found on cell phones, have very poor optics, so it's a total waste to cram a ton of pixels on the sensor.

So why do they do it? Because the general public thinks more megapixels is better. It actually costs MORE to produce a chip with more sensors. So the manufacturer counters this by using pixel sensors of lower quality. Which makes the final picture worse.

When you use high-end lenses for full-frame dSLRs (the sensor is the same size as the frame of a 35mm film camera), you only need 6-10mpx to capture the detail that the lens provides. For cameras with crappier optics, you'd need fewer megapixels. Most consumer cameras can therefore get away with only 3mpx and still produce the same quality image as a 10-15 mpx sensor.

So because of the general public's stupidity, we have no choice but buy cameras with way too many megapixels, which does nothing to improve image quality and forces us to find more storage space.
 
CyanogenMod-6 encoding in H.264 . I'm testing as we speak to see if there is a difference.
Just a heads up.

Woot - in addition to video - or at least this if you can't post a vid - kindly provide an info page so we can see the codec info and the bitrate it used.

Did I mention w00t?!?!

PS -

http://forum.xda-developers.com/showthread.php?t=735596&page=45

No 720p just yet...

Still - H.264 vid - w00t!! Going for the trilogy: w00t!!!

Still huntin' to see what audio codec they've got... prolly, it's fab.
 
Woot - in addition to video - or at least this if you can't post a vid - kindly provide an info page so we can see the codec info and the bitrate it used.

Did I mention w00t?!?!

PS -

[ROM] CyanogenMod-6 - No Sense at ALL! - V6.0.0-RC1 (07/25/2010) - Page 45 - xda-developers

No 720p just yet...

Still - H.264 vid - w00t!! Going for the trilogy: w00t!!!

Still huntin' to see what audio codec they've got... prolly, it's fab.

I'm trying but i am at work so no ways to mess around. Work first eh. But i will when i head home soon. Again woot woot. :eek:
 
ssadasd.PNG

Hopefully this is the right one. I have been too busy sorry if anything.
 
Hopefully this is the right one. I have been too busy sorry if anything.

Yes, THANK YOU!

OK - we still have the AMR audio codec - exactly what I expected so far.

Hey - Rome wasn't built in a day, this is great progress!!!!

Avoid the 720p stuff, I think with the most recent build, as I've lurked that that leads to green screens and crashes - again, gotta crawl before ya walk before ya run, but hats off to Cyanogen for this breakthrough.

I'd have never thought to see it so soon, and I'm bowled over that it's come from the dev community rather than the big-iron vendor.

If you get a chance to show the same again with bitrate on the vid, fabulous, otherwise, no pressure nor worries.
 
Yes, THANK YOU!

OK - we still have the AMR audio codec - exactly what I expected so far.

Hey - Rome wasn't built in a day, this is great progress!!!!

Avoid the 720p stuff, I think with the most recent build, as I've lurked that that leads to green screens and crashes - again, gotta crawl before ya walk before ya run, but hats off to Cyanogen for this breakthrough.

I'd have never thought to see it so soon, and I'm bowled over that it's come from the dev community rather than the big-iron vendor.

If you get a chance to show the same again with bitrate on the vid, fabulous, otherwise, no pressure nor worries.

Actually, I've got some time to kill, so I'll be recording three versions of the same room with my Evo

1. Using the default MPEG4 codec, running Fresh 1.0.1, bit rate increased to 10 Mb/s.
2. Using the default MPEG4 codec, running Fresh 1.0.1, bit rate left at stock value, which is either 6 or 8 Mb/s.
3. Using the h.264 codec, running CyanogenMod 6 RC1, bit rate set to 2 Mbps, what Cyanogen has it set to.

The video I'll be recording is in relatively poor lighting conditions, but I'm hoping it will at least be a little bit useful.

Edit: For anybody who's interested, I'll be uploading the raw footage for download in case you don't trust Youtube or just want to see what the actual output looks like.

Using the default MPEG4 codec, bit rate increased to 10 Mb/s (Poor lighting conditions)
DOWNLOAD: http://www.mediafire.com/?wjdflhikdf2lfhr

Using the default MPEG4 codec, bit rate set to 6 Mb/s (Default bit rate for Evo) (Poor lighting conditions)
DOWNLOAD: http://www.mediafire.com/?lavt5dta4fcj7xh

Using the h.264 codec, bit rate set to 2 Mb/s this is what Cyanogen has it set to, for some reason (Medium lighting conditions)
DOWNLOAD: http://www.mediafire.com/?yz0faqyy7yi6i0k

Using the default MPEG4 codec, bit rate increased to 10Mb/s (Medium lighting conditions)
DOWNLOAD: http://www.mediafire.com/?h8co3jowsujyibo

Using the default MPEG4 codec, bit rate set to 6 Mb/s (Default bit rate for Evo) (Medium lighting conditions)
DOWNLOAD: http://www.mediafire.com/?nw40oy986gvnbrz

Using the default MPEG4 codec, bit rate increased to 10Mb/s (Excellent lighting conditions)
DOWNLOAD: http://www.mediafire.com/?8bp7pg8t8145gzg

Using the h.264 codec, bit rate set to 2 Mb/s (Excellent lighting conditions)
DOWNLOAD: http://www.mediafire.com/?bb673wqz182sgz6

Using the h.264 codec, bit rate set to 13 Mb/s (Moderate lighting conditions)
DOWNLOAD: http://www.mediafire.com/?v4a5z0850t3ef9d

Using the h.264 codec, bit rate set to 13 Mb/s (Excellent lighting conditions)
DOWNLOAD: http://www.mediafire.com/?cl6ivxnj7n727o8

Using the h.264 codec, bit rate set to 13 Mb/s (Excellent lighting conditions) Take Two!
DOWNLOAD: http://www.mediafire.com/?fty4o0dbuxc8j3t
 
This is a hardware issue, so there's not much HTC can do to drastically improve image quality. For any camera (SLR, P&S, or cell phones), it's all about sensor size per megapixel. The iPhone 4 and EVO both have the same size sensors (1/3.2") yet the EVO needs to fit 8 megapixels compared to iPhone's 5 megapixels in the same area. There just isn't enough light reaching each pixel on such a dense chip. HTC should have stepped it up and used a 4-6 megapixel sensor instead of cheapened out with an 8.

That is why high end compact cameras use 10 megapixel sensors whereas cheapo $50 cameras use 14 megapixels.

Couldn't we just change the resolution setting to 5mp then and in theory get a better quality photo?
 
Actually, I've got some time to kill, so I'll be recording three versions of the same room with my Evo

1. Using the default MPEG4 codec, running Fresh 1.0.1, bit rate increased to 10 MB(b?)/s.
2. Using the default MPEG4 codec, running Fresh 1.0.1, bit rate left at stock value, which is either 6 or 8 MB(b?)/s.
3. Using the h.264 codec, running CyanogenMod 6 RC1, bit rate set to whatever Cyanogen set it to (I can't find those settings using this rom)

The video I'll be recording is in relatively poor lighting conditions, but I'm hoping it will at least be a little bit useful.

Thanks for the video upload. It does look like the 10Mb/s looks a little better. If you look at the lower quality one, the pixels become larger/blockier with faster movement.

P.S.

I think its 10Mb instead of 10MB
 
Does anyone else find it a little sad that the hobbyist developer community is having to fix all of these things that HTC is incapable of or can't be bothered to fix?

It's leaving a pretty sour taste in my mouth and as much as I like my Evo it will probably be my last HTC phone.
 
Does anyone else find it a little sad that the hobbyist developer community is having to fix all of these things that HTC is incapable of or can't be bothered to fix?

It's leaving a pretty sour taste in my mouth and as much as I like my Evo it will probably be my last HTC phone.

Nope..

How do you know HTC is not working on them?

They could possibly have some fixes with the new update arrives.

But I understand your frustration..
 
Does anyone else find it a little sad that the hobbyist developer community is having to fix all of these things that HTC is incapable of or can't be bothered to fix?

It's leaving a pretty sour taste in my mouth and as much as I like my Evo it will probably be my last HTC phone.
Nah, it's a universal problem across all phones (aside from BB for the most part). Phone manufacturers are incentivised by the market to put out products that are never fully complete and/or have all of the kinks worked out.

The reason for this is the speed in which the phone tech industry evolves. When almost any phone is first conceptualized and schematically laid out, it utilizes the most cutting edge technology... because that's what buyers want. Thus, when they finally come out with a solid piece of hardware (several several months later) that may be glitchy in the software, they must throw it into the market for sale asap. This is because another developer that started their phone later on (think EVO vs Epic) will drop their phone into the market asap, and will inherently have better hardware because they started later when the industry had evolved further.

So considering that most sales occur right after the release date, if HTC were to wait until ALL of the bugs were worked out with the Evo, they wouldn't be able to drop it into the market until about the same time as the Epic. And if that happened, which one would you buy? The older hardware that will become obsolete sooner, but has solid software? Or the newer hardware that will resist obsolescence longer, but you may have to wait for just a few updates to fix the software shortcomings (nothing critical to use, but things that are in fact just glitchy)? I for one would just buy, or wait a couple weeks to buy, the newest hardware... Because I am impatient and I want my phone now before something else that's promising more starts to shine in the not-so-distant future.

If every producer were to wait until they had squeaky clean software then, all developmental time being relative, it wouldn't be a big deal (exept that EVERYONE would be buying old-news hardware at the time of release). However, you are always going to have companies fighting for market share, meaning that they are going to drop their products into the market asap along with an understood promise that they will fix the issues later on (unless of course you are dealing with Samsung).

So no, I don't find it sad. And I expect to see some improvement by HTC in the 2.2 update. Sure we have to wait longer to get everything in one package, but such is the nature of the beast. And based on your previous argument, if this is going to be your last HTC phone then I should recommend going to a BlackBerry because they seem to have a very high return user turnaround (because of their target demographic, and their software doesn't seem to play well with other phones). Thus they can afford to take more time on making their phones as solid as possible upon release.
 
I was watching the camera videos filmed at droid Dog site of the samsung g vibrant and another camera beats ours. The iphone 4 is the leader in video but htc can't even beat samsung. Is this hardware or software? This is worth rooting over if we can match the competition video quality. I love the phone but come on htc you can do better.
that would be great if then make a fix
 
The 10Mb/s seems to help with the lighting conditions (graining reduction) and reduce motion blur somewhat. Looks promising , but I hope the file isn't super large when you're done recording. This is about twice the size of the stock file.


Where is the Cyanogen vids already???
 
Ok cyan video encodes are h264/h263/m4v and audio codecs are amrnb/amrwb/aac.

From what i read h264 is the best for video, but for audio which one should i be looking at more.
 
Back
Top Bottom