I don't believe that is correct. Not all videos on YouTube are available in HQ. Standard definition on YouTube is 320x240 which the YouTube player scales up to 480x360 in the browswer window which makes the video quality degraded. When playing a video that is capable of being displayed in HQ it displays natively at 480x360 without scaling. 480x360 is higher resolution than the G1's native 320x480.
The JaceMan's AC Forum Stats
Kind Words Spoken = 0
Helpful Information Provided = None
Persons Owned = Many
Plans to Change Said Operation = See "Kind Words Spoken"
=-=-=-=-=
To view links or images in signatures your post count must be 5 or greater. You currently have 0 posts.
|
To view links or images in signatures your post count must be 5 or greater. You currently have 0 posts.
!
=-=-=-=-=
My Android App =
To view links or images in signatures your post count must be 5 or greater. You currently have 0 posts.
touche.
where does the frame size limitation of the g1 video player come in then jaceman? because one defintely exists.
To view links or images in signatures your post count must be 5 or greater. You currently have 0 posts.
To view links or images in signatures your post count must be 5 or greater. You currently have 0 posts.
, coming 2011
follow
To view links or images in signatures your post count must be 5 or greater. You currently have 0 posts.
-
currently:
imported nexus one on vodafone nz
cyanogenmod 6.0.0-n1 | amon ra recovery 1.7.0.1
radio 4.06.00.12_7 | 16gb class 6 sd
graveyard:
imported t-mobile g1 on vodafone nz
cyanogenmod 4.2.15.1 | ra recovery 1.2.3
radio 2.22.19.26I | 16gb class 6 sd
If there is a specific limitation (resolution and not processing power) I don't know what it is. My educated guess would be that if YouTube HQ (480x360) doesn't match the G1's limits, the next logical stop would be 640x480 VGA playback limitation. But as the G1's native resolution is only 320x480, I wouldn't bother encoding anything at a higher resolution than 480 (width) as you really wouldn't gain anything except larger file size.
If the question is: what to encode at? Then it would be foolish to go beyond 480x360 as it would be a waste. If the question is: will it play this video I downloaded? I'd have to answer with: 'Try it and see.'
The JaceMan's AC Forum Stats
Kind Words Spoken = 0
Helpful Information Provided = None
Persons Owned = Many
Plans to Change Said Operation = See "Kind Words Spoken"
=-=-=-=-=
To view links or images in signatures your post count must be 5 or greater. You currently have 0 posts.
|
To view links or images in signatures your post count must be 5 or greater. You currently have 0 posts.
!
=-=-=-=-=
My Android App =
To view links or images in signatures your post count must be 5 or greater. You currently have 0 posts.
Just my 2p worth here...
A few months ago I was reading a T-Mobile G1 transcoding thread I'd stumbled upon, while Googling something else Android related, which just caught my attention briefly. They were discussing the command-line parameters to pass to some transcoding software on Linux to transcode AVIs into a suitable format for playback on a G1.
The outcome boiled down to two formats:
427 x 320 x 30fps (or fps of original if less) for 4:3 content.
480 x 270 x 30fps (or fps of original if less) for 16:9 content.
In both cases, as JaceMan pointed out, you're not going above the G1's native resolution (which would be pointless).
It's also worth noting that the G1 can play HQ YouTube videos very well. The lowest HQ YouTube quality (of which there are 3 types), uses MPEG4, which is essentially what DivX is. So I would assume the overhead of DivX decoding would be similar.
However, I do not know which of the HQ formats the G1 chooses to use. The higher quality of the three HQ formats YouTube uses is FLV - which could be anything wrapped in Flash - I've not bothered to check.
Bookmarks