I could build the database model, tomorrow if life allows it, but it would be important to choose the engine (MySql maybe?).
Yes, that would be useful. And also the mic names, which can sometimes not be obvious from their abbreviations, and key switch info (perhaps with links to user-made DAW articulation sets)I’d love to have a database of sample offset times for each patch for grid-based composition. That info is really hard to find most of the time. Performance Samples seems to be the only company that really features that info clearly.
Might be tackled with something like a tagging system (like Netflix etc. for recommendations)?! Where you can tag e.g. style of music a library is designed for (or capable of playing), section sizes, hall/room, engine, dongle etc....With some of these, the recommendations we'd give as people would be somewhat tricky to get a wiki to return with a simple search - for example, for the horns maybe putting them together from Audio Modeling and Sample Modeling, or using Project Sam Swing/Swing More, which contain a lot more than just horns.
Could be bypassed by including something like a "sale tracker" where past sales and events are tracked for all companies. Then sorted by companies and a page with something like a calendar thing for a quick overview (?!).And I'm not sure if we want to get into the "do they do sales" questions, as that's potentially a minefield, but OTOH it's something people really do want to know.
I really like the format. Sure, having separate lists of piano-specific fields like half-pedaling and string-specific fields like divisi will make things harder to set up and maintain, but in the right format it's not too bad, and it would potentially make the wiki really, really good at giving the users what they're looking for.There is a piano VI spreadsheet you have permission to use on your free to access wiki. It is neither complete or accurate but has 183 VIs. Link to spreadsheet is here:
Getting the popular VIs is relatively quick. Finding the esoteric VI pianos took a majority of the time and effort.Also, 40 hours to make a list of 183 piano VIs - that's a great number to know. We can extrapolate. . .
Yes - But that'll be a bit complex I imagine since the number of instruments can change - from e.g. on "Solo Violin" to a pack like Amadeus or similarNo need for me to do any db modeling then
@MatFluor Would it be possible to change the way instruments and mics are in the "Instrument Details" field ("Violins I (4), Violins II (3)...") to tabular fields?
Maybe pairs like instrument/type/number (Violins/I/4, Violins/II/3, Strings/Hi/38, Violin/Solo/1...). It could appear like it does now in a single output field, but would allow to use the search function to find things like "Violins between 3 and 5" easily, and avoid string mismatches.