Welcome, Guest. Please login or register.
Pages: [1] 2 3 4 5 ... 10
 on: April 30, 2022, 01:03:17 PM 
Started by conductbri - Last post by TBoliske
The templates and midi maps will need to be copied from their previous Finale locations because you have updated to a new full version of Finale. Are you using Windows or Mac operating system? The locations where these folders and files are located is different for each system.

Each system has 2 locations where the files may be stored. you can check your Finale Preferences or look in each of the locations for the contents of your previous version of Finale.

For Mac OS -
Common: /Library/Application Support/MakeMusic/Finale(it may add a 25or 26 if you have installed the newest version while keeping older versions)

User: /(your account name)/Library/Application Support/MakeMusic/Finale(it may add a 25or 26 if you have installed the newest version while keeping older versions)

Windows (these locations work for Windows 7 - 10, I have note tested on 11)
Common: C:\ProgramData\MakeMusic\Finale

User: C:\Users\[user name]\AppData\Roaming\MakeMusic\Finale[version]

Note: some of these folders may be hidden by default so you would need to Google for how to 'unhide/make visible folders'

The XML MIDI Maps should be copied to the MIDI Device Annotation folder.

The Template files should be copied to the Music Files/Templates folder.

Once you have completed copying these files go to your Finale Preferences and make sure that Finale it looking at the proper locations. This especially important for the templates. I usually copy the files to both the Common and User locations just as a precaution.

 on: April 29, 2022, 06:57:07 PM 
Started by jitkor - Last post by Hugh Smith
Perfect! Glad to hear you got it going again.

 on: April 29, 2022, 01:42:13 PM 
Started by conductbri - Last post by conductbri
Help!  I updated to Finale 27 from 25 and had several problems.  None of my maps or templets transferred over and now I can't find where anything should go.  Can anyone tell me what I should be looking for and where it goes.  I can't find my original info and don't want to but a new copy. 

 on: April 28, 2022, 01:03:00 PM 
Started by jitkor - Last post by jitkor
Problem solved!!!

I went to take the screenshot and noticed that although it said VDL, the soundset was general midi. So I was able to select the VDL template and assign it to be the soundset for VDL, restarted and BOOM. It works now!

 on: April 26, 2022, 01:31:03 PM 
Started by jitkor - Last post by Hugh Smith
Hi, welcome to the forum!

Please attach a screenshot of your Playback Configuration.

You also mention VDL 2.5.2. The Template is made to support VDL 2.5.5. Double check which version you're using. (Upgrade if you need to.)

 on: April 25, 2022, 12:35:58 PM 
Started by jitkor - Last post by jitkor
I use Windows 10, VDL 2.5.2 and the Write Score 7.0 template. Everything worked perfectly for years. My hard drive got to be full, so I purchased a larger drive and cloned the old one to the new one. It should be an exact copy... and yet my playback in Sibelius completely stopped. I ended up uninstalling and re-installing a copy of Sibelius (version 2018.7) and then my Sibelius sounds began working, but still no VDL sounds. VDL DOES sound in standalone Kontakt player. So I'm sure it's just a pathway issue. Something is in the wrong place. But I don't know how things work and when I read what other's have posted, it sounds like a foreign language to me. I need someone to help. I've fallen two months behind in my writing schedule and I need to get back on track

 on: February 10, 2022, 01:45:04 PM 
Started by ryanwms - Last post by Hugh Smith
In the Mixer, set the appropriate playback device for each instrument. This will help Sibelius not have to guess. Still leave the VDL patches on (Auto) though.

There isn't any reason i know of where the VDL Template SoundSet file would cause a lag. You say others have the same issue as you? Get 'em on here and let's discuss.

 on: February 04, 2022, 11:59:31 AM 
Started by ryanwms - Last post by ryanwms
I posted this on the FB VDL users' Group, but bringing it here for hopefully some other insights.

A ways back I was trying to figure out why my VDL mapping in Sibelius was all fouled up - and then I realized I missed the install step of copying the XML File (from The Write Score) into the Sibelius Library folder. So I did that and all my mapping is great now.
However. 😇
My playback setup is NotePerformer for winds, VDL for percussion. Now that my XML file is in the correct spot, I'm getting the same stupid amount of lag/latency that others have complained about. My inclination is that the XML file is forcing Sibelius to unload/reload playback libraries that differ between VDL & NP.
Has anyone figured out how to solve this problem?

Adding to this...
Before I copied the XML file from TWS, I had zero lag when combining NP & VDP.

Using Dorico, I have zero lag between NP & VDL.

The problem starts with the XML file from TWS.

 on: January 14, 2022, 02:21:42 PM 
Started by ryanwms - Last post by Hugh Smith
Yup, it's often something 'simple'.

Happy writing!!

 on: January 13, 2022, 07:28:48 PM 
Started by ryanwms - Last post by ryanwms
Holy moly.

That was it.
I never did that step.

Fixed this problem.
I'll bet it solves other problems, too.


Pages: [1] 2 3 4 5 ... 10