Beta version v6.4.06 for Z9X/Z10 Pro/Z1000 Pro/UHD3000/NEO S/NEO X release

Your Zidoo always thinks the TV supports DV and the signal going to the TV is always LLDV regardless of whether the file is DV or not.

The VS10 logo just tells you that VS10 is converting whatever is input into LLDV and the Double D symbol tells you that the file is DV anyway so is passing through without needing to be converted to LLDV.

1. Yes
2. Yes
3. Yes it shows VS10 DV for reasons stated above. No, because HDR10+ is irrelevant to VS10.
4. It will show VS10 DV

 

Strange problem after last update.
In posterwall, after a clean library and complete scan with NFO priority, all collection are gone (only 3/4, before were +100).
If I select a cast member no filmography is shown.

Vincenzo
Z1000 Pro, 6.4.06 with 1700 film stored on Qnap 653d

 

As far as collections go, open an NFO for a movie that should be in a collection but isn't and see if there's a <set>..</set> entry - that defines collections. seem to remember an early bug where that was missing when NFOs were exported.

eg:

<set>
<uniqueid type="tmdb" default="true">645</uniqueid>
<name>James Bond Collection</name>
<overview>The James Bond film series is a British series of spy films based on the fictional character of MI6 agent James Bond, codename "007". With all of the action, adventure, gadgetry &amp; film scores that Bond is famous for. (We do not consider the 1954 release of Casino Royale for this series because it was actually a television episode and not a theatrical film.)</overview>
</set>

Cast member/filmography etc details aren't exported with NFO and they don't update at runtime - I've asked about this a few times but have always been told it's too difficult to implement...

 

Um i found a "crash" sample: https://drive.google.com/file/d/1p5l32hDbaHOMAeRD5O5XpdVsoJ5_TGnt
Sample is from here: https://drive.google.com/drive/folders/17z94AGSQN7m0VLS1oDEkViQlr0wvpWhG

I know sounds strange, but after i play (5-10seconds) or try to play (sometimes i get black screen) this file, all kinds of weird shit happens afterwards. I cant play any other files anymore...or more precisely i get a black screen a lot. If i try to pause/resume files the player just freeze or closes. I cant get back to the home-screen reliably anymore, also getting black screens.

I literally have to reboot the z9x to fix this.

Settings: VS10 enabled for DV/HDR and prefer LLDV, 4k@60hz refresh switching is off, MaxCLL is on, all set to 422 12bit, limited color, enhanced hdmi, no hdpc.

 

No idea what's going on with that file - I think it's to do with a dodgy codec ID.

That's the Mehanik White 900-4000nits test pattern and the version I have (which has a codec ID of hev1) plays perfectly.

https://mega.nz/file/5aJHSAiT#2Lmh8BL9kS9CMO_zSTKEgIPucDRmuDyLgy5tUFR_iDE

 

My sample also has "hev1"?

If i extract the video streams i see those differences:
your sample:
x265 (build 128) max-cll=4000,360

my sample:
x265 (build 151) max-cll=4000,1000

 

Your sample is hvc1

 

Hi Mark,
THANKSSSSS!
Rebuild library with no NFO parsing and all collections and cast details now are perfect!
Only drawback is some film not matched, but minor pain.
Maybe I have to save library for backup?

Vincenzo

 

mhh LAV filters reports "biCompression: HVC1" on your sample, while ffprobe reports "hev1" ?

Also i cant see any flashing boxes in your sample, while i can see those (if the file plays) in mine?

Also did you try play the sample and replicate my initial bug? I can get my z9x very reliably in a state where i just get black screens after i play this "crash" sample? I don't think this should happen at all?
It seems the sample somehow leaves the gpu/VS10 engine in a bad state?

 

Yes - you can make a backup and I would maybe suggest a backup every few weeks or so as HT develops because things can change in the database.

It's a SQLite database and when you make a backup it takes a copy of that database and relevant settings.

 

Yes - I can get my box to lock up with your file quite reliably too - Must admit I haven't had a look at a debug log to see what the player is doing though.

The flashing boxes is to do with tone mapping metadata - in yours MDL is 4000, in mine it's 1000 which actually shouldn't make a difference because it's just a statement of the capabilities of the mastering display monitor used in post, but some displays incorrectly use it to tone map - so it would seem that on your display, MDL is taken as MaxCLL so the tone mapping stops at 1000 - I bet you can just see the 900 nit box flashing?

 

VS10: yes up to 950 nits, my sample i can see up-to 3600 nits?
Auto: i can see up to 1800 nits on your sample

Playing with the native TV player, i get identically results for both samples and see flashing up to 1800 nits.

So whats going on now, why do we get so many different result combinations and why does VS10 on your sample clips so early?

 

How do you get that view? I can't seem to get that on mine.

 

Upper right hand corner of the cover view screen...select the smaller cover button until you get the smallest size (I think there is 3 or 4 size options). I like it cause you get that pop out window with the quick details of each movie without having to select it. But it does have that small bug that is ruining the feature.

 

Here is a picture to make it easier to explain.... The blue one is the smaller covers. Keep selecting till the covers look like that.

 

OK found it. Needed to have 'Slip the detail at overspread interface' checked in Preferences.

The display is fine for me as TMDb and TvMaze scraping brings back no more than two lines of genre descriptions. Your screen shot shows more than the pop out window can handle, Why have so many?

 

Yes it is... check in your HT4 settings for the option of the pop out option for the small covers...

 

Thank you for the hint. I totally forgot that.

BTW, do you have the same bug I showed earlier? I see that the pop-out also shows genre and some keywords so maybe an option to edit them out could help getting the flags to show properly.

 

It's got to be to do with Max MDL - which is Mastering Display Luminance - it's supposed to represent the maximum luminance capability of the PVM (Professional Video Monitor) used in mastering the file but to be honest it's often wrong. There are very very few monitors that can reach 4000nits - I only know of the Dolby Pulsar range and a few Sony ones, so most are 1000nits or less. I've seen files with MDL at 4000nits and I know for a fact they were mastered on Sony PVMs that can't get anywhere near that. I've also seen it reported as 10,000nits and there are just no displays anywhere that can do that!!

It sounds like the TV is tone mapping to MDL rather than MaxCLL which a lot of displays do. Most displays have "issues" with following the PQ curve correctly - probably the most accurate are LG and that's why they're the only consumer displays
Dolby recommend for final testing (not mastering though).

If you had an HDFury Vertex2 for example you could send a dummy HDR SEI with DML at 1000nits and prove what was happening.

In all honesty, in the real world, it really doesn't matter. Diffuse white was until recently defined at 100nits, but with better displays around, it's now defined at 200nits and anything above that is only specular highlight - if it wasn't, we'd all have to wear sunglasses watching telly!!

 

Ok i'm confused now!
So what should be the "correct" outcome on those files? If i follow the guide.pdf on those test files, than i should actually see most of the boxes if the TV tonemaps "correctly", since the Tv should tonemap down to its supported nits's range with the MAXCLL 4000 info.

Yet only the zidoo in VS10 mode and using your version, seem to get limited to 950 nits? The native TV app or zidoo in "auto" mode will get half the way to 1800 nits?
Isn't this a hint that only VS10 is doing something funny with the MDL and MAXCLL values and ofc that my TV's tonemapping is also not the "best"?