On 25 Jan 2010 at 14:36, Christopher Smith wrote: > On Mon Jan 25, at MondayJan 25 2:25 PM, David W. Fenton wrote: > > > One computer approach might be to use a multi-pass approach, i.e., do > > a default spacing, then look at it a second time to see if there are > > any suspicious things that need to be fixed. I'm not sure how easy it > > is to examine the Finale data for that, but it might be possible to > > fix certain kinds of errors in a second pass (or flag them and ask > > the user what you want to do about them). > > Actually, we kind of already do that. I use the default Finale > spacing that gets things apart from things that shouldn't be > touching, then apply TG Tools or Patterson plugins to any area that I > think needs touchup, finishing up with some manual spacing (ugh!) But > are you referring to PROGRAMMING a multi-pass spacing algorithm?
Yep. Programming-wise, sometimes it's easier to start from one state, calculate a new state, and then start over from that state with a new calculation than it is to try to get there in one pass. It also eases the resource requirements in terms of CPU and memory (though these days with quad-core CPUs and 8GBs of RAM and more, that's hardly an issue). > I know guys like Johannes and the two Dennises do this kind of thing > constantly and probably have it streamlined, but I would LOVE to have > some of my manual spacing tasks taken over by a plugin. Some of them > are pretty simple and could easily be programmed. I wrote in about a > week ago asking a very specific question about spacing of seconds > (and other intervals, for that matter!) in different layers when the > downstem layer is higher than the upstem layer, but got no response, > so I imagine that particular problem is not automatically addressable. This raises the old plugin argument, i.e., whether MM gets away with not improving Finale's internals because someone steps up and ameliorates the problems with a plugin (Patterson Beams, anyone?). Since I use a really old version of Finale (2003), I still have to deal with old spacing problems like the colliding 2nds in layers and terrible grace-not spacing. I believe both of these have been fixed in later versions (the colliding 2nds long ago, the grace notes much later, and if I recall correctly, not 100% fixed). Those kinds of things ought to be fixed in the basic spacing algorithms within Finale (and my melisma problem should be, too), not addressed with a plugin. On the other hand, there are some things that I think a plugin should do. For instance, I wish there were some way to use the beat charts that would not require moving all the handles. That is, if you could, say, widen a measure, allocate more space for the first beat (by shift-draggin the 2nd-beat handle) and then tell your plugin to space the 2nd beat on to use the available space (as opposed to the music bumping up against the bar line). Probably a bad example, but it's something I have to do regularly frequently, i.e., use beat charts to fix an internal spacing problem, but then have to respace the rest of the measure manually. Much of that is caused by the fact that I have to get a lot of music into a very small space (because of the limits of 2 pages per piece/movement for my viol consort), so one of the reasons I run into the issue is because I'm forcing the music into less space than is ideal. But nonetheless, I see that kind of thing as very much appropriate to implementation as a plugin type. General spacing defects should be fixed within Finale, though. -- David W. Fenton http://dfenton.com David Fenton Associates http://dfenton.com/DFA/ _______________________________________________ Finale mailing list [email protected] http://lists.shsu.edu/mailman/listinfo/finale
