Post by Admin on Nov 6, 2013 13:21:17 GMT
Manual Sound Set - No Unpitched Sound ID
Article applies to: Sibelius 7
Description
When assigning an unpitched percussion (or other unpitched) patch to a device/channel, the manual sound set displays "none" for the Sound ID.
Solution
This is the expected behavior.
For pitched instrument patches, which generally consist of only one instrument, each patch is assigned one Sound ID so Sibelius displays this in the manual sound set dialog.
Unpitched instruments, by contrast, contain many different sounds and/or instruments, each assigned to a different note in the patch. Rather than assign these patches a single Sound ID, they are instead assigned to a drum map which contains Sound ID's for every note/sound in the patch. Since the drum map assignment replaces the individual Sound ID assignment, Sibelius displays "none" in the manual sound set dialog.
As long as the patch name is displayed in the "Program" column, the unpitched patch is correctly assigned in the manual sound set.
Saving Score Doesn't Save Loaded Sounds
Article applies to: Sibelius 7
Description
Patches, or patch settings, manually loaded in a plugin are lost when revisiting a saved score after exiting Sibelius.
Solution
Sibelius does not save sounds as part of the score; instead, when saved, each score references the playback configuration in use at that time. The benefit of this is that the same playback configuration can be reused for many scores without having to create it every time.
When manually loading the sounds, or when editing settings or other aspects of those sounds, be sure to save the playback configuration afterwards from the Playback Devices dialog so that those patches/settings will be recalled the next time the configuration is used.
Sounds Load Twice
Article applies to: Sibelius 7; Aria; Kontakt/Kontakt Player 5
Description
When selecting a playback configuration Sibelius immediately begins loading sounds. After exiting the Playback Devices dialog and starting playback or making a selection in the score, Sibelius loads sounds again which may cause delays, crashes, or instability.
Solution
This happens when using autoloading sound sets and a playback configuration is saved while sounds are loaded. The autoload function is such that Sibelius loads all patches 'fresh' from the hard drive as they are required and will ignore any sounds that are already in the plugin that were not loaded through this function. Sounds that are recalled with a Playback Configuration are recalled from a separate file and therefore Sibelius doesn't recognize them and loads the patches again.
To fix double-loading, open the interface for each plugin in your configuration that uses an autoloading sound set and delete all patches that are loaded. Save the configuration and restart Sibelius.
To prevent double-loading, avoid saving a playback configuration while sounds are loaded when using an auto-loading sound set. If you must make changes, it's recommended to do so prior to opening a score by starting Sibelius and opening the Playback Devices dialog first. After making your adjustments and saving the playback configuration, you can open the score and sounds will be loaded (once).
See also: Sounds Load When Sibelius Starts
Sounds Load When Sibelius Starts
Article applies to: Sibelius 7
Description
During startup, Sibelius loads sounds into various plugins.
Solution
Sibelius recalls the playback configuration last used when it is started, which may result in sounds loading during startup if sounds had been saved in that configuration.
To avoid this, you can designate a playback configuration that should be selected when Sibelius starts from the "Preferences" dialog. If you frequently use large configurations with many sounds loaded we recommend creating an empty configuration to use as your default Sibelius start-up configuration.
Staff Library Prefix Lost
Article applies to: Sibelius 7
Description
A custom instrument staff's library prefix is lost when returning to the Add/Create Instruments dialog.
Solution
The instrument prefix is only displayed in the Sibelius dialogs until the instrument is added to the score. Once the instrument staff is added to the score, returning to the dialog will display the staffs "Long Name" (which is generally the standard name) as it appears in the score. Despite the prefix being lost, this is still the same staff.
If it is important to maintain the prefix, you can edit the staff so that the library prefix is a part of the in-score name, however by default the name given in the score will always reflect the most appropriate name for printing rather than playback.
Volume Set in Plugin Changes on Playback
Article applies to: Sibelius 7
Description
Patch volume level that is set directly in a plugin is lost when playback starts.
Solution
Many patches have a master 'volume' that is linked to MIDI CC7. The Sibelius staff mixer faders are also linked to MIDI CC7. When playback begins, whatever level is set in the mixer is sent to the patch and your setting is lost.
Use the Sibelius mixer to balance patch levels rather than adjusting the settings in the plugin directly when the patches volume is linked to MIDI CC7.
Article applies to: Sibelius 7
Description
When assigning an unpitched percussion (or other unpitched) patch to a device/channel, the manual sound set displays "none" for the Sound ID.
Solution
This is the expected behavior.
For pitched instrument patches, which generally consist of only one instrument, each patch is assigned one Sound ID so Sibelius displays this in the manual sound set dialog.
Unpitched instruments, by contrast, contain many different sounds and/or instruments, each assigned to a different note in the patch. Rather than assign these patches a single Sound ID, they are instead assigned to a drum map which contains Sound ID's for every note/sound in the patch. Since the drum map assignment replaces the individual Sound ID assignment, Sibelius displays "none" in the manual sound set dialog.
As long as the patch name is displayed in the "Program" column, the unpitched patch is correctly assigned in the manual sound set.
Saving Score Doesn't Save Loaded Sounds
Article applies to: Sibelius 7
Description
Patches, or patch settings, manually loaded in a plugin are lost when revisiting a saved score after exiting Sibelius.
Solution
Sibelius does not save sounds as part of the score; instead, when saved, each score references the playback configuration in use at that time. The benefit of this is that the same playback configuration can be reused for many scores without having to create it every time.
When manually loading the sounds, or when editing settings or other aspects of those sounds, be sure to save the playback configuration afterwards from the Playback Devices dialog so that those patches/settings will be recalled the next time the configuration is used.
Sounds Load Twice
Article applies to: Sibelius 7; Aria; Kontakt/Kontakt Player 5
Description
When selecting a playback configuration Sibelius immediately begins loading sounds. After exiting the Playback Devices dialog and starting playback or making a selection in the score, Sibelius loads sounds again which may cause delays, crashes, or instability.
Solution
This happens when using autoloading sound sets and a playback configuration is saved while sounds are loaded. The autoload function is such that Sibelius loads all patches 'fresh' from the hard drive as they are required and will ignore any sounds that are already in the plugin that were not loaded through this function. Sounds that are recalled with a Playback Configuration are recalled from a separate file and therefore Sibelius doesn't recognize them and loads the patches again.
To fix double-loading, open the interface for each plugin in your configuration that uses an autoloading sound set and delete all patches that are loaded. Save the configuration and restart Sibelius.
To prevent double-loading, avoid saving a playback configuration while sounds are loaded when using an auto-loading sound set. If you must make changes, it's recommended to do so prior to opening a score by starting Sibelius and opening the Playback Devices dialog first. After making your adjustments and saving the playback configuration, you can open the score and sounds will be loaded (once).
See also: Sounds Load When Sibelius Starts
Sounds Load When Sibelius Starts
Article applies to: Sibelius 7
Description
During startup, Sibelius loads sounds into various plugins.
Solution
Sibelius recalls the playback configuration last used when it is started, which may result in sounds loading during startup if sounds had been saved in that configuration.
To avoid this, you can designate a playback configuration that should be selected when Sibelius starts from the "Preferences" dialog. If you frequently use large configurations with many sounds loaded we recommend creating an empty configuration to use as your default Sibelius start-up configuration.
Staff Library Prefix Lost
Article applies to: Sibelius 7
Description
A custom instrument staff's library prefix is lost when returning to the Add/Create Instruments dialog.
Solution
The instrument prefix is only displayed in the Sibelius dialogs until the instrument is added to the score. Once the instrument staff is added to the score, returning to the dialog will display the staffs "Long Name" (which is generally the standard name) as it appears in the score. Despite the prefix being lost, this is still the same staff.
If it is important to maintain the prefix, you can edit the staff so that the library prefix is a part of the in-score name, however by default the name given in the score will always reflect the most appropriate name for printing rather than playback.
Volume Set in Plugin Changes on Playback
Article applies to: Sibelius 7
Description
Patch volume level that is set directly in a plugin is lost when playback starts.
Solution
Many patches have a master 'volume' that is linked to MIDI CC7. The Sibelius staff mixer faders are also linked to MIDI CC7. When playback begins, whatever level is set in the mixer is sent to the patch and your setting is lost.
Use the Sibelius mixer to balance patch levels rather than adjusting the settings in the plugin directly when the patches volume is linked to MIDI CC7.