Hello!
When I import XML files from PhotoScore, sometimes I get an incomplete import. In this case, the entire lower three staves come in blank. When I open the same XML in Finale or MuseScore, everything comes through just fine. I then export XML from Finale or MuseScore and import a second XML file into Dorico and everything comes through. Is there something I should be doing to be able to import this correctly the first time? I’m including an XML file that causes this problem.
Thanks so much!
Alceste 4.xml (596.0 Kiba 
)
Dorico is particularly sensitive to rhythmic errors, and it’s possible for them to compound in such a way that the rhythms become un-notatable, which is what results in the remainder of the part ending up blank.
Other applications can handle this better because they effectively “reset” their understanding of the current rhythm at every barline, whereas Dorico takes all of the music in one voice in a single span, then applies barlines on top at the end.
If possible, make sure you have corrected all rhythmic errors before you export MusicXML from PhotoScore, and you should get a better result.
1 Like
Daniel, Photoscore XML export is really dreadful. I’ve had to buy a Sibelius licence to keep using it (there were some bargains lately) because it’s the only way to make it work efficiently. For instance, it cannot export a grand staff instrument as such. You have to deal with two one-staff-pianos. If the meter is 3/4, there’s an awful mess — I’ve had to heal some files before I bought Sibelius and it was really painful, although the music was really simple. Had I been at home, I probably would have notated them from scratch and saved some time!
Problem is the latest Photoscore update is 5 years old. I’m not too confident on another update. There would be a serious revamp needed in that area.
1 Like
Yes–Photoscore is somewhat of a Windows 95 interface. If there is a score scanned in with a staff hidden–like in a piano/vocal piece where the first few lines are piano only–its export process puts everything to the top of the score, no matter what instrument it shows it on in the photoscore doc. It’s always been dreadful at that. I think the way Dorico handles rhythm and missing staves, though, kinda makes it worse. I guess I’ll keep musescore around once Finale goes bye-bye.
On an un-related/related note–if anyone has alternative Photoscore apps to recommend, I’ll take them!
Thanks for the clarifications!
Here’s a recent review of music scanning products:
2 Likes
This was perhaps my biggest challenge coming from Finale, where I was used to the unit of measure being the, um…measure.
1 Like
I agree with Marc that importing XML files from Photoscore into Dorico is difficult to work with, even when all the music has been corrected. For example, in the case of a simple score with mutirests, the measure numbers are often altered and do not match.
I also have to keep using Sibelius to import the data.
Even though Photoscore hasn’t been updated recently, I still consider it the best solution for reading a full score, and I haven’t found a better alternative on the market.
1 Like
PhotoScore certainly has its shortcomings. But once you know what they are, each is relatively easy to resolve (either by editing the original in PhotoScore, or leaving it to Dorico).
My personal checklist includes:
Extensive re-voicing (cures many PhotoScore mis-reads)
Cross-stave notes
Double flats (need to run through Notepad to change double-flat to flat-flat)
Multirests (add a text comment in PhotoScore - then insert mode in Dorico)
Misinterpreted treble clefs and accidentals misinterpreted as key changes (both quite easy to resolve in Dorico using shift-I)
I suppose the big question is would I purchase PhotoScore today? Perhaps not, though the alternatives all seem to have similar shortcomings.
1 Like
That one is nerve-wracking! I sent them a ticket to request them to put a warning message each time the French violin clef appeared on a staff that had a G clef before. But since there were no updates since I sent it, it’s still painful 
Yes! This overarching rhythmic structure in Dorico is a serious challenge. I hope at some point being able to work measure by measure can come along. I’m not seeing the advantage of this current single-span approach.
This very, very, very much seems to be a Photoscore problem to me, and not something to unfairly blame on Dorico. Especially in the light of Dorico’s innumerable advantages because of this approach…
B.
2 Likes
Not blaming Dorico at all for Photoscore’s lack of updates or ability to export xml properly. 
It’s the all-or-nothing approach that Dorico has that is difficult, though. When the same XML imports into three other apps correctly, Dorico’s approach to the rhythmic structure much more difficult to work with. I still don’t understand the advantage of this approach. Can someone enlighten me? Meaning this with sincerity and not trying to start an internet argument. 
Well, you can literally move events (start of notes, end of notes) anywhere you want with simple keyboard shortcuts. That is huge. Same with dynamics, ornaments, etc. A different world.
SmartScore 64 Pro. Nuff said.