I'm not that into the R2R thing, but I do feel like they release a lot, and a lot of different things in all sorts of variations. I wonder how they organize it all, respect. And if a Togo release goes under and what comes later... honestly? who cares, really? Because it's coming, and if it takes another year, everyone will use the Togo versions from a year ago and I don't think anyone will notice. I mean, a trance synth doesn't suddenly turn into a tuba or a linplug sax ;)

 

This was my point with my original reply to the thread. One sentence, and I get some guy trying to condescend over what is normally a basic thing to understand. That is not going to happen. Not when I can see old "patched demos" on the news site, and see the results of that. Funny comments. Many work out just like this. Showing Demo.

Demos will often function correctly until the demo period expires in 3 weeks or 30 days, etc. The Demo period starts the day/date it was installed.

Beta versions, such as the example U-He everything bundle which was [k]'d by Trazor, released and later deauthorized; often do not have a expiration date based on the users' install date. The expiry can be fixed to be a certain date. Example: U-He Zebralette 3 Public beta, mine still has not expired and way further out already than a normal trial period.

With large applications, they (developer) often strip features like save, export, etc; and also the content to shrink the amount of bandwidth consumed by people downloading official Demo versions. It's also an additional form of drm/copy protection.

Trials very frequently now, are the entire plugin. Examples Schwabe, Sonnox, etc. When they expire, they often revert back to a Demo; but from some developers, they become completely disabled.

As you know, Teams quite often get supplied with original installers. On The Dark Side (Mac), demos are often patched-only and never show up on Sister Site. People supply original installers frequently, just not the credentials.

 

Okay I'm back wit some context!

Using Windows 11 latest version up to date

I first had r2r version 2.7.2 I think it was...Then I upgraded to 2.8.0 with the keygen from the website..Not r2r release but r2r keygen and it worked fine...

I seen that Tcd released a all in one bundle so I
grabbed that to test..I installed every plug...

Cause it was the latest versions!

Then tcd had a update release only...I grabbed that because someone else was saying Demo/
Noise in the orignal release..Before I applied the update only Tcd release ..Tal Drum started hissing/Noise and had Demo in Bold letters across the gui...So I applied Tcd fix update only!

Overwriting my 2.7.7 version i left everything intact!..Hoping it was fixed...I tested and tested
all seemed fine on all the plugs..

Then a few hours later I see that Tracer has a patch for it...So I snagged that after reading more comments on that thread and noticed a thread was posted on Sex...Where I read about Hiss/Noise and deleting the xml...

I started up the newly updated tcd release.
And Bam again!....The words Demo in Bold were gone but the hissing/Noise persists.

I tried generating a key for it from the older r2r release and it worked..For a Day or So!

What i didn't do was test the other plugs!

So I said screw it i uninstalled every plug and used Revo to find and clean up remnants...

So upon reinstalling this time I installed the same tcd release (All in One)but applied tracers patch to them..It seemed to work as the were working just fine for again a Day or Two..

Then Bam!... Noise/Hiss no Demo words on gui tho..

I keep my daw offline mostly...And in airplane mode...I tested Studio One 7 and Ableton 11..And Nuendo 14 all same result...I've un/re
Installed a few times i went back to the 2.7.2 r2r
release and now thats doing it as well Noise/Hiss..

What am I missing here?....Is Revo not cleaning everything or that's just the protection causing it?....I have my Anti-virus disabled for my music work on my machine.

Could it be sending out some signal without me knowing I use Simple Wall firewall which tells me all connections inbound and outbound..I haven't seen a thing in regards to it wanting to connect!

Maybe Hosts File Block is needed...

Dunno I'm lost...No reports on Tracers patch being faulty...Just doesn't work for me

There's only one other thing I can think of
Is that the patcher applies it to Tal Drum vst3
which it should.

But wait the icon on the vst3 has a picture of the plug unlike any other plugs I have installed they
usually Grey Cube looking Togu plugs opens up a folder with a few options if you expand click on it..

I traced that folder and it seems the plug is installed in x86 x64 win folder...A subfolder inside of the Tal Drum Vst3..Every plug from that company has the same thing...I patched it anyway....The patcher sees this Main folder first
which says vst3 clearly...All .xml files have been
deleted!

But you can expand it further to show I guess the real vst3..I patched them both i even tried to manually input the generated key in the plug but it says invalid immediately.

I see theres new comments saying sorta the same thing not working on the Tracer release.

I've used tracers patches in the past (Thanks)
and they have all worked...

 

Last edited: Jul 21, 2025 at 8:59 PM

Trust the R2R team and download the working plugins individually and save yourself the hassle of installing TCD.

Togu Audio Line TAL-Drum v2.7.0 WIN MAC LIN Incl Keygen-R2R
Togu Audio Line TAL-Dub-X v2.2.1 WIN MAC LIN Incl Keygen-R2R
Togu Audio Line TAL-U-NO-LX-V2 v4.9.4 WIN MAC LIN Incl Keygen-R2R
Togu Audio Line TAL-J-8 v1.9.0 WIN MAC LIN Incl Keygen-R2R
Togu Audio Line TAL-G-Verb v1.2.8 Incl Patched and Keygen-R2R
Togu Audio Line TAL-Sampler v4.7.1 Incl Keygen [WIN MAC LINUX]-R2R
Togu Audio Line TAL-BassLine-101 v3.9.3 Incl Keygen [WIN MAC LIN]-R2R
Togu Audio Line TAL-Pha v1.1.8 Incl Keygen [WIN MAC LIN]-R2R
Togu Audio Line TAL-Mod v1.9.6 WIN MAC LIN Incl Keygen-R2R