JVET-Q0044: slice index with subpictures

Aligned syntax and semantics of slice_subpic_id and slice_address with VVC draft8 Included constraint on coding order of slice NAL units

added 1 commit

• 47ff0117 - JVET-Q0044: slice index with subpictures

Compare with previous version

resolved all threads

merged

mentioned in commit 179edc64

Hi Virginie,

I notice that this merge request causes the following encoding command not working, ../bin/EncoderAppStatic -c ../cfg/encoder_randomaccess_vtm.cfg -c ../cfg/per-sequence/BasketballDrill.cfg -b str_RA_S03_BasketballDrill_q0_42_4Slice2SubPic.bin -q 42 -f 1 -i ~/HEVC/ClassC/BasketballDrill_832x480_50.yuv --SEIDecodedPictureHash=1 -c ../cfg/nonCTC-SliceConfigExamples/subpicture_4Slice2VerSubPic.cfg

the encoder report the following error: ERROR: In function "write" in /home/biaowang/git/SubPicVer/vvcsoftware_vtm/source/Lib/CommonLib/BitStream.cpp:113: Unsupported parameters

while one commit before, the same encoding works fine, could you please fix the error? Thanks.

Bests, Biao

Hi Biao,

Please use the attached configuration file instead, which is a slightly different way to signal the same partitioning. This configuration file solves the issue.

Best Regards, Virginie

subpicture_4Slice2VerSubPic.cfg

Hi Virginie,

Thanks a lot for your prompt reply. I would like to know why the configuration file needs to be updated. Ideally, both configuration files shall work.

Bests, Biao

Hi Biao,

This is actually a design issue, whereby the current specification fails when the slices are signalled in a different order than their coding order. I plan to provide a contribution to the next meeting to address this issue, but in the meantime, I suggest that you use only configuration files that signal the slices in the same order in which they are coded.

Best Regards, Virginie

Do we need to fix any of the example files?

I would say that is your decision as software coordinator. If you decide to fix a file, then it is only the file mentioned above that has the issue (subpicture_4Slice2VerSubPic.cfg). However, the group may decide that it is better to have existing files working as well. My personal opinion is that this is rather a topic to be discussed during a meeting, and then to be fixed according to the decision.

Since I use these files for verification of functionality, I would prefer to replace the file with the version that works. It's also likely to be confusing for people who are unaware of the issue, if an example file would not work.

We definitely should discuss it at the meeting. Depending on the outcome we should then either have a fix for the design issue or a check that gives a proper error in case of a disallowed configuration.

mentioned in merge request !1441 (merged)

mentioned in merge request !1451 (merged)