As part of Justin's plea deal with the Justice Department, due to his authorship of WinAmp (really kicks the llama's ass) - Justin had to in co-operation with the copyright police, code a honeypot DAW, hence the name REAPER, it was designed to kill piracy. Reaper collects all your info and sends it directly to the NSA with a backup copy going to the CIA and Bill Gates is CC'd on every record.

If I was you, I'd erase my hard drive, change my name, apply for foreign citizenship and starting doing charitable work with orphans so it will look good when your case comes to court.

was it really worth it? just to get a shitty reverb plugin that you could emulate with a mic and a speaker in your bathroom?

only you can decide.....

 

Cockos fucks you in the ass

 

It's all in their name, isn't it?

 

Cuckos get fucked in the llama's ass!

 

Last edited: May 9, 2024

Or as they say in German 'Kotzkotz Reepah'

 

Never heard that term. Lol

 

You shouldn't be moving already installed VST files around. Plugins that are entirely contained within one single .dll or .vst3 file can be moved around however you want (as long as you make sure that Reaper scans the folder you have placed them), but many larger plugins today use more than just one single .dll or .vst3 file. They have data/resource folders that might be placed together with the VST files, or they can be placed somewhere else on your C: drive. Many of these plugins need to be installed to your C: drive to work correctly, or at the very least can't have the VST files and their data folders on separate drives. For plugins like this you would need to use symlinks so that your system and the plugins themselves believe they are installed to your C: drive.

Uninstall the affected plugins, remove all traces of them from your system and install them again properly in your system VST folder. After you've done this, make sure that all plugins show up in Reaper and work correctly. If they still don't work or show up in Reaper you probably have traces left from the old installation.

If you are really desperate to not have the plugins installed to your system VST folder you can read a bit about how to create symlinks. I use Link Shell Extension, but you can do it manually from CMD or PowerShell as well.
https://schinagl.priv.at/nt/hardlinkshellext/linkshellextension.html

EDIT: Saw that you mentioned that Studio One still scans the files correctly. Do these plugins also work correctly when you open them in S1? If so, then it's definitely something your Reaper settings that is messed up. Like many others here have said, I'm also a Reaper user and I haven't experienced any problems at all with iZotope plugins (R2R) or Soundtoys plugins (AudioUTOPiA). I've never tried any of the UJAM plugins though.

 

Last edited: May 9, 2024

I've occasionally had this problem where the same version of Reaper loads VST's fine on one PC, but fails on another.
The solution was to copy the second part of the VST's hash string in a working reaper-vstplugins64.ini, and paste it on to the first part the hash string of the reaper-vstplugins64.ini that isn't working.

For example, not working entries look like this;

Sound_Delay.vst3=00A153874574DA01

After pasting just the second part of the hash string from the working entry;

Sound_Delay.vst3=00A153874574DA01,1047815863{DD701D5731AE478FBD4B12F90CCEB1A0,Sound Delay (Voxengo)

Restart Reaper and the problem VST should be fixed.


Another solution is to replace the second part of the hash string with zero's, so that

Sound_Delay.vst3=00A153874574DA01

becomes

Sound_Delay.vst3=00A153874574DA01,0{0,Sound Delay (Voxengo)


Both solutions have worked for me without any problems. But use at your own risk!

 

I cannot say I have ever seen this issue firsthand, but it would seem that there is some very serious retarded coding going on with reaper in general to have this be a semi-known issue going on for any length of time. And since reaper isn't really free anymore it would seem this would be a red-flag to anyone who would be considering it for a Main DAW role in their workflows. I use reaper mainly just to test plugins and not much else.

 

all software comes with bugs, its a feature, not a flaw, or maybe its the other way around. anyhow, you know we pick our poison and hold our nose until the smell becomes unbearable and then we change DAWs. its just the way it is...

 

Everything works just fine in Reaper for me and I'm a legit crack user.

 

Glass Pipe?

 

this works.... also nice for browning the meringue...
interestingly this is next to the checkout registers in walmart amongst the "impulse buy" goods, candy bars and crazy lighters
just in case you forgot...

 

I get you.. Tested a LOT of plugins with reaper, and as I said, haven't ever experienced that particular "bug". It may have more to do with the local machine and setup thereof rather than reaper itself since not everyone seem to experience the same issue.

 

haven't read through the thread. just a direct answer to your post. if someone else has provided the same please forgive. the 1st photo is my recently downloaded k'd ujam releases from the sister that i can comfirm work perfectly so far. the 2nd is just my izotope folder in reaper of which most is legit but vocalsynth and a few of the others are also k'd. the 3rd is just my PA folder where you can see many vst3's that i can also verify all work.

are you on the latest updated version of reaper right now? that may be crucial info for myself and others. i know i'm several updates behind (lazy) so i wonder if this is something they've added through a recent update.. which would REALLY suck

 

Could you try the latest cracked UJAM Iron 2, please?

 

Last edited: May 10, 2024

I gave it a shot today. Clean installed Reaper Portable and followed your instruction, but the result is the same.
Could you try the latest cracked UJAM Iron 2, please?

 

In instances like this, could you include the actual version number, and the releaser, Team you are trying? There are a few releases which are not from R2R, and one of them has some problem with it. Just make sure you do not leave it as a link.

 

As far as I know, the latest cracked version is 2.3.0 by P2P on May 4th, 2024. Thanks!

 

UJAM Virtual Guitarist Iron 2 v2.3.0 Cracked Fixed

Search for this on Sister Site. It's 45meg file. I'm not on Windows so your guess is as good as mine.