Hi,
I’ve encountered an issue with my remote driver script that worked perfectly in C13 but seems to behave differently in C14. Here’s what’s happening:
The mTimeDisplay.mSecondary function is only logging the primary time value, regardless of the secondary setting. I tested the script to ensure it logs both the time value and its type (e.g., Bars & Beats, Timecode, etc.), but the results are inconsistent:
- Scenario 1: Primary set to Bars & Beats, Secondary set to Timecode
- Logged result: The secondary value shows the primary Bars & Beats value, but the type is logged as “Timecode.”
- Scenario 2: Primary set to Timecode, Secondary set to Bars & Beats
- Logged result: The secondary value logs the primary Timecode value, but the type is logged as “Bars & Beats.”
This behavior seems to suggest that mTimeDisplay.mSecondary is not correctly referencing its assigned value, but instead mirrors the primary value with the secondary type.
Has anyone else experienced this? Is this a bug, or could there have been changes to remote MIDI scripting that weren’t reflected in the documentation?
Cheers,
DMDComposer
// Secondary Transport Value
transport.mTimeDisplay.mSecondary.mTransportLocator.mOnChange = function (
activeDevice,
activeMapping,
time, // time value
time2 // type of time value (bars-beats, timecode, etc.)
) {
console.log(time.toString())
console.log(time2.toString())
}