Squash a live vocal flat on the console itself. No laptop in the insert, no interface round trip.

Avid VENUE consoles run 64-bit AAX DSP only. They do not load AAX Native, and they do not load Hybrid. So a native VST3 or AAX plug-in cannot go on an S6L at all, however good it sounds: the usual workaround is a laptop running a plug-in host, patched into a channel insert through an interface, with the round trip and the extra failure point that implies.
This build is the other answer. It is a separate binary compiled for the console's own TI DSP chips, and it inserts on a channel like any stock VENUE processor. No laptop in the signal path, no interface, no extra thing to go wrong at 8pm.
One bundle installs both plug-ins. HotPressor FOH goes for polish; HotPressor Monitor runs gentler and errs open, because a dropout in someone's in-ears is fatal. They stay separate on purpose, so a monitor rig can never sit in FOH mode by accident. Control-surface page tables are included for both S6L and S3L-X.
This is the first release of the console build, and a live rig is the worst place to be surprised. So, plainly:
VENUE consoles load 64-bit AAX DSP plug-ins only. They do not support AAX Native or Hybrid at all, so a native build cannot run on the console under any setting. Running a native build at a show means hosting it on a computer patched into a channel insert through an interface.
Yes. It is one product and one licence. The console build and the DAW build read the same licence file and derive the same machine ID, so authorizing one machine covers both formats on it. The DAW build is in early access right now and is included when it ships.
The plug-in shows a request code starting BJREQ1. Take it to any device that does have internet, redeem it at brucejames.studio/offline, and paste the returned BJLIC1 code back into the plug-in. Nothing needs to connect from the console. Re-issuing a code for a console you have already authorized is free and does not use another seat.
It passes audio through clean, exactly as if it were bypassed, with identical declared latency. It never mutes the channel and never drops the vocal.
Fewer than later versions will allow. This release reports no worst-case cycle counts, so the DSP shell gives each instance a chip of its own instead of sharing one. That is deliberate: a plug-in scheduled onto a chip using a budget nobody measured is how you lose audio mid-show. Your ceiling is therefore the number of DSP chips your engine has. Measuring the real figures is the next piece of work, and it raises that ceiling in a free update.
Yes, and they install as two separate plug-ins from one bundle. FOH goes for maximum polish. Monitor compresses more gently, because singers need dynamics to pitch, and errs open so in-ears never drop out. Keeping them separate means a monitor rig cannot accidentally sit in FOH mode.
One purchase, both console variants, and the DAW build when it ships. Authorize once, offline, and forget about it.