there is this huge orchestral librairy. in the libs archive there is the raw wav sample
we can work together to map this to xrni format. for example i do the bassoon and somebody do the violon
because it'sa huge work for one person but if multiple does each one xrni it could be fast
the link to the librairy is
who is interested ?
A little over a year ago I was in a similar situation. I wanted to convert many orchestra instruments to XRNI to have them. But this raised a couple of problems. Only I comment to keep it in mind.
1) If you create XRNI of complex instruments with all the notes and with their different levels of volume (which is how they would sound more real), you will have very heavy instruments, they will occupy much space, even if they are compressed in FLAC (or WAV). Then, if afterwards you load many orchestral instruments into a song, this song when saving it will weigh a lot (is a XRNS, a ZIP container).
2) Unfortunately, one of Renoise's control panels that is basic (not advanced) is the keyzones editor, especially if you have to add several wav files to each note. It's costly. You're going to waste a lot of time on conversions. If you decide to do it, try to use tricks or some fast repetitive method. Keyzones allows some fixes on the instrument together, but it does sort the names of the wav files well to fit the XRNI instrument. I've always missed a better automation editor and a better editor for keyzones. I hope they undergo a thorough review at some point. However, XRNI instruments are excellent for even percussive instruments. Here it is worth it.
My conclusion with this theme is that it is better to have VSTi libraries would be, so the XRNS song file basically only saves an XML with written information, and there is no FLAC (or WAV) inside it, taking up space. So you can save countless versions of the same project, and you'll always use the same libraries, those installed with their VSTi. I do not know if there is any trick to save the project without using XRNI instruments, but then you have to load them separately.
An extreme example of XRNI is an 88-key piano withs 5 leves of volume for each note. 88 x 5 = 440 FLAC archives, And if each one occupies almost 1MB, you have a full quality piano of 410-430MB. But most instruments are few octaves, from 2 to 4, so you can have instruments between 50 and 200MB each. You imagine using various instruments to form a small orchestra, stored in an XRNS. You can have XRNI songs over 1GB or 4GB, or more. If you save the project, you will not be able to go back.
An alternative to all this is to use VSTi to accept adding samples, a sampler.
But if you manage to gather all the instruments of orchestra in XRNI, you will be able to enjoy the advantages that offers XRNI format within Renoise, that are many. I use my favorite piano in XRNI format, and with Renoise you can change it to your whim very easily. But I recognize that hard disk space is a problem. So I prefer to use libraries loaded under a VSTi. You only install them once and they serve you for all the songs. To compose electronic music is very different. The libraries are very light and many VSTi do not bring libraries, they are instruments not based on libraries and they take up very little space.
I just wanted to comment on these things for you to keep in mind, and think about how to do it faster so you do not waste so much time.