Will do - bare with me 
The only thing that sticks out is the resolution of this being odd for a fullsbs. It’s 3840 x 804 rather than 3840 x 1080. Unsure if that would play into it.
Yeah, that’s right. The kernel does all the calculations based on that 1080 height. In your case 804 could indeed be the root cause.
Good to know… Here’s a cut from a fresh rip just for you lol
Same issue for me on this one.
If it’s just resolution playing up, then I still need to figure out why some MVC’s aren’t working either, even if their resolution is correct. Happy to tackle that one after with a log and clip though, more for my own sanity than anything else…
Turns out I can’t replicate my MVC file issue, but I’ve found a preset on DVDFAb that hasn’t let me down yet. So that’s one issue ticked off lol
I can reproduce that issue with your clip. I’ll have a look at it in the next days.
1 Like
Thank you, looking forward to seeing your thoughts!
Indeed, it looks like the video resolution is the culprit here. I need to think about a proper fix, because I can’t tell whether Kodi is doing it wrong, or the kernel or if I just misinterpreted the calculations done in the kernel.
No problem, thank you for verifying.
I have some fanmade conversions that don’t work either, and I can see it was 1920x1036 so that explains that one too.
Fingers crossed for a full fix! As far as end users go, would be great if it relied on title info (h-sbs, sbs or mvc) as opposed to actual resolution but I understand that’s easier said than done lol.
That issue is not related to title info. If the resolution isn’t exactly 1920x1080 then Kodi tries to center the clip which makes sense. There are a couple of calcutlations done both in Kodi and in the kernel to get it centered and somehow it’s screwed up 
.
Does this mean there’s no way to fix it?
No no, not at all. When I added MVC support years ago I had no documentation about Kodi and the kernel when it comes to 3D playback. That’s why I made some assumptions that worked perfectly until you came along and told me about difficulties with your clips. That tells me that some of my assumptions were not (or just partly) correct. Now I just need to figure out what’s wrong, and then I’ll implement a fix for it.
1 Like
Now that’s the right attitude!
Legend, will keep my eyes peeled and fingers crossed.
Let me see if i summarize correctly, so that we can hopefully update the kodi wiki 3d page accordingly where it is not correct or complete:
AFAIK, Kodi (PI) does recognize a files 3D format from either naming or file metadata.
AFAIK, mp4 does not have 3D metadata, but mkv has. So you do not need to have 3D guidance in the file name if its mkv. But of course it makes it a lot easier as a user to know which file is supposedly 3d. But just changing the file name will not make kodi ignore 3d metadata in an mkv.
You can see the 3d metadata with “mediainfo” program. It will show stereoscopic video and its format.
Simply 3D in the file name is of course never sufficient, because kodi needs to know how the two eyes videos are placed - SBS or TAB. Or else, kodi could not appropriately render e.g.: a TAB video onto a SBS screen.
I don’t think OSMC PD code for vero changes any of the above.
PI Kodi does not care about 3D in EDID. It can of course not decode MVC stereoscopic video or switch to specific 3D resolutions of the display. But when it recognizes a 3D video, it will ask which rendering it should generate to match the display. For PI, the only two relevant ones are TAB and SBS. If need be, Kodi converts the input to match the displays required format and it renders GUI/subtitles accordingly to the choosen output format.
With just such a PI Kodi running, you need to explicitly switch your display to 3D SBS or TAB as desired.
In OSMC Vero 4/V, the 3D EDID formats are read from the display, and the player actively switches to the correct 3D video resolution, making it unnecessary to do so manually. And of course it supports MVC decode.
Seems the use of EDID may get you into trouble if the display reports incorrectly what it can support, but not quite sure about this.
1 Like
I can’t tell much about the PI since I’ve never really looked into that implementation. For the Vero 4k/4k+/V you are correct:
- the info from video metadata is preferred, the file name extensions are only taken as fallback
- the 4k/4k+/V automatically switch to the stereo mode that either was set because of the video metadata or the mode the user has chosen. You mentioned it, one can configure Kodi to ask the user on playback start what he wants to get; it’s also possible to select a mode that doesn’t match the video stereo mode like e.g. playing a HSBS file as “hardware based” (frame packed), or playing a HTAB clip as HSBS if you want. But cross converting stereo modes is work in progress and might not work as you would expect. There’s still some work left to get that fully functioning.
- the 4k/4k+/V devices rely on the EDID information and can indeed get into troubles if that information is incorrect; that’s why we introduced a file called
disp_cap_3d. If that file exists in Kodi’s userdata directory, then all the info about available 3D resolutions and modes is taken from it and the 3D related part in EDID is ignored