Skip to content

v0.3.1.1 - fixed offsets for Resolve 21.1.2 only (no code reading)

Choose a tag to compare

@JaySNL JaySNL released this 03 Nov 14:15

Warning

For DaVinci Resolve 21.1.2 only. On any other Resolve this build reads and writes at the wrong offsets. Resolve 21.1.0 and earlier: use v0.3.0.1. Anything newer than 21.1.2: use v0.3.1 or later, never this.

v0.3.1 with its member offsets as fixed numbers for 21.1.2, and without the code that reads them out of Resolve. For anyone who would rather not run v0.3.1 while its antivirus detection stands. v0.3.1 remains the main release.

Why this exists

Microsoft Defender's machine-learning engine flags v0.3.1's libfxbridge.so as Trojan:Script/Wacatac.C!ml. No other engine on VirusTotal does, and v0.3.0.1 was never flagged. It is a false positive, reported to Microsoft, and checked here:

  • the v0.3.1 binary rebuilds bit-identically from its tag, so it is exactly the published source
  • compared with v0.3.0.1 it adds exactly one source file, src/member_layout.cpp: one new import (dladdr1), four new functions and 56 new strings, all from that file. Of the 704 functions both builds share, only the 7 that use the new offsets changed
  • the build toolchain's Ubuntu packages pass dpkg --verify
  • no network code, no running other programs, no access to other processes

What v0.3.1 added is the likely trigger: it looks up five functions in Resolve's own libBMDAudioPlugins.so and scans their machine code for instruction patterns, to find where Resolve keeps each field. That is what lets it survive Resolve updates. It is also what cheat loaders and malware do to find code, and the model cannot tell the two apart.

What changed against v0.3.1

src/member_layout.cpp returns the nine offsets measured on 21.1.2.0010 as constants:

Member 21.1.2
input / output channel counts 0x158 / 0x160
bypass flag 0x171
dirty flag / AudioPlugin parent 0xa1 / 0x40
name record 0x558
resource tree 0x368
panel width / height 0x3b0 / 0x3b4

There is no symbol lookup, no dladdr1, no reading of Resolve's code and no instruction-pattern strings in this binary. Everything else is v0.3.1, unchanged.

The cost

It is right for exactly one Resolve. Every one of these offsets moved by eight bytes between 21.1.0 and 21.1.2, and this build cannot tell which Resolve it is in, because that is the part that was taken out. When Resolve updates past 21.1.2, move to v0.3.1 or a later release.

The bridge log (~/.local/share/DaVinciResolve/logs/ResolveDebug.txt) shows which build is running:

[fxbridge] layout: FIXED for Resolve 21.1.2 (v0.3.1.1) - channels +0x158/+0x160, bypass +0x171, ...

Verified

Live in Resolve 21.1.2.0010: offsets logged as FIXED, lock fix patched, 122 plugins listed, instances claimed and named, channel counts, panel, preset load, editor and project save. Built in the Ubuntu 20.04 sandbox (GLIBC floor 2.16).

Install

These download links are not under latest, so fetch them from this release: close Resolve, put libfxbridge.so, libfxbridge-gate.so, fxbridge-scan and resolve-with-fxbridge into ~/.local/share/BMDAudioPlugins/ (check with sha256sum -c SHA256SUMS), and keep starting Resolve through resolve-with-fxbridge. config-fairlight.dat needs no change.