Opened 3 years ago

Closed 3 years ago

#1500 closed defect (invalid)

problem with croma components for format 4:2:2 packed

Reported by: iulia Owned by:
Priority: major Milestone:
Component: VTM Version: VTM-13.0
Keywords: Cc: ksuehring, XiangLi, fbossen, jvet@…

Description

Hello,

I got a purple shade and strange artefacts on the encoded sequences at high QP, between 45 to 51 with a step of 1. The input sequence is YUV 4:2:2 8 bit packed format. I think that is a problem with Croma components for this format. Could you check if the results are reproducible on a similar standard sequence or to tell if it is an aspected result?

Regards,
Iulia

Attachments (3)

Capture.PNG (167.6 KB) - added by iulia 3 years ago.
visual example of the results
intra_log_visible_QP51.log (1.8 KB) - added by iulia 3 years ago.
encoder output log file
encoder_intra_vtm_modified.cfg (6.4 KB) - added by iulia 3 years ago.
encoder configuration file

Download all attachments as: .zip

Change history (8)

Changed 3 years ago by iulia

visual example of the results

comment:1 Changed 3 years ago by XiangLi

Hi Iulia,

Could you provide exact command line settings so that we could reproduce your encoding result? Please also attach you encoding log. Thanks.

Changed 3 years ago by iulia

encoder output log file

Changed 3 years ago by iulia

encoder configuration file

comment:2 Changed 3 years ago by iulia

Hello,

Thank you for your response.
I have attached the encoder configuration file and the encoder log file.
The command line used is: ./bin/EncoderAppStaticd -c encoder_intra_vtm_modified.cfg >intra_log_visible_QP51.log

Regards,
Iulia

comment:3 Changed 3 years ago by XiangLi

Could you also upload AAT_20120113_extrait_vue_visible.yuv? One-frame yuv would be enough as you only coded one frame.

comment:4 Changed 3 years ago by iulia

Hello,

Here it is a google drive link to the requested sequence. Please, don't share it further. It is a YUV 4:2:2 packed format (UYVY) of resolution 1920x1080:

https://drive.google.com/file/d/1O8GKkT7USOx49C_3FGNzzzI8aaJ4zQJK/view?usp=sharing

The research is about the coding of cockpit video screen content and we are trying to do a preliminary study about how VVC is behaving on our content.

Regards,
Iulia

comment:5 Changed 3 years ago by ksuehring

  • Resolution set to invalid
  • Status changed from new to closed

This issue was confirmed to be an issue with the input image format (VTM expects planar format) in email discussion.

Note: See TracTickets for help on using tickets.