BUG - Secondary TimeDisplay OnChange isn't showing Secondary but Duplicating Primary Value

Cubase
,
1

Hi,

Could anyone else test the following using the Midi Remote API. As for me, using an mOnChange method on the Secondary > TransportLocator results in it just reproducing what the Primary value is.

For example, if I have bars n beats in Primary, and timecode in Secondary. The Secondary will just send out the Primary instead of the Secondary, so I will get 2 Bars n Beats.

Here is my code below, in case something is wrong with the code. Or, is this a cubase API bug?

// Primary Transport Value
// BARS (hex 0xf0, 0x42, 0x41, 0x52, 0x53)
page.mHostAccess.mTransport.mTimeDisplay.mPrimary.mTransportLocator.mOnChange = function (
  activeDevice,
  activeMapping,
  time, // time value
  time2 // type of time value (bars-beats, timecode, etc.)
) {
  var msg = [0xf0, 0x42, 0x41, 0x52, 0x53 /*, more initial bytes ...*/]
  for (var i = 0, len = time.length; i < len; ++i) msg.push(time.charCodeAt(i))
  msg.push(0xf7)
  midiOutput.sendMidi(activeDevice, msg)
  console.log("SysEx Primary time message sent: " + msg.toString())
}

// Secondary Transport Value
// TIME (hex 0xf0, 0x54, 0x49, 0x4d, 0x45)
page.mHostAccess.mTransport.mTimeDisplay.mSecondary.mTransportLocator.mOnChange =
  function (
    activeDevice,
    activeMapping,
    time, // time value
    time2 // type of time value (bars-beats, timecode, etc.)
  ) {
    var msg = [0xf0, 0x54, 0x49, 0x4d, 0x45 /*, more initial bytes ...*/]
    for (var i = 0, len = time.length; i < len; ++i) msg.push(time.charCodeAt(i))
    msg.push(0xf7)
    midiOutput.sendMidi(activeDevice, msg)
    console.log("SysEx Secondary time message sent: " + msg.toString())
  }

Cheers,
DMDComposer

1 Like
2

Hi, I’ve noticed this one too, but I forgot to post it, good that you did!
It’s obviously a bug. In fact, the secondary sends correctly the secondary format, but wrongly, the primary value.

1 Like