On a purely philosophical plane it doesn't have to be either/or. But on a practical level, it seems that it has to be either/or because as they have added and improved higher quality playback, they longstanding bugs haven't been resolved.
But I have a sneaking suspicion that they haven't been resolved because with the current very old source code base, the long standing bugs simply can't be resolved. So the thought of investors buying the company and infusing a lot of money into rewriting the code to bring it up to current computing levels is a good one. On the other hand, the amount they're talking about investing might not be sufficient to do the job properly. Only time will tell. David H. Bailey On 7/31/2012 4:41 AM, Raymond Horton wrote: > Why must it be either/or? > > Fix the bugs, keep adding notation capability, keep improving > playback, let it tie my shoes if it wants to. > > > Raymond Horton > Bass Trombonist, Louisville Orchestra > Minister of Music, Edwardsville (IN) UMC > Composer, Arranger > VISIT US AT rayhortonmusic.com > > > On Tue, Jul 31, 2012 at 1:53 AM, Jonathan Smith <lismoremu...@wanadoo.fr> > wrote: >> +3 >> >>> >>> >>> +2 >>> >>> On 31/07/2012, at 12:24 AM, Dick Hauser wrote: >>> >>>> +1 >>>> >>>> On Jul 29, 2012, at 10:45 PM, Craig Parmerlee wrote: >>>> >>>>> I cannot see myself ever producing a finished audio product within >>>>> Finale, so I'd rather see them put that effort into fixing the many bugs >>>>> and annoyances in the basic product. >>> >> >> _______________________________________________ >> 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 > > -- David H. Bailey dhbai...@davidbaileymusicstudio.com _______________________________________________ Finale mailing list Finale@shsu.edu http://lists.shsu.edu/mailman/listinfo/finale
