OSC: Incorrect isPlayingQueued and isStopQueued

[TommyC81]

Software:
Bitwig 4.3.4
DrivenByMoss-17.5.0-Bitwig
Windows 10

When launching a clip, the messages "isPlayingQueued" and "isStopQueued" are always sent out together and with the same value attached (1 or 0). This seems to be wrong, surely the "isPlayingQueued" message should only be sent when a clip is queued to be played, and vice versa for the "isStopQueued" message when a stop is queued.

When stopping a clip, no message is sent out at all ("isStopQueued" would be expected) until an "isPlaying 0" is sent out.

Extract from OSC log below:

22:50:00.043 | RECEIVE    | ENDPOINT([::ffff:192.168.0.101]:53217) ADDRESS(/update) INT32(1)
22:50:00.043 | RECEIVE    | ENDPOINT([::ffff:192.168.0.101]:53217) ADDRESS(/track/1/clip/1/isPlayingQueued) INT32(1)
22:50:00.043 | RECEIVE    | ENDPOINT([::ffff:192.168.0.101]:53217) ADDRESS(/track/1/clip/1/isStopQueued) INT32(1)
22:50:00.043 | RECEIVE    | ENDPOINT([::ffff:192.168.0.101]:53217) ADDRESS(/track/selected/clip/1/isPlayingQueued) INT32(1)
22:50:00.043 | RECEIVE    | ENDPOINT([::ffff:192.168.0.101]:53217) ADDRESS(/track/selected/clip/1/isStopQueued) INT32(1)
22:50:00.043 | RECEIVE    | ENDPOINT([::ffff:192.168.0.101]:53217) ADDRESS(/update) INT32(0)
22:50:00.071 | RECEIVE    | ENDPOINT([::ffff:192.168.0.101]:53217) ADDRESS(/update) INT32(1)
22:50:00.071 | RECEIVE    | ENDPOINT([::ffff:192.168.0.101]:53217) ADDRESS(/play) INT32(1)
22:50:00.071 | RECEIVE    | ENDPOINT([::ffff:192.168.0.101]:53217) ADDRESS(/time/str) STRING(0.00.00:000)
22:50:00.071 | RECEIVE    | ENDPOINT([::ffff:192.168.0.101]:53217) ADDRESS(/beat/str) STRING(1.1.1:00)
22:50:00.071 | RECEIVE    | ENDPOINT([::ffff:192.168.0.101]:53217) ADDRESS(/track/1/clip/1/isPlayingQueued) INT32(0)
22:50:00.071 | RECEIVE    | ENDPOINT([::ffff:192.168.0.101]:53217) ADDRESS(/track/1/clip/1/isStopQueued) INT32(0)
22:50:00.071 | RECEIVE    | ENDPOINT([::ffff:192.168.0.101]:53217) ADDRESS(/track/selected/clip/1/isPlayingQueued) INT32(0)
22:50:00.071 | RECEIVE    | ENDPOINT([::ffff:192.168.0.101]:53217) ADDRESS(/track/selected/clip/1/isStopQueued) INT32(0)
22:50:00.071 | RECEIVE    | ENDPOINT([::ffff:192.168.0.101]:53217) ADDRESS(/update) INT32(0)
22:50:00.092 | RECEIVE    | ENDPOINT([::ffff:192.168.0.101]:53217) ADDRESS(/update) INT32(1)
22:50:00.092 | RECEIVE    | ENDPOINT([::ffff:192.168.0.101]:53217) ADDRESS(/track/1/clip/1/isPlaying) INT32(1)
22:50:00.092 | RECEIVE    | ENDPOINT([::ffff:192.168.0.101]:53217) ADDRESS(/track/selected/clip/1/isPlaying) INT32(1)
22:50:00.092 | RECEIVE    | ENDPOINT([::ffff:192.168.0.101]:53217) ADDRESS(/update) INT32(0)

22:50:02.286 | RECEIVE    | ENDPOINT([::ffff:192.168.0.101]:53217) ADDRESS(/update) INT32(1)
22:50:02.286 | RECEIVE    | ENDPOINT([::ffff:192.168.0.101]:53217) ADDRESS(/time/str) STRING(0.00.02:171)
22:50:02.286 | RECEIVE    | ENDPOINT([::ffff:192.168.0.101]:53217) ADDRESS(/beat/str) STRING(1.4.4:92)
22:50:02.286 | RECEIVE    | ENDPOINT([::ffff:192.168.0.101]:53217) ADDRESS(/track/1/clip/1/isPlaying) INT32(0)
22:50:02.286 | RECEIVE    | ENDPOINT([::ffff:192.168.0.101]:53217) ADDRESS(/track/selected/clip/1/isPlaying) INT32(0)
22:50:02.286 | RECEIVE    | ENDPOINT([::ffff:192.168.0.101]:53217) ADDRESS(/update) INT32(0)

[git-moss]

Looks to be like a Bitwig bug. Will report it.