Skip to content

Memory (re)allocation called from application

As a follow-up to the presentation by Cadence (https://forge.3gpp.org/rep/ivas-codec-pc/ivas-codec/-/wikis/Meetings/Reports/2023-09-21%20Meeting%20Report), I am starting a branch that would help in further discussions about following the recommendations.

As a first step, there is a move of memory (re)allocation from the encoder library to the application. For the moment, it concerns a code restructuralization which I believe is better to be done sooner than later. Then, the next step is to think about

  • using custom malloc()/free() functions
  • list/store memory requirements
  • (re)initilize memory in IVAS_ENC_Initialize() and IVAS_ENC_Reconfigure() using a master malloc()/free()

When comes to the decoder, the (re)initialization is already done at one place - function IVAS_DEC_Setup(). I expect that this function would just need to be called from the application, i.e. to be moved one level up (tagging @bayers for awareness).