DeviceBank device proxies pointing to wrong devices

[minortom]

Wondering if anyone else has run into this or I'm just in a bad dream.

* Bitwig 4.4, API 17 (but I'm positive I've seen this intermittently for a while now)
* In an extension:
- create a TrackBank of 8 tracks
- from each track .createDeviceBank(8)
- for each bank, get 8 Devices via bank.getItemAt()
- markInterested() on exists(), etc.
* In app:
- open a new project (two tracks, no devices)
- add a new device to one of the two tracks
* Observe that:
- EVERY first device in all of the 8 banks now reports the same .exists() value, color, type, etc. as the device you've just added — as if all those device proxies got updated to point to the new device

Additional observations:
* Everything goes to normal after restarting the extension, it's only adding devices to empty slots that causes this
* If a slot already contained a device, it's proxy will not be overridden
* If a new device is added to a slot and its proxy was previously overridden, it will correct itself

[Tj Shredder]

What a nice bug report. I’d send it to support…

[minortom]

What a nice bug report. I’d send it to support…

Thank you. Already sent.

[Kirkwood West]

Nice find!