Ahhhh. OK… Pity cant know which film is that. Would make some research possibly. Thanks.
2 Likes
Btw have you tried @doppingkoala DV on your x96plus? You will be amazed to get DV on that.
I have never done it myself, but have read up on it before.
Its essentially a two stage process, first you need to have a decrypted BD Disc (I guess BDMV and/or ISO) or MVC-MKV (both can be easily obtained with MakeMKV) and then use https://www.videohelp.com/software/BD3D2MK3D.
It is a reencode though, so you can lose quality depending on your settings and it might take a while, but the tool can essentially convert MVC into any half/full format of TAB, SBS, FS.
Edit: Further Reading/Guide: https://www.avsforum.com/threads/how-to-rip-3d-blu-ray-full-resolution-for-lg-4k-3d-for-native-plex-playback.2966524/
1 Like
New CoreELEC user here, just got the Ugoos A6B+ going with Kodi 21. Loving it!
I Google’d MVC playback and have been catching up on this thread.
I’m excited to see it looks like developers are closing in on solving/adding 3D playback! I have a few hundred Mkv and Iso rips that I’ve been using a Z9X for with my Awol 3500. Looks good but I’m excited to leave that clunky gui behind and move on to Kodi with CoreELEC!
So newb question, I tried downloading the dev tar update from a few days ago, but upon installing it froze my ugoos and I had to revert back to the latest nightly. Is that because I’m on Kodi 21 or did I miss a step?
Hey Mozy,
no that should work in principle. I tried updating to the latest dev build in this thread from CE19.5 and from the latest nightly CE21. One thing you need to be careful with: Set CE to 1080p for the GUI resolution before updating, else you get flicker and nothing works. At least that happened to me when it was set to 4k prior to updating.
2 Likes
Hi,
I’m following this thread with huge interest and respect to the work done on this as 3D is only thing I’m missing from my current CE box. Unfortunately I had no luck to try this.
My box is NOKIA 8010. I have installed stable CE21 NG. Wired network didn’t work but wireless was working. After update from this thread latest devel wireless stopped working completely so I can’t access files over network.
I have a questions. Will this eventually go into NE (NO) builds also afterwork is completed on this feature?
And if anyone have suggestion how to make network work on my NOKIA 8010 box for this devel version please let me know.
Thanks.
@Xenothar thanks for the tip! That was my problem. 3D FP works and looks awesome!!
I wanted to confirm that this threads Dev builds are only working in HD flavors at the moment, is that correct?
I get bad playback and flicker and then freeze/crash if I try and play a 4K UHD title unless I switch back to Nightly builds.
This build test 3D only.
1 Like
@Portisch Is it possible to add WiFi to your last build while we wait for next development thx.
Nice topic.
I also still use a older 4k Oled with 3D support, it is great what it can show with MVC 3D.
I used to use a Intel based HTPC, with special Kodi build for 3D support, but I stop using that. Now I’m only use Android/Google TV devices as mediaplayer, but never could find a solution for (real) 3D support i.c.w. Android TV.
I saw some things that were dropped by AmLogic for the SEI804 series (Homatics, Dune, Nokia), and beside VC1 (no license), MVC was also one of those.
Now, when playing a MVC 3D sample, I can get it to work with the V21 build that was shared some time ago. But I miss a important 3D setting in CoreElec/Kodi settings, for 3D interlace support. The format used on LG Oled 3D.
So, it that a impossible thing to add as setting? I can’t say.
Wow, the devs here are amazing!!
I wanted to ask how hard/easy it would be to merge the latest 3D build in this thread and latest DoVi build (with the payload generator) while we wait for a official update?
I’m not a coder, but I thought maybe I should ask if this is something that can even be done, or is that a super bad idea?
Hey,
tl;dr: Interlacing the two fields is not a Kodi/Andoid-Box/PC issue, but is happening in the TV. Interlacing signals are very uncommon and have nothing to do with MVC/frame packing really.
Long version:
Are you talking about interlaced support in terms of the signal being sent from Kodi? As in, your TV cannot interpret side-by-side/top-and-bottom as an alternative to MVC/frame packing and needs an interlaced signal? That would be very odd, since the 4k OLED should have no issue with SBS/TAB I think and also interlaced/checkerboard signals are like suuuuper rare.
Just to clear a few things up, how all of this works, in case it wasn’t clear to you or others:
MVC is just a second stream of data (not a picture by itself), which contains the differences between the (usually) left eye, which is the normal video stream on a 3D bluray, and the right eye. There is no interlaced, there is no side-by-side, no top-and-bottom from the bluray/bdmv/m2ts/mkv itself yet, this happens later in the processing chain.
In step 1 the hardware calculates the second eye (right eye), also called a “field”, from the MVC delta-data.
In step 2, this now needs to be sent to the TV somehow. There is a variety of ways to do this in principle. The “true”/recommended/official bluray-player way, which is also what happens, when you choose the “Hardware” option in the Kodi popup, is called “frame packing” or Full HD 3D (FHD3D), possible since HDMI1.4. This is two 1080p fields (left and right eye) packed vertically in one frame with some deliberate active blank space (45px to be exact) inbetween, resulting in a 1920 x 2205 pixel frame. Due to limitations of HDMI back then, it was solved that way and the 2x1080p frame packed signal was limited to 24p (so no more than 24 of this vertically packed frames). Other options for sending the data to the TV are/were “(half) side-by-side”, “(half) top-and-bottom” (also called (half) over-under) and “frame sequential” as well as the much rarer “interlaced” and “checkerboard”. They have no blank space, so full top-and-bottom is not the same as frame packed but almost.
Sidenote: If you have to choose and have no frame packed signal available, generally for passive interlacing 3D-displays you should always prefer the top-and-bottom signals over side-by-side. To my knowledge interlaced signals and checkerboard signals fell out of favor quite early and were not really used anymore in the later days of 3D. I think, they were even patched out of the later TVs as a possibility (my LG 4k OLED only shows options for SBS and TAB), therefore I think, you are not talking about the signal itself, but how the TV displays this signal, which is step 3.
Step 3: The TV now has to display the two “fields” within the frame it got sent. It unpacks it first and then shows it on the screen. How exactly depends on the TV model/brand. A passive LG usually (maybe always) does this by interlacing, as you mentioned, where every other horizontal line is polarized differently, so that your 3D glasses will only let light from half of the total horizontal lines to each eye, meaning, you lose half the resolution theoretically on a 1080p 3D passive display. This interlacing has nothing to do with the signal coming out the Kodi-box and is purely how the TV processes and shows the picture on screen.
Sidenote: Active displays didn’t suffer from the resolution loss, but had other drawbacks and issues. 4k passive displays had enough pixels to cope with the interlacing-drawback without losing detail for frame packed, FSBS and FTAB, that’s why they are renowned as the best 3D TVs ever made.
If you really want/need an interlaced signal, then technically this is not that difficult. Personally, I would not see a need to implement it though. The only benefit would be, that you do not even need to switch on 3D-mode, as the signal would already be in the “right format”. That is, if left and right eye are not swapped of course. Oh, and you get 60 fps back, as an hsbs/htab/interlaced or checkerboard signal acts within the normal 1080p frame. But thats a moot point for 24 fps movies. Also, the interlaced signal would be quite useless for active displays, which need to deinterlaced it first. Checkerboard would be even worse in this regard for both TVs.
Also, this would be a general 3D issue and has nothing to do with MVC, therefore, it belongs in another/new topic, as this is about MVC and frame packing signals.
Nice, a fellow AWOL 3500 and Zidoo Z9X owner! I am also seriously considering dropping the Z9X, which has amazing video/audio support and top-notch DoVi support, but a clunky, slow, often maddening UX. The Ugoos AM6B Plus plus CoreELEC seems to be a really smart way to go in the future, but I am unlikely to make the switch until there is support for 3D (ideally, multiple types, such as FSBS and MVC). Watching the thread intently!
1 Like
For those joining this thread, Portisch is currently working on adding support for the S928X and will likely return to this afterwards.
When still using the Windows HTPC and those specific Kodi builds, the hardware option was the way to go, before getting my LG Oled. My LG 4k Oled 950V uses the same 3D technique as yours I guess, but I specifically used the Interlaced mode as the TV produces a 4K output. When I still was active in the 3D “scene”, what the LG Oled could offer me with the interlaced output was at least on the level what MVC would gave you on a non Oled 4K passive 3D TV. It was outstanding.
So in stead of using the Hardware option with HDMI 1.4 (which I could not because I used an active DP1.2 to HDMI2.0a convertor), I switched to the Interlace mode.
But I understand, this is offtopic here 
Next test image:
2 Likes
Can’t see any difference with the previous build for now. Thanks @Portisch
FSBS and 4k should now work.
I don’t have a top bottom sample.
My 3D TV is 2k so can’t test FSBS nor FOU and 4K.
Here is a Full Top/Bottom sample (1920*2160)
Vero can not display it correct. Also ffmpeg does not detect automatic top/bottom.
EDIT:
Looks like when set manual to over/under in kodi the standard 3D TopBottom mode with 1920x1080 @ 23.976 Hz does work.
The full with width: 1920, height: 2072, fps: 23.976 not yet.
EDIT:
FTAB should normally be 1920x2160. So the sample looks not really ok as the two frames 2072 / 2 = 1036 aren’t properly aligned together.