I searched the w3c/musicxml for "To Coda" and it doesn't seem to address it.
I'm pretty sure you're always supposed to play the measure first, then the "To Coda", hence the placement at the end of the measure. That's from my experience as a musician. It makes sense to let the musician know at the end of a measure when they need to do a measure skip after the measure.
how can I change cursor element into a image element like this
@hallvors it's mainly historical, early on most properties were lowercase and private, and only some that should be public had getters and/or setters. But having getters and setters for everything in Typescript creates piles of boiler plate code, so we just made the properties public, and kept the lowercase in some cases for backwards compatibility.
cursor repetition support is already working in the audio player, will be integrated into osmd soon, see #379 (which you commented on), and #864
@nguyenphuonglinh2k that is unfortunately not possible right now, you would have to create your own cursor class and add that cursor to OSMD.
@phamconganh yes, osmd is probably currently slower than vexflow-musicxml, because vexflow doesn't have a solid bounding box and collision detection system for many elements, so we have to check where vexflow draws, which costs a lot of performance. We are currently checking if we can optimize that performance in #937.
also, i'm not sure how accurate vexflow-musicxml is compared to OSMD, we should check that out in more detail to have a reference.
Thanks for explaining Simon. Legacy tends to make architecture messy :)
Also terrific to hear that cursor repetition support is not far away. I was wondering if I could hack my own but didn't see methods for making the cursor jump to a specific measure..so it seemed complicated. Plus there are too many ways to annotate repetitions and since I'm not a musician my note comprehension is amateur-level :)
Also terrific to hear that cursor repetition support is not far away. I was wondering if I could hack my own but didn't see methods for making the cursor jump to a specific measure..so it seemed complicated. Plus there are too many ways to annotate repetitions and since I'm not a musician my note comprehension is amateur-level :)
@nguyenphuonglinh2k I made some changes to get several cursors at the same time. I use one now for the tempo, small grey, and a green one similar to the one in your question placed before the next notes to play. Have a look at https://michaelecke.com/pianoplay/. If you have interest I can send you the modified files to have a look.
It's impossible for one OSMD instance to render 2 MusicXML files at the same time.
@sschmidTU because the lib vexflow-musicxml is out of date. And I want use musicxml standard to render music score. So I want use the XML reader of OSMD without "solid bounding box and collision detection system" and vexflow to improve the performance render and full controller the layout and cursor.
@phamconganh ok, as i said, just use
vexflow-musicxml is severely outdated, and the maker joined the OSMD team (and actually worked on the collision detection system in OSMD). So, there will be many challenges for you if you want to use MusicXML without OSMD's vexflow rendering settings and adjustments, unless your scores are very simple, then something like vexflow-musicxml could have have been enough.
osmd.load() without osmd.render(), then the interpreted xml model is in osmd.sheet.vexflow-musicxml is severely outdated, and the maker joined the OSMD team (and actually worked on the collision detection system in OSMD). So, there will be many challenges for you if you want to use MusicXML without OSMD's vexflow rendering settings and adjustments, unless your scores are very simple, then something like vexflow-musicxml could have have been enough.
0xfe/vexflow#829 looks promising to use Vexflow 3.0.9
@sschmidTU Thank you for the response. There is no way to obtain the measure-info or anything remotely close to what the voices or notes maintain by querying the SVG <g> elements in javascript. We would like to capture a user selection based on click/touch events and move the cursor to that position. am I missing something?
i just wrote above how to get the measure info
@sschmidTU i do have access to osmd. When you render sheet music in javascript, osmd draws it on a canvas using SVG. When a user now selects a position on the canvas rendered by osmd, the touch event is generated on the SVG which does not have any positions info related to osmd iterator or cursor. So i am not sure how to move the cursor to the selection whithout being able to relate the svg position with the probable measure number.
I wonder if
osmd.graphic.getClickedObject() might help with this problem? If you calculate mouse coordinates relative to the SVG and pass an object with x and y to getClickedObject() you might get something to iterate to.. But I still don't know OSMD well enough, so maybe I'm barking up the wrong tree..
1 reply
@hallvors i'm working on click events right now which are almost finished. But it's good that you mentioned this method because i overlooked it. I'll have to check if it still works or if it would also need a similar overhaul to what i've done so far, but it could be very useful.
2 replies
:up:
Two small layout-related questions: the script for creating SVG accepts width and height arguments, but I'd like to only constrain the width and let the height be unlimited. Is there a pageFormat argument that allows this?
I'd like to be able to style the output with CSS, but the generated SVG elements tend to have fill and stroke set directly. Is it possible to make Vexflow omit those?
Two small layout-related questions: the script for creating SVG accepts width and height arguments, but I'd like to only constrain the width and let the height be unlimited. Is there a pageFormat argument that allows this?
I'd like to be able to style the output with CSS, but the generated SVG elements tend to have fill and stroke set directly. Is it possible to make Vexflow omit those?
(Also, feel free to ignore the stroke and fill question - I'll use CSS filters for my styling needs :) )
@sschmidTU can I hide the note word?
@phamconganh you can try creating a new cursor yourself. there will also be
osmd.rules.DefaultColorCursor in osmd 0.9.3
@sschmidTU i try "osmd.rules.RenderChordSymbols = false" and it does not change.
@phamconganh that is a weird MusicXML sample.
you can't easily remove these "words" expressions yet,
we can create an EngravingRule for that soon,
but you can try something like this after osmd.load():
removeUnknownExpressions() {
for (let i: number = 0; i < osmd.graphic.ParentMusicSheet.SourceMeasures.length; i++) {
const sourceMeasure: SourceMeasure = osmd.graphic.ParentMusicSheet.SourceMeasures[i];
for (let j: number = 0; j < sourceMeasure.StaffLinkedExpressions.length; j++) {
if (!this.graphicalMusicSheet.MeasureList[i] || !this.graphicalMusicSheet.MeasureList[i][j]) {
continue;
}
for (let k: number = 0; k < sourceMeasure.StaffLinkedExpressions[j].length; k++) {
sourceMeasure.StaffLinkedExpressions[j][k].unknownList = [];
}
}
}
}but i haven't tested this. this is modified from MusicSheetCalculator.calculateMoodAndUnknownExpressions().