Hi,
I had some days off until today and, well, I am very happy to see, that there seem to be quite some positive reactions and - best of all, Herb likes the idea as well. Thank you (and your team) for your cooperative and effective attitude once again. I have seen so many companys rejecting efficient ideas just because they feared to loose their "absolute power" and control over their products!
Yes, I have been aware of the naming issue and I was just curious with what you guys come up with. I will bug Bernard of CDXtract to implement a conversion-option that would provide an intelligent function to re-reference and fix the wave-file-links within any .exs, .fxp or .nki-file without having to re-import the whole wave-data. I am thinking of
1. A search-algorithm, that would find waves within any kind of (sub-)folder-strucure
2. A renaming-algorithm, that would even be able to re-reference files that are named differently according to a pre-defined condition-set
If anyone had a good wire to Garth of Chickensys, maybe he would be interested in such a very helpful option, too. This even seems to be no real "VSL-special", IMO it was very helpful for ANY user to be able to use exactly the same wave-pool-folder for a .nki, exs and/or .fxp-patch at the same time.
Cm, how could such a database-thing look like in the real world? Sounds very interesting, but I have no idea how this could be done.
All the best
Roman