What doesn’t get handled are file names, an arbitrary end-of-line character for the xml output and a host of other irritating oversights on the part of the software. It’s non-trivial, there are a lot of things that SmartScore messes up but at least 85-95% of the drudge work is done by the computer. I used PrintMusic/SmartScore to convert to xml and imported the xml into EasyAbc and then compared the print to the score and made the necessary corrections. It’s a good think that disk space is so cheap these days. Nominally, they have to be about 450dpi/inch before the somewhat limited software I used could generate reasonably accurate output. tiff files and if there are more than one tunes per page, a separate tiff file for each needs to be generated. It’s a bit onerous though since the first step would be to scan all of the pages to.
However, I did come up with a work flow for doing what you’re describing. In one of my many moments of musical insanity, I once thought that it would be neat to convert the King Street Sessions pdf file to abc notation only to find out after way too much time expenditure that there already was a KSS.abc file and I dropped the whole thing for all of the obvious reasons. I didn’t manage to get Audiveris to run on my Mac as a quick try so I’ll have to look into the configuration in depth. There isn’t yet any straight forward printed to abc/xml/anydigitaltype yet although the Audiveris looks promising.
