Vero 4K General Discussion

Still seeing 8-bit output for 10-bit content with the April '17 update

@swrobel Indeed – that’s why we haven’t marked it as fixed in this update.

The good news is I can see the issue (it’s how some TVs advertise their capabilities) and will have an update for you soon. I’ll let you know when it’s ready for testing if you don’t mind being a (slight) guineau pig.

Sam

1 Like

Ready and waiting! :hamster:

This might be a silly question but if a 4K file has DTS-HD 7.1 but I only have a 5.1 system will the Vero 4K downmix to 5.1 only? I don’t want to be missing channels.

If you use passthrough, your receiver needs to do that as downmixing requires decoding.

@Sam:

does the “8-Bit-Bug” of 10Bit-Content exist on all HDR-Devices?

Thanks + BR
Peter

No – it appears to only affect a subset of devices.

Ok, thanks for reply;-)

Hi sam,

Thanks for the good work. I just received my vero 4k and tried to playback the “Rogue One” (4K.HDR.10bit.BT2020.Chroma.422.Edition.DTS.HD) on it with my old Samsung 1080p TV. Unfortunatly it did not start to play, it keeps restarting the buffer spinner.

The journalctl -f has those lines:

May 04 00:40:09 vero1 kernel: codec:video_blackout_policy_store(0) May 04 00:40:09 vero1 kernel: [tsync_avevent]event:1, param 1 May 04 00:40:09 vero1 kernel: video pause! May 04 00:40:09 vero1 kernel: tv_vout: vout [tv_set_vframe_rate_end_hint] return mode = 20, policy = 1! May 04 00:40:09 vero1 kernel: tv_vout: vout [framerate_automation_set_mode] mode_target = 20 May 04 00:40:09 vero1 kernel: fb: current vmode=1080p24hz May 04 00:40:09 vero1 kernel: DI: di_receiver_event_fun , is_bypass() 0 trick_mode 0 bypass_all 0 May 04 00:40:09 vero1 kernel: DI: di_receiver_event_fun: vf_notify_receiver unreg May 04 00:40:09 vero1 kernel: codec:keep exit is di May 04 00:40:09 vero1 kernel: [tsync_avevent]event:2, param 0 May 04 00:40:09 vero1 kernel: codec:video first pts = 0 May 04 00:40:09 vero1 kernel: di_uninit_buf keep cur di_buf 6 (0 1 -1) May 04 00:40:09 vero1 mediacenter[25316]: [codec_close_cntl]video codec close return=0! May 04 00:40:09 vero1 kernel: codec:uninit_buf_list, blackout 0 r0 buf_mode 1 r1 rel_cma_flag 0 hevc->predisp_addr 1924792320 pre_alloc_addr(0, 0) May 04 00:40:09 vero1 kernel: codec:uninit list May 04 00:40:09 vero1 mediacenter[25316]: [codec_init 733]type =1 May 04 00:40:09 vero1 kernel: codec:hevc video changed to 0 x 0 0 fps clk->200MHZ May 04 00:40:09 vero1 kernel: codec:HEVC stbuf alloced at 0000000067c00000, size = 15728640 May 04 00:40:09 vero1 kernel: codec:free_alloced_keep_buffer (null). (null). (null) May 04 00:40:09 vero1 kernel: codec:h265:pts_unstable=0 May 04 00:40:09 vero1 kernel: codec:h265: ver (201602101,0) decinfo: 3840x1608 rate=4004 May 04 00:40:09 vero1 kernel: DI: di_receiver_event_fun: vframe provider reg May 04 00:40:09 vero1 kernel: tv_vout: vout [tv_set_vframe_rate_hint] duration = 4004, policy = 1! May 04 00:40:09 vero1 kernel: tv_vout: vout [framerate_automation_process] duration = 4004 May 04 00:40:09 vero1 kernel: tv_vout: framerate_automation_process[1111] fps_playing_flag = 1 May 04 00:40:09 vero1 kernel: tv_vout: fr_vsource = 2397 May 04 00:40:09 vero1 kernel: tv_vout: mode_target=20,is_receiver_supported=1 May 04 00:40:09 vero1 kernel: tv_vout: vout [framerate_automation_set_mode] mode_target = 20 May 04 00:40:09 vero1 kernel: fb: current vmode=1080p24hz May 04 00:40:09 vero1 mediacenter[25316]: [codec_init 741] May 04 00:40:09 vero1 mediacenter[25316]: [codec_reset:1203]ret=0 May 04 00:40:09 vero1 kernel: codec:hevc video changed to 4096 x 2048 30 fps clk->667MHZ May 04 00:40:09 vero1 kernel: codec:video first pts = 0 May 04 00:40:09 vero1 kernel: codec:video_blackout_policy_store(1) May 04 00:40:09 vero1 kernel: codec:video first checkin pts = 161bce May 04 00:40:09 vero1 kernel: codec:first check in vpts <0x58:0x161bce> ok! May 04 00:40:09 vero1 kernel: codec:Bit depth luma = 10 May 04 00:40:09 vero1 kernel: codec:Bit depth chroma = 10 May 04 00:40:09 vero1 kernel: codec:set pic_list_init_flag 1 May 04 00:40:09 vero1 kernel: codec:allocate begin May 04 00:40:09 vero1 kernel: codec:reuse cma buffer[0] (3088,1998192640,1998192640) May 04 00:40:09 vero1 kernel: codec:reuse cma buffer[1] (3088,2010906624,2010906624) May 04 00:40:09 vero1 kernel: codec:reuse cma buffer[2] (3088,1756364800,1756364800) May 04 00:40:09 vero1 kernel: codec:reuse cma buffer[3] (3088,1769013248,1769013248) May 04 00:40:09 vero1 kernel: codec:reuse cma buffer[4] (3088,1781661696,1781661696) May 04 00:40:09 vero1 kernel: codec:reuse cma buffer[5] (3088,1794310144,1794310144) May 04 00:40:09 vero1 kernel: codec:reuse cma buffer[6] (3088,1806958592,1806958592) May 04 00:40:09 vero1 kernel: codec:reuse cma buffer[7] (3088,1819607040,1819607040) May 04 00:40:09 vero1 kernel: codec:reuse cma buffer[8] (3088,1832255488,1832255488) May 04 00:40:09 vero1 kernel: codec:reuse cma buffer[9] (3088,1844903936,1844903936) May 04 00:40:09 vero1 kernel: codec:reuse cma buffer[10] (3088,1857552384,1857552384) May 04 00:40:09 vero1 kernel: codec:reuse cma buffer[11] (3088,1870200832,1870200832) May 04 00:40:09 vero1 kernel: codec:reuse cma buffer[12] (3088,1882849280,1882849280) May 04 00:40:09 vero1 kernel: codec:reuse cma buffer[13] (3088,1895497728,1895497728) May 04 00:40:09 vero1 kernel: codec:reuse cma buffer[14] (3088,1908146176,1908146176) May 04 00:40:09 vero1 kernel: codec:reuse cma buffer[15] (3088,1920794624,1920794624) May 04 00:40:09 vero1 kernel: codec:not enought buffer for [16],12648448 May 04 00:40:09 vero1 kernel: codec:allocate end May 04 00:40:09 vero1 kernel: codec:init_decode_head_hw: (3840, 1616) body_size 0xbf4000 header_size 0x6180 May 04 00:40:09 vero1 kernel: codec:init_buf_spec2 3840 1616 May 04 00:40:09 vero1 kernel: codec:set pic_list_init_flag to 2 May 04 00:40:09 vero1 kernel: codec:set pic_list_init_flag to 3 May 04 00:40:09 vero1 kernel: codec:cur lcu idx = 72, (total 6120), set error_mark May 04 00:40:09 vero1 kernel: codec:cur lcu idx = 72, (total 6120), set error_mark May 04 00:40:09 vero1 kernel: codec:cur lcu idx = 72, (total 6120), set error_mark

Should it be possible to playback a 4K HDR movie on a 1080p non-HDR TV?
My rawedid of the tv is the following:
$ cat /sys/class/amhdmitx/amhdmitx0/rawedid 00ffffffffffff004c2d09050100000030120103801009780aee91a3544c99260f5054bdef80714f8100814081809500950fb3000101023a801871382d40582c4500a05a0000001e662150b051001b3040703600a05a0000001e000000fd00184b1a5117000a202020202020000000fc0053414d53554e470a2020202020016f020327f14b901f0413051403122021222309070783010000e2000fe305030167030c001000b82d011d007251d01e206e285500a05a0000001e011d00bc52d01e20b8285540a05a0000001e011d8018711c1620582c2500a05a0000009e011d80d0721c1620102c2580a05a0000009e000000000000000000000000000000001d

Hi

Kodi logs might help here.
Are other videos playing as expected?
Do you have a 4K TV to try this on?

Sam

Hi!

Kodi.log is as follows (video is started via File-Explorer mkv over NFS share via wired ethernet)

01:35:55.559 T:4111025072 NOTICE: VideoPlayer: Opening: nfs://10.0.1.41/nas/videos/Movies/Rogue.One.A.Star.Wars.Story.4K.HDR.10bit.BT2020.Chroma.422.Edition.DTS.HD.MA-VISIONPLUSHDR1000/Rogue.One.A.Star.Wars.Story.4K.HDR.10bit.BT2020.Chroma.422.Edition.DTS.HD.MA-VISIONPLUSHDR1000.mp4 01:35:55.560 T:4111025072 WARNING: CDVDMessageQueue(player)::Put MSGQ_NOT_INITIALIZED 01:35:55.560 T:3230659568 NOTICE: Creating InputStream 01:35:55.581 T:3230659568 NOTICE: Creating Demuxer 01:35:56.694 T:3230659568 NOTICE: Opening stream: 0 source: 256 01:35:56.694 T:3230659568 NOTICE: Creating video codec with codec id: 174 01:35:56.712 T:3230659568 ERROR: Unable to load libamplayer.so, reason: libamplayer.so: cannot open shared object file: No such file or directory 01:35:56.712 T:3230659568 WARNING: CAMLCodec::CAMLCodec libamplayer.so not found, trying libamcodec.so instead 01:35:56.716 T:3230659568 NOTICE: Creating video thread 01:35:56.716 T:3173237744 NOTICE: running thread: video_thread 01:35:56.716 T:3230659568 NOTICE: Opening stream: 1 source: 256 01:35:56.716 T:3230659568 NOTICE: Finding audio codec for: 86020 01:35:56.716 T:3230659568 NOTICE: Creating audio thread 01:35:56.717 T:3213882352 NOTICE: running thread: CVideoPlayerAudio::Process() 01:35:56.717 T:3230659568 NOTICE: Opening stream: 4 source: 256 01:35:56.727 T:3213882352 NOTICE: Creating audio stream (codec id: 86020, channels: 6, sample rate: 48000, pass-through) 01:35:56.867 T:3173237744 NOTICE: CAMLCodec::OpenDecoder - using V4L2 pts format: 64Bit 01:36:00.227 T:3230659568 WARNING: VideoPlayer::Sync - stream player video does not start, flushing buffers 01:36:28.398 T:4111025072 WARNING: Previous line repeats 5 times. 01:36:28.398 T:4111025072 NOTICE: Display resolution ADJUST : 1920x1080 @ 24.00 - Full Screen (23) (weight: 0.001) 01:36:31.949 T:3230659568 WARNING: VideoPlayer::Sync - stream player video does not start, flushing buffer

Unfortunatly i do not have any 4K TV here at the moment.

I downloaded other videos at http://demo-uhd3d.com/categorie.php?tag=hdr (eg NASA & world in hdr/4k) and they played as expected.

Please upload a debug log (see the Wiki)

Sam

Hi Sam,

Here you are: http://paste.osmc.io/humojileyi

Thanks in advance!

00:07:09.662 T:3369198576 WARNING: VideoPlayer::Sync - stream player video does not start, flushing buffers

00:07:09.662 T:3369198576   DEBUG: CVideoPlayer::FlushBuffers - flushing buffers

Check that rip. If everything else plays as expected, I’d be inclined to blame the clip.

Sam

I just checked another one “The Martian” which worked ok with the following specs:

Codec: HEVC
Profile: Main 10
Level: 150
Resolution: 3840x1600
Aspect ratio: 2.40:1
Anamorphic: No
Interlaced: No
Framerate: 23.97602
Bitrate: 49176 kbps
Pixel format: yuv420p10le
Ref frames: 1

The previous file (which did not work) had this specs:

Codec: HEVC
Profile: Rext
Level: 150
Resolution: 3840x1608
Aspect ratio: 2.40:1
Anamorphic: No
Interlaced: No
Framerate: 23.97602
Bitrate: 46234 kbps
Pixel format: yuv422p10le
Ref frames: 1

Maybe it is because of the Pixel Format (4:2:2 vs 4:2:0) or the profile (Rext vs Main 10).
Any other file that I tried from http://demo-uhd3d.com/categorie.php?tag=hevc had also HVEC Profile Main 10 and yuv420p10le.

Cheers

16 posts were split to a new topic: Vero4k only decodes 8bit with 10bit 4K HEVC material

Hello, so I have a vizio p75 TV, with yamaha reciever that only does 4k passthrough but not HDR.
In this set up, and with this player, what do I need to make sure in my chain to have proper display of HDR content?
Right now I have couple of popcorns and a neo u1, which does 4k but not HDR…
please advise

HDMI 2.0a is needed for HDR. I suspect your AV receiver is HDMI 2.0 compliant but not HDMI 2.0a.

The device Vero 4K is directly connected to, be it an AV receiver or a display needs to support HDMI 2.0a for HDR to work correctly

I hope this clears things up

Thanks Sam, and I am assuming this vero will not be able to connect to the TV for video and reciever for audio?