* https://forge.3gpp.org/rep/sa4/audio/ivas-basop/-/issues/1828 \[regression-merge\] LTV MASA 2TC 16 kHz in 48 kHz out at 64 kbps has a spike in main-pc
* @multrus this doesn't seem to be a blocker
* decide in tomorrow's meeting whether we proceed with merge
- How to deal with down-mix exceeding of 16-bit range?
- How to deal with down-mix exceeding of 16-bit range? --\> did not discuss
- #1793, #1520, #1773 (last three on McMASA).
- @multrus: How severe is #1793?
- @pihlajakuja: Need to check. Showing up in objective scores, but unsure if it is serious. Probably not (medium, minor prio)
...
...
@@ -84,12 +84,12 @@
* @tyagiri can help with the review. I need to understand better
* @svedberg is this for the EVS code too?
* @multrus yes. In a lot of places overflow bit is set but not handled
- Clean up of switches
- Clean up of switches --\> skipped
- Set of switches to accept was agreed in https://forge.3gpp.org/rep/sa4/audio/ivas-basop/-/wikis/Meetings/Reports/2025-07-16%20IVAS%20BASOP%20report.
- Accept after merge of main-pc into main.
*\--\> @kiene to handle after merge.
# Float porting backlog
# Float porting backlog -\> did not discuss
* IVAS PC conversion work status https://forge.3gpp.org/rep/sa4/audio/ivas-basop/-/wikis/IVAS-PC-MR-conversion-status
* Status
...
...
@@ -114,7 +114,7 @@
* Do we want to have the HRTF sets in ROM in their final state? Changes are mostly inaudible but some are also non-BE.
* @all: Review table.
# Merge requests (other than float porting above)
# Merge requests (other than float porting above) --\> did not discuss
* Merge regressions
* !1946 \[non-BE\] Resolve "\[regression-merge\] Decoder-Output for BINAURAL_ROOM_REVERB with rend_config_hospital_patientroom.cfg very different in BASOP vs. Float"
