Hervé Bitteur
Hervé Bitteur
Nobody is perfect! :-)
Back to your top example, here is what I did: 1/ Downscale the image by half (resolution was too high, rejected by Audiveris) 2/ Make the rather thin beams collected...
Regarding the 5 locations (numbered according to music flow): 1. Half (just the lower one). See picture below. 2. Both 3. Both 4. None (same problem: 2 stems that go...
Bug fixed for the tuplet-related staff (in "development" branch)
Regarding the beam scaling in SCALE step, perhaps we could offer the user the ability to modify some of the scale retrieved parameters. To be investigated.
When you manually assigned the tuplet. You said: _If I manually correct the trioles, in some cases they assignement goes to the system above or below, in this score this...
Abscissa gap between clef and key signature was a bit too wide (case of staves with treble clef). I tuned the parameters, it's ok now. Note that the natural-only key...
about the parameters: Yes, we can! In theory, the OMR engine is just a bunch of algorithms with no hard-coded constants. A source value is defined for each constant in...
Current policy is that links are searched at (manual) insertion time of symbol A **only if** A needs such link. In the 2 cases mentioned here, the policy gives: -...
This already worked when inserting a stem near beams. This now works also when inserting a compound note (head+stem): beam potential links are displayed when moving the compound and they...