JVET-V0079 Reference software cleaning proposal [F. Galpin, T. Poirier, P. De Lagrange, F. Le Léannec, E. François (InterDigital)]

This contribution proposes a set of cleanup changes on top of the VTM reference software. The main motivation for this cleaning is to ease the development and testing of new tools inside the reference software. As the proposed cleaning involves significant files refactoring, it is not compatible with a series of merge requests (might also require a new management approach for the repository). A first version of cleaned software is also proposed as a basis for discussions and further improvements.

The HLS was not cleaned up yet.

The current version does not have speedup compared to the VTM.

Currently VTM 11 – one major change is the update of GDR in VTM12 – would that be a difficulty? Proponents believe it is not.

It is pointed out by software coordinators that various other issues would be desirable to be cleaned. It might be difficult however to get exactly same results of VTM encoder then.

Switching to another package may also be causing new bugs.

The motivation for the new software (as per proponents) is about better support for explorations. Even though, having a compatibility with VTM / conformance with VVC is highly desirable.

Would a speedup be more important for explorations?

Question: If the software is more flexible, should it not be simple to get same results as VTM encoder?

Could the current EE2 software easily be ported? This would give an evidence of advantages of the software package.

Experts are asked to study the software for possible advantages of being used in EEs. By the next meeting, it should be decided if a switch of the software has an advantage for progress in the EEs. It is also pointed out that in the past a good point of switching software is by the time when a new standardization is started.

Implementation studies (5)

Contributions in this area were discussed in session X at 1655–1800 UTC on Monday 26 April 2021 (chaired by JRO).