Sounds awesome. But please, please, under no circumstances, do anything with the Pi5 build that might touch its spectacular, unmatched MVC 3D quality
! The Pi5 obviously has no performance issues with your current builds.
Posts by vobs
-
-
Yes, I tried every possible setting on the Zidoo as I really wanted to see it being on a par with the Pi5. But, honestly, it couldn't get there ¯\_(ツ)_/¯
-
As an aside, after further testing, I found that with the above-noted Zidoo settings ('Priority RGB444 8-bit for non-4K content' and 'HDMI Range 16-235'), still images from both systems appear almost identical. However, I can't quite put my finger on it, but playing a high-quality 3D scene with popcornmix LibreELEC 3D fork on the Pi5 feels even crisper and easier on my eyes than with the Zidoo. I can hardly believe it, but that's just how it seems to me (and ht2tweak seems to see it similarly)

-
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

-
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?
-
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

-
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.
-
cinemaONE Oh boy, you nailed it!! I just changed the display colour settings on the Zidoo from 'Priority YUV444 10BIT' to 'Priority RGB444 8BIT' for non-4K, and I think this made all the difference - thanks a lot

We now have the perfect Zidoo 3D experience, which is no longer available anywhere, and a brand new perfect 3D Kodi LibreElec fork experience, which will be the way forward popcornmix

-
Excellent insights, thanks. With full rez 3D content, Pi's appears sharper. vobs and another user on AVSForum concurred when he tested as well. But, AMD's is as good as Zidoo's, and that's saying a lot.
Indeed. Yesterday, I repeatedly switched between Zidoo (HDMI1) and Pi5 (HDMI2), both paused in the same 3D scene. It may be my setup and can't be taken as a general rule, but I definitely have a punchier picture with the Raspberry Pi.
-
Maybe a quick feedback regarding the Netflix add-on that I tried to install but failed:
Since this 3D build is based on the Kodi 22.0-BETA1 (Piers) branch, it looks like the underlying Python and HTTP library changes in Kodi 22 break the CastagnaIT Netflix add-on’s network requests (resulting in the 404 / pathEvaluator errors). CastagnaIT currently targets stable Kodi 20/21 releases, so bleeding-edge Kodi 22 builds may run into compatibility issues with how the add-on routes its API calls.
However, please take this information with a pinch of salt – I was accompanied by Gemini
- just wanted to drop this info here, nothing more. And thanks again for your awesome work! -
Guys, I know this sounds silly, but is the 3D picture on popcornmix PI5 LibreELEC fork maybe just a tad sharper than on the Zidoo? ht2tweak already mentioned it in his YouTube video. Technically, I can hardly imagine it, but every time I watch an MVC 3D video on the PI5 and then on the Zidoo, it seems to me like it’s a bit sharper on the PI5
. Anyone else? -
edit: do you have a whitelist set up? I think if you do (and it includes [email protected]/1920x1080@24) then you'd get the FP output. I'll look into making that happen without a whitelist.
Awesome, thanks for the tip! I hadn't set up a whitelist. I have one now and it's working
By the way, will we have to create a new image and set everything up from scratch when you release a new version? Or will it appear in the LibreELEC update process? -
Some feedback from playing around: I tested a 3D file in 4K FSBS format (3840 x 2160), which is used for VR. Anyway: The Zidoo Z9X Pro appears to recognise, downsample and send it as 3D Framepacking, which is quite impressive. On the Pi 5, it is just sent as a standard SBS image which has to be manually switched to 3D using the projector's remote control. I guess this results in more resolution loss than with the Zidoo processing. However, to be fair, with the highest 4K FSBS resolution we sometimes see (7680 x 2160) the RTD1619BPD based Zidoo completely refuses to play.
-
For interest, what happens with "HDMI LINK" on, but CEC settings disabled on Pi.
That should narrow down if its purely enabling "HDMI LINK", or if it's something it interprets from the CEC data that makes it choose to do the glitches.
Also does the projector have any sort of firmware update mechanism? It could be a bug they've fixed.- "HDMI LINK" on, and CEC settings disabled on Pi -> no glitches
- "HDMI LINK" on, and CEC settings enabled on Pi -> no glitches
- "HDMI LINK" off, and CEC settings disabled on Pi -> no glitches
- "HDMI LINK" off, and CEC settings enabled on Pi (which was the standard setting) -> glitches!The projector has no firmware update mechanism.
-
I'm afraid this still doesn't make any sense. "HDMI LINK" is CEC. No obvious reason why it would affect the glitches.
Fully agree - that's why I haven't tried it any sooner. If I turn "HDMI LINK" off, the glitches come back immediately. Turn it on again and they disappear for good.

-
I have now ordered an HDFury Communicator HDR HDMI 4K from a nearby store to see if it makes any difference with this box in between.
No success even with the HDFury Communicator HDR HDMI 4K in between

(....)
But wait wait wait!!! I Think I found it: Just went through all the projector settings again and switched "HDMI LINK" ON. And boom! Not one single glitch since then (the movie has been playing for 10 minutes now - fingers crossed...). Why this?

-
vobs' issue is hard to understand. Nothing makes much sense. Seems to be a fault of the projector, but it presumably only applies to some configuration. vobs Do you have any picture processing options on projector? (e.g. motion smoothing, de-noising etc? I'd be tempted to turn everything off). If you can configure the input as a PC rather than a BluRay that often disables processing to reduce latency.
I turned off everything related to picture processing on the projector. I don't understand it either. Regarding the HDMI inputs, there is no configuration option apart from Source Lock and HDMI Link (which is turned off). I have now ordered an HDFury Communicator HDR HDMI 4K from a nearby store to see if it makes any difference with this box in between.
-
A debug log file will confirm if stereoscopicpreferframepacking setting has been read correctly.
If you say you can watch a SBS video without glitches when 3D mode is disabled on projector, but it starts glitching when you press the 3D button on projector (which the Pi will have no knowledge of), it's hard to see how this is the fault of the Pi.
Totally agree, that's what I meant by 'sounding weird'.. But I have news: I just tried another 3D projector — a Vivitek H1188. It's lamp-based, but has a similar age and specs like the SIM2 Nero 3 Plus LED (HDMI 1.4 and 144 Hz triple flash 3D). And surprise: no issues there! To be sure, I tested DLP Link and RF 3D — both worked without a single glitch. The SIM2 has no issues with Zidoo hardware-coded 3D, but definitely with the current PI5 Kodi/LibreELEC version.