![]() ![]() These programs can’t handle transposed instruments in a transposed score. This was a fairly simple saxophone quartet. I did another project with SmartScore this evening. I am going to try two more very similar scores this weekend and will try to take better notes. I was frantically trying different combinations of both programs, and they each had their own set of obstacles. When you toss in transposed instruments all %$% breaks loose.Īnd to be honest, I’m not positive whether it was SmartScore or PDF2XML that caused the meter-related problems I mentioned above. I don’t doubt that it would do OK with piano scores. it works well enough to be useful and I am reasonably adept at making minor corrections within SmartScore. I am not really unhappy with the scanning part. I am using the pro version X2 and the latest patches (which are few and far between). And I wonder also about the clarity of what you are scanning. I found lite version in Finale impossible for my purposes. So this makes me wonder if you using the stand-alone SmartScore X Pro or later. ![]() It does leave out occasional bar lines, but these are easily inserted within SmartScore. For example, it recognized Beethoven’s 32 piano sonatas with only a few hitches. While I am not scanning orchestral scores, I am able to OCR complex piano music in SmartScore without such errors. But it feels like navigating a minefield. Fortunately whatever garbage was deposited by the XML was not carried across in my cut-paste operation, so I ended up with a “normal” Dorico flow. I eventually gave up and created a clean flow, cutting and pasting everything from the damaged flow. I added a bar number change on the first measure, and that seem to have no ill effects, but is just one of those rough edges. This is the kind of thing that makes the XML input so tedious.Īnother example on this same file is that all the measures are shifted off by two, as if there are two phantom measures at the beginning. For some reason, Dorico doesn’t believe the time remains 4/4, but there are no signposts that would indicate there are any hidden meter changes. I have tried every layout option and the only way I could get that to work is to force in a 4/4 every affected measure. If I don’t force in a 4/4 on every measure, then you get the bad notation that is seen in in measure 44, with a quarter crossing the half-measure. For example, on my latest project, the whole thing is 4/4 time, the meter is getting lost somehow. But then measures get all mis-aligned because of multi-measure rests that are read wrong or bar lines that are missing.Īnd if I get past all of that, there invariably is rubbish in the Dorico (or Finale ) file that causes other notation problems. I find my only real option is to SmartScore one instrument at a time if I have parts available. I think my biggest frustration with SmartScore is that I really can’t use it on scores that include transposed instruments because it simply doesn’t recognize that a BB trumpet is not a concert instrument. SmartScore doesn’t usually create really wacky notation when imported. And again, it fails different ways in different programs. Most of my meltdowns are in the integration (i.e. But my main point was that I can live with the accuracy of scanning it delivers. ![]() When it doesn’t work, it takes years off my life. But the program has saved me many hours of needless work and for that alone I think it is worth every penny I paid for it. ![]() All I expect from SmartScore X Pro is note input and would never do any substantial editing within SmartScore for the reasons you mentioned. Cparmerlee, you didn’t say, but perhaps you use SmartScore. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |