2014-05-15, 10:51
OK a little history: go back to frodo - half sbs and half tab files play fine for most people - the computer thinks it is just a 1920x1080 frame and sends it as such out the hdmi port.
The TV sees it as a 3D file, generally because it is told to do so by the user via the tv's remote control. It interprets the sbs or tab file accordingly and does the right thing. But xbmc knows nothing about the difference between 2d and 3d, it is simply passing the signal on same as it would for any 1080p movie. Bring up the OSD and all is f***ed up, because the TV doesn't know that the OSD overlay is any different to the sbs/tab signal and drops it all over the place. Also because ffmpeg doesn't know about MVC it doesn't render MVC in 3D, it renders it in the 2D view.
Move on to Gotham, it can render the OSD in 3d and will do so when it recognises a 3D movie. It recognises that by the filename - it knows strings like SBS, HSBS, TAB, HTAB in the filename. However this only tells it to render the OSD in the correct fashion, it knows nothing about what buttons it has to press on your TV remote to switch it to the correct 3D mode. There are some addons developed by Clever People ™ which can switch TVs to the correct 3D mode via the TV's network control protocol or some other such voodoo, but such protocols are very manufacturer and model dependent. Many people will still have to use their TV remote.
TVs are however trained to switch to 3D mode when they receive a framepacked signal http://www.best-3dtvs.com/what-is-frame-packing-3d/ . This is a signal where each frame is sent as two subframes with special signalling, namely a 45 pixel blanking between the two subframes. The signalling tells the TV what to do. The TV says "this is a framepacked signal, the top subframe is the left eye, the other subframe is the right eye, act accordingly." Trouble is most graphics cards cannot send this type of signal. Afedchin's builds can do it on the right OS and video card.
TL;DR for 3D to work as people expect when they compare to their 3D Bluray player, XBMC needs to support MVC to decode the Bluray format for 3D, and needs to output framepacked output via some open source driver.
Probably the current over obsession for 3D will dissipate before that happens. I quite like 3D myself, but find it majorly overused and abused.
The TV sees it as a 3D file, generally because it is told to do so by the user via the tv's remote control. It interprets the sbs or tab file accordingly and does the right thing. But xbmc knows nothing about the difference between 2d and 3d, it is simply passing the signal on same as it would for any 1080p movie. Bring up the OSD and all is f***ed up, because the TV doesn't know that the OSD overlay is any different to the sbs/tab signal and drops it all over the place. Also because ffmpeg doesn't know about MVC it doesn't render MVC in 3D, it renders it in the 2D view.
Move on to Gotham, it can render the OSD in 3d and will do so when it recognises a 3D movie. It recognises that by the filename - it knows strings like SBS, HSBS, TAB, HTAB in the filename. However this only tells it to render the OSD in the correct fashion, it knows nothing about what buttons it has to press on your TV remote to switch it to the correct 3D mode. There are some addons developed by Clever People ™ which can switch TVs to the correct 3D mode via the TV's network control protocol or some other such voodoo, but such protocols are very manufacturer and model dependent. Many people will still have to use their TV remote.
TVs are however trained to switch to 3D mode when they receive a framepacked signal http://www.best-3dtvs.com/what-is-frame-packing-3d/ . This is a signal where each frame is sent as two subframes with special signalling, namely a 45 pixel blanking between the two subframes. The signalling tells the TV what to do. The TV says "this is a framepacked signal, the top subframe is the left eye, the other subframe is the right eye, act accordingly." Trouble is most graphics cards cannot send this type of signal. Afedchin's builds can do it on the right OS and video card.
TL;DR for 3D to work as people expect when they compare to their 3D Bluray player, XBMC needs to support MVC to decode the Bluray format for 3D, and needs to output framepacked output via some open source driver.
Probably the current over obsession for 3D will dissipate before that happens. I quite like 3D myself, but find it majorly overused and abused.
