Garry
Senior Member
Ok, so we had the VI-C blinded violins shootout, the results of which are here. There were many contributions, and it generated a lot of interest - thanks to everyone who participated.
The question now is how we can best capitalise on this to really help each other in our purchasing decisions, and to keep it fresh to incorporate future libraries?
I have a suggestion: that we create a database comprising only 1 of each of the best representations of each library. This is not a contest of libraries, but we'll need a fair and transparent way to identify which entry should represent each library. We will of course iterate on the rules, using the input of forum memkmnbers, but here's a provisional overview:
RULES OVERVIEW:
THE PURPOSE: the aim is to create a database with all major violin libraries, which allows users to review a library and compare it with another, on the basis of having the SAME melodic lines. This will address the concern that some libraries may not have been represented at their best in the blind shootout. Here, our aim is not to do this blind, but to generate the best possible representation. Then, if you already have library A, and are thinking of buying library B, you can go to this database, and hear how it sounds, being able to directly compare it performing the same lines - something that is currently not possible, with all developers having their own individual demos; these are useful too, but they make comparison difficult.
Of course, there are many factors that go into whether to purchase a library (workflow, number/quality of articulations, price, developer, etc), and this will NOT address these, nor is it intended to. It will however, give you an idea of the comparison of timbre between libraries: likely a key, (though not the only) factor in your purchase.
If you think this is useful, please vote in the poll above; based on the results of the poll, we'll go ahead and create the database, or not, as the forum decides.
The question now is how we can best capitalise on this to really help each other in our purchasing decisions, and to keep it fresh to incorporate future libraries?
I have a suggestion: that we create a database comprising only 1 of each of the best representations of each library. This is not a contest of libraries, but we'll need a fair and transparent way to identify which entry should represent each library. We will of course iterate on the rules, using the input of forum memkmnbers, but here's a provisional overview:
RULES OVERVIEW:
- We will again use 'Saxer's Seven': a MIDI file which contains 7 melodic lines with different challenges for the library to meet
- Anyone (developers included) can submit a version of the library
- There will be 2 categories: library alone (can only include anything within the library), and library-plus (can include elements from other plugins, but all details must be stated)
- We'll take a poll to determine which entry is to represent each library. Note this will NOT be blinded: this is not the purpose this time. Also note: this is NOT a competition across libraries (also, not the purpose this time). The polling is only to get the majority opinion of which entry best represents a library and should enter the database. The winning entrant wins kudos and fame amongst the VI-C community beyond their wildest dreams!
- The library will then be stored within the database, and can be updated as newer libraries come along. Anyone can access the database at any time to listen to each library performing the same lines.
- Each entry to include a screenshot of the CC data to help others get an idea of working with that library (credit to @brek) and their general impressions of the library (strengths and weaknesses) (credit to @pipedr)
THE PURPOSE: the aim is to create a database with all major violin libraries, which allows users to review a library and compare it with another, on the basis of having the SAME melodic lines. This will address the concern that some libraries may not have been represented at their best in the blind shootout. Here, our aim is not to do this blind, but to generate the best possible representation. Then, if you already have library A, and are thinking of buying library B, you can go to this database, and hear how it sounds, being able to directly compare it performing the same lines - something that is currently not possible, with all developers having their own individual demos; these are useful too, but they make comparison difficult.
Of course, there are many factors that go into whether to purchase a library (workflow, number/quality of articulations, price, developer, etc), and this will NOT address these, nor is it intended to. It will however, give you an idea of the comparison of timbre between libraries: likely a key, (though not the only) factor in your purchase.
If you think this is useful, please vote in the poll above; based on the results of the poll, we'll go ahead and create the database, or not, as the forum decides.
Last edited: