OffsetX returns write-memory error only when not read before attempted write

[sjeapes-meta]

Description

When attempting to write to OffsetX (having already reduced Height and Width below sensor max) arv-tool (and libaravis) return a write-memory-error
This only happens for OffsetX (not OffsetY, which works as expected) and only happens if the write happens before any read. If I read OffsetX and then attempt to write the same value it's fine
We have observed this with 2 different camera models from 2 different vendors

To Reproduce
Steps to reproduce the behavior:

System - Ubuntu 22.04
Cameras we've see issues with are Allied Alvium and Lucid Pheonix

1 - Connect camera and make sure it's present
2 - Write Height and Width to be less than max (and > than desired offset values)
3 - Attempt to write OffsetX

Expected behavior
The first attempt to write OffsetX takes the value without needing to be read first.

Camera description:

• Manufacturer : Allied
• Model Alvium 1242c
• Interface USB3

Platform description:

• Aravis version: seen on both 0.8.29, 0.8.30 and 0.9.0
• OS: Ubuntu 22.02
• Hardware x86_64

Additional context
Here's a screenshot of this occuring
offsetx_2