Skip to content

[script.audiooffsetmanager.evolved@nexus] 1.3.0 - #2873

Merged
romanvm merged 1 commit into
xbmc:nexusfrom
matthane:script.audiooffsetmanager.evolved@nexus
Aug 12, 2026
Merged

romanvm merged 1 commit into
xbmc:nexusfrom
matthane:script.audiooffsetmanager.evolved@nexus

Conversation

@matthane

@matthane matthane commented Aug 6, 2026

Copy link
Copy Markdown

Add-on details:

Adjust Kodi's audio offset during playback the way you always have. Audio Offset Manager: Evolved remembers the value for that stream's HDR type and audio format, with optional finer splits by frame rate, spatial audio format, channel count, and audio output device, then re-applies it automatically on every matching playback. Includes seek-back after adjustments, playback notifications, and a management view of everything it has learned.

Description of changes:

v1.3.0 (2026-08-06)

  • Stored offsets are backed up automatically and restored if the file is ever damaged
  • The offset saved notification shows the value it replaced
  • Stored offsets can be copied to the current audio output from Manage stored offsets
  • Settings help text now says where an option depends on what your Kodi build reports
  • Fixed: an adjustment made just as the stream changed could be saved to the wrong profile
  • Fixed: a codec switch could briefly follow the wrong output device when PCM and passthrough use different ones
  • Fixed: re-teaching a value deleted moments earlier did not trigger the seek-back replay

v1.2.0 (2026-08-03)

  • Distinct output device offsets: optional toggle that keys offsets by Kodi's configured audio output device, so a soundbar and a pair of headphones can each keep their own value. Off by default
  • An output device change during playback is picked up within a second and the matching offset is applied
  • The management view groups by output device, then HDR type, and skips a level when it holds only one entry
  • Device offsets belong to the machine that learned them and do not transfer to another one; every other offset still does
  • Stored offsets upgrade to a new file format on first save. Version 1.1.0 and earlier can still read the file but will not add to it

Checklist:

  • My code follows the add-on rules and piracy stance of this project.
  • I have read the CONTRIBUTING document
  • Each add-on submission should be a single commit with using the following style: [plugin.video.foo] v1.0.0

@kodiai

kodiai Bot commented Aug 6, 2026

Copy link
Copy Markdown

Kodiai Add-on Review

Summary

Reviewed 1 changed addon on nexus across 30 scoped patches in 44 evidence chunks. Found 2 model-backed contextual rule findings.

Findings

  • WARN script.audiooffsetmanager.evolved/resources/lib/aome/script_router.py:234: Comment indicates export destinations outside Kodi home directory. Verify implementation requires explicit user file selection via dialog or picker per Kodi access-control rules.
  • WARN script.audiooffsetmanager.evolved/resources/lib/aome/view/logexport.py:17: Documentation describes reading Kodi log lines with timestamp and traceback bodies; verify explicit user consent is obtained before runtime access to system debug log files outside addon profile.

Verdict

Needs human review: 0 errors and 2 warnings found. Final approval remains with a human reviewer.

@matthane

matthane commented Aug 6, 2026 •

Copy link
Copy Markdown
Author

Hi Roman + team, both warnings point at the "Export addon log" feature, which these same checks flagged on the 1.1.0 submission (#2864) and which was explained there. The feature is unchanged since then: a documentation pass rewrote its docstrings, which is what the review picked up here, and the export code itself is identical.

@romanvm romanvm added the Approved Approved and is ready to merge label Aug 9, 2026
@romanvm
romanvm merged commit 61c4fce into xbmc:nexus Aug 12, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Approved Approved and is ready to merge

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants