My symptoms are exactly like yours, except a lot more extreme. That is to say, the display usually freezes somewhere around the 70% point. If I watch the actual file size, it grows rapidly (at an expected rate) up to the point when the display freezes. But from that point onward, the file growth slows ALMOST to a halt. It does keep growing, but maybe at 1/100th the speed that the first 70% happened. And indeed, sometimes it does, in fact, finish within 5 or 10 minutes even though the display is frozen (and becomes unfrozen when the export completes.)
But in most cases -- especially the cases where I really, really meed it to not screw up -- it grinds down to the point of only adding something like 1000 bytes every 15 seconds -- a rate that might take 24 hours to complete. It is so unreliable, I just can't afford to waste any time on it. I hope and expect this will have been a major area of improvement in Finale 2014 (or whatever it is called). I also hope and expect I will be able to use VSTs more easily directly in Finale, greatly reducing the need to export Finale material to a DAW. And I also hope that the new version not only exports the full mix reliably to WAV or MP3, but also includes the option to export the entire score as a set of WAVs, one WAV file per Finale staff in the score. That would make the transfer to audio files to a DAW much more practical, giving us much better control over the mix. I can dream, can't I? On 9/12/2013 12:38 PM, Phil Buglass wrote: > It does work for me, but only wav files. I > didn't know the bit about using VST (thanks > Dennis), but I tested it out, and that is > correct. I can get an mp3 direct, but only with > midi files. I much prefer the sound from GPO4, > so its worth the hassle of converting the file externally. > > I am busy hacking a bunch of old midi files, so > that I can use the music as backing for videos > going on to facebook, to get past the copyright > police! I have done a couple which have been > about 700 measures or so. It *does* sometimes > appear to stop after maybe 10% of the file, but > it is just the display. After 2 or 3 minutes, > the file finishes and the display comes back. I > don't think it has ever taken more than 10 > minutes or so. I just finished one, at 699 > measures long. It played it to itself > internally, and then started writing. The > display froze at 2%, about 4 minutes in to the > whole process. I kept monitoring the growing > output file, and it finished at between 8 and 9 > minutes. The display never altered past that 2% mark, though. > > Phil. _______________________________________________ Finale mailing list [email protected] http://lists.shsu.edu/mailman/listinfo/finale
