If you don't ask you don't get.
Visions change. Products evolves. Sometimes.
True,
but before asking, one should demonstrate that they have at least understood how it works. It often happens that some guy pretend to want to do things in an incorrect way, like those who play a slow legato and expect to perform fast passages. and if There's a Slow Legato, there's a reason for that. A slow legato is a slow legato and should be played that way.
It's pointless to force it to do things for which it was not developed. But this is something that needs to be understood. The same goes here for the phrase builders.
The question to ask is, "Why can't I achieve what I might hear in the videos? Am I sure I've understood how to use it?" I've explained multiple times how they should be used.
And if the answer is, "Yes, but I want to do it this way," and I tell you that's not the way to use them, it's not a matter of me needing to change; it's a matter of you needing to understand and study how to use a product. Because, as I've mentioned, there are also technical limitations that prevent certain things from being done.
Furthermore, as I've explained, I have an idea, and I don't necessarily have to change it for anyone. The wonderful thing is that there are many developers, so everyone can find the developer closest to their taste. If, for me, sound quality is important, for another developer, it might be more important to let you insert all the syllables you want, even if the sound quality is debatable and fairly fake. If, for you, sound quality, expressiveness, and a credible and professional final result are more important, you'll buy a different library.
So when I introduce something, I always have this thought in mind:
Is it credible or is it fake? Because if it sounds fake, I won't do it. It doesn't interest me. Even if is it more Flexible.
The Ethera Gold series has been tremendously successful and continues to be, thanks to you, and I've listened to your requests a lot, so I say always thanks , and all the feedbacks are crucial for me.
Whenever possible, I've added everything that's been asked for. WHEN POSSIBLE, because it's not always possible.
And then, I always recommend learning how to use a library.
To use creativity, to make the most of it, which is something that often isn't done.
People often think about the things that might be there and don't focus on how to make good use of what's already available.
The potential here is truly high; you just have to put it into practice.
In Conclusion
As I mentioned in another post,
I will continue to listen, keep evolving this series, and if the interest remains alive,
I will continue to offer my vision because, first and foremost,
I have to do what makes me satisfied, because first of all I'm a composer/sound designer ... I use what I create, it is not only business...
Otherwise, I can't put in the passion.
I have to do what I'm capable of because I'm not perfect, of course.
When I created ELEMENTS MSS, I did it because I wanted a library like that, and I couldn't find any made in that way. With that engine, it allowed me to do certain things quickly.
There might be more complex libraries out there, but I can't achieve the same results with them. So, Elements MSS became my "go-to" library for all those hybrid/ambient-style things, not just because I made it. The same goes for Elements CR.
In fact, as I often show in my videos, I also showcase the OTHER( not mine ) libraries I use.
It's not a problem for me. I don't make tutorials and only show what I've created.
In all of this, I will certainly try to incorporate all the requests within my capabilities.