Latest Trumpet patch - Kontakt 3.5 - Mutes not working
Just done a fresh install after new DAW build.
Kontakt 3.5, The Trumpet 2.5.1
Patches load fine, but choosing the MUTE menu and changing mutes does not change the sound at all. What has gone wrong?
K
Kontakt 3.5, The Trumpet 2.5.1
Patches load fine, but choosing the MUTE menu and changing mutes does not change the sound at all. What has gone wrong?
K
Comments
what happens if you turn the virtual CC100 knob on the instrument GUI ("Controllers 3") using the mouse? Or switch using the Mute menu? I guess it works fine...
On some systems the incoming CC100 is not recognized. This bug will be fixed soon.
The remedy: open another Trumpet in the same Player, load the mute using the mouse and switch using different MIDI channels, for example.
Sorry for the inconvenience.
Best
Peter
what happens if you turn the virtual CC100 knob on the instrument GUI ("Controllers 3") using the mouse? Or switch using the Mute menu? I guess it works fine...
On some systems the incoming CC100 is not recognized. This bug will be fixed soon.
The remedy: open another Trumpet in the same Player, load the mute using the mouse and switch using different MIDI channels, for example.
Sorry for the inconvenience.
Best
Peter
Thanks for replying Peter,
Problem is that changing the mute in the menu does not work. I have just downloaded 2.5.1 again and loaded the main trumpet patch into Kontakt 3.5 (all freshly installed). Changing between mutes does nothing. I have tried using the cc100 and that does nothing either. cc11 is working fine, keyswitching is working fine too. I have tried all the trumpet patches and none of them respond to mute changes either with the mouse or cc100.
K
OK, this is a different story. This happened to another customer already. The reason for that kind of problem is a wrong file structure of the library or a wrong library path, so that the application cannot find the right Impulse Responses folder. This may happen mainly due to some errors by copying the content of the new version, for example. But actually it does not matter what went wrong - we must simply nail the problem.
Please start the Kontakt/Kontakt Player 3.5 or 4 and launch The Trumpet. Open the instrument options (NOT Kontakt options), clicking on the gear icon above the small trumpet logo. Choose the page "Infos". You will see the window "Instrument path". Please check if the path displayed there is exactly as it should be, leading to the NEW instrument "The Trumpet v. 2.51". If not - this is the reason of your problem. But even if it does - please continue anyway:
1. Locate the Trumpet in the Kontakt Browser and remove the library clicking on the appropriate menu behind the small "*" icon to the right (near "i"). Make sure that The Trumpet does not appear in the browser any more.
2. Close the Kontakt application
3. Locate the "old" folder "The Trumpet" containing the previous version you have installed using the previous installer. Rename it, adding for example ..."old".
4. Locate the folder "The Trumpet v. 2.51" which contains the new files.
5. Make sure that it contains the following files:
- Impulse Responses.nkx
- Samples.nkx
- The Trumpet_info.nkx
as well as the folders "Instruments" and "Documentation".
If it doesn´t, follow the update procedure from the beginning, exactly as described in the readme file of the updater ZIP.
(Make sure that "Instruments" contain the nki files.)
6. There are three .nkc files (named exactly as the nkx files). Please delete them (delete only the nkc files - NOT the nkx!)
7. Make sure that there are no other copies of the Trumpet folder on your system (nor other files belonging to the library). This is essential.
8. Start your Kontakt application and click on the button "Add library" in the browser. Navigate to the NEW folder "The Trumpet v. 2.51"
9. Restart Kontakt and load the trumpet.
Now your mutes should work properly (I mean - when switched via the Menu or the virtual CC100 knob on the GUI)
Please note that this is a case for the NI support, or our own one which is available via our contact page. If you experience any further problems, please contact us that way.
All the best
Peter
I knew it had to be something to do with the paths. All is now working well.
Many thanks for sorting this.
K