May be a minor thing: I have lots of full side-by-side files with names like 'Movie.Year.3D.FSBS.mkv', but Kodi doesn't recognise them as 3D movies. I would have to rename them like 'Movie.Year.3D.SBS.mkv' – it seems that the letter 'F' is preventing the 3D recognition.
[RPi] 3D Support builds
-
popcornmix -
July 31, 2026 at 7:35 PM -
Thread is Resolved
-
-
I would have to rename them like 'Movie.Year.3D.SBS.mkv' – it seems that the letter 'F' is preventing the 3D recognition.
First world problems

-
May be a minor thing: I have lots of full side-by-side files with names like 'Movie.Year.3D.FSBS.mkv', but Kodi doesn't recognise them as 3D movies. I would have to rename them like 'Movie.Year.3D.SBS.mkv' – it seems that the letter 'F' is preventing the 3D recognition.
That one can be fixed without renaming. Kodi detects 3D from the file name with three patterns, and the side-by-side pattern only accepts "sbs" with an optional "h" in front, so "SBS" and "HSBS" match but "FSBS" does not (the same goes for "FTAB"). The patterns can be overridden in /storage/.kodi/userdata/advancedsettings.xml:
Code<advancedsettings> <video> <stereoscopicregexsbs>[-. _][fh]?sbs[-. _]</stereoscopicregexsbs> <stereoscopicregextab>[-. _][fh]?tab[-. _]</stereoscopicregextab> </video> </advancedsettings>If the file already exists, put the two lines inside its existing <video> section instead. Restart Kodi afterwards. The name still needs the "3D" part as well, which yours have.
Prepared with Claude Code (Anthropic)
-
Talking about RPi4 overclocking, worth doing w/RPi5?
That's up to you. I think a pi5 is fast enough that it's not critical to overclock.
But you may find you can get up to 25% extra performance for free, so if you are willing to do some experimentation it may be worth it for you.
I'd say overclocking to 2800MHz is likely to work, 3000MHz needs a bit of luck with the silicon lottery.
If arm_freq=<N> is not reliable adding over_voltage_delta=<M> may help. M is in microvolts.
Try 25000, but you can go higher.
Note: if you push too far, then random crashes are quite likely (although it shouldn't be possible to permanently damage a board).
-
I'd have assumed FP (so over/under) would be the preference if supported by display and not disabled in advancedsettings. If not FP, then it should use your preference from settings. A log file would be useful.
So, captured a video showing 3D MVC playing in SBS mode w/20260909195900-6f94f34, then downgraded to 20260904144932-66d24f6, and playback was expected over/under. Updated back to 20260909195900-6f94f34, and enabled debug logging to share, but now playback is also over/under. So, I guess no problem to report :).
-
The graphical issues with for example Cars is still present on both RPi4 and RPi5 versions.
Can you test one of these builds for a potential fix for garbled right eye on Cars: Pi5 Pi4
edit: updated links - attempted to clear menu when playing a second disc without stopping first.
Also enabled more BluRay logging. Can you enable logging and Blu-ray specific logging, and reproduce the issue where the 3D menu said you needed a 3d TV.
-
Yes, this did make a difference w/my Zidoo as well, but RPi5 and AMD still have sharper 3D, and more pop than Zidoo. I'd say RPi5 and AMD would be A++, Zidoo using Priority RGB444 8BIT for non-4K an A, and Amlogic-based h/w-decoding boxes a B+.
I must agree: the 3D image on the RPi5 (and probably on AMD as well) still looks better than the one on the Zidoo with “Priority RGB444 8BIT for non-4K content". Since I have several Zidoo RTD1619BPD devices for 3D in use and don’t want to replace them all with RPi5s right away, I'm wondering if there are any other settings on the Zidoo that differ from the default values and could produce a similar 3D result to the RPi5

-
I have 3 Zidoo's as well: 2x Z9X Pro's and an X9S. According to Gemini, these are the most recommended settings for 3D:
- Non-4K (1080p / 3D MVC): Priority YUV444 10BIT (or 10BIT RGB)
- HDMI Color Range: 16-235 (Limited)
You've already tried YUV444 10BIT. Wonder if 10BIT RGB would be better. I'd be surprised if so as we're talking 8-bit content. If the PQ you got with 8BIT RGB is the best we're going to get, then it's likely due to Realtek's MVC hardware decoder and picture processing.
-
I think Gemini is wrong. The Pi5 appears to output RGB(16-235). On the Zidoo, selecting "Priority RGB444 8BIT for non-4K content" and "HDMI Range 16-235" (important: do not let it on auto!) produces a similar result. All the other options were worse in some way. With these settings, the 3D on my Zidoo is on par with the Pi5, or at least very close. What results do you get when you compare these settings?
-
Can you test one of these builds for a potential fix for garbled right eye on Cars: Pi5 Pi4
edit: updated links - attempted to clear menu when playing a second disc without stopping first.
Also enabled more BluRay logging. Can you enable logging and Blu-ray specific logging, and reproduce the issue where the 3D menu said you needed a 3d TV.
Logs: https://www.swisstransfer.com/dl/01a09982-0a…fb-d398c60dec5f
I have now tested both the RPi5 and RPi4 versions and Cars now seems to play without glitching
The menu issues are unchanged. Most fail to play the menu but then fall back to playing the movie instead. But on Dune (2021) it crashes when you try to open the menu. No problems playing from the playlist.
I usually play my 3D ISOs on my PS3s. The PS3 is known for being a bit picky with playlist issues on some movies, causing skipping or complete failure of playback. So for some of these problematic movies I have made remuxed versions that play without issue. I tried John Carter that I know have this issue and I get the same problem here.
The resume issues are also still present.The attached log is from my RPi5 and have the following:
1. I am playing Money from Home using the menu and getting the no 3D TV error.
2. I try playing the menu on Dune (2021) and it crashes hard.
3. I try to play the menu on Jurassic World, it skips directly to the movie.
4. I play the menu on Jurassic World: Dominion and it works. This menu also has a 3D/2D option like Money from Home and I selected the 3D option and it plays the movie in 3D. However it flips between 2D and 3D several times while loading the menu.
5. I try to play the menu on Jurassic World: Fallen Kingdom, it skips directly to the movie.
6. I play the full ISO of John Carter, it starts but after I try to skip 20-30 min into the movie it crashes.
7. I play the remux ISO of John Carter, here I have no issues skipping in the movie.
8. I play Avatar: Fire and Ash that is 2 discs. I start from the playlist and it starts. I try to skip past the break point and I manage after i few failed attempts. It shows the playlist or menu box, I choose playlist and it starts playing disc 2. So kinda works but a bit janky
-
I think Gemini is wrong. The Pi5 appears to output RGB(16-235). On the Zidoo, selecting "Priority RGB444 8BIT for non-4K content" and "HDMI Range 16-235" (important: do not let it on auto!) produces a similar result. All the other options were worse in some way. With these settings, the 3D on my Zidoo is on par with the Pi5, or at least very close. What results do you get when you compare these settings?
Note, this should all just work automatically if all the components in the chain do the right thing.
The EDID from the sink (display) reports the list of HDMI modes it supports.
These include CE/CEA modes (TV-style timings) and IT/DMT modes (monitor-style timings).
There are different default rules for RGB quantisation range: CE/CEA video timings generally use limited range, while IT/DMT timings generally use full range (with some exceptions).
When the source (Pi) outputs HDMI, it can indicate the RGB quantisation range in the AVI InfoFrame. The sink should use that signalling, or the appropriate default for the video format, to interpret the pixel values correctly.
So everything should just work by default. However, it is not uncommon for devices in the chain to get this wrong - for example, a sink might not correctly respect the InfoFrame signalling, or a source might choose or signal the wrong limited/full-range setting. This results in things such as blacks being crushed or looking grey, and whites being clipped.
Colourspace/colourimetry (for example BT.601 vs BT.709) is another similar setting. The source signals the colour encoding in the AVI InfoFrame, and the sink is expected to interpret the pixels accordingly. Again, this should normally work without any manual settings, but interoperability bugs or incorrect signalling can result in incorrect colours.
-
The menu issues are unchanged. Most fail to play the menu but then fall back to playing the movie instead. But on Dune (2021) it crashes when you try to open the menu. No problems playing from the playlist.
I think most menus you are having trouble with are java ones (2,3,5). You need to install the "JRE for BD-J menus" addon from LibreELEC repo to support those.
1. wasn't obvious from log. I'd probably need a sample menu that behaves like that to debug further.4. looks fixable.
6. looks like a bad rip:
Codedemuxer seek to: 2410868.000000 bluray.c:925: Unable to seek clip 00800.m2ts! bluray.c:1720: Seek to 9400237248 bluray.c:824: Read past EOF ! Process - eof reading from demuxer CVideoPlayer::OnExit()
the indexes point beyond the end of the file - we hit EOF and end. It may be possible to treat that as switch to next item in playlist which may behave better. -
1. I am playing Money from Home using the menu and getting the no 3D TV error.
I'm getting this on Cube2 and Rocktek G2, both w/AVDVPlus build, and w/Vero V, all h/w-based MVC decoding. Could it be an authoring issue? Choosing the 2D version plays the 3D version.
The Pi5 appears to output RGB(16-235). On the Zidoo, selecting "Priority RGB444 8BIT for non-4K content" and "HDMI Range 16-235" (important: do not let it on auto!) produces a similar result. All the other options were worse in some way. With these settings, the 3D on my Zidoo is on par with the Pi5, or at least very close. What results do you get when you compare these settings?
Re-tested w/several titles, and PQ is very close, but still find RPi5 and AMD slightly better (but, noticeable). One issue I am seeing on AMD is frame skips (or possibly micro-stutters); will post debug log in the other thread.
-
I think most menus you are having trouble with are java ones (2,3,5). You need to install the "JRE for BD-J menus" addon from LibreELEC repo to support those.
1. wasn't obvious from log. I'd probably need a sample menu that behaves like that to debug further.4. looks fixable.
6. looks like a bad rip:
Codedemuxer seek to: 2410868.000000 bluray.c:925: Unable to seek clip 00800.m2ts! bluray.c:1720: Seek to 9400237248 bluray.c:824: Read past EOF ! Process - eof reading from demuxer CVideoPlayer::OnExit()
the indexes point beyond the end of the file - we hit EOF and end. It may be possible to treat that as switch to next item in playlist which may behave better.Ah, I'll try the JRE for 2,´ 3 and 5. Edit: I tried them after installing JRE but same same thing.
6 is not a bad rip it's a badly authored disc. There are quite a few of them that has been released over the years. PS3 for example is known to be picky and has issues with them. You can play that ISO on PowerDVD 18 without problem.
1 is not a bad disc. The menu works fine on the PS3 funnily enough
Launches the 3D version, no problem.
Regarding 3D subtitles and dynamic depth there are still some ways to go. To help in this I have made this demo disc that has many different variants of dynamic and static depth for subtitles. I even included a torture test that sweeps between the max (127) and min (-127) depths possible with changes every single frame.
ISO can be downloaded here: https://archive.org/details/big_bu…tle_demo_ntm-3d
I have a capture playing the torture test on my real PS3, i handles it without issue
External Content youtu.beContent embedded from external sources will not be displayed without your consent.Through the activation of external content, you agree that personal data may be transferred to third party platforms. We have provided more information on this in our privacy policy. -
Note, this should all just work automatically if all the components in the chain do the right thing.
(...)
However, it is not uncommon for devices in the chain to get this wrong
(...)
Yes, I'm afraid, this sometimes may be the case with the default settings on Zidoo devices:
Option A (Zidoo's default setting) gives YUV444 10-bit priority to non-4K content. The 3D file is in YUV 4:2:0 (8-bit) format. The Zidoo takes this signal and artificially upsamples the colour data to YUV 4:4:4 (10-bit). The HDMI cable then transmits this artificially upsampled YUV 10-bit signal. The projector receives the YUV signal and runs it through its own colour matrix. It then converts YUV to RGB and downsamples the 10-bit data back to the 8-bit resolution of the DLP mirrors. So the signal is processed and converted twice. Conservatively tuned video chips in projectors often apply a slight anti-aliasing filter during the YUV-to-RGB conversion, which causes fine details and colour edges to become slightly blurred.
Option B (Zidoo setting: 'Priority RGB444 8-bit for non-4K content'): The 3D file is in YUV 4:2:0 (8-bit) format. The Zidoo’s media chip mathematically and precisely converts the video to 8-bit RGB in a single, direct step. The HDMI cable then transmits the final pure RGB 8-bit signal. The projector completely disables its internal YUV conversion stage. It passes the RGB data directly to the driver and the RGB DLP mirrors without any intermediate steps. There is only a single conversion at the optimal point (Zidoo). This means that the image retains its full native sharpness and the colour edges remain just as crisp as they are stored in the source.
However, take this with a pinch of salt — I admit, I've chatted with AI

-
Regarding 3D subtitles and dynamic depth there are still some ways to go. To help in this I have made this demo disc that has many different variants of dynamic and static depth for subtitles. I even included a torture test that sweeps between the max (127) and min (-127) depths possible with changes every single frame.
I've downloaded. It would be useful if you could describe where the output is wrong?
e.g. at 00:30 sub should have increased depth compared to 00:29, but was the same.
-
Don't know if this has been asked before but can this build output frame packed mode all the time? My projector takes some time to sync over to 3D mode, so I lose about 10 or more secs of the movie when starting. On my old build on pc, I could have it in 3D mode all the time so there was no sync delay. Awesome build btw

-
I've downloaded. It would be useful if you could describe where the output is wrong?
e.g. at 00:30 sub should have increased depth compared to 00:29, but was the same.
You can see the list on the Internet Archive page of what each subtitle should be doing. You also have an overlay at the top left corner that says what the currently selected subtitle is configured to do as you switch between subtitle 1-12 that are the demo ones. After changing subtitle track you need to wait until the next text line fore the overlay shows but after that stays on for the rest of the movie.
Currently none of the dynamic subtitle tracks are updating properly, there at a lot of missed and inconsistent depth updates. Sometimes seconds between updates.
If you watch the video I provided you can see how one subtitles where the depth change every frame behave on a real PS3. It updates the subtitles depth every frame just as instructed, making the subtitle smoothly sweep between -127 and +127 in depth.Don't know if this has been asked before but can this build output frame packed mode all the time? My projector takes some time to sync over to 3D mode, so I lose about 10 or more secs of the movie when starting. On my old build on pc, I could have it in 3D mode all the time so there was no sync delay. Awesome build btw

Go to Settings/System/Display - "Stereoscopic 3D mode / Current": Over / Under
This will switch frame packing on.
But I would suggest to instead set Settings/System/Display - Delay after change of refresh rate: 10.0 seconds
Or what every value your switching delay is. That will pause the start of the movie for that amount of time after activing frame packing. -