1. No user installed addons are supported, python or otherwise.
2. No, they really are not supported.
3. They are not coming back
4. Read from 1. again
Any mention of illegal streaming sites, addons or any pirated material will not be tolerated. This is not democracy and any offenders will be banned and posts deleted immediately without warning.
Other than that, we hope you enjoy MrMC so far and we welcome any input and feedback you might have.
Team MrMC.
2. No, they really are not supported.
3. They are not coming back
4. Read from 1. again
Any mention of illegal streaming sites, addons or any pirated material will not be tolerated. This is not democracy and any offenders will be banned and posts deleted immediately without warning.
Other than that, we hope you enjoy MrMC so far and we welcome any input and feedback you might have.
Team MrMC.
3D MKV
-
robneal81
- Posts: 5
- Joined: 22 Dec 2015, 15:41
Re: 3D MKV
Thanks for the reply. Is there any other lossless format I can try? Maybe .ts?
-
timstephens24
- Posts: 894
- Joined: 09 Dec 2015, 22:43
Re: 3D MKV
No, the Apple TV isn't going to be able to play frame-packed 3D MKVs, most likely ever, and that's why I use a Raspberry Pi 2 to solely play 3D MKVs.
It's nice that the Apple TV will play the left-eye portion of the MKV though, that way I don't need one file for 3D and one for 2D. Just one file to do everything that I want, since I don't always want 3D.
It's nice that the Apple TV will play the left-eye portion of the MKV though, that way I don't need one file for 3D and one for 2D. Just one file to do everything that I want, since I don't always want 3D.
-
noggin
- Posts: 28
- Joined: 19 Nov 2015, 10:12
Re: 3D MKV
Frame Packing is an output format over HDMI (it allows Full HD 3D to be output), it is not an encoding format.walorith wrote:Hi,
MVC within the filename is not working for me. I understand that there are two issues, right?: 1st, No API from aTV for automatic switching of 2D->3D or other resolution switching. 2nd, No hardware 3D (full frame packing) decoding implemented. For the 2nd point I don't know if it is a software or hardware problem? Maybe someone can comment on that?
The encoding format for 3D Blu-ray in full resolution is MVC. MVC as used by Blu-rays is actually a dual-stream format. The core stream is normal Full HD 1920x1080/24p AVC/H264 2D video - which is one of the two eye feeds. There is a secondary stream, which rather than being a totally separate eye feed, is actually a compressed 'eye-difference' feed. This, when combined with the regular 1080p H264/AVC stream allows the second eye video to be generated.
On players which can output Frame Packed 24p the two eye feeds are combined in a Frame Packed HDMI format - which is 2 x 1920x1080 eye feeds combined into a single 1920x2205/24p stream with the two eye feeds on top of each other with 45 lines of blanking between them.
To play 3D MVC MKVs and Blu-ray ISOs in 3D you need MVC decoding. However to play them in regular 2D shouldn't be a problem.
HOWEVER - early Raspberry Pi MVC decode builds required the video to be flagged as 3D, but there wasn't a suitable 3D flag for MVC content at the time (as the Pi was - and remains - the only Kodi player with native MVC support) so instead the SBS 3D flag was suggested. HOWEVER - if you do this, players without MVC decode (like MrMC on the Apple TV) will interpret this as meaning the 2D 1080p stream in the MVC MKV is a 3D SBS file and will attempt to replay this in 2D compatible mode, i.e. zoom a half-width 960x1080 to 1920x1080 - stretching the left or right hand side of the picture to twice its normal width.