RMV Library Management

[Bramblepatch]

Hi

I'm currently trialling RMV as it looks like at long last there is an all in one solution to my rhythm tracks, and reading the marketing copy and my tentative explorations are leading me to believe there is some incredible potential here.

The file import options look great so far in that I can get anything I want into the instrument without too much trouble.

My two main areas of concern however are to do with export and managing the bottomless pit that the RMV library could easily become.

I'm normally fairly tight in my requirements for sounds so an 8gb (or whatever it is) library of clicks and pops may be a bit excessive for my needs if I want to audition some sounds and put a backing track together.

So the first question is can I pare down the supplied library to a manageable minimum without adversely affecting the program's operation.

Secondly, particularly with regard to REX loops can I maintain my loops in REX format to be used in other apps as well as use them in RMV without having to duplicate the same loops in any of RMV's proprietary formats. I get shy of stuff that uses proprietary formats as it smacks of getting one dependant on the particular app when flexibility is MY particular preference.

So if I slice up a loop (for example) in RMV can I get it back out again for use in anything else or do I end up being 'chained' to RMV?

I understand the need for proprietary formats to cover instrument specifics like kits and pads etc. but like for midi's wavs and Rex's can I use industry standard formats within the RMV library that I can then use in anything else as well?

[Kyran]

If you want to use the library features of RMV (which provides very nice search facilities) you will need to import your loops into the RMV library. This copies the file into a folder somewhere, but keeps the original format.
There's apparently no way to have it just import a file reference.

Your files do not need to be in the library to use them with RMV though. You can load a rex or wav from anywhere on your system into the program.
You just can't search for them using the librarian (which is a kick ass feature as it supports tags, a star system and more).

I think you can also just remove the content from the library you do not want (I haven't tried this though). I must say I'm very happy with the overal quality of the supplied content, so be sure to audition something before throwing it out.

[Bramblepatch]

If you want to use the library features of RMV (which provides very nice search facilities) you will need to import your loops into the RMV library. This copies the file into a folder somewhere, but keeps the original format.
There's apparently no way to have it just import a file reference.

Your files do not need to be in the library to use them with RMV though. You can load a rex or wav from anywhere on your system into the program.
You just can't search for them using the librarian (which is a kick ass feature as it supports tags, a star system and more).

I think you can also just remove the content from the library you do not want (I haven't tried this though). I must say I'm very happy with the overal quality of the supplied content, so be sure to audition something before throwing it out.

Thanks for the input Kyran,

Yes I'm liking the library features on the demo and like I say I'm impressed at the import capabilities as well as what I've heard of the demo library content so all's well there.

I'll try ripping stuff out of the demo library to see if it impacts on the program in any bad way but I should imagine it's OK as I would think the Demo lib is a stripped down version of the full monty anyway.

My main concerns are getting stuff out again so am I gonna be able to set up my loops in RMV's editor and use them outside of RMV or am I still stuck with my usual REX editing workflow if I want to use my newly sliced loops outside of RMV?

Also I've got a massive midi library so I'm a bit worried about the .mi4 format I'm seeing in RMV as only being useful within RMV.

[Kyran]

if you import stuff into RMV and then export it again it's in the same format as you put it in (so rex's will still be rex's)
The only stuff in the propriatary format is the included content, all your stuff is in whatever you want it to be.

[Peter from LinPlug]

Unfortunately thats not exactly right, or at least a bit misleading. Its this: when you import a REX,
- OF COURSE the original REX is not changed or anything
- when you save the loop you made from the REX it is saved in the library and available for searching, rating etc, however, its in RMV's proprietary format then (obviously as it also contains specific setting like filters or moduleation for each slice etc etc)
- when you export the loop, its still RMV proprietary format, as the export is meant as an export from the library, so it contains no references inside the library and can be exchanged with someone else using RMV. We cannot (!) export in REX format, mainly becuae it would mean you potentially throw away a lof of what makes up a particular loop.

I clearly see your point about avoiding proprietary formats, however, at a certain point you have to jump into it when you want to use the advantages (e.g. rating or search capabilities, additioanal signal processing ...).

Another feature which would be handy, but not yet made it into RMV is keeping the REX as a reference only. Unfortunately this has a lots of potential pitfalls so we not have it yet available.

[Peter from LinPlug]

Ah .. and the other part of your question: yes, you can take anything out of the library without making RMV unuseable, however, some parts depend on each other, so the pads and kits need some samples, removing only samples would mean you might get error messages when loading pads or kits.

However, as one usually not looks at the content one by one, rather by using some critery to seach for, you usually not "see" how large the lib is. The only thing to reduce it would be if you have an exceptional small harddrive, but on the typical PC (500 Gb HD) we just use 2% so ....