tieBack and tieFor in MuseScore 3
I made Shakuhachi, Koto, Shinobue and Numbered plugins.
I'm currently modifying that for MuseScore 3.
Is this specification change or bug?
note[i].tieBack and tirFor method return always "undefined".
"null" or "Ms::Tie(0x7ff44905e3c0)" etc. returned in the ver.2.
How can I find the beginning and end of tie?
Comments
Hello,
Did you find the answer? I get the same problem trying to get the tieBack and TieFor values. I output to log and they're all "undefined".
In reply to Hello, Did you find the… by Lance Phung
I have not solved it yet.
offsetX and offsetY also won't work as I expected.
In reply to I have not solved it yet… by tcbnhrs
FYI, I am seeing the same issue
In reply to FYI, I am seeing the same… by music_by_jeff
Looks like a bug. You can use code like the following to see the available properties:
for(var key in note2) {
if (note2[key] != undefined) {
console.log(key + " -> " + note2[key]);
}
}
tieFor and timeBack are supposed to be in elements, but they're not there. I do see things like this:
Debug: objectName ->
Debug: type -> 19
Debug: name -> Note
Debug: offsetX -> 0
Debug: offsetY -> 0
Debug: selected -> true
Debug: generated -> false
Debug: color -> #000000
Debug: visible -> true
Debug: z -> 1900
Debug: small -> false
Debug: line -> 3
Debug: fixed -> false
Debug: fixedLine -> 0
Debug: headType -> -1
Debug: headGroup -> 0
Debug: mirrorHead -> 0
Debug: dotPosition -> 0
Debug: tuning -> 0
Debug: offset -> QPointF(0, 0)
Debug: fret -> -1
Debug: string -> -1
Debug: ghost -> false
Debug: play -> true
Debug: timesigNominal -> Ms::PluginAPI::FractionWrapper(0x91ccd30)
Debug: timesigActual -> Ms::PluginAPI::FractionWrapper(0x877abe0)
Debug: placement -> 1
Debug: lineColor -> #000000
Debug: timesig -> Ms::PluginAPI::FractionWrapper(0x93dfbe0)
Debug: timesigGlobal -> Ms::PluginAPI::FractionWrapper(0x8829dc0)
Debug: timesigStretch -> Ms::PluginAPI::FractionWrapper(0x86d6dc0)
Debug: spannerTick -> Ms::PluginAPI::FractionWrapper(0x875e200)
Debug: spannerTicks -> Ms::PluginAPI::FractionWrapper(0x9117280)
Debug: lyricTicks -> Ms::PluginAPI::FractionWrapper(0x91c13a0)
Debug: duration -> Ms::PluginAPI::FractionWrapper(0x9053e80)
Debug: track -> 0
Debug: autoplace -> true
Debug: sizeSpatiumDependent -> true
Debug: systemFlag -> false
Debug: voice -> 0
Debug: position -> Ms::PluginAPI::FractionWrapper(0x5cffd90)
Debug: accidentalType -> 0
Debug: dots -> [object Object]
Debug: elements -> [object Object]
Debug: pitch -> 72
Debug: tpc1 -> 14
Debug: tpc2 -> 14
Debug: tpc -> 14
Debug: veloType -> 0
Debug: veloOffset -> 0
Debug: objectNameChanged -> function() { [code] }
Debug: userName -> function() { [code] }
Debug: clone -> function() { [code] }
Debug: subtypeName -> function() { [code] }
Debug: _name -> function() { [code] }
In reply to Looks like a bug. You can… by music_by_jeff
Rather a not-yet-ported item since the rewrite of MS3 (https://dmitrio95.github.io/plugins/html/class_ms_1_1_plugin_a_p_i_1_1_…)
Feel free to add a request to bring it back into the issue tracker.
In reply to Rather a not-yet-ported item… by jeetee
Thank you music_by_jeff and jeetee.
I would like to request these to the MuseScore developers.
In reply to Thank you music_by_jeff and … by tcbnhrs
Then enter it into the issue tracker as "S5 - Suggestion"
In reply to Then enter it into the issue… by Jojo-Schmitz
Looks like exactly what is requested in #293008: Expose tie information read-only to QML plugins.
tieBack
andtieFor
will be available again in MuseScore 3.3 version.In reply to Looks like exactly what is… by dmitrio95
Thank you for the great news!
I would like to build-in it into my plug-ins.
In reply to Looks like exactly what is… by dmitrio95
Thanks!