Due to JCT3V-C0137 adoption, which changes implicit motion inheritance to explit merge mode, the derivation process anyIvRefPicFlag for depth was obsolete. Specifically, the result of depth's anyIvRefPicFlag derivation is equal to the result of texture's anyIvRefPicFlag derivation.

I talked this part with the original IC proponent and they confirmed this part is obsolete and agreed that this part's removal.

While basically this change is editorial change, HTM also needs to be fixed.

At new HTM-6.2-dev integration phase, my simulation sometimes failed. I thought this was due to memory usage increase of the integrated version and checked memory usage before and after integration (HTM-6.2 and HTM-6.2-dev). Then i found the following strange behaviour (potential bug) in HTM encoder.

The memory usage of 720p was constant (2.4 G bytes in my environment) while that of 1080p varies from 2.8G bytes to 3.9Gbytes. The memory usage varies by runs!

This strange behavior occcued at leaset in HTM-6.0, HTM-6.2 and HTM-6.2-dev branch2. Please see the attached file.

Attached is my memory usage reports, which is got by qacct -j $job | grep maxvmem

I suppose this "randomly" different memory usage occured "only in 1080p" suggests potential bugs in HTM.

Setting cfg file to encode two views and two depth maps, encoder stops running after encoding the first frame. Error message: Assertion failed: 0, file ..\..\source\App\TAppEncoder\TAppEncTop.cpp, line 1506