Posts: 24
Joined: Jan 2013
Reputation:
0
Darjk
Junior Member
Posts: 24
2013-01-22, 07:58
(This post was last modified: 2013-01-22, 08:02 by Darjk.)
I'm still having issues with render output resolution, aspect ratio, scaling, etc on the ATV1200. And part of the problem is /sys/class/video/axis - setting the permissions is only done for the current session. Once its shut down and loaded back up, permissions are reset back to normal which is due to init.rc I believe, though after editing that, its still setting them to 0664. Essentially a lot of the video's look like they're being zoomed or scaled to be "full screen", stretching the vertical dimensions removing the black bars at the top and bottom. Even changing the render style, all of them are wrong. And if I set it to "original" for a 1080p video, I just get a fullscreen of maybe 1/4 of the actual video as its zoomed in that much. Kind of like XBMC is rendering with the assumption that video output is 720p when its infact 1080p. If I change android to 720p it seems to match a bit better but the video is still being stretched to fullscreen.
I've also tested the Stagefright test build on the MK808B (proper) which is working great for the most part (the odd movie or 2 has line of 3-4 pixels of corruptions horizontally through it and with 1080p still stuttering a bit), and noticed its rendering correctly the aspect ratio's though not at the correct resolution as far as I could tell. Which leads me to the issue being with ATV1200 (firmware) and not the android build of XBMC. Also noticed the video settings (pressing M) only has a handful of settings that can be changed as opposed to on the MK808B - though one is using the latest stagefright test build while the other is using Xios build.
Are there any other system files (apart from axis) that might be worth checking that XBMC needs permissions to in regards to aspect and everything? Its the only flaw I'm currently experiencing which is leading me to still use MX Player to be able to watch a full, proper video without being cropped, zoomed, or scaled.
Thanks!
Edit:
Also fixed my 3TB drive issue. Even though the ATV1200 can read NTFS drives, I needed to install Paragon NTFS/HFS+ drive mounter (I assume for its ntfs-3g cability). The other NTFS drive mounting apps mounted the drive just as Android would, but had the same issue - could see the root directories and 10 of the files on the drive but not the rest. Came to this conclusion after mounting the HDD to a Macbook Air (10.6.8) and it had the same issue until I installed ntfs-3g drivers.
Posts: 57
Joined: Jan 2013
Reputation:
0
2013-01-22, 17:44
(This post was last modified: 2013-01-22, 17:45 by theINSKIP.)
Hi all.....
I have just purchased one of these in the hope to replace my playonHD mini media player with a XMBC.
But i have just had a panic, i have checked over most codec's, etc but forgot to check that it will play 3d SBS rips. Im assuming it does but after a bit of googling, i can't find any confirmation.
I have only just been introuced to XMBC and I am amazed by it and its features (plugins), i hope ive made the correct purchase.
Reading through these posts tells me that its a new piece of kit but is receiving quiet quick firmware updates. Which is good.
Thanks
Pete
Posts: 11,582
Joined: Feb 2008
Reputation:
84
davilla
Retired-Team-XBMC Developer
Posts: 11,582
2013-01-23, 08:34
(This post was last modified: 2013-01-23, 08:35 by davilla.)
Rendering the GUI in 720p is no big deal, most all GUIs skins are 720p anyway. So no real big deal, it's more a specmenship thing.
HW decoders decode at what ever the video rez they are given. That is scaled (or not) to the DISPLAY resolution.
As to how may ponies does it take, it all depends how good their code is done. There is no hard and fast rule.
Also, remember a 40 inch 1080p display looks the same as a 720p display at 8 feet away. Your eyes can't physically tell the difference.
Posts: 830
Joined: Jan 2012
Reputation:
5
so to conclude?
It seems to me that the ATV1200 is the fastest android box on the market.
Also it seems that it is now working great with xbmc since the most recent firmware that was released mid jan on the 15th. ("firmware" is effectively a term that in this context means 'android version released by the manufacturer specifically for this device')
The two biggest contributors to this thread that seem very tech savvy and knowledeable are "srle" and "xardos". One has xbmc working perfectly (slre) and one has xbmc working perfectly except for one major issue (the sound fails after ten or twenty minutes of every video).
So in conclusion buying this box is just like every other android box ie it is a gamble to see if you are a lucky customer or an unlucky one?
Is that a fair conclusion, can anyone please correct me if they thing I have got something wrong.
I'm just trying to clarify because it's sometimes difficult to absorb all the information in technical threads like this.
Posts: 830
Joined: Jan 2012
Reputation:
5
srle, i noticed your "bottom line" comments in the firt post on this thread.
Have these changed now since the performance of the box has improved since then?
Just wondered because it seems a bit harsh in the new context of xbmc working a lot better recently.
"The bottom line:
- Android is not Linux - Linux is way, way better
- If You want XBMC, and price is not an issue, buy a box that works with Linux builds
- If You want XBMC, and price is an issue - go with the somewhat slower but much cheaper Raspberry Pi
- If You want this box and no other - well read this tutorial
- If the optical/coax audio out does not get fixed in future builds then there is hardly any reason to go with this, and not with some cheaper box with analog audio out"