By admin on Apr 15, 2008 in Featured, Finale 2008, Finale Issues | comments(6)
This error looks like it is specifically linked to bug in Microsoft’s Cumulative Security Update for Windows, which causes errors in memory management when using Java.
There is no “fix”, but I do think that there is a way around the issue.
Continued
By admin on Apr 8, 2008 in Finale 2008, Finale Issues, Finale Tools | comments(0)
There is an issue that causes a crash within Finale 2008 on Vista in regards to articulations that draw vertically, specifically the Rolled Chord Articulation. Adding this articulation to your score will cause a hard crash as soon as you choose to save the document.
There is no fix for the issue at this time, but there is a work-around.
Follow these steps to add the rolled chord articulation into your score without crashing.
Continued
By admin on Apr 3, 2008 in Finale 2008, Finale Issues | comments(0)
This is a confirmed Vista Windows issue with tech support, but there appears to be a fix.
It looks like completing a compact installation of Finale (not Garritan) will reinstall the necessary files to allow the A update to take.
Just pop your Finale 2008 disc in your drive, and uncheck everything but Finale. Install.
If this fails, try uninstalling and reinstalling Finale completely and then reapplying the update.
By admin on Mar 12, 2008 in Advanced Tips, Audio, playback | comments(4)
Let’s say that even after the below steps, Finale still crashes after you start playback or enter a few notes. What could the problem be? Continued
By admin on Feb 18, 2008 in Audio, Hardware | comments(1)
Realtek has recent driver/audio codecs updates for their soundcards. These were updated around 10/9/2007.Being one of the worlds largest, low-end, sound card manufacturer’s, this could create a playback issue for many Finale users.The new driver number is 5.10.0.5559 for XP, and 6.0.1.5559 for Vista.You can check your driver version by using your device manager(here is an article about the Device Manager from Microsoft),don’t let the device manager search the web for the driver as it will rarely find the correct file,by accessing the Realtek HD Audio Manager that may be installed on your machine or by running a DXdiag (system profile) of your machine.Realtek has a README file that is available along with the driver download.It contains the detailed instructions for downloading, uninstalling and reinstalling the newest driver.Here are the links:Realtek Site: Realtek AC 97:Realtek HD:Remember - Finale will only perform as well as your machine will allow.
By admin on Feb 15, 2008 in Finale 2008, Finale Issues | comments(2)
Had a client that ran into a little scanning issue today.
When Selecting Scanning:Smartscore Lite an error would pop-up that would read “An error that SSlite or one of it’s components are missing.”
We did a little search of the Finale Knowledge Base and found an article that not only provided us with the steps, but also with the .dll files necessary to fix the issue!
You can find the article here.
It looks as though a Windows Update may have been either corrupted or not installed, causing the issue. Luckily the replacement System32 file did the trick!
By admin on Feb 8, 2008 in Advanced Tips, Audio | comments(5)
Ever been using Finale’s “SmartMusic SoftSynth” (Midi) sounds and wished that you could just have some different sounds? Well - you can. And you can use them when you create the Audio Files from Finale. As long as they are in sf2 format you can certainly use these sounds.Here’s how: Continued
By admin on Dec 19, 2007 in Finale Issues | comments(0)
If you are running Finale pre-2004 you may experience a crash when closing the program. The reason is that these programs are were not necessarily designed to run on XP. The fix is simple. Right-click on the Finale icon and choose Properties from the bottom of the list. This will open the Properties Window for the version of Finale that you are running. Choose the Compatibility Tab across the top and then set the Compatibility Mode for Windows 2000. Click Apply and then OK.
The error message should now be gone.