gabriel81: Don't get me wrong, I'm not trying to be rude at all- I just don't see any merit to your points.
gabriel81 wrote:Reduced Featureset for "common" sequencers
What does this mean? Cubase and Pro Tools will have reduced features? That's a no. Do you mean that VSL's wouldn't have as many features? It wouldn't need to. VI Pro doesn't do everything that Kontakt does, for a reason. It's sitll successful. If neither of those were the point you were trying to make then please elaborate.
gabriel81 wrote:Problems in adding additional libraries
Do you mean more VSL libraries or 3rd party. The notation could work in general, but be custom tailored to automatically work with VSL. MIR knows a VSL horn automatically. For EW, as far as I've read (maybe it was MIR Pro, can't remember) you have to use a preset or something. I just don't see any problems here that are so big to prevent this concept.
gabriel81 wrote:Less sales, because some products are "quasi standards" so VSL might be lessl likely to be purchased if not 100% running there
Everything VSL does is high standard. VI Pro 2.0 will have new features... does that mean VSL is pushing their limits? If they never added features then they wouldn't be in business. In this area, no one has offered an adequate option. If VSL did this it would only bring business in. The idea that they shouldn't branch out by adding more features, in fear of making something shabby, is entirely uncompetative- how does that translate to less sales? New features, like in VI Pro 2.0 leads to more sales. A VSL-tailored notation editor would only increase sales. What composer hasn't ever wanted a 'natural notation' composing experience?'
gabriel81 wrote:Less time for VSL Developers in doing the things we all love ;)
Again, what composer hasn't wanted a 'natural notation' composing experience?' I realize that plenty of people like controller input but certainly don't discount that many people want a natural notation experience. There is a whole forum for notation software because of these people. I personally would only ever use notation, the only reason I don't is because it's FAR too much trouble and it's not a playback/performance-friendly method. If VSL did this, I'd sell half of what I own to buy it because it's what I've wanted since I started using cakewalk when I was around 14 years old. I know many others with the same desire. This is because it's the natural composing experience.
---
Despite my mentality, there are others who want to use VSL in this way so it's certainly a valid point. I definately don't want to start another one of these forum arguments, lol... I only mean that to me your points aren't enough to invalidate what I feel is a need of mine, and what others are also wanting.
Here's how I'd coin it: 'Midi is the protocol for the machine; but notation is our protocol, being human.'
No one has successfully developed software that does what we are describing and if we want a VSL tailored notation experience (or at very least a VSL-tailored DAW experience), then it would have to come from VSL. If there is any way to save us time in setup and performance, and offer features that take full advantage of this library... then this is the way.
-Sean