* Additional nice-to-have jobs from IVAS PC repo could be added to nightly schedule, e.g. `check-no-duplicates-in-self-test`, `check-bitexactness-hrtf-rom-and-file`, `check-first-frame-is-sid`, `check-bitexactness-ext-and-transport-format`.
* Sanitizer jobs already part of schedule in main.
* Make pipelines robust to changed target (main)
* The MR pipelines should run with a fixed target commit which is grabbed at the start of the pipeline. If a push to main happens during run, the post-validate job should end with warning but the pipeline should still complete.
* Ongoing here: !1929
* @kiene: Should be ok to warn if post-validate is outdated.
*\--\> Finalize outstanding comments and then merge. Will need to be merged in CI merge.
* Coordination of porting work
* Work on porting ongoing in parallel
# Technical issues
- Work stalled due to multiple regressions for merging main-pc to main. Reported regressions from merge to main:
* #1835 \[regression-merge\] Decoder: Loudness difference ivas-float-update vs. float-pc for MC BINAURAL_ROOM_IR + Headrotation output
* https://forge.3gpp.org/rep/sa4/audio/ivas-basop/-/issues/1834 \[regression-merge\] different levels for SBA to BINAURAL_ROOM_REVERB between ivas-float-update and float-pc
* https://forge.3gpp.org/rep/sa4/audio/ivas-basop/-/issues/1833 \[regression-merge\] SBA Decoder rendering to BINAURAL/BINAURAL_ROOM_IR - max. abs. diff regression BASOP vs. Float
* https://forge.3gpp.org/rep/sa4/audio/ivas-basop/-/issues/1832 \[regression-merge\] SBA decoder in float-pc and main-pc applies different bandwidth extension than ivas-float-update
* https://forge.3gpp.org/rep/sa4/audio/ivas-basop/-/issues/1831 \[regression-merge\] Decoder-Output for BINAURAL_ROOM_REVERB with rend_config_hospital_patientroom.cfg very different in BASOP vs. Float
* 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
- How to deal with down-mix exceeding of 16-bit range?
- #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)
- @vasilache: Are these issues still present?
- @multrus: Would be good to understand how big the current damage is, prioritizing this over e.g. porting work.
-\--\> Check how severe the issues are @vasilache.
- Cleanup of \_o vs \_sat operators, where Overflow is ignored.
-
- Clean up of switches
- 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
* IVAS PC conversion work status https://forge.3gpp.org/rep/sa4/audio/ivas-basop/-/wikis/IVAS-PC-MR-conversion-status
* Status
* Skipped MRs:
* No. 70 - \[NON-BE\]\[NON-IO\] Complete OMASA EXT output implementation (Nokia) --\> work in progress by Nokia, depends on main update
* new test vectors (config. files) are required in BASOP repo
* Sync this offline @szczerba , @kiene , @norvell
* !2176 should include this once main-pc supports the tested operation points
* Next steps:
* Complete update from main and ivas-float-update (done).
* Merge back to main and ivas-float-update.
*\--\> @kiene Will do CI merge, which is the only parts that needs merging. Will prepare MR and set up reviewer.
* Continue with list up to 130, but skip 117 since it depends on 70.
* Plan for vacation time porting work so that work does not halt for small changes
* @pihlajakuja: Freeze should already be in place. No more pushes to main-pc and float-pc until merge has happened.
*\--\> Delete main-pc and float-pc after merge. Set tag before deletion for reference. @kiene
*\[WANTED CHARACTERIZATION\]
* Currently 18 MRs listed. All relevant MRs tagged?
* Should we already prioritize these, or wait until a later time?
* Do we need most of the non-BE reverb-related MRs for the reverb characterization?
* 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 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"
* CI
* !1281 \[CI\] add ltv version of encoder dmx comparison
* Other
* !1941 MCT issue in debug mode
* !1933 possible fix for #1766, mld goes from 23.75 to 11.72 on the mono output [allow-regression]
* !1931 Resolve "Replace carry/overflow-using 32-bit operators by 64-bit version"
* !1927 Resolve "Usage of W_mac_32_32() + ONE_IN_Q30"
* !1895 Resolve #1808 "BASOP Asserts for BINAURAL_ROOM_REVERB output on main-pc"
* !1860 Resolve "replace L_shr_o by overflow-free alternatives"
* !1856 Resolve "Replace shl_o by overflow free alternatives"
