I don't think it's fair to call the Steinberg product "vaporware." Steinberg is an established software company that has hired an established development team (almost the entire Sibelius staff) headed by one of the most respected people in the industry, Daniel Spreadbury. So far, they've refrained from making outlandish claims or hyping specific features. The development diaries have been down-to-earth, process-oriented, and realistic about the challenges they face. They've released their music font, Bravura, which is quite nice. <http://blog.steinberg.net/2013/05/introducing-bravura-music-font>.
To qualify as "vaporware," a product typically has to make and then break promises (usually release dates), or make hyped-up promises it can't possibly keep. I don't see any indication so far that that's the case here. Cheers, - DJA ----- WEB: http://www.secretsocietymusic.org On Sep 17, 2013, at 1:35 PM, Robert Patterson <rob...@robertgpatterson.com> wrote: > I agree with Darcy's list of wishes long before playback features, and to > them I would add music spacing options by region and part. > > BTW: if you are looking for an open framework, there is MuseScore. I > haven't been following exactly where it is going lately, but I think it has > the potential to leave all the others in the dust, just because of the > large number of people that seem to be contributing. I certainly think that > any new commercial product will have trouble competing with it. The > Steinberg offering, for example, seems to be 100% vaporware. If I had a > dollar for every vaporware announcement that never saw the light of day, I > would be a rich man. > > > > > On Tue, Sep 17, 2013 at 12:02 PM, Jari Williamsson < > jari.williams...@mailbox.swipnet.se> wrote: > >> On 2013-09-17 14:34, Robert Patterson wrote: >> >>> Could you explain the process? >> >> During the projects I've done this year, I've used a system where I've >> pasted code from my other my different plug-in sources into an automate >> plug-in. That plug-in used a number of control files (in text format) to >> set the distances in the cases where there needs to be a correction >> compared to the default positioning (taking stem direction, other >> artics, slur tips, ledger lines, etc into account). After all >> positioning comes spacing (including changing certain types of measures >> to specific widths), then alignment and then I make a approximate >> calculation of the vertical span of a system, and respace. >> >> The whole process goes outwards in the layout in one step (starting with >> articulation placement, ending with system positioning placement). >> >> Although the process is automatic, the thing that doesn't work good >> enough yet is the pre- and post-spacing, and the system isn't that >> flexible (I've more or less just added the editing cases I've needed). >> I'm now moving towards a totally script-based solution instead, which is >> almost a totally opposite approach, but it's also a much better way to >> handle complex tasks such as spacing. >> >> >> Best regards, >> >> Jari Williamsson >> >> >> >> _______________________________________________ >> Finale mailing list >> Finale@shsu.edu >> http://lists.shsu.edu/mailman/listinfo/finale >> >> > _______________________________________________ > Finale mailing list > Finale@shsu.edu > http://lists.shsu.edu/mailman/listinfo/finale > _______________________________________________ Finale mailing list Finale@shsu.edu http://lists.shsu.edu/mailman/listinfo/finale
