You seem very frustrated -- I really am trying to help sort this out with you.
Technical pursuits such as these will require some intellectual discussion, *especially* if you want it to have real-world application in your workflow -- that's the whole reason there are forums such as these.
I stand by my original observation that 8bit colorspace and 10bit data streams seem to be getting confused for one another and incorrectly interchanged -- this is common. Hence why I want to clear it up for those interested in getting it once and for all.
As I mentioned a couple times -- A 10bit data stream DOES NOT EQUAL 10bit colorspace.
Per Apple's spec, a 10BIT container is necessary for a ProRes MOV as well as Uncompressed 422 10bit MOV. A 10bit container (due to the 10bit subsampling) will offer better RGB color reproduction than the same MOV with 422 8bit subsampling. -- this shows us that the extra 2 bits aren't merely empty and wasted.
This being the case, I'm willing to bet that anyone claiming that the D800(e) video output is "capped" at 8bit is referring to the fidelity of the 8bit colorspace, NOT the data stream -- any links you can share that discuss this "capped" at 8bit claim would be very helpful.
So, If someone says the D800(e) is capped at 8bit integer color output, that is correct -- if someone says that the HDMI data output on the D800(e) is "capped" at 8bit, that is false.
You and I both agree that, whether the stream is 10bit or not, the footage that results from it is ONLY ever 8bit integer color (0-255). Right? So, the fact that the stream is technically 10bit, is really irrelevant to those simply concerned with the proper COLORSPACE management. There is no need to even discuss 10bit COLOR from here on out.
The links to your screen shots were were accompanied by zero explanation -- just 2 images that showed some basic info (maybe that was your point). Crack open your Quicktime files and look at the atoms in Quicktime Dumpster -- I was attempting to explain why you weren't seeing the info you were looking for (i.e. 10bit container)
As I stated, it's not about what you might see with the naked eye -- those able to manipulate the footage with professional imaging software WILL notice the difference -- again, your naked eye may not see a difference but the SOFTWARE will; and this will result in higher quality output. This is why I asked several times what software you were using.... AfterEffects? Fusion? Nuke? Something else? I'm happy to offer you a test you could run on your own so you could check for yourself whether it made a difference in your workflow -- that's all man -- plain and simple, I was trying to help you see if it made a difference for your needs or not...
Uncompressed quicktimes captured using Blackmagic Shuttle 2 are superior to the Ninja Pro-Res capture -- as stated by the links to Apple, DSLRReview, and B&H photo, to name a few.
ProRes 422 movs are 8bit RGB color represented by 422 10bit subsampled YCbCr DATA -- again as stated by Apple (the company that makes it).
The software you use, your process, and your end goals will ultimately determine what's best for your workflow. If using the best possible master footage is a concern, "Uncompressed 422 10bit" from the Blackmagic Shuttle 2 is the way to go.. until Ninja decides to do a firmware upgrade and offer uncompressed -- that would be AWESOME. I'd love to take advantage of all Ninja's features...
Again, if anyone is honestly interested in setting up tests that show the difference between quality and will allow you to make the best choice of quality based on workflow, I am more than happy to help.
I also am happy to answer any questions about color space, software, and methodologies -- if you think I can be more clear on something or possibly document something better, I am more than happy to follow your suggestions and answer any questions.
Ron I hope this helps -- if you choose to reply, please include the links that discuss the data cap. To someone that just joined this forum in hopes of learning and sharing (me), I find your tone and style to go directly against the goal of fostering an open and comfortable communication of information. I am trying to help you here, man -- cut me some slack... work with me... unless you're just trolling, in which case this board got WAY MORE INFORMATION about color,codecs, and containers than they ever wanted! ;)