-
Ideal rendering options for Motorola Xoom?
-
[Randy Brown] “Thanks so much JR…just one more question; the default bit rate of 8,000,000 means 8mbps right?”
Yes, 8Mbps is 8,000,000 in Vegas.
[Randy Brown] “You guys in that old thread were talking about 3mbps so I rendered out to 3,000,000 and it looked pretty bad (lots of blocking).”
3Mbps is just a starting point. It depends on how much detail is in your footage. I would keep adding 1Mps until it looks good. So try 4Mbps then 5Mbps etc. 6Mbps should be pretty good but you may get away with less. It’s really trial and error depending on your content.
~jr
http://www.johnrofrano.com
http://www.vasst.com -
I had found that the 8mbps looks nice on the computer, and often plays well on the Xoom. Sometimes the playback gets a little jerky on the zoom, but not enough for me to care in the context I’m using it in. Someday I’ll play with it more to try and find the “perfect” compromise between video quality and playback smoothness for my Xoom.
-
yessir, 6 mbps looks decent enogh I’ll send him that and hopefully he gets good playback…thanks again JR!!!
-
yessir, 6 mbps looks decent enough I’ll send him that and hopefully he gets good playback…thanks again JR!!!
-
-
When I did my original benchmarks (on a Notion Ink Adam, running the same Tegra 2 as the Xoom) I was on Android 2.3. The most objectionable thing I found was that the player itself was broken.
The occasional bit of jerkiness is usually easy enough to avoid in a good media player design, but not the end of the world. All consumer-level players on PCs have to account for the occasional bit of PC overload, so they double or triple buffer the video, and they sync video to audio. If the video decoder gets behind, they’ll drop a frame — simple enough.
Only, at least in Android 2.2, that didn’t happen. It sure looked to me as if the audio and video were being processed by unrelated threads. Not a problem up to 6Mb/s with Main Concept AVC, 720/24p I think I was running. But much beyond that, and it wasn’t glitching that was a problem, it was the audio walking away from the video, as the player endeavored to show every video frame. There probably had to be a limit on the de-sync, but I didn’t find it.
That issue could easily be solved by a proper player design. As I have ICS on there now, it’s probably time to try it again and see if they actually did fix it (I reported the problem.. know a few more people at Google these days, though not necessarily involved in Android). All Tegra2 AVC decoding is supposed to be done by a special processor on the Tegra (not the GPU, but a special video decoder module, usually the case on ARM SOCs), but there’s no telling if all implementations use this… and some of the nVidia stuff is still closed source, so I may be seeing worse-case performance than an OEM build would today.
-Dave
-
Thanks Dave,
With JRs help we finally got a 5mbps render to play on his xoom…he’s never updated it in the year that he’s had it so I encouraged him to look for an update to which he said he would.
Thanks again,
Randy -
Reply to this Discussion! Login or Sign Up