What are the specs of your computers and how long are your average encodes taking ?. I'm looking to buy some new gear soon so I'm just looking to find out how fast the encodes can be.
I have over 100 720p films to convert so its gonna be very time consuming.
mug2k said:
What are the specs of your computers and how long are your average encodes taking ?. I'm looking to buy some new gear soon so I'm just looking to find out how fast the encodes can be.
I have over 100 720p films to convert so its gonna be very time consuming.
Click to expand...
Click to collapse
I just encoded Tron Legacy on a Core i5 2500 using the handbrake profile that's been posted. It took about 40 minutes. I'm sure it would take longer if I used my laptop that is a Core i3 540
I've never used it, but if you have an NVIDIA GPU, you could look at Badda Boom. It's supposedly something like twenty times as fast as a CPU encode.
*Daedalus said:
I've never used it, but if you have an NVIDIA GPU, you could look at Badda Boom. It's supposedly something like twenty times as fast as a CPU encode.
Click to expand...
Click to collapse
http://www.badaboomit.com/
Haven't tried it though.
Depends on how long the video is. For a 1 hour video, takes about 30minute for 1pass only. 2pass takes longer and compresses better.
So your source material is 720p or are you converting to 720p from 1080p?
Anyways Here are my specs and time, also CUDA FTW
I use mediacoder because the CUDA support it the best i have found for free
I dont have any 1080p source material so i downloaded some 1080p high profile trailers
Main Specs:
i7 860 - 2.8Ghz - Overclocked To 3.4Ghz
Nvidia GTX 470
Clip:
1080p HighProfile Trailer 1:48
Converting To 720p Normal Profile:
i7- 2.8Ghz (4 Cores, 4 Threads)
85 Seconds So A 90 Minute movie would take 1 Hour and 10 minutes using CPU
Converting To 720p Normal Profile:
Nvidia GTX 470
26 Seconds So A 90 Minute movie would take 21 Minutes using GPU!!
SlimDan22 said:
So your source material is 720p or are you converting to 720p from 1080p?
Anyways Here are my specs and time, also CUDA FTW
I use mediacoder because the CUDA support it the best i have found for free
I dont have any 1080p source material so i downloaded some 1080p high profile trailers
Main Specs:
i7 860 - 2.8Ghz - Overclocked To 3.4Ghz
Nvidia GTX 470
Clip:
1080p HighProfile Trailer 1:48
Converting To 720p Normal Profile:
i7- 2.8Ghz (4 Cores, 4 Threads)
85 Seconds So A 90 Minute movie would take 1 Hour and 10 minutes using CPU
Converting To 720p Normal Profile:
Nvidia GTX 470
26 Seconds So A 90 Minute movie would take 21 Minutes using GPU
Click to expand...
Click to collapse
That's some pretty impressive times. I'd be converting 720p HighProfile to 720p Normal Profile or 720p HighProfile to 480p Normal Profile.
I figure 720p is overkill for a 10.1" screen.
mug2k said:
That's some pretty impressive times. I'd be converting 720p HighProfile to 720p Normal Profile or 720p HighProfile to 480p Normal Profile.
I figure 720p is overkill for a 10.1" screen.
Click to expand...
Click to collapse
Yeah thats what i think too, but people still insist on trying to play 1080p content on the transformer =P, but 720p main looks great on the TF
Key with CUDA is the best performance comes when you use h264 content as a source, but i get really good speeds from Windows Media Video though
Here is some 720P specs for you that i just ran:
Clip:
720p High Profile 2:19
CPU:
94 Seconds
GPU:
22 Seconds
SlimDan22 said:
Yeah thats what i think too, but people still insist on trying to play 1080p content on the transformer =P, but 720p main looks great on the TF
Key with CUDA is the best performance comes when you use h264 content as a source, but i get really good speeds from Windows Media Video though
Here is some 720P specs for you that i just ran:
Clip:
720p High Profile 2:19
CPU:
94 Seconds
GPU:
22 Seconds
Click to expand...
Click to collapse
Are those times for High Profile to Normal Profile conversions ?. Also would it be any faster converting from 720p to 480p. Lastly are the GPU conversions solely dependent on the card and not the cpu at all ?.
mug2k said:
Are those times for High Profile to Normal Profile conversions ?. Also would it be any faster converting from 720p to 480p. Lastly are the GPU conversions solely dependent on the card and not the cpu at all ?.
Click to expand...
Click to collapse
Yes they where from High Profile to Normal, it would be a faster going from 720p to 480p from my experience, because that's what i use to encode videos for my 1st Gen Ipod Touch =)
Also, the GPU conversions do not really depend on the CPU that much i believe because when using my GPU, my processor is only being 20% utilized
Also i used to have a Nvidia 9500 GT with a Pentium D, then when i built my new system with my i7 i kept the 9500 in there for a while (until blackfriday ) and my GPU conversion speeds stayed the same
If you plan on getting a new Graphics cards, (Nvidia) anything over the GTX 460 will fly, also if you SLI the cards the speed does not increase but you can convert two videos at once (one on each card)
Using CUDA encoder to convert is certainly the fastest, but the bitrate to quality pales in comparison to a CPU encoder like x264. If you're willing to suffer quality for speed, it's perfectly fine to use CUDA encoders.
frosty5689 said:
Using CUDA encoder to convert is certainly the fastest, but the bitrate to quality pales in comparison to a CPU encoder like x264. If you're willing to suffer quality for speed, it's perfectly fine to use CUDA encoders.
Click to expand...
Click to collapse
Depends what program you use, badaboomit does not give you access to the the advanced cuda settings, whereas mediacoder does in my experience
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Only thing with cuda is you cant do multiple passes
I dont have a bluray source to convert, so i dont know what the quality would be over 10Mbps
[dont know why you would want anything over 5Mbps on a 10.1" LCD with a resoulution of 1280 × 800 anyways]
FYI i encoded all those trailers from 12Mbps to 10Mbps,
SlimDan22 said:
Depends what program you use, badaboomit does not give you access to the the advanced cuda settings, whereas mediacoder does in my experience
Only thing with cuda is you cant do multiple passes
I dont have a bluray source to convert, so i dont know what the quality would be over 10Mbps
[dont know why you would want anything over 5Mbps on a 10.1" LCD with a resoulution of 1280 × 800 anyways]
FYI i encoded all those trailers from 12Mbps to 10Mbps,
Click to expand...
Click to collapse
Does mediacoder support openGL encoding?
For reference I tried badaboom with my GTX 480 SOC on a 720p sample pop video.
Handbrake took 1m 50s to convert, Badaboom took 46s (xoom profile)
Edit: specs are Win7 64bit, [email protected]
Related
You be the judge - there was some "is the screen really that bad" threads, so I did a quick AB(CD) test.
First, the original JPEG, cropped. This is the baseline:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Next, an IPS screen, captured by my camera:
Third, GTAB at the with the original 50 Hz refresh:
Lastly, GTAB with a 70 Hz refresh:
These are accurate depictions of the screen, except for the lines in the 50 Hz GTAB which you can't see with the naked eye. My conclusions are that the IPS screen is a bit softer than the original picture, which I think is definitely true. The 50 Hz GTAB is the worst of the lot, very harsh on the eyes and almost video-like in its appearance, and the 70 Hz GTAB is definitely better and actually has brighter color over the IPS screen (although this test doesn't take into account viewing angles - we won't even go there). But still a little bit more contrast than the IPS screen - remember this was spot-on portrait, not tilted.
Granted, this is a very subjective test as the camera I used could be a factor, but I think it's a fairly accurate depiction. It's also showing me that there is a definite improved difference in the LCD when using the 70 Hz change.
The 60 Hz version will likely go into TNT Lite 4.2.0. I feel fairly confident that it's a good balance between stability and enhanced visuals.
you can see a huge difference if you look from different side of the screen .that is the main difference from IPS,I don't care as long as the device is fast(with your rom),by the way,will that 60Hz rom come to vegan tab?
Gojimi is still building his rig for the next version of VEGAn (possibly a Gingerbread port) - I'll keeping my sights on TnT Lite, at least for now. Tnt Lite still gets a lot of use, so it's not dead quite just yet. Plus VS is about to release a new update.
Does the 60hz that you plan putting into 4.2.0 look as good as 70 shown here? Appreciate the hard work and look forward to the next release.
Keep in mind that the camera is picking things up that we can't actually see - so it's really hard to say. I just feel that 60 Hz is a good balance, especially since 60 is what netbook LCD's would use, and so would other tablets (yes, I've checked the few that I've owned). We still don't know why our tablet is at 50 Hz to begin with, or if that's some Tegra default.
Thanks Roebeet! I hope an update zip can be created so we can just flash as an option for all the ROMS including Vegan and Zpad using CM. I know Gojimi is wanting to release an all new Vegan ROM but hopefully he can make an optional update just for now.
xmr405o said:
Thanks Roebeet! I hope an update zip can be created so we can just flash as an option for all the ROMS including Vegan and Zpad using CM. I know Gojimi is wanting to release an all new Vegan ROM but hopefully he can make an optional update just for now.
Click to expand...
Click to collapse
I was considering making a supplement, but the problem is that the file it changes is pretty important for bootup. If the perms aren't 100% correct, the device will hang at boot. And I'm not 100% sure that the perms are the same between all the mods, so it's a little risky. I wasn't even too sure that I wanted it in a TnT Lite supplment, but a full update I can live with since it's more of a "major update" vs. a supplement.
Btw, this bumps up Quadrant just a bit - you'll see some of the tests that maxed at at 50 fps go up to 60 fps. I assume that the 70 Hz version would increase that even further.
EDIT: 60 Hz version -- testing this on a prototype TNTL 4.2.0, right now. Looks very similar to 70, to my eyes:
60 hz is better anyway as most tv shows and movies are at 60fps
stanglx said:
60 hz is better anyway as most tv shows and movies are at 60fps
Click to expand...
Click to collapse
no..they're not.
roebeet said:
Keep in mind that the camera is picking things up that we can't actually see - so it's really hard to say. I just feel that 60 Hz is a good balance, especially since 60 is what netbook LCD's would use, and so would other tablets (yes, I've checked the few that I've owned). We still don't know why our tablet is at 50 Hz to begin with, or if that's some Tegra default.
Click to expand...
Click to collapse
I think the use of 50Hz has to do with the default framerate for cameras and film which is around 24.something fps. This puts you close on the 50hz without tearing. If we use a modified value, i personally think 75hz would be smart to use.
With the modified version I have used I have been able to create tearing with fast movements. I'm not sure why there would be any benefit to going with 60hz instead of 75hz, the native max refresh rate, in terms of stability. If a display is rated for a refresh rate and your video hardware can support it, I'm not sure why you would scale to a slower speed except to deal with syncing issues for tearing.
EDIT: And the reason for 50hz instead of 75hz is most likely because not all displays support 75hz.
Because I'm testing the waters, with TNTL. After the data2loop issues, my preference is to be conservative at this point.
Plus, 60 is the standard on other tablets I've used, including the PDN I currently own - it's still a bump up and I think it's makes a difference visually, even if just slightly. I'm not sure that the reason why it's 50 versus 60 is because 50 and 75 doesn't tear, but 60 does - I wish I knew the reason why it was setup this way.
Is there anyway you could send out an update and have each hz, available.
I would probly like to try each on my own if it was an option.
If its hardcoded into the os just forget what i said.
lol
Maybe I'm just blind or my monitor is bad, but I can't see much difference between 50 and 70 except for additional vertical lines which you said aren't visible to the eye.
Also would like to second that. Have some kind of option in the settings where you could change refresh rate.
Here's a good discussion of refresh rate:
http://www.tomshardware.com/forum/280224-33-refresh-rate-gaming-60hz-75hz
BTW, I agree that making it adjustable with a default would be ideal.
Also BTW, what effect/impact does this have on the HDMI output?
Jim
dblanketyblank said:
Maybe I'm just blind or my monitor is bad, but I can't see much difference between 50 and 70 except for additional vertical lines which you said aren't visible to the eye.
Also would like to second that. Have some kind of option in the settings where you could change refresh rate.
Click to expand...
Click to collapse
Cool comparison - good work.
Movies: 24 FPS (often 23.976 or 25 depending on capture device - that's why converted video and audio sometimes go out of sync)
TV (NTSC color): 29.97 fps
If you set your camera on shutter priority, and use a longer exposure (1/30th or longer) the scanlines should vanish. Your camera was "catching" artifacts that are too brief for the eye to see.
For North American use, I suggest staying away from 60hz - too likely to pick up visual artifacts from 60Hz fluorescents - remember the flicker/headache problems caused by the 60Hz VGA monitors way back when... Changing them to 72Hz fixed most most of the issues.
I don't mind the 50Hz we have stock. Would rather concentrate on increasing the fps of the scrolling/UI stuff. Remember that the special effects at the movies look wonderful, and are presented with a ~24Hz refresh (except ImaxHD @ 48 fps)
xmr405o said:
Thanks Roebeet! I hope an update zip can be created so we can just flash as an option for all the ROMS including Vegan and Zpad using CM. I know Gojimi is wanting to release an all new Vegan ROM but hopefully he can make an optional update just for now.
Click to expand...
Click to collapse
Roebeet,
I would also like to see a Vegan specific 60 and 70hz update to try first hand.
You can tell us what to set permissions to.
It's a few pages long, but here's the thread: http://forum.xda-developers.com/showthread.php?t=912197
I grabbed the 60 Hz version from gojimi, and he has a few other versions as well. The perms need to match what was there before, which on TnT Lite would be root.shell and 755.
roebeet said:
It's a few pages long, but here's the thread: http://forum.xda-developers.com/showthread.php?t=912197
I grabbed the 60 Hz version from gojimi, and he has a few other versions as well. The perms need to match what was there before, which on TnT Lite would be root.shell and 755.
Click to expand...
Click to collapse
Here is the original link I was looking for in the thread...#43
http://forum.xda-developers.com/showpost.php?p=10604940&postcount=43
Has Vegan Beat 5.1 60 an 70hz.
thanks Roebeet!
PAL Video standard uses 50hz, popular in EU and parts of asia.
Likely just a forign engineer thinking of 50hz as a standard, as opposed to us in the US think of 60hz being a standard (NTSC 60hz).
What is more important is what works better...
GameDoctor said:
PAL Video standard uses 50hz, popular in EU and parts of asia.
Likely just a forign engineer thinking of 50hz as a standard, as opposed to us in the US think of 60hz being a standard (NTSC 60hz).
What is more important is what works better...
Click to expand...
Click to collapse
You beat me to it. VS (USM) imported the malata and printed their name on it, didn't change anything that worked, hardware wise, and voila 50hz display.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
As you may be aware that our beloved Galaxy R is not among the best cellphones out there in terms of video playback. The native video player cannot play a Full HD (1080p) video without some form of conversion/down scaling in terms of resolution and bit-rate to a format compatible with the Galaxy R. Even 3rd party video players like MX video player use s/w decoding for such unsupported videos which leads to stuttering and skipping
Galaxy R is a WVGA device ie. it has a screen resolution of 800 x 480. So a video which has been down scaled to this resolution looks best on our device. Though it can natively play some(Not all) 720p (1280 x 720) videos, such videos are a waste of free space in my opinion because Galaxy R does not support video out(MHL) nor does it have a HD screen resolution, as such that extra resolution is wasted.
Rather what I have noticed is, down scaling a video to the native device resolution (800 x 480) with a higher bit-rate gives a much more smoother video playback (equal to or even better than a 720p video). The in-built video converter that pops-up on your computer when transferring a non-compatible video does not produce videos of the best quality because of lower quality codecs used. After researching with a few video converters I have concluded that Handbrake is the best and optimum video converter for our device with superior quality codecs plus it is a freeware:good:
How to use Handbrake for converting videos?
OR
What are the optimum settings for our Galaxy R?
1. Download the Handbrake video converter from this link.
2. Install it and open it.
3. Load the video to be converted using the Source >>> Video File button. Once loaded, Click on iPod Legacy in presets and then change the settings to resemble this: (Picture Tab)
Note: Don't forget to set the destination file name. For those of you who still want 720p videos remember to change the width and height to 1280 & 720 resp.
4. Head over to the Video Tab, change the settings to resemble this:
Note: Higher the avg bit-rate better the quality of the video. You can increase the bit-rate as per your quality choice.
5. Head over to the Audio Tab, change the settings to resemble this:
Note: Keep the bit-rate maximum for better sound quality.
6. That's it. Hit the Start button and wait for your video to be converted.
7. Transfer the converted video to your device and enjoy!!!
Note: The above settings are known to work and give optimum results.
If you are feeling more adventurous you can play with a few advanced settings like audio gain, different sound codecs, frame rates, bit-rates etc until something breaks...
If you have any queries, do post them below!
Thnx!!
The-Droidster said:
If you have any queries, do post them below!
Thnx!!
Click to expand...
Click to collapse
Great one buddy. let me try & let you know after.:good:
Nice..one.......research.....
Bt if v cld do all these steps with the help of mobile device nly...it wld b grt...
Sent from my GT-I9103 using Tapatalk 2
Hey Droidster.. Great post.. :good:
Can you post some stats.. about size reduction in the resulting video files? i mean.. if we have a 1280x720 50 mb file, how much will it reduce in size when we use your optimum settings on handbrake with 800x480 resolution?
chandanbs said:
Hey Droidster.. Great post.. :good:
Can you post some stats.. about size reduction in the resulting video files? i mean.. if we have a 1280x720 50 mb file, how much will it reduce in size when we use your optimum settings on handbrake with 800x480 resolution?
Click to expand...
Click to collapse
It actually depends on the bit-rate that you are using. If the bit-rate is not high, then there will be a considerable size reduction. A 50 MB file would come down to 30-35 MB. But if you want higher quality...you need to up the bit-rate a bit...which leads to size increase of around 5MB per 5000Kbps.
Superb buddy..Now I felt the real HD in R
I found it interesting. ..but want some more details
Actually I got fitted a mega audio system in my car which supports 800×480 resolution and when I used handbrake for descaling some videos for the same..videos get converted but are not played on the system...win ce is the operating system and 6.2 inc is the display
Saw this online today and was wondering if anyone else thinks it could actually end up being a hit for serious android users who are into gaming. Here's a link to the product page on the manufacturers website. It shows off it containing some pretty good specs too such as, USB OTG, HDMI output, lot's of hardware buttons, pre-rooted, Jellybean 4.1.1, Cloud gaming app, etc.
Here are pics from the link above:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
S7300 Specifications
Games support Millions of Android games, 9 kinds of Simulator games (PS1, N64, Arcade CP1/CP2/Neo-Geo, GBA, SFC, MD, FC), Game cloud
Games control 5 point capacitive touch, Perfect button controls (Android buttons mapping, Visual control of 360 degree, Double LR buttons, Two sticks), G-sensor control
Color
Black, White
Size
Length: 9.50inches
Width: 4.77inches
Depth: 0.56inches
Weight: 0.90pounds
Storage
8GB
Chip
Amlogic MX (Cortex A9 CPU, ARM mali400 GPU), Dual core, 1.5GHz
DDR
1GB DDR3
OS
Android 4.1
Network
3 ways: Wi-Fi (802.11 b/g/n), External connection to Ethernet and 3G
Screen
7.0-inch (diagonal) LCD, 1024*600 pixel
Touch System
5 point Capacitive Touch Screen
Sensor
3 Axis Gravity Sensor
Buttons
Direction key, ABXY, Double LR buttons, Two sticks, Select, Start, Volumn, Reset, Power
Camera
0.3M Front Camera
Speaker
Stereo Double Speaker
Video
Support RMVB, AVI, MPEG-4, ASP, DIVX, WMV, F4V, FLV etc. (Support extension of the third-party applications)
Audio
Support MP3, WMA, FLAC, OGG etc. (Support extension of the third-party applications)
E-book
Support PDF, TXT, CHM, UMD, HTML etc. (Support extension of the third-party applications)
Pictures
Support JPG, BMP, PNG etc., browsing and slide show
Battery
Built-in rechargeable lithium-polymer battery
Charging via 5V 2A DC power adapter or USB to computer system
I/O
USB2.0 High Speed
OTG Connector (External connection to bluetooth keyboard mouse, USB flash disk and hard disk)
3.5-mm stereo headphone mini jack
Micro TF Card Slot, Max 32GB
TV-out
HDMI Dual-screen display, Up to 1080P
Languages
Multilanguage support
Operate Environment
Windows 98SE/ME; Windows2000; Windows XP or above
In the box Device S7300 , User's Manual, USB cable
Click to expand...
Click to collapse
THOUGHTS!?!?
Update: This area on the website shows other android-based knockoffs.
This device seems really cool. Wouldn't mind owning one of them if it performs well.
VengeMobile said:
This device seems really cool. Wouldn't mind owning one of them if it performs well.
Click to expand...
Click to collapse
Agreed- if it performs well, it would probably be similar to the xperia play, except with a dozen more hardware buttons that can probably all be custom mapped too!
This device is awsome.
I had a play with one recently.. pretty impressed with the build quality and it seemed fairly slick/smooth in operation. Didn't have enough of a WOW factor to make me buy one though - that and the fact that the wife was with me moaning on about how I've already got a PSP that I don't play etc.. LOL!
pangster said:
I had a play with one recently.. pretty impressed with the build quality and it seemed fairly slick/smooth in operation. Didn't have enough of a WOW factor to make me buy one though - that and the fact that the wife was with me moaning on about how I've already got a PSP that I don't play etc.. LOL!
Click to expand...
Click to collapse
which one did you try? I'm curious bc if it's an older model hopefully this one will be even more slick
mcmb03 said:
which one did you try? I'm curious bc if it's an older model hopefully this one will be even more slick
Click to expand...
Click to collapse
Thats a good question!!... until i clicked on the above link i hadnt realised they did more than one version!! I had never heard of this manufacturer until about 2 weeks ago..
I'm back in the UK now.. but for anyone else local i saw it in the small Android shop on 2F Amoy Plaza, Kowloon, Hong Kong.
I might even have a picture of it somewhere to see if that can shed any light on it..
Wonder what the battery life is like?
Sent from my Amazon Gindle Fireoid
Actually looks good
skydragon team
guitarman2010 said:
Wonder what the battery life is like?
Sent from my Amazon Gindle Fireoid
Click to expand...
Click to collapse
yeah, definitely a deal-breaker there!
The Tronsmart Pavo M9 is Tronsmart’s first HDMI recording TV box. Running Android 4.4 with a heavily customised “Pavo M9 UI”, the M9 features 1GB RAM and 8GB of onboard storage.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I want to say thanks to GeekBuying for sending me a sample of the Tronsmart Pavo M9 to review. You can purchase one from them here.
For more detail, benchmarks and lots more photos, click here to view the full review at Home Theatre Life.
Tronsmart Pavo M9 Technical Specifications
Operating System: Android KitKat 4.4
Chipset: Mstar MSO9180D1R
CPU: Quad core ARM Cortex A9
GPU: Octa core ARM Mali-450 GPU
Memory: 1GB DDR3
Internal Storage: 8GB eMMC + MicroSD card slot
Connectivity: 802.11 b/g/n WiFi (Realtek 8188), 10/100 Ethernet
Audio/Video Output: HDMI 1.4, SP-DIF, Composite Video Out
Video Input: HDMI In
Interfaces: 2 x USB 2.0, 1 x USB 3.0
Design
The Tronsmart Pavo M9’s design an unobtrusive black square that stays out of the way but I can’t help but wish they made something that looked distinctive.
Using It
Powering up the device takes around 30 seconds, almost identical to the Zidoo X9.
The “Pavo M9 UI” is intuitive and animates smoothly. It’s locked to 720p but movies play at the correct resolution (i.e. 1080p).
The unit is rooted out of the box. HDMI CEC isn’t supported as far as I can tell.
HDMI Recording
The HDMI recording UI is identical to that of the Zidoo X9. You can set the recording resolution and format, and even schedule a time to start recording. Unfortunately, there’s no option to schedule recurring recordings.
I've embedded a HDMI recording sample below
Media Playback
Video playback was pretty good. Kodi did have issues with some codecs that MXPlayer played back fine so I’m guessing this is related to the Kodi not leveraging the SoC’s hardware acceleration.
Gaming Performance
Gaming performance was great, although I suspect this is partially due to the 720p UI lock. Both Jetpack Joyride and Beach Buggy Racing played, even on the highest graphics settings.
Networking Performance
In real-world usage, WiFi performance seemed solid. I was able to stream my 4K and 1080p samples from an NFS share and watch Netflix without any noticeable buffering.
Verdict
The Tronsmart Pavo M9 is a solid Android media player, particularly if you’re after HDMI. Getting all this functionality for under $70 is impressive. However, it’s let down by minor issues such as the lack of Bluetooth.
For more detail, benchmarks and lots more photos, click here to view the full review at Home Theatre Life.
has someone found a way to do recurring scheduled recordings??
yeahman45 said:
has someone found a way to do recurring scheduled recordings??
Click to expand...
Click to collapse
I don't think recurring recordings are an option - only scheduling a single recording. It's a frustrating oversight but hopefully one they'll fix in a future firmware update. Probably worth asking Tronsmart directly.
USB Mouse/Keyboard Support
Hi - Did you test mouse and keyboard support? I suspect the Pavo M9 does not support this... Would you be able to try it and post the result?
Thank you!
yup i supports mouse and keyboard
---------- Post added at 07:39 PM ---------- Previous post was at 07:37 PM ----------
DarkscytheX said:
I don't think recurring recordings are an option - only scheduling a single recording. It's a frustrating oversight but hopefully one they'll fix in a future firmware update. Probably worth asking Tronsmart directly.
Click to expand...
Click to collapse
you can try this app : http://forum.zidoo.tv/index.php?threads/my-scheduling-recording-app.1203/
Hello, xda user
i have question and sorry if my question is noob but can mx player play video h265 HEVC like h264 (smooth without audio sync problem)
and if i convert video HEVC.mkv to Mp4 is make speedup or same ? and maybe frameskip help to raise speed, sorry for my bad engglish
lopers12 said:
Hello, xda user
i have question and sorry if my question is noob but can mx player play video h265 HEVC like h264 (smooth without audio sync problem)
and if i convert video HEVC.mkv to Mp4 is make speedup or same ? and maybe frameskip help to raise speed, sorry for my bad engglish
Click to expand...
Click to collapse
If you convert Hevc in to mp4, your device may support playback with hardware and performance will be smooth.
It work with my galaxy-s4. You add a custom patch and you put it on the decoder
Sent from my GT-I9505 using Tapatalk
MP4 = container format, and container has no direct bearing on playback performance. The encode of the video stream is independent of the container format.
Hardware acceleration depends on what codec the video is encoded in; currently no devices have hardware HEVC support yet.
The Galaxy S4 plays HEVC with software decoding; there's no hardware acceleration.
CDB-Man said:
MP4 = container format, and container has no direct bearing on playback performance. The encode of the video stream is independent of the container format.
Hardware acceleration depends on what codec the video is encoded in; currently no devices have hardware HEVC support yet.
The Galaxy S4 plays HEVC with software decoding; there's no hardware acceleration.
Click to expand...
Click to collapse
What about one plusone
neeraj5696 said:
What about one plusone
Click to expand...
Click to collapse
CDB-Man said:
Hardware acceleration depends on what codec the video is encoded in; currently no devices have hardware HEVC support yet.
Click to expand...
Click to collapse
CDB-Man said:
MP4 = container format, and container has no direct bearing on playback performance. The encode of the video stream is independent of the container format.
Hardware acceleration depends on what codec the video is encoded in; currently no devices have hardware HEVC support yet.
The Galaxy S4 plays HEVC with software decoding; there's no hardware acceleration.
Click to expand...
Click to collapse
I beg to differ. The Samsung Galaxy Note5 (and other devices with Exynos 7420) can play HEVC encoded files with HW acceleration. See screenshot here: goo.gl/0G3hcx
However, Exynos 7420 does not support HW acceleration of Hi10P encoded HEVC files.
pmredulla said:
I beg to differ. The Samsung Galaxy Note5 (and other devices with Exynos 7420) can play HEVC encoded files with HW acceleration. See screenshot here: https://goo.gl/0G3hcx
However, Exynos 7420 does not support HW acceleration of Hi10P encoded HEVC files.
Click to expand...
Click to collapse
Well now, that's a recent development; the Note 5 only came out in August 2015. Everything else before this point though would not support HW HEVC.
I don't foresee the main10 profile of HEVC being hardware supported in the near future; one reason of which is that the standards setters haven't agreed if the "HEVC supported" accreditation for devices will also require main10 support.
CDB-Man said:
Well now, that's a recent development; the Note 5 only came out in August 2015. Everything else before this point though would not support HW HEVC.
I don't foresee the main10 profile of HEVC being hardware supported in the near future; one reason of which is that the standards setters haven't agreed if the "HEVC supported" accreditation for devices will also require main10 support.
Click to expand...
Click to collapse
Here's the specification of the Snapdragon 820:
Multimedia
• 10-bit 4K decode
• 1080p240 FPS decode
• 4K HEVC video at 60FPS with 10-bit color
• Simultaneous 1080p30+1080p30 inbound/outbound
• WCD9335 audio codec
• Hi-Fi 24bit/192kHz FLAC playback
What's not clear is whether the 10-bit it refers to is Main10 or Hi10. Probably devices using the 820 will appear on the 2nd quarter of next year.
pmredulla said:
Here's the specification of the Snapdragon 820:
Multimedia
• 10-bit 4K decode
• 1080p240 FPS decode
• 4K HEVC video at 60FPS with 10-bit color
• Simultaneous 1080p30+1080p30 inbound/outbound
• WCD9335 audio codec
• Hi-Fi 24bit/192kHz FLAC playback
What's not clear is whether the 10-bit it refers to is Main10 or Hi10. Probably devices using the 820 will appear on the 2nd quarter of next year.
Click to expand...
Click to collapse
There are already some SOCs which can decode the h265. This just indicates the ability of the chip.
The issue is that whether the OEM will implement the support or not. OEM may need to pay for additional licensing fees to use the h265 decoding. That's why many OEMs hasn't implemented the native support for h265.
Sent from my SM-G900H using Tapatalk
ktsamy said:
There are already some SOCs which can decode the h265. This just indicates the ability of the chip.
The issue is that whether the OEM will implement the support or not. OEM may need to pay for additional licensing fees to use the h265 decoding. That's why many OEMs hasn't implemented the native support for h265.
Sent from my SM-G900H using Tapatalk
Click to expand...
Click to collapse
What KT said; the OEMs are fighting to have Main10 support dropped from the minimum standard required for the "HEVC Supported" certification; I hope they don't win.
CDB-Man said:
Hardware acceleration depends on what codec the video is encoded in; currently no devices have hardware HEVC support yet.
Click to expand...
Click to collapse
Wrong. Qualcomm has supported it since the S801.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Klaos3000 said:
Wrong. Qualcomm has supported it since the S801.
Click to expand...
Click to collapse
Uh, read down a couple posts; that point has already been addressed, and then some.