ZIDOO Z9X

Discussion in 'HDD Media player(RTD 1619DR)' started by DELUCAS, Aug 4, 2020.

  1. Markswift2003

    Markswift2003 Well-Known Member Beta test group Contributor

    HDMI only supports 50i & 60i (interlaced) in Standard Definition (720x480 & 720x576) so anything else will be upscaled to current GUI resolution.
     
    cappy1 likes this.
  2. pilgrim

    pilgrim New Member

    Будет ли работать голосовой поиск в YouTube и других приложениях с g20s или другим пультом дистанционного управления с микрофоном?
     
  3. mutt

    mutt New Member

    I mentioned here in the past some problem with TV picture. I have an older one TV panasonic (plasma) so i only use FullHD. It doesn't happen often, but somethimes. And I can see this problem when I'm in the device menu as well. I don't know the correct english word for this, but it is some purple granulation, as you can see in the picture:

    TV3.jpg

    At first i thought it was a wrong color setting, but yesterday I found out, that this is related to the refresh rate. If I set "auto", then it is 1080P/60hz and then I have this picture problem. But if I set manualy 1080P/50hz or 1080P/24hz, than the picture is OK:

    TV4.jpg
     
  4. Markswift2003

    Markswift2003 Well-Known Member Beta test group Contributor

    I'd have to assume your TV doesn't like 1080p60 - I just tried a 1080p60 EDID and the output was ok in all modes.

    What have you got set in Settings/Display/Colour Settings/Non-4K ?
     
  5. cappy1

    cappy1 Member

    Thanks, Mark!
     
    Markswift2003 likes this.
  6. Whitfield

    Whitfield Member

    Next to what @Markswift2003 already explained, if the source video woud be native ntsc @ 29.97fps interlaced, my guess is that the player would output @59.94fps and not 23.976.

    In case of movie-dvd's, these being played @ 23.976fps is not uncommon. And very much preferred over 29.97fps.

    As most movies are shot @ 24fps on film, on dvd's they are often stored as (slightly slowed-down) 23.976 progressive (so, the full frames). Normally, a dvd-player will run these frames through a process (called telecine) into ntsc's 29.97fps interlaced.

    However, a so-called "progressive scan" compatible dvd-player recognizes this kind of content en can output these 23.976 full frames per second. Of course, the receiving display must also be 23.976fps compatible.

    I think this is what the Zidoo player does and it therefore states "23Hz" (which should be read as 23.976Hz)
     
    cappy1 likes this.
  7. cappy1

    cappy1 Member

    Thanks. I just looked at a typical movie DVD (At First Sight) with MediaInfo and it reports this movie file as “720x480 (16/9) at 23.976 FPS”. However, while playing this movie, Z9X INFO shows the input as 720x480 @ 29.970 fps, due to telecining you mentioned.
     
  8. Markswift2003

    Markswift2003 Well-Known Member Beta test group Contributor

    Does MediaInfo show both "Frame Rate" and "Original Frame Rate"?
     
  9. cappy1

    cappy1 Member

    MediaInfo just reports the original frame rate, even if checked while movie is playing. (It just looks at the source file).
     
  10. Markswift2003

    Markswift2003 Well-Known Member Beta test group Contributor

    When MediaInfo (PC version) reports "Frame Rate" it does it by calculation from time codes from the first few frames and then checks if it's within a certain percentage of a standard frame rate, if it is then it reports that standard frame rate.

    Original Frame Rate, if used, is written into the stream header. Sometimes the two are different because the movie has been telecined for TV presentation - I think that's what you're seeing here - it's been telecined for NTSC presentation, so the actual frame rate is 29.97fps.
     
    Cyclion likes this.
  11. cappy1

    cappy1 Member

    Here is MediaInfo screen shot on my Mac that I see whether or not file is playing.
     

    Attached Files:

    Last edited: Oct 26, 2020
  12. Markswift2003

    Markswift2003 Well-Known Member Beta test group Contributor

    Ah - I was referring to MediaInfo from:

    https://mediaarea.net/en/MediaInfo

    So I assume your Mac is reading the header rather than the file itself.
     
    cappy1 likes this.
  13. cappy1

    cappy1 Member

    This is what I have, but never played around with settings. I downloaded it years ago and never had a need to use it until today. I see now that View was in the “Easy” setting, apparently the default. The “Tree” setting now shows all the data. Thanks, Mark.
     
    Markswift2003 likes this.
  14. Markswift2003

    Markswift2003 Well-Known Member Beta test group Contributor

    Any time.
     
  15. mutt

    mutt New Member

    There is set YUV444 8BIT.

    Edit: now I have changed HDMI settings. Before I had "auto", if I set 16-235 there is the same problem, but if I set 0-255 it is OK no matter if I have 60Hz, 50Hz or 24Hz...
    I know you prefer 16-235 in recommended settings, so is it OK if I set 0-255? In fact, I have no idea what this setting is good for...

    Edit2: so no, 0-255 is not a good solution, i tried watch a movie and the dark scenes are too dark... this might explain why there is no granulation problem in this setting, because the granulation I can see usually in light colors or white color - and if everything is darker then there is no granulation...
     
    Last edited: Oct 26, 2020
  16. Markswift2003

    Markswift2003 Well-Known Member Beta test group Contributor

    So I think you found out - 16-235 isn't a preference, it's the way content is encoded. 0-255 is generally for RGB computer displays for example.

    When stuff is encoded at 16-235 (DVD, BluRay, UHD BluRay etc etc), it means black is at 16 and white at 235 which has to match the display settings otherwise you crush black as you've seen.

    I assume from your post that most material you watch is 1080p @ 23.976fps? So in that case I'd set resolution to 1080p23 and as long as auto frame rate and resolution is on, if any content is different from that it will change automatically.

    When you set "Auto" in <HDMI Mode> that just sets the maximum allowed by the TV's EDID which is not always ideal.
     
  17. Joao Franco

    Joao Franco New Member

    In my case i set to auto because in 16-235 the colours are involved in something like a fog.
    Washed and the blacks are not so black.
    Maybe some grey.
    If i set to Auto everything are great.
     
    Osmar likes this.
  18. Markswift2003

    Markswift2003 Well-Known Member Beta test group Contributor

    It's possible you TV doesn't have a selectable quantization range in the EDID - but hey, whatever works :)
     
    Joao Franco likes this.
  19. Joao Franco

    Joao Franco New Member

    My tv is the Panasonic Oled 55FZ800 but i don´t understand nothing about selectable quantization range in the EDID :)
    But to my eyes the image it´s better in auto :)
     
  20. Markswift2003

    Markswift2003 Well-Known Member Beta test group Contributor

    Have to honest, that's all that matters - quantization range defines whether or not the range (0-255, 16-235) can be switched - I have a Samsung that allows switching in RGB but does not allow it in YCbCr.

    Don't worry about it and just use Auto.
     

Share This Page