I don't think the speed of my machine is an issue. It is a dual core AMD running Win7 64-bit, with 6GB of physical RAM. There are certainly faster machines around, but this one is feast enough. The first 75% of the file is generated very quickly, then it grinds to a halt. I had this same problem on Finale 2011, and I mostly use 2012 now.
I have given up hope that it will be fixed on 2012, but I do expect that the new Finale should have a big emphasis on DAW integration and rendering of audio files. On 9/13/2013 6:52 AM, Dennis Bathory-Kitsz wrote: > I've observed that the process has several stages: the initial 'scan' (which > is what also happens before ordinary playback with VST and human playback), > what appears to be a compilation of the actions into a temporary file, and > saving the compiled information into the final audio file. Each stage is shown > -- a dialog box, then a percentage on the status bar, and finally the progress > bar on the status bar. > > It can fail due to various bugs, but that's mostly the first stage (and also > fails the same way on human playback). If the file plays back all the way, it > should also save all the way. It's a fairly intensive process, though, > demanding lots of CPU and memory, so if your machine is older, slower, or > 'underpowered', it's going to do a lot of extra work swapping information on > and off the hard drives. > _______________________________________________ Finale mailing list [email protected] http://lists.shsu.edu/mailman/listinfo/finale
