Builds on first page updated with improvements for menus and switching to 3D.
Posts by popcornmix
-
-
Here's a 'smaller' 11GB ISO (on Google Drive) w/few more m2ts/ssif files removed. Trying to be careful not to nix those that might need to remain intact.
Can't get that to open menu - I do see attempts to open missing files: 00002.m2ts 00008.m2ts 00010.m2ts
I'll see if I can fix it up.
edit: I think I've got it to open. -
That file is 14GB! Can it really be that big just for a menu? Yikes.
I'm sure more m2ts/ssif files could be removed. You might want a few remaining that are used as animated scenes between menu items, but they are probably only seconds long, so very small.
-
Hacky way it is. Deleted all m2ts and ssif files larger than 2GB.
Any chance of a different file host. That says I need chromium when accessed from firefox, and then from chromium gives be a "buy pass" button for £3.90 to download it.
Google drive is often a good choice. -
The few 3D ISO's with menus I have are 40GB+. Too large to share. No idea how to get a small sample that includes menus. Know how to extract samples from MKV's and movie only files. I don't care for Blu-ray menus myself, but some users do.
I have had cut down iso file previously (as samples for bug reports). I think both from an authoring tool and the hacky way.
The hacky way is to mount the iso so you can see the file structure. Delete the larger m2ts files in BDMV/STREAM (i.e. the main feature and any substantial bonuses), and then zip it up. I should be able to play it from the file structure and see the menus, and most of the 40GB+ is gone.
-
ht2tweak if you get me a sample with incorrectly rendered 3d menus I'll take a look.
-
FeinTech Support assured me the splitter doesn't interfere with EDID in COPY ALL mode and the switch should be completely unaware of EDID anyways (according to FeinTech).
If that were true, how would you explain the fact the diagnostic shows "EDID:none" when the splitter is in place, and "EDID:ok" when the splitter is removed?
I think the only explanations are:
1) The splitter prevents the EDID from being read
or
2) The additional HDMI cable prevents the EDID from being read
-
The splitter not correctly handling EDID is weird since I purchased a FeinTech SP210 that (supposedly) has EDID Management built in and I made sure to set it to COPY OUT with the TV connected to the relevant output.. Could anything else go wrong there?
If direct connection to TV shows an EDID and through splitter doesn't, then it's the splitter or the second hdmi cable you are presumably using that doesn't support reporting the EDID.
-
When I connect it through the Splitter without anything connected, I see:
display: DISP0: HPD=1 EDID=none #0 DISP1: HPD=0 EDID=none #0
That is the key information. EDID=none means your splitter is not forwarding (or provising its own EDID).
That means downstream devices (i.e. LibreELEC) do not know what hdmi modes are supported.
That is a fault with the splitter (it is not hdmi compliant).
You may be able to work around it with getedid create, ran when the spliter is not connected (i.e. directly connected to TV) to capture the EDID to a file. Then you add back in the splitter and LE can see the HDMI modes available from the EDID file.
-
popcornmix, this is expected behavior right w/framepacked?
In HDMI terms, framepacking uses a 1920x2205 framebuffer (1080 left eye + 45 blanking + 1080 right eye) which kodi treats as the gui being in Over/Under mode, so very similar to TAB mode, but full rather than half resolution, and with a 45 pixel gap.
So yes, I'd expect the Over/Under mode for framepacking.
-
Connect to hdmi (through the problematic splitter). Power the pi without an sdcard (or anything else connected).
You shoud see a diagnostic display on TV. What does the "display:" line show?
-
First of all, thanks for doing awesome work on 3D playback and MVC decoding! 3D is not dead! (... yet)
Does this mean full-SBS (3840x1080) files are processed on the fly "to" frame-packed, and sent as frame-packed video (1920 x 2205) to the display or projector? Is the RPI4/5 fast enough to do this conversion on the fly?
Yes, conversion is done on the fly.
(What are the chances that we see this 3D implementation working on x86 hardware? What would be missing? If I understand it correctly, MVC streams are software-decoded, so no special hardware decoder is needed? Does the drm/gbm display stack on x86 need fixes, or is this "only" a Kodi fix?)
Need someone to put the bits together and test it. But I don't use x86 for kodi so it's not me.
-
Updated latest build in first post with tweaks for hdmi mode chosen.
It will try harder to choose a 3d mode (e.g. if gui was 4k it will switch to 1080p24 FP).
The whitelist removes 3d variants so isn't as long.
If you enable 1080p24 then it will be willing to switch to any supported 3d variant of that mode.
FP is preferred if available, otherwise it prefers the setting in video/stereoscopy/preferred mode.
-
Thanks, look forward to any enhancements. Just thrilled we have another 3D-capable Kodi device now. Appreciate your work, aided by Monsieur Claude :).
Oh, in the future, would there be .tar like updates vs full image? Been a while since I've used LE.
Do you need the tar? The img.gz can be used for updates too. Just copy to /storage/.update and reboot.
-
No need for log currently. I might tweak the resolution/3d mode switching to be a bit more foolproof tomorrow.
Let me know if you have any issues. -
Yes - it's not choosing the 3d mode. Are settings set to 1920x1080?
Setting a whitelist that includes "[email protected] TAB" and setting "preferred mode" to "over/under" is also likely to get FP mode enabled. If not, another debug log. (don't enable component logging - the windowing/video makes the log very big). -
kmsprint (without the -m) while playing a 3d file will show you the 3d mode chosen.
But switch settings to 1920x1080 first as I think that is wanted currently.
-
Depends on you settings. From original post:
FP mode supports the full 1920x1080 resolution (SBS and TAB half the resolution).
If your movies are half-SBS or half-TAB, then "same as movie is fine".
If they are full-SBS or full-TAB then you ideally want FP mode.
If you set "preferred mode" to "over/under" and your display supports FP, then that should be selected by default.
Also can you set your resolution (in settings/system/display) to 1920x1080? I think you may be ending up at 3840x2160 when playing video (which doesn't support 3d) and will stop the autoswitch.A whitelist would allow this, but it seem without a whitelist kodi won't lower the resolution when starting a video.
run "kmsprint" to check which type of 3d mode you are in (it should say one of fp/sbs/tab).