It would be great to be able to set the default sound on new channels, (perhaps even on a per track basis). The felt sound really isn’t the best of sounds, particularly when it comes to chords and most users will likely have at least a small library of viable altneratives.
Thanks!
I understand your idea, but I think that changing the instrument is already very easy and fast and we can select whatever sound we like.
For example, Rock Bass as default for all bass tracks would suit some users, but some others would prefer Funk Bass or so. Accordingly, someone will always change the instrument, as we all do with felt piano. But maybe the team will find something to surprise us.
But this is my point. We all have different needs. And by allowing us to set our own presets, it would more efficiently allow us to meet them.
I agrree.
As the internal sounds are fast to load, maybe this could work, but I am affraid that this would be technically challenging to set a default sound with external plugins, especially Kontakt-based. What if we need to change the sound in a different project? This would be similar to the current situation.
As I mentioned in my first post , we don’t know which ace do the developers have in a sleeve 
I don’t think you need to go as far as trying to support third party plugins with this stuff. Just have a means for us to choose a global built-in instrument and then to override it with another built-in instrument default for each motion type. So you could set soft piano as the main default but have a bass sound for bass lines, a string ensemble for chords, a guitar for strums, a synth for melody etc.
I think that this simplified version could work!
As the developers read all posts, I believe that they will have something to offer in this department once the serious things finish.
I agree that implementing this with third parties such as kontakt would be more complex because it would likely load it “empty”, but again, leave it to the user to decide whether or not that works for them. Maybe it’s another third party that isn’t “shell based”. It’s not about imposing limitations. It’s about removing them. Maybe it’s just picking another built in instrument. And of course, if I know I always want to use a contact instrument, it’s just one less step for me to then load the appropriate instrument within there and get on with the fun stuff! 
Of course you could always create a few S3 template presets with your favourite Kontakt instruments preloaded. I have a few DAW templates setup with several instances of Scaler 2 containing built-in instruments. I get an arrangement going and only then replace the instruments with better ones. I like the built-in instruments because they load quickly and are of adequate quality for the job. I even have a few songs where the felt piano survived in the final mix.
This is actually a great suggestion I should have considered myself! That said, software developers should always do all they can to facilitate usability, so your suggestion is excellent and they should still consider the request! 