Audified MixChecker Ultra v1.0.0 READ NFO-R2R

Audified MixChecker Ultra v1.0.0 READ NFO-R2R

The ultimate evolution of the referencing tool. Perfect your mix! With over 90 simulated pro-audio and consumer devices, a dashing new graphic style, and a practical analytical part, MixChecker Ultra is the next step of evolution in checking your reference mixes. Super-realistic device simulations C

资源介绍

Team R2R | 2024.009.07 | 119.5 MB

The ultimate evolution of the referencing tool.

Perfect your mix!

With over 90 simulated pro-audio and consumer devices, a dashing new graphic style, and a practical analytical part, MixChecker Ultra is the next step of evolution in checking your reference mixes.

Super-realistic device simulations

Choose from 90+ device simulations of the most famous and popular audio devices. Includes up-to-date consumer devices such as laptops, phones, or earbuds. Try the sound profile of the industry-standard studio monitors and headphones. Check how your mix translates in cars, club PAs’, or small Bluetooth speakers. You also have the ability to check your mixes in real-world noisy environments such as subways, noisy streets, shopping malls, and others.

IR loader

With MixChecker Ultra, you can import your custom Impulse Response. You can check how your mix would sound in popular acoustic spaces, your friend’s studio, or even a cathedral. (Supports standard WAV IR files)

Advanced device controls

To understand better how your mix translates on the devices, easily adjust the settings of each device. Adjust the volume of each device independently or set the simulation stereo base to match the real-world conditions better. Our engine also considers the non-linear behavior of the devices and simulates their distortion and clipping. You can easily turn on the distortion and see if your mix would clip or distort on the selected devices.

A witch says,

  • Our release uses less resourse especially you run the multiple plugin instance. This also solves minor Audified's license glitch between the threads.

  • LexActivator emulator is injected to the plugin, which returns valid license information to the software and handles callback system. It also avoids writing broken data to the registry (LexActivator's bug).

After Audified dropped PACE/iLok in 2022, they started using licensing service called "Cryptlex" and its "LexActivator" SDK to use the service. Here is our work - solving LexActivator's bug and Audified's bug, no periodical license server sync required.

Have fun reading the technical note :)

Spoiler:

TECHNiCAL NOTE - CRYPTLEX, AUDiFiED AND OTHER CRACKERS' WORK

If you don't have interests in deep software development talking, skip [1] and

[2].

[1] Cryptlex and LexActivator


[1.1] About Cryptlex

Cryptlex : https://cryptlex.com/

Cryptlex is licensing solution. It provides web API (JSON).

[1.2] About LexActivator

LexActivator is Cryptlex's native SDK. SDK is also provided to non native

language. With this SDK, developer doesn't need to handle original web API

and JSON.

Here is the simplest license verification with LexActivator.


SetProductData(YOUR_PRODUCT_DAT_CONTENT);

SetProductId(YOUR_PRODUCT_ID);

if (IsLicenseGenuine() == LA_OK) {

// License is genuine

} else {

// License is not genuine

}


LexActivator doesn't have any special tricks to protect the software. It's a

simple licensing solution. No packing, no obfuscation. It's not anti piracy.

SDK is publicly available. Anyone can check the specification.

https://github.com/cryptlex/lexactivator-c

[1.3] The bug of Windows LexActivator

In Windows, LexActivator stores the license and other data to registry.

HKEY_CURRENT_USER\Software\Classes\csetz

However, LexActivator uses wrong Win32 API to store the license. The data will

be broken (unexpected). If you have run any LexActivator powered software,

you should have broken entries under "csetz" key.

This happens because LexActivator passes ANSI string to RegSetValueExW. They

should pass UNICODE string to that API, or use RegSetValueExA instead.

If LexActivator fixes this bug, all previous data incl.license will be

incompatible, unfortunately. Users will need to activate the software again.

But it's better than leaving that bug, isn't it? :)

This bug is what we have waited for a long time to be fixed, but no action

from Cryptlex.Inc yet. So we finally decided to release it with injected emu

instead of the keygen, which does not put "csetz" garbage to the registry.

[1.4] LexActivator in the audio plugins

LexActivator is static (not instantiable). It is not really made for the multi

instance environment. In the DAW, one DAW process would have multiple instance

of the plugin A, and also would have mutiple LexActivator powered plugins

A, B, C. Developer needs to face with this to avoid conflict, or simply give

up using LexActivator and manually process Cryptlex Web API instead.

  • While LexActivator API and manual is publicly available, there aren't enough

technical information about multi-instance usage. We can find some questions

and bug reports on their support forum.

[1.5] LexActivator is currently used by....

Audified, Dear Reality, Landr FX, Maddix Rumble and so on

Now you know why we haven't released any of them. Should we wait for another

months or years to see the fix of registry issue?

[2] Audified and LexActivator


[2.1] Structure of Audified plugin.

+- Plugin A ----------------------------------------------------+

| |

| +- LexActivator (Static) -+ +- Instance (1) -----------------+|

| | | | LexActivator watching thread ||

| | LexActivator API | | License State ||

| | Server Syncing Thread | +--------------------------------+|

| | | +- Instance (2) -----------------+|

| +-------------------------+ | LexActivator watching thread ||

| | License State ||

| +--------------------------------+|

| +- Instance (n) -----------------+|

| | LexActivator watching thread ||

| | License State ||

| +--------------------------------+|

+---------------------------------------------------------------+

The problem of this design :

  • Every instance has its own LexActivator-watching-thread. When you load

10 instance of plugin A in one DAW project, you would have 10 watching

thread.

  • Every instance initializes LexActivator and calls API, while LexActivator

is static (only one instance). We confirm this makes some glitch between

the threads.

  • LexActivator syncs license state with Cryptlex server periodically, as SDK

document says. When it succesfully syncs with server, it wakes all

watching-thread.

If we were the developer who needs to use LexActivator...

  • Code AudifiedLicenser.exe that checks / activate all Audified licenses

  • Licenser saves own cache file to %APPDATA%

  • Every Audified plugins load license from the cache at the startup of first

instance. Store the license data to global area in the plugin. No need to

load cache in every instance.

By this method, no real LexActivator code will run in the actual DAW process.

Developer does not need to care the undocumented conflict issue. Plugin will

be more light weight because no SDK is linked.

[2.2] Bugs of Audified

We write only license related issue here.

Wrong API Usage : releaseFlags in CheckReleaseUpdate() is set to 0 in the

Audified's code. This is undefined value. Use 1 (LA_RELEASES_ALL) or 2

(LA_RELEASES_ALLOWED). In our emulator, that value is ignored.

Desync License State : Sometime LexActivator-watching-thread misses the

LicenseCallback. In R2R relase, that Audified's watching thread is re-written

by us :)

Deactivation : The returned value of DeactivateLicense() is set to license

state. When the plugin is activated and deactivation fails, plugin should be

still activated. But Audified's code invalidate the activation state. In our

emulator, DeactivateLicense() always returns 1 (LA_FAIL), then plugin

activation status also becomes 1 (LA_FAIL) from 0 (LA_OK). We haven't fixed

this because R2R user shouldn't try to deactivate the plugin.

Some initialization issue : Some hosts like VSTHost (SAVIHost) does not call

initialization code of Audified's VST3 plugin. License info says "License

is not Trial nor Full, what the hell?!". If you see that License info in your

plugin host, you should avoid using Audified plugins with that host.

[2.3] We hate that licensing scheme

Currently Audified does not support offline auth. Users have to re-activate

(sync with Cryptlex server) every week. Some users are even saying that iLok

was better. Customer got another reason to use R2R release.

  • LexActivator does have API to support offline auth!

[3] Audified releases from other crackers


[3.1] First of all

After first Audified + LexActivator crack appeared in the public in 2023, many

crackers released the Audified but all of them have the issue. Basically they

are the same crack (except XAIR which isn't cracked at all); They just changed

one of the LexActivator's API to return 0. This ends up causing tons of

noticeable and unnoticable problems.

[3.2] Reveiws for other releases

  • Audified.GK.Amplification.3.Pro.v3.1.1.WiN-MOCHA

The first Audified crack appeared after dropping iLok.

Simple API modification : return 0; in the head of routine.

We can find completely wrong patching in other spot (libcurl).

Original Code (Pseudo) :

int function() {

void* memory = calloc(1, 0x190);

if (memory == NULL) {

return 0;

}

/* Some process here */

free(memory);

return 0;

}

Patched Code (Pseudo) :

int function() {

return calloc(1, 0x190);

}

Memory leak can't be simpler than this.

  • Audified.1A.Equalizer.V1.0.0.WiN-XAIR

While one of the return value is modified to fix the string to "activated",

it isn't cracked at all.

  • Audified.MixChecker.ULTRA.v1.0-BUBBiX

Simple API modification : return 0; in the head of routine.

One more trick which changes the internal magic number.

  • Audified.Complete.Effects.Bundle.v2024.8.17-TeamCubeadooby

Basically, TCD's release is just a copy of MOCHA's work, while it is not

mentioned in their NFO. It even has "return calloc(1, 0x190);" which is

apparently copied from MOCHA's work - the direct memory leaking.

TCD also tried to fix some issues (made by themselves, not by Audified)

Quote from "Audified.1A.Equalizer.REPACK.ReadNFO.v1.0.0-TeamCubeadooby"

Binaries have been patched to alleviate the error on removing an instance

of the plugin, .....

This will likely not be necessary for future versions as Audified will

likely have this fixed as of then.

Quote from "Audified.Complete.Effects.Bundle.v2024.8.16-TeamCubeadooby.Rev1"

Audified playing games. The new RZ plugs have the license sceen ...

So - this functionality, it's not a bug it's a feature - is stripped.

TCD ended up removing some required functions (like memory free-ing) and

stripping original software functions. Audified doesn't have anything to fix

for TCD, actually 1A Equalizer is still v1.0.0. That license screen isn't a

"functionality" or "new game".

Moreover, TCD's extra pathces don't have any real fixes. For an example, TCD

bypassed memory deallocation to avoid the access violation. What TCD really

should do is finding the cause of that access violation.

For the people who can't understand what we are talking about:

Leacher "Hey doctor, My left leg hurts since yesterday!"

TCD "Cut that leg. Burn and stop the bleeding."

Leacher "Hey doctor, after 10 minutes, it started hurting again!"

TCD "That is fixed in Rev2. Take this fentanyl."

Leacher "Wow, this works 100%. You are the most active doctor in my town!"

  • These TCD's Bypass Everything Technology (TM) is also applied to other TCD

releases too. Remember, no one posted the real reviews about TCD releases in

the public forum. You can't know the real reliability unless you are a

reverse engineer and you don't hesitate spending time to reverse what they

bypassed / its side effects. This Audified case proves.

  • If they really care about release quality, they never release FabFilter

plugins which does not even pass our FabFilter Signature Checker (released

in Feb.2023).

[4] What can we say from the Audified releases


As we explained in [1] and [2], most Cryptlex + LexActivator specifications

are officially documented and in public status. After a hacker reads the

documents, he/she can find nothing special in the Audified's LexActivator

implementation. Lately, the trend on the audio warez scene has been "quantity

over the quality" and "faster is better". This Audified case is as if it were

emblematic of the current state of the scene.

We feel ashamed that it took us a week to check internal / public spec of the

LexActivator to make the tools and keygens. Coding / reviewing the minimal

emulator also took days. We are beginner hackers : it takes very long time for

just 1 auth system. What is worse, we weren't able to find that groundbreaking

protection that Audified developed. So, our release should timebomb after the

minutes. Anyway, happy to say, we haven't added new bugs to the software.

Let's fix the timebomb later - if there were ;)

[5] Greetz to some guys outside UPAWG


  • Congrats to someone for unpacking PACE wrapper for Mac.

  • We expect more keygen works from you, MOCHA.

  • Greetings to sneakz for some nice keygens.

相关推荐