What If I Modified the Programming?
We can support the programming files as delivered, but we may not be able to troubleshoot files that have been changed, reorganized, edited, or modified by the customer.
If you modified the programming and something no longer works, the safest solution may be to return to a fresh copy of the original KeyboardTEK files.
Table of Contents
Why Modified Files Are Hard to Support
Examples of Changes That Can Cause Problems
Before Editing KeyboardTEK Files
Related Articles
What Counts as a Modification
A modification is any change made to our programming after delivery.
This may include:
- Moving patches
- Renaming patches
- Deleting patches
- Changing mappings
- Changing Layout mode assignments
- Moving samples or sampler instruments
- Copying sounds between keyboard books
- Combining keyboard books
- Editing channel strips
- Changing MIDI routing
- Changing outputs or buses
- Adding third-party plug-ins
- Saving over the delivered file after making changes
Some small changes may be harmless, but others can break sounds, samples, mappings, or patch behavior.
Why Modified Files Are Hard to Support
Our programming is built and tested in a specific structure.
If files, samples, instruments, mappings, or channel strips are moved or changed, the programming may no longer behave as intended.
Once a file has been modified, we may not be able to determine what changed or restore the file manually.
In those cases, we may ask you to return to the original delivered version.
Examples of Changes That Can Cause Problems
Common changes that may create issues include:
- Moving instruments or samples between books
- Deleting a patch or folder that another part of the concert depends on
- Reassigning screen controls in Layout mode incorrectly
- Changing sustain, expression, Next, Previous, or Panic mappings
- Moving sample folders out of the MainStage package
- Renaming internal sample or instrument folders
- Combining two keyboard books into one file without custom programming
- Adding plug-ins that are not installed on the performance computer
- Saving the file while a pedal, key, or controller is pressed
These changes can cause missing samples, silent patches, incorrect patch changes, reversed pedal behavior, or other unexpected issues.
If You Need to Start Over
If modified programming is no longer working correctly, contact our Support Team.
In many cases, we may recommend downloading a fresh copy of the original files and starting over.
If your original download link is no longer active, we may be able to review the order and reinstate access when appropriate.
Do not continue editing a broken file if you are close to rehearsal, tech, or performance. It may be faster and safer to return to the original delivered version.
If You Need a Custom Change
If your production needs a specific change, such as cuts, combined books, custom patch order, custom mapping, or a special playback/setup request, contact our Support Team before modifying the files.
Some changes may require custom programming or review.
We cannot guarantee that every custom change is possible, especially if the change affects the licensed orchestration, show structure, or technical reliability of the programming.
Before Editing KeyboardTEK Files
Before making any changes:
- Make a backup copy of the original file.
- Rename your working copy clearly.
- Keep the original download or original unzipped folder untouched.
- Test changes immediately after making them.
- Do not move samples, sampler instruments, or internal package files unless instructed.
Keeping an untouched original copy makes it much easier to recover if something goes wrong.
Related Articles
You may also find these articles helpful: