Hi

I've been working with a few UVI libraries, but I'm in the process of cutting back on them. I really enjoy using the tag library, but from what I can tell, the issue doesn’t seem to be related to the library itself (which I've since deleted), but rather to the R2RUVI file.
Is there any way to read the gipperisch content of this file to figure out which file is associated with which library? Any help would be much appreciated.

Thanks so much for your time!

 

Hello @Thomba, you can't read the files.

However, you can either download the corresponding soundset you want to delete again and then copy the registration key into the directory via drag and drop. The existing key will then be highlighted in blue, and you'll know which one you need to delete. Do you perhaps still have the files on your hard drive?

Attached is an old text of mine for reference:

Installation instruction for the UVI - Falcon v2.5.3 VSTi / Emulator / Factory / Expansions

Falcon VSTi
1.) Download and Unrar the " UVI.Falcon.v2.5.3.Incl.Emulator-R2R "
2.) Click on the " Setup Falcon v2.5.3 "
3.) Inside the Folder is the " 00000E10F2DD0E11.R2RUVI "
4.) Copy the " 00000E10F2DD0E11.R2RUVI " into " C:\ProgramData\UVI\R2R "

UVI Emulator
1.) Click on " Setup UVIEMU v1.0.8 "

Factory
1.) Download and unrar the " UVI.Falcon.Factory.Library.v2.5.1-R2R "
2.) Create a folder with the name " Falcon " and copy it to where you have space. (Preferably SSD)
3.) Copy the File " Falcon Factory.ufs " into the new " Falcon " Folder
2.) Inside the Folder is the " 00000E10F2DD0E11.R2RUVI "
3.) Copy the File into: " C:\ProgramData\UVI\R2R "

UVI Library / Expansions
1.) Download and unrar
2.) Copy the " B-5 Organ V3.ufs " into the " Falcon " Folder (ending *.ufs)
3.) in the R2R Folder is the Registration File with the ending: *. R2RUVI
4.) Copy the Registration File " 000025694821256A.R2RUVI "
4.) into " C:\ProgramData\UVI\R2R "

Open Falcon in your Digital Audio Workstation (DAW)
1.) Click on the tool wrench
2.) Scroll down to " Preferences "
3.) A new window opens and select "Soundbanks"
4.) Add the new Soundbanks path, Falcon folder, where your expansions are in.

 

R2RUVI is just a key(licence file) it cant cause any problems if installed to the right folder, what is gipperisch content?
you can leave them where they are

just describe the issue

 

R2RUVI files are 48 BYTES long only. What do you want to read from them?

You can open such a file in any text editor, for example, Windows Notepad. But it just a series (two short lines) of unreadable symbols wich start from "R2R". It contains almost nothing. I'm almost sure it is just a key which iLok uses to decrypt libraries.

 

He already said what he was planning to do; he has too many sound libraries and wanted to delete some. Since the registration keys are encrypted, he doesn't know which ones belong to the ones he wants to delete. Please read my post; then you might understand.

 

I understood everything without you, and your information about the installation is completely irrelevant.
And such advice to install each no longer needed library just to find out which key belongs to what is completely pointless and useless work
especially since there are UVI libraries more than 20-30 gigabytes

 

Last edited: Nov 17, 2025 at 2:04 PM

Basically, delete the unwanted library .ufs file. Forget about the R2RUVI files left behind because the file size is negligible and not worth the hassle. It will not affect you negatively. Furthermore, should you become interested in said library again, its simple to just put the .ufs file back and not worry about keys.

If you want to be obsessively compulsive (and waste time), then redownload the libraries and organize them better with their keys so that you can keep track. Keep in mind, you can't buy that time back in your life.

 

On the Russian site where some of us find torrent files all UVI libs stay unencrypted. You don't need to download them, just find "List of files" ("Список файлов" in Russian) under the link with the torrent file. You'll find here the number. You know the libraries you installed and then deleted, so you should just look at them and delete what you don't need.

But it is real waste of time, these files don't affect the way Falcon functions in any way. And they are hardly related to the tag library as they contain just a key.

 

You mean they are not compressed. It seems like nothing on there is compressed so that people can selectively download portions of any torrent.

 

most easy strategy in case want to delete unused keys would be just put them out to some temporary folder and adding by back in packs of 5 when a library asks them, yeah or check the number on a russian tracker
just dont touch the factory library ones:

Spoiler: -

000014FE9A7C14FF
000013306AA41331
0000139F6D6C13A0

but I never bothered still have a bunch keys from deleted libraries or old versions libs

 

Last edited: Nov 17, 2025 at 4:54 PM

Thanks for all your replies - the above did second my assumption that the files are not linked to the tag library set-up. I henceforth deleted the library profile, started everything from scratch and that did the trick for me.

Thanks again

 

I noticed this very early on with the R2R uvi stuff. I found no way to "decode" the mile long, what seems to be encrypted filenames to their respective real world actual library names.

So, therefore you have one of two options:

- What I did was keep a text file in that same folder - every time you install a lib for falcon make certain you enter into this file the R2R UVI file name referenced to the real world library name right next to it. This way you now know exactly which UVI goes to what library. Simple.

- OR, grab up (from wherever) the R2R install package for the lib(s) in question and get the UVI file name from it. Then do a quick search in your UVI folder to find the matching file. In my case I keep all the install packages so not a big deal. Might be a bigger deal if you didn't keep them...

There is another less accurate way to possibly determine which file goes where. You can look at the file dates on when the lib file and UVI file were loaded onto the system. This method only really works if you didn't install a crap load of libs at the same time, i.e. the same day/time.

 

Last edited: Nov 17, 2025 at 7:37 PM